IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Attempted Bypass of Okta MFA
editAttempted Bypass of Okta MFA
editAn adversary may attempt to bypass the Okta multi-factor authentication (MFA) policies configured for an organization in order to obtain unauthorized access to an application. This rule detects when an Okta MFA bypass attempt occurs.
Rule type: query
Rule indices:
- filebeat-*
- logs-okta*
Severity: high
Risk score: 73
Runs every: 5 minutes
Searches indices from: now-6m (Date Math format, see also Additional look-back time
)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Identity
- Okta
- Continuous Monitoring
- SecOps
- Identity and Access
Version: 4 (version history)
Added (Elastic Stack release): 7.9.0
Last modified (Elastic Stack release): 7.11.2
Rule authors: Elastic
Rule license: Elastic License
Investigation guide
editThe Okta Filebeat module must be enabled to use this rule.
Rule query
editevent.dataset:okta.system and event.action:user.mfa.attempt_bypass
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Credential Access
- ID: TA0006
- Reference URL: https://attack.mitre.org/tactics/TA0006/
-
Technique:
- Name: Two-Factor Authentication Interception
- ID: T1111
- Reference URL: https://attack.mitre.org/techniques/T1111/
Rule version history
edit- Version 4 (7.11.2 release)
-
- Formatting only
- Version 3 (7.11.0 release)
-
- Formatting only
- Version 2 (7.10.0 release)
-
-
Updated query, changed from:
event.module:okta and event.dataset:okta.system and event.action:user.mfa.attempt_bypass
-