Cross-source coverage

T1621 / ATT&CK

Multi-Factor Authentication Request Generation

30 rules across 6 sources.

From MITRE ATT&CK 19.2

Adversaries may attempt to bypass multi-factor authentication (MFA) mechanisms and gain access to accounts by generating MFA requests sent to users.

Adversaries in possession of credentials to Valid Accounts may be unable to complete the login process if they lack access to the 2FA or MFA mechanisms required as an additional credential and security control. To circumvent this, adversaries may abuse the automatic generation of push notifications to MFA services such as Duo Push, Microsoft Authenticator, Okta, or similar services to have the user grant access to their account. If adversaries lack credentials to victim accounts, they may also abuse automatic push notification generation when this option is configured for self-service password reset (SSPR).

In some cases, adversaries may continuously repeat login attempts in order to bombard users with MFA push notifications, SMS messages, and phone calls, potentially resulting in the user finally accepting the authentication request in response to “MFA fatigue.”

Platforms
Windows · Linux · macOS · IaaS · SaaS · Office Suite · Identity Provider
Telemetry
azure:signinlogsNSM:ConnectionsAWS:CloudTrailWinEventLog:Securityauditd:AUTHsaas:oktamacos:unifiedlog

How MITRE says to detect it DET0160

Detection Strategy for Multi-Factor Authentication Request Generation (T1621)

Identity Provider Analytic 0449

Monitor for excessive or anomalous MFA push notifications or token requests, especially when login attempts originate from unusual IPs or geolocations and do not correspond to legitimate user-initiated sessions.

  • azure:signinlogs Multiple MFA challenge requests without successful primary login
  • NSM:Connections PushNotificationSent

IaaS Analytic 0450

Detect abnormal MFA activity within cloud service provider logs, such as repeated generation of MFA challenges for the same user session or mismatched MFA device and login origin.

  • AWS:CloudTrail AssumeRole or ConsoleLogin with repeated MFA failures followed by repeated MFA requests

Windows Analytic 0451

Detect repeated failed login events followed by MFA challenges triggered in rapid succession, especially if originating from service accounts or anomalous IP addresses.

  • WinEventLog:Security EventCode=4625

Linux Analytic 0452

Monitor PAM and syslog entries for unusual frequency of login attempts that trigger MFA prompts, particularly when MFA challenges do not match expected user behavior.

  • auditd:AUTH pam_unix or pam_google_authenticator invoked repeatedly within short interval

SaaS Analytic 0453

Detect anomalous OAuth or SSO logins that repeatedly generate MFA challenges, particularly where MFA approvals are denied or timed out by the user.

  • saas:okta MFAChallengeIssued

macOS Analytic 0454

Detect user account logon attempts that trigger multiple MFA challenges through enterprise identity integrations, especially if MFA push requests are generated without successful interactive login.

  • macos:unifiedlog authd generating multiple MFA token requests

View on attack.mitre.org ↗

splunk/security_content

18 rules
Detection Severity Format
ASL AWS Multi-Factor Authentication Disabled Undefined SPL
AWS Console Login Failed During MFA Challenge Undefined SPL
AWS Multi-Factor Authentication Disabled Undefined SPL
AWS Multiple Failed MFA Requests For User Undefined SPL
Azure AD Authentication Failed During MFA Challenge Undefined SPL
Azure AD Multiple Denied MFA Requests For User Undefined SPL
Azure AD Multiple Failed MFA Requests For User Undefined SPL
GCP Authentication Failed During MFA Challenge Undefined SPL
GCP Multiple Failed MFA Requests For User Undefined SPL
O365 Multiple Failed MFA Requests For User Undefined SPL

+ 8 more from splunk/security_content → showing the 10 highest-severity

panther-labs/panther-analysis

4 rules
Detection Severity Format
Okta Login Without Push Critical Panther Python
Potential Compromised Okta Credentials Critical Panther Python
Auth0 Push Notification Fatigue High Panther Python
AWS Unsuccessful MFA attempt High Panther Python

elastic/detection-rules

3 rules
Detection Severity Format
Potentially Successful Okta MFA Bombing via Push Notifications High Elastic TOML
Potential Okta MFA Bombing via Push Notifications High Elastic TOML
Entra ID User Reported Suspicious Activity Medium Elastic TOML

SigmaHQ/sigma

2 rules
Detection Severity Format
Multifactor Authentication Denied Medium Sigma
Multifactor Authentication Interrupted Medium Sigma

chronicle/detection-rules

2 rules
Detection Severity Format
okta_mismatch_between_source_and_response_for_verify_push_request Medium YARA-L
okta_user_failed_number_challenge_during_push_notification Medium YARA-L

socfortress/Wazuh-Rules

1 rule
Detection Severity Format
operation. · office_365.LogonError = UserStrongAuthEnrollmentRequired Low Wazuh XML

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.