IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Possible Okta DoS Attack Potential Admin Group Account Addition »
Elastic Docs ›Elastic Security Solution [8.2] ›Detections and alerts ›Prebuilt rule reference

Potential Abuse of Repeated MFA Push Notifications

edit

Potential Abuse of Repeated MFA Push Notifications

edit

Detects 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: 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: 2 (version history)

Added (Elastic Stack release): 8.1.0

Last modified (Elastic Stack release): 8.2.0

Rule authors: Elastic

Rule license: Elastic License v2

Investigation guide

edit
## Config

The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.

Rule query

edit
sequence by user.email with maxspan=10m [any where event.module ==
"okta" and event.action == "user.mfa.okta_verify.deny_push"] [any
where event.module == "okta" and event.action ==
"user.mfa.okta_verify.deny_push"] [any where event.module == "okta"
and event.action == "user.authentication.sso"]

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 2 (8.2.0 release)
  • Formatting only
« Possible Okta DoS Attack Potential Admin Group Account Addition »