Adaptive MFA is a response to authentication fatigue and attack abuse

At a glance

What this is: This is a SecureAuth analysis arguing that constant MFA prompts are creating fatigue, user workarounds, and attack exposure, and that adaptive MFA should replace one-size-fits-all prompt logic with contextual risk decisions.

Why it matters: IAM and security teams need to treat MFA fatigue as both a usability and control-design problem, because repetitive prompts can erode user judgement, increase help desk load, and create openings for account takeover.

By the numbers:

• 68% of users are frustrated by MFA prompts, according to SecureAuth.
• 23% approve requests without reading, according to SecureAuth.
• 40% actively seek workarounds, according to SecureAuth.
• 156% increase in MFA fatigue attacks, according to SecureAuth.

Context

MFA fatigue is the pattern where repeated authentication prompts condition users to approve requests without scrutiny or to bypass controls altogether. In identity programmes, that turns a protective step into a reliability problem, especially when attackers intentionally time prompts to interrupt attention and exploit routine behaviour.

SecureAuth positions adaptive MFA as a response to that failure mode, not a replacement for MFA. The underlying governance issue is that static prompt logic treats every access request the same, even though risk varies by device, location, behaviour, and session context.

For IAM and security teams, the real question is no longer whether MFA exists, but whether it still produces trustworthy user decisions under pressure. If prompt volume is high enough to change user behaviour, the control is already part-way to failure.

Key questions

Q: What breaks when MFA prompts and access checks create authentication fatigue?

A: When prompts become repetitive, people stop paying attention and may approve requests without thinking. The article links this to alert fatigue, mindless approvals, and workarounds that weaken control effectiveness. The failure is not MFA itself, but overuse without context. Continuous, contextual authorization can reduce unnecessary interruptions and keep users engaged with the decision at hand.

Q: Why do repeated MFA prompts create account takeover risk?

A: Repeated prompts work because they pressure the user into a fast decision. The attacker is not bypassing the factor directly. They are overwhelming the person behind it until one approval completes the session. That is why human vigilance alone is not a durable control and why organisations need context-aware step-up policies and stronger factors for higher-risk access.

Q: How can security teams tell whether adaptive MFA is working properly?

A: Look for a lower challenge rate on routine sessions, a higher challenge rate on suspicious transactions, and stable or improved conversion. If adaptive MFA is triggering everywhere, it is behaving like blunt MFA. If it rarely triggers on risky actions, the policy is too weak to matter.

Q: When should organisations use passkeys instead of push approvals?

A: Use passkeys when phishing resistance and user experience both matter, especially for workforce access that is frequently targeted by password theft and push spam. Passkeys remove password reuse from the equation and reduce prompt dependency. Push approvals should become a fallback method, not the default trust mechanism, where stronger options are available.

Technical breakdown

Why MFA fatigue breaks prompt-based authentication

Prompt-based MFA works only when a user can reliably distinguish legitimate requests from malicious ones. MFA fatigue attacks exploit repeated push notifications until the user approves one out of habit, distraction, or annoyance. That turns the second factor into a low-friction approval channel rather than a meaningful challenge. The issue is not MFA itself, but the assumption that human attention remains stable across repeated interruptions. Once that assumption fails, the control becomes predictable and therefore abusable.

Practical implication: reduce repeated approvals and add mechanisms such as number matching or alert suppression for high-frequency prompts.

How adaptive MFA uses risk signals instead of fixed prompts

Adaptive MFA evaluates contextual signals before deciding whether to challenge the user. Typical inputs include device trust, location, time of access, network type, behavioural patterns, and threat intelligence. A low-risk login can proceed with minimal friction, while unusual access triggers step-up verification. This changes authentication from a static checkpoint into a policy decision that responds to current conditions. The design goal is not fewer controls, but better-targeted controls that preserve assurance while reducing unnecessary interruptions.

Practical implication: define risk signals, threshold logic, and exception handling before expanding adaptive policies beyond pilot groups.

Why passkeys and device trust reduce attack surface

Adaptive MFA is more effective when paired with phishing-resistant methods such as passkeys and with device trust for managed endpoints. Passkeys remove password reuse and reduce the value of credential theft, while certificate-based device attestation helps distinguish corporate devices from unknown ones. Behavioral biometrics can add silent verification, but only when tuned carefully and used as one signal rather than a standalone trust decision. The architecture matters because fatigue attacks exploit user response, while credential theft exploits authentication reuse.

Practical implication: prioritise phishing-resistant authentication and trusted-device recognition before relying on behavioural scoring alone.

Threat narrative

Attacker objective: The attacker wants to convert a stolen password into account takeover by making the user approve the second factor under pressure.

1. Entry begins when an attacker acquires a username and password through phishing or another credential theft path.
2. Escalation follows as the attacker sends repeated MFA push requests, often timed to catch the user when they are tired or distracted.
3. Impact occurs when the user approves one of the prompts, allowing the attacker to take over the account and reach enterprise systems and data.

Breaches seen in the wild

• Cisco Yanluowang breach 2022: A password synced to a personal Google account plus vishing and MFA fatigue opened Cisco's VPN; the attacker then abused machine accounts.
• Uber breach 2022: A contractor's stolen password and MFA fatigue gave a Lapsus$-linked attacker Uber's internal tools; Uber rotated keys to many services.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Adaptive MFA is a governance response to human attention limits, not just an authentication tuning exercise. The article shows that repeated prompts change user behaviour, which means the control design itself has become part of the attack surface. In identity programmes, that shifts MFA from a binary enablement question to a question of how often a challenge remains trustworthy. The practitioner takeaway is that MFA policy must be measured against user decision quality, not just deployment coverage.

Static MFA assumes that every login deserves the same treatment, and that assumption no longer holds. Risk varies by device, location, time, behavioural context, and session intent. When those signals are available but ignored, organisations create unnecessary friction while preserving the very attack path fatigue campaigns depend on. The implication is that authentication design now belongs inside continuous risk governance, not as a fixed access gate.

Number matching, prompt throttling, and alert suppression are not usability extras; they are controls against approval abuse. Repeated push prompts work because they exploit reflexive approval, so the control objective has to be to interrupt that reflex. This is a prompt-integrity problem as much as an identity problem. Practitioners should treat approval ergonomics as a security control surface, not a UX afterthought.

Prompt fatigue debt: the longer organisations rely on repetitive MFA prompts, the more they accumulate user distrust and unsafe workarounds. That debt shows up as ignored prompts, shared devices, delayed logins, and help desk noise. Over time, it weakens both assurance and adoption. The practical conclusion is that reducing prompt volume is a governance priority, not a convenience enhancement.

Passkeys and trusted-device policies point in the right direction, but they only work when the access policy understands context. The article’s deeper message is that identity assurance is moving from point-in-time verification toward continuous, context-aware decisions. That trajectory aligns with zero-standing-friction thinking across IAM and workforce identity. Practitioners should align authentication policy, device trust, and step-up rules as one programme rather than separate projects.

From our research library:

• Across one million observed logins, 1 in 4 were password-based rather than SSO, 2 in 5 were not protected by MFA and 1 in 5 used a weak, breached or reused password.

What this signals

Prompt integrity is now part of IAM governance. Security teams can no longer treat MFA as a binary control because the attacker goal is to manipulate the user into approving access. Adaptive policies, number matching, and trusted-device logic are becoming the practical boundary between authentic login and approval abuse.

The operational signal to watch is not only failed logins but user behaviour under repeated challenge pressure. When prompt volume drives workarounds or training fatigue, the authentication programme is creating the very conditions attackers need.

Adaptive authentication should be governed as a risk policy, not a product setting. That means threshold logic, exception handling, and step-up criteria belong in access governance reviews. Teams that leave these decisions buried in configuration will struggle to prove whether the control is reducing risk or merely redistributing friction.

For practitioners

• Measure prompt fatigue before changing policy Track prompt frequency, approval latency, help desk tickets, and user-reported friction by application and user group so you can separate real risk from avoidable noise.
• Deploy number matching on push notifications Require a code or matching challenge for push approval so repeated prompts cannot be accepted reflexively during fatigue attacks.
• Introduce device trust for managed endpoints Use certificate-based attestation and device registration so known corporate devices can receive streamlined authentication while unknown devices trigger stronger checks.
• Move high-risk access to step-up controls Reserve additional verification for sensitive actions, unusual locations, or new devices instead of forcing every login through the same challenge path.
• Pilot adaptive policies in shadow mode Run risk scoring without enforcement first, then calibrate thresholds against observed behaviour before widening deployment to more applications.

Key takeaways

• MFA fatigue turns repeated approval prompts into a control weakness because users eventually respond reflexively instead of deliberately.
• The article links this problem to real-world attack patterns and cites strong growth in fatigue-driven abuse, which makes the issue operational rather than theoretical.
• Adaptive MFA, device trust, and phishing-resistant methods such as passkeys are most effective when they are governed as one policy set, not separate tools.

Key terms

• MFA Fatigue: MFA fatigue is the behavioural pressure created when repeated login prompts make a person more likely to approve access without checking carefully. It is a control failure in the authentication experience, and it becomes dangerous when the approved session carries broad privilege or long-lived access.
• Adaptive MFA: A multi-factor authentication pattern that changes the challenge based on user context, risk, and policy. It reduces unnecessary friction by avoiding one-size-fits-all prompts, while still increasing assurance when a session, device, or location looks unusual.
• Number Matching: Number matching is an MFA method that requires the user to enter or confirm a number shown on the login screen. It reduces blind approvals by linking the approval to the specific session, which makes random taps or reflexive acceptance far less effective.
• Device Trust: Device trust is the confidence that a requesting endpoint is known, managed, and in a compliant state. It matters because identity alone does not prove safety. In zero trust programmes, device trust becomes one of the inputs used to decide whether access should be granted or sustained.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.