Detection rules › YARA-L
Okta User Password and MFA Factor Reset or Deactivated
Detects when an Okta user's password is reset and MFA factor(s) are deactivated or reset within a 30 minute time window. This activity may indicate that the user account has been compromised.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Persistence | |
| Credential Access |
References
Telemetry coverage
Rules detecting the same action
These rules filter on the same operation.
- Attempt to Reset MFA Factors for an Okta User Account (Elastic)
- MFA Deactivation with no Re-Activation for Okta User Account (Elastic)
- New Device/Location sign-in along with critical operation (Kusto)
- Okta Investigate MFA and Password resets (Panther)
- Okta MFA Reset or Deactivated (Sigma)
- Okta Multi-Factor Authentication Disabled (Splunk)
- Okta Support Reset Credential (Panther)
- Okta User MFA Reset All (Panther)
Rule body
// Copyright 2025 Google LLC. Licensed under Apache-2.0.
rule okta_user_password_and_mfa_factor_reset_or_deactivated {
meta:
author = "Drew Pilarski - Tempus AI"
description = "Detects when an Okta user's password is reset and MFA factor(s) are deactivated or reset within a 30 minute time window. This activity may indicate that the user account has been compromised."
rule_id = "mr_a4344fef-2310-4fed-8f3a-8e76237cfc1f"
rule_name = "Okta User Password and MFA Factor Reset or Deactivated"
reference = "https://developer.okta.com/docs/reference/api/event-types/"
mitre_attack_tactic = "Credential Access, Defense Evasion, Persistence"
mitre_attack_technique = "Modify Authentication Process: Multi-Factor Authentication"
mitre_attack_url = "https://attack.mitre.org/techniques/T1556/006/"
type = "Alert"
platform = "Okta"
data_source = "Okta"
severity = "Medium"
priority = "Medium"
events:
$pw.metadata.product_name = "Okta"
$pw.metadata.vendor_name = "Okta"
(
$pw.metadata.product_event_type = "user.mfa.factor.reset_all" OR
$pw.metadata.product_event_type = "user.mfa.factor.deactivate"
)
$user_id = $pw.target.user.product_object_id
$mfa.metadata.product_name = "Okta"
$mfa.metadata.vendor_name = "Okta"
$mfa.metadata.product_event_type = "user.account.reset_password"
$user_id = $mfa.target.user.product_object_id
match:
$user_id over 30m
outcome:
$principal_user_email = array_distinct($pw.principal.user.email_addresses)
$principal_ip = array_distinct($pw.principal.ip)
$risk_score = 65
$mitre_attack_tactic = array_distinct("Credential Access, Defense Evasion, Persistence")
$mitre_attack_technique = array_distinct("Modify Authentication Process: Multi-Factor Authentication")
$mitre_attack_technique_id = array_distinct("T1556.006")
condition:
$pw and $mfa
}
YARA-L rule structure
Condition
Fires when at least one $pw event in the 30m window and at least one $mfa event in the 30m window.
Events
$mfa
metadata.product_event_type = "user.account.reset_password"
$pw
metadata.product_event_typeis one of:user.mfa.factor.reset_alluser.mfa.factor.deactivate
Match and correlation
Outcome
Outcome variables add context to a detection. When the rule generates an alert, $risk_score is displayed with it.
| Field | Expression |
|---|---|
principal_user_email | array_distinct($pw.principal.user.email_addresses) |
principal_ip | array_distinct($pw.principal.ip) |
risk_score | 65 |