T1201 Google Chronicle · YARA-L

Detect Password Policy Discovery in Google Chronicle

Adversaries may attempt to access detailed information about the password policy used within an enterprise network or cloud environment. Password policies enforce complexity requirements that make passwords harder to guess or crack through brute force. By discovering lockout thresholds, minimum length, and complexity rules, adversaries can tailor dictionary and brute force attacks to comply with the policy — maximizing credential testing while avoiding account lockout. Discovery occurs via command-line utilities (net accounts, Get-ADDefaultDomainPasswordPolicy, chage, pwpolicy), cloud APIs (AWS GetAccountPasswordPolicy), and network device CLIs. This technique is commonly observed in the early reconnaissance phase of intrusions by groups including OilRig, Turla, and Chimera.

MITRE ATT&CK

Tactic
Discovery
Technique
T1201 Password Policy Discovery
Canonical reference
https://attack.mitre.org/techniques/T1201/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1201_password_policy_discovery {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects Password Policy Discovery (T1201) via process execution of net accounts, PowerShell AD cmdlets, chage, pwpolicy, NtdsAudit, or CrackMapExec password policy enumeration."
    mitre_attack_tactic = "Discovery"
    mitre_attack_technique = "T1201"
    severity = "MEDIUM"
    priority = "MEDIUM"

  events:
    $e.metadata.event_type = "PROCESS_LAUNCH"
    $e.principal.process.file.full_path != ""

    (
      // net.exe accounts or net1.exe accounts
      (re.regex($e.principal.process.file.full_path, `(?i)(net\.exe|net1\.exe)$`) and
       re.regex($e.principal.process.command_line, `(?i)accounts`))
      or
      // PowerShell AD password policy cmdlets
      (re.regex($e.principal.process.file.full_path, `(?i)(powershell\.exe|pwsh\.exe)$`) and
       re.regex($e.principal.process.command_line, `(?i)(Get-ADDefaultDomainPasswordPolicy|Get-ADFineGrainedPasswordPolicy|Get-ADFineGrainedPasswordPolicySubject|Get-PassPol)`))
      or
      // NtdsAudit utility
      re.regex($e.principal.process.command_line, `(?i)NtdsAudit`)
      or
      // CrackMapExec-style password policy flags
      re.regex($e.principal.process.command_line, `(?i)(--pass-pol|--password-policy)`)
      or
      // Linux chage -l / --list
      (re.regex($e.principal.process.file.full_path, `(?i)chage$`) and
       re.regex($e.principal.process.command_line, `(?i)(-l\b|--list)`))
      or
      // macOS pwpolicy getaccountpolicies
      (re.regex($e.principal.process.file.full_path, `(?i)pwpolicy$`) and
       re.regex($e.principal.process.command_line, `(?i)getaccountpolicies`))
    )

  condition:
    $e
}
medium severity high confidence

Chronicle YARA-L 2.0 rule detecting T1201 Password Policy Discovery. Matches PROCESS_LAUNCH UDM events where command-line arguments indicate enumeration of password policy settings using native OS utilities or common offensive security tools.

Data Sources

Google Chronicle UDM via Endpoint sensorWindows Sysmon forwarded to ChronicleChronicle Unified Data Model PROCESS_LAUNCH events

Required Tables

UDM PROCESS_LAUNCH events

False Positives & Tuning

  • Privileged IT staff running Get-ADDefaultDomainPasswordPolicy as part of regular Active Directory audits or compliance checks
  • Security assessment tools (e.g., PingCastle, BloodHound) querying AD password policy during authorized assessments
  • Linux system administrators using chage -l to review user account aging settings for compliance
Download portable Sigma rule (.yml)

Other platforms for T1201


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Local Password Policy Discovery via net accounts

    Expected signal: Sysmon Event ID 1: Process Create with Image ending in net.exe or net1.exe, CommandLine='net accounts'. Security Event ID 4688 (if command line auditing is enabled) with same details. Parent process will be cmd.exe or the calling shell.

  2. Test 2Domain Password Policy Discovery via net accounts /domain

    Expected signal: Sysmon Event ID 1: Process Create with Image=net.exe, CommandLine='net accounts /domain'. Net.exe internally calls net1.exe which also generates a process creation event. The query contacts the PDC emulator — Sysmon Event ID 3 (Network Connect) may show a connection to the DC on port 445 or 135.

  3. Test 3Domain Password Policy via PowerShell Get-ADDefaultDomainPasswordPolicy

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe, CommandLine containing 'Get-ADDefaultDomainPasswordPolicy'. PowerShell ScriptBlock Log Event ID 4104 capturing the full command. Sysmon Event ID 7 (Image Load) may show Microsoft.ActiveDirectory.Management.dll being loaded.

  4. Test 4Linux Password Policy Discovery via PAM configuration

    Expected signal: On systems with auditd: syscall audit records for openat()/read() on /etc/security/pwquality.conf and /etc/pam.d/common-password (auditd rule: -w /etc/pam.d/ -p r -k pam_policy_read). Process creation event for chage with -l argument. On MDE Linux agent: DeviceProcessEvents event for chage with ProcessCommandLine containing '-l'.

Unlock Pro Content

Get the full detection package for T1201 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections