Multi-Factor Authentication Request Generation T1621
Tactic: Credential Access
Adversaries may attempt to bypass multi-factor authentication (MFA) mechanisms and gain access to accounts by generating MFA requests sent to users.
Authoring guide
These 31 rules share fields, values, and exclusions.
Fields filtered most (64 distinct)
These fields appear most often in rule filters.
Top indicator values (115 distinct)
These values appear most often in rule predicates.
Exclusions (6 distinct)
These values appear most often in top-level exclusions.
Rules under this technique
These vendors publish rules tagged with this technique.
Sigma 3 rules
- MFA Push Fatigue - detects when a user is repeatedly prompted for MFA push.
- Multifactor Authentication Denied
- Multifactor Authentication Interrupted
Elastic 3 rules
- Entra ID User Reported Suspicious Activity
- Potential Okta MFA Bombing via Push Notifications
- Potentially Successful Okta MFA Bombing via Push Notifications
Splunk 18 rules
- ASL AWS Multi-Factor Authentication Disabled
- AWS Console Login Failed During MFA Challenge
- AWS Multi-Factor Authentication Disabled
- AWS Multiple Failed MFA Requests For User
- Azure AD Authentication Failed During MFA Challenge
- Azure AD Multiple Denied MFA Requests For User
- Azure AD Multiple Failed MFA Requests For User
- GCP Authentication Failed During MFA Challenge
- GCP Multiple Failed MFA Requests For User
- O365 Multiple Failed MFA Requests For User
- Okta Authentication Failed During MFA Challenge
- Okta Mismatch Between Source and Response for Verify Push Request
- Okta Multiple Failed MFA Requests For User
- Okta Successful Single Factor Authentication
- PingID Mismatch Auth Source and Verification Response
- PingID Multiple Failed MFA Requests For User
- PingID New MFA Method After Credential Reset
- PingID New MFA Method Registered For User
Kusto 1 rule
YARA-L 2 rules
- Okta Mismatch Between Source And Response For Verify Push Request
- Okta User Failed Number Challenge During Push Notification