IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Potential Abuse of Repeated MFA Push Notifications
editPotential Abuse of Repeated MFA Push Notifications
editDetects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured for an organization to obtain unauthorized access.
Rule type: eql
Rule indices:
- filebeat-*
- logs-okta*
Severity: high
Risk score: 73
Runs every: 5m
Searches indices from: None (Date Math format, see also Additional look-back time
)
Maximum alerts per execution: 100
References:
Tags:
- Use Case: Identity and Access Audit
- Data Source: Okta
- Use Case: Identity and Access Audit
- Tactic: Credential Access
Version: 103
Rule authors:
- Elastic
Rule license: Elastic License v2
Investigation guide
editRule query
editsequence by user.email with maxspan=10m [any where event.dataset == "okta.system" and event.module == "okta" and event.action == "user.mfa.okta_verify.deny_push"] [any where event.dataset == "okta.system" and event.module == "okta" and event.action == "user.mfa.okta_verify.deny_push"] [any where event.dataset == "okta.system" and event.module == "okta" and event.action == "user.authentication.sso"]
Framework: MITRE ATT&CKTM
-
Tactic:
- Name: Credential Access
- ID: TA0006
- Reference URL: https://attack.mitre.org/tactics/TA0006/
-
Technique:
- Name: Brute Force
- ID: T1110
- Reference URL: https://attack.mitre.org/techniques/T1110/