MFA is being undermined when users receive repeated authentication prompts that no longer reflect genuine risk and start approving them automatically. That pattern creates fatigue, lowers attention, and can let attackers exploit social engineering or push abuse. Teams should treat an increase in unexpected prompts, especially for high-risk logins, as a signal that controls need stronger risk-based logic.
Why Repeated MFA Prompts Are a Warning Sign
Prompt fatigue is not just an inconvenience. It is a sign that authentication has stopped feeling meaningful to the user, which means the control is drifting away from real risk detection and toward routine noise. When that happens, attackers do not need to defeat MFA technically in every case; they only need a user who is tired enough to click through.
That matters because repeated approval requests often indicate one of two problems: the environment is generating too many false positives, or an attacker is actively hammering the user until one request succeeds. NHI Management Group sees this pattern as especially dangerous when the prompts appear outside normal working hours, repeat in short bursts, or target high-value accounts with broad access. In practice, many security teams discover the problem only after a user has already approved something they did not properly inspect.
How Prompt Fatigue Shows Up in Practice
The most common sign is frequency. A healthy MFA flow should be occasional and explainable, not a constant stream of prompts that users learn to dismiss. If people begin approving requests reflexively, the control has shifted from verification to habit.
Look for these operational signals:
- Repeated prompts for the same account in a short window, especially after a successful login.
- Approvals that cluster during meetings, travel, shift changes, or outside normal hours.
- Users reporting that prompts arrive when they are not actively signing in.
- Push approvals from geographies, devices, or times that do not fit the user’s normal pattern.
- Help desk tickets describing MFA as “annoying,” “constant,” or “easy to ignore.”
From a control perspective, the issue is usually not MFA itself but the policy behind it. Risk-based authentication should reduce unnecessary challenges, while sign-in telemetry, device posture, location, and session context should help distinguish legitimate reauthentication from suspicious activity. Where repeated prompts are caused by short token lifetimes, unstable sessions, or poorly tuned conditional access rules, users are trained to expect interruption rather than scrutiny.
The practical test is whether the prompt still contains decision value. If the user cannot tell why the request appeared, or the system keeps asking without changing the underlying risk signal, the control is too noisy to trust. Teams should also check whether approved prompts are followed by new device enrollment, impossible travel, mailbox rule changes, or other signs that the approval was part of a broader compromise chain.
NHI Mgmt Group research highlights how fragile identity controls become when visibility is weak: only 5.7% of organisations report full visibility into their service accounts, which is a useful reminder that repeated authentication noise often sits inside a larger identity-governance gap. The same pattern appears with human MFA when monitoring is not tied to clear behavioral baselines. These controls tend to break down when high-volume prompt traffic is treated as normal because no one has separated genuine sign-in friction from active abuse.
When Noise Becomes Abuse
Tighter MFA enforcement often increases user friction, so organisations must balance stronger challenge coverage against the risk of teaching users to approve without thinking. That tradeoff becomes most visible when attackers deliberately generate request volume to wear down attention.
Best practice is evolving, but current guidance suggests treating repeated approval requests as a potential abuse pattern, not only as a usability issue. A sudden rise in prompts for a specific user, especially when paired with unfamiliar IP addresses, legacy protocol access, or impossible travel signals, should trigger investigation rather than simple reset-and-retry handling. The goal is to determine whether the system is over-challenging legitimate users or whether an attacker is actively testing persistence against the account.
One useful distinction is between control misconfiguration and adversary pressure. If the prompts continue after token revocation, password reset, or device re-enrollment, the problem may be stale sessions or multiple authentication paths still in play. If the prompts stop once the user stops responding, the account may be under active push fatigue or social engineering pressure. In either case, the security team should treat repeated approvals as evidence that authentication confidence is eroding.
For a broader identity-control baseline, the NIST control family on access enforcement is helpful for aligning MFA with monitoring and review expectations: NIST SP 800-53 Rev 5 Security and Privacy Controls. For a concrete breach pattern involving identity abuse and repeated access attempts, see Microsoft Midnight Blizzard breach.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Agentic AI Top 10 and MITRE ATT&CK address the attack and risk surface, while CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Agentic AI Top 10 | A2 — Human Oversight & Authorization | Prompt fatigue weakens human approval of authentication requests. |
| Recommendation — Reduce repeated approvals by requiring stronger human confirmation for suspicious authentication events. | ||
| CIS Controls v8 | 5 — Account Management | Repeated prompts often signal poor account/session governance and access noise. |
| 6 — Access Control Management | MFA fatigue is a sign that access decisions need tighter contextual enforcement. | |
| Recommendation — Review authentication noise and revoke or retune accounts that generate excessive MFA prompts. Enforce contextual access checks so MFA prompts only appear when risk warrants them. | ||
| NIST CSF 2.0 | PR.AA-03 — Identity Proofing, Authentication, and Binding | Prompt fatigue shows authentication binding is losing assurance value. |
| DE.CM-01 — Security Continuous Monitoring | Repeated prompts are a monitoring signal for active abuse or control misconfiguration. | |
| Recommendation — Strengthen authentication logic so repeated prompts do not become routine or ignorable. Monitor authentication prompt volume and investigate abnormal spikes as potential abuse. | ||
| MITRE ATT&CK | T1621 — Multi-Factor Authentication Request Generation | Attackers can abuse repeated MFA requests to exhaust user attention. |
| Recommendation — Detect and block MFA request flooding associated with push fatigue campaigns. | ||
Practitioner Guidance
What to prioritise: Separate harmless friction from active abuse by checking whether repeated prompts correlate with unusual sign-in context, new devices, or logins outside expected hours. A spike that is user-specific and time-bounded is more concerning than a broad rise caused by policy drift.
What to verify: Confirm that every approval request is tied to a real authentication event and that users can see enough context to make a meaningful decision. If prompts lack location, device, or application cues, the control is too opaque to support reliable user judgment.
Decision rule: If users are approving prompts they cannot explain, treat that account as at elevated compromise risk even if no login has been confirmed. The behavior itself is evidence that the control is losing effectiveness.
Common mistake: Interpreting prompt fatigue as a training problem only. Awareness helps, but noisy authentication flows usually need policy tuning, session redesign, or stronger contextual checks, not just reminders to “be careful.”
Practitioner takeaway: Repeated MFA prompts are dangerous when they become predictable, because predictable prompts train users to obey the control instead of evaluating it.
Related resources from NHI Mgmt Group
- How can teams tell whether MFA is causing approval fatigue?
- How should security teams design approval workflows for agentic AI so repeated requests do not train people to approve blindly?
- What are the signs that a custom authentication stack is no longer working well enough for a growing product?
- What are the signs that SAML is the more practical authentication choice?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 8, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
