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
Patterns shared across the 31 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (66 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (114 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (6 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
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