Okta User MFA Own Reset

Severity: informational
Log types: Okta.SystemLog
Reference: https://support.okta.com/help/s/article/How-to-avoid-lockouts-and-reset-your-Multifactor-Authentication-MFA-for-Okta-Admins?language=en_US
Source: github.com/panther-labs/panther-analysis

User has reset one of their own MFA factors

Rule body yaml

AnalysisType: rule
Description: "User has reset one of their own MFA factors"
DisplayName: "Okta User MFA Own Reset"
RuleID: "Okta.User.MFA.Reset.Single"
Enabled: true
Filename: okta_user_mfa_reset.py
Reference: https://support.okta.com/help/s/article/How-to-avoid-lockouts-and-reset-your-Multifactor-Authentication-MFA-for-Okta-Admins?language=en_US
Severity: Info
Tests:
  - ExpectedResult: true
    Name: User reset own MFA factor
    LogType: Okta.SystemLog
    Log:
      {
        "eventtype": "user.mfa.factor.deactivate",
        "version": "0",
        "severity": "INFO",
        "displaymessage": "Reset factor for user",
        "actor":
          {
            "alternateId": "homer@springfield.gov",
            "displayName": "Homer Simpson",
            "id": "11111111111",
            "type": "User",
          },
        "client":
          {
            "device": "Computer",
            "ipAddress": "1.1.1.1",
            "userAgent":
              {
                "browser": "CHROME",
                "os": "Mac OS X",
                "rawUserAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36",
              },
            "zone": "null",
          },
        "outcome":
          { "reason": "User reset FIDO_WEBAUTHN factor", "result": "SUCCESS" },
        "target":
          [
            {
              "alternateId": "homer@springfield.gov",
              "displayName": "Homer Simpson",
              "id": "1111111",
              "type": "User",
            },
          ],
        "authenticationcontext":
          { "authenticationStep": 0, "externalSessionId": "1111111" },
        "p_log_type": "Okta.SystemLog",
      }
  - ExpectedResult: false
    Name: Other Event
    Log:
      p_log_type: "Okta.SystemLog"
      actor:
        alternateId: homer.simpson@duff.com
        displayName: Homer Simpson
        id: 00abc456
        type: User
      authenticationcontext:
        authenticationStep: 0
        externalSessionId: abc12345
      client:
        device: Unknown
        ipAddress: 1.2.3.4
        userAgent:
          browser: UNKNOWN
          os: Unknown
          rawUserAgent: Chrome
        zone: "null"
      debugcontext:
        debugData: {}
      eventtype: application.integration.rate_limit_exceeded
      legacyeventtype: app.api.error.rate.limit.exceeded
      outcome:
        result: SUCCESS
      published: "2022-06-10 17:19:58.423"
      request: {}
      securitycontext: {}
      severity: INFO
      target:
        - alternateId: "App "
          displayName: App
          id: "12345"
          type: AppInstance
      transaction:
        detail: {}
        id: sdfg
        type: JOB
      uuid: aaa-bb-ccc
      version: "0"
DedupPeriodMinutes: 60
LogTypes:
  - Okta.SystemLog
Threshold: 1

Detection logic

Condition

event_type eq "mfa_reset"

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_type`	eq	`mfa_reset`

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
`event_type`	`eventtype`
`severity`
`actor`
`client`
`request`
`outcome`
`target`
`debug_context`	`debugcontext`
`authentication_context`	`authenticationcontext`
`security_context`	`securitycontext`
`ips`	`p_any_ip_addresses`
`alternateId`	`actor.alternateId`

`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)