ZIA Password Expiration

Severity: medium
Log types: Zscaler.ZIA.AdminAuditLog
Reference: https://help.zscaler.com/zia/configuring-password-expiration
Source: github.com/panther-labs/panther-analysis

This rule detects when password expiration was set/removed.

MITRE ATT&CK coverage

Tactic	Techniques
Discovery	`T1201` Password Policy Discovery

Rule body yaml

AnalysisType: rule
RuleID: ZIA.Password.Expiration
Description: This rule detects when password expiration was set/removed.
DisplayName: ZIA Password Expiration
Runbook: Verify that this change was planned. If not, revert the change and ensure this doesn't happen again.
Reference: https://help.zscaler.com/zia/configuring-password-expiration
Enabled: true
Filename: zia_password_expiration.py
Severity: Medium
Reports:
  MITRE ATT&CK:
    - TA0007:T1201 # Password Policy Discovery
LogTypes:
  - Zscaler.ZIA.AdminAuditLog
DedupPeriodMinutes: 60
Threshold: 1
Tests:
  - Name: Administration Management > Administrator Management > Set Password Expriration 180 days
    ExpectedResult: true
    Log:
      {
        "event": {
          "action": "UPDATE",
          "adminid": "admin@16991311.zscalerbeta.net",
          "auditlogtype": "ZIA",
          "category": "LOGIN",
          "clientip": "123.123.123.123",
          "errorcode": "None",
          "interface": "UI",
          "postaction": {
            "passwordExpirationEnabled": true,
            "passwordExpiryDays": 180
          },
          "preaction": {
            "passwordExpirationEnabled": false,
            "passwordExpiryDays": 180
          },
          "recordid": "331",
          "resource": "None",
          "result": "SUCCESS",
          "subcategory": "PASSWORD_EXPIRY",
          "time": "2024-10-22 22:12:25.000000000"
        },
        "sourcetype": "zscalernss-audit"
      }
  - Name: Administration Management > Administrator Management > Remove Password Expriration
    ExpectedResult: true
    Log:
      {
        "event": {
          "action": "UPDATE",
          "adminid": "admin@16991311.zscalerbeta.net",
          "auditlogtype": "ZIA",
          "category": "LOGIN",
          "clientip": "123.123.123.123",
          "errorcode": "None",
          "interface": "UI",
          "postaction": {
            "passwordExpirationEnabled": false,
            "passwordExpiryDays": 180
          },
          "preaction": {
            "passwordExpirationEnabled": true,
            "passwordExpiryDays": 180
          },
          "recordid": "331",
          "resource": "None",
          "result": "SUCCESS",
          "subcategory": "PASSWORD_EXPIRY",
          "time": "2024-10-22 22:12:25.000000000"
        },
        "sourcetype": "zscalernss-audit"
      }

Detection logic

Condition

event.errorcode eq "None"
event.result eq "SUCCESS"
event.action eq "UPDATE"
event.category eq "LOGIN"
event.preaction.passwordExpirationEnabled cross_field_compare "event.postaction.passwordExpirationEnabled"

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

Field	Kind	Values
`event.action`	eq	`UPDATE`
`event.category`	eq	`LOGIN`
`event.errorcode`	eq	`None`
`event.preaction.passwordExpirationEnabled`	cross_field_compare	`event.postaction.passwordExpirationEnabled` transforms: `op:ne`
`event.result`	eq	`SUCCESS`

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

Field	Source
`action`	`event.action`
`admin_id`	`event.adminid`
`category`	`event.category`
`client_ip`	`event.clientip`
`preaction`	`event.preaction`
`postaction`	`event.postaction`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)