Common signs include repeated helpdesk complaints, high rates of password-reset or token-reset tickets, and users being blocked or slowed during routine access. The article also points to frustration when employees must always use the same factor regardless of device or location. If security controls generate avoidable friction, teams often see workarounds, lower adoption, and weaker overall assurance.
How to tell when MFA is becoming a usability problem
When MFA is too rigid, the signals show up in day-to-day support and user behaviour. Repeated helpdesk complaints, frequent password or token reset requests, and people getting blocked during normal sign-in are early warnings. A second signal is consistency without context, where every login demands the same factor even when the device, network, and risk level are very different.
Rigid MFA usually means the control is being applied as a fixed hurdle instead of a risk control. That creates friction at the exact moments when people need fast, routine access, which is why the issue often appears first in ticket volume, abandonment, and workarounds rather than in an explicit security incident.
In practice, the question is not whether MFA is present, but whether it fits the workflow the business actually runs. If the control forces users to spend noticeable time proving the same thing over and over, the organisation may be paying the cost of stronger prompts without getting proportionate security value.
Where rigidity creates friction, workarounds, and weaker adoption
Rigid MFA tends to push users toward whatever path is easiest, not what is safest. That can mean delayed logins, repeated approvals, shared devices, or informal support requests that bypass the intended process. Over time, the organisation may see lower adoption of the MFA flow itself, especially if the same friction hits office staff, mobile workers, contractors, and remote staff alike.
The deeper problem is that poor fit can reduce assurance in two ways at once. First, users may stop treating MFA as a meaningful security step and start looking for shortcuts. Second, support teams may become more willing to grant exceptions, which weakens consistency and can expand the number of cases where access is handled outside the normal policy path.
For this reason, a modern workforce usually needs more than one usable path through authentication, with stronger factors reserved for the situations that justify them. Phishing-resistant methods, step-up checks, and recovery flows should be designed together so that legitimate users do not experience every sign-in as a high-friction event.
How to judge whether the control is still doing its job
A rigid MFA design should be judged against both security and operational fit. If the control creates avoidable resets, repeated prompts, or long recovery queues, that is a sign the policy is not aligned to the workforce’s actual patterns of access. The most useful test is whether the user can complete routine access without unnecessary interruption while still facing stronger checks when risk is higher.
It also helps to distinguish between healthy friction and unnecessary friction. Some prompts are appropriate when the user changes device, location, or session context. But if the experience is effectively identical for a trusted workstation and an unfamiliar one, the policy is probably too blunt to reflect risk in a modern environment.
Workforce Identity Security Guide is useful here because it covers phishing-resistant MFA, passkeys, SSO, help desk resets, and recovery, the same operational areas where rigidity usually shows up first.
Risk and Threat Considerations
Rigid MFA is not just an inconvenience issue. When users are slowed down or blocked, they look for alternate paths, and those paths often create weaker assurance than the original control was meant to provide. Excessive friction can also make recovery workflows, helpdesk processes, and exception handling more attractive targets for social engineering.
Failure mechanism: A fixed MFA policy fails when it ignores context, so legitimate users face the same challenge regardless of device trust, location, session state, or business urgency. That drives resets, bypass requests, and informal workarounds that reduce the real strength of the authentication flow.
Impact: The organisation gets poorer adoption, more support load, and a larger chance that access will be granted through exception handling instead of the intended control. In the worst case, frustration shifts the risk from the MFA prompt itself to the recovery or approval path around it.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST SP 800-53 Rev 5, NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | SP 800-63 — Digital Identity Guidelines | Explains authentication assurance and adaptive sign-in choices for workforce users. |
| Recommendation — Use assurance levels and phishing-resistant authenticators to match authentication strength to access risk. | ||
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Addresses user authentication controls that become onerous when poorly tuned to workforce access patterns. |
| Recommendation — Adjust organizational-user authentication so routine access stays usable while higher-risk access gets stronger checks. | ||
| NIST CSF 2.0 | PR.AA-05 — Identity Management, Authentication, and Access Control Processes | Covers authentication and access control processes that should balance security with operational usability. |
| Recommendation — Review authentication workflows and exceptions so controls remain effective without creating avoidable friction. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Supports managing access friction, resets, and exceptions in day-to-day identity operations. |
| Recommendation — Tighten access control workflows so exceptions, resets, and sign-in paths stay governed and usable. | ||
Practitioner Guidance
What to prioritise: Start with the highest-friction journeys, usually password resets, token resets, and repeated sign-ins for the same users. If those flows are generating most of the complaints, the issue is likely control design rather than user resistance.
What to verify: Check whether the MFA policy varies appropriately by device trust, location, session risk, and user role. A good design does not remove security checks, it concentrates them where the risk justifies the interruption.
Practitioner takeaway: The goal is not to make MFA disappear, it is to make it adaptive enough that security decisions follow risk instead of forcing every user through the same friction at every login.
Related resources from NHI Mgmt Group
- What are the signs that a security automation workflow is too rigid for modern threats?
- What are the signs that workforce identity controls are too weak for modern fraud and deepfake attacks?
- What are the signs that a cloud security assessment approach is too rigid for modern environments?
- What are the signs that privileged access monitoring is too rigid to catch modern healthcare attacks?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org