Look beyond factor count and measure phishing resistance, step-up coverage, and recovery abuse. Passkeys and hardware keys are stronger than SMS or basic push because they bind authentication to origin, while number matching and adaptive challenges reduce fatigue attacks. If recovery paths remain weak, MFA may still be bypassed.
How to tell whether MFA is reducing risk in practice
MFA is reducing risk when it blocks the attacks you actually see, not just when it adds a second prompt. The useful question is whether sign-in attempts that start with stolen passwords, phishing, push fatigue, or recovery abuse are being stopped, delayed, or made visible before an account is taken over.
The strongest signal is a mix of control quality and attack resistance. Phishing-resistant methods such as passkeys and hardware keys should outperform SMS or basic push, while number matching and adaptive challenges should cut down on approval fatigue. If recovery flows are still easy to social-engineer, the programme can look strong while remaining bypassable.
That is why organisations should measure the whole authentication journey: enrolment, everyday sign-in, step-up prompts, recovery, and exception handling. A low-friction MFA rollout can still leave a weak back door if legacy protocols, forgotten accounts, help desk resets, or backup codes remain easier to abuse than the primary login path.
What the right MFA metrics actually capture
Factor count is a poor proxy because it says nothing about attacker resistance. A better metric set shows whether the control is reducing successful compromise paths, not just increasing inconvenience for users. That means measuring how often phishing-resistant methods are in use, how often step-up is triggered for risky access, and whether those prompts are tied to the right events.
Look for signals that reveal the quality of the control, not the volume of prompts. A healthy MFA programme should show fewer successful phishing-based logins, fewer suspicious recovery events, lower approval fatigue success, and fewer cases where an attacker gains access through a weaker alternate path. If you cannot separate primary sign-in from recovery and exception use, you cannot tell where the risk really moved.
- Track adoption of phishing-resistant sign-in methods versus legacy methods.
- Measure the share of high-risk sessions that receive step-up authentication.
- Review rejected, delayed, or failed attempts tied to phishing, relay, or fatigue patterns.
- Monitor recovery events, especially resets, bypasses, and help desk assisted changes.
Where MFA still fails even when the login prompt looks strong
Many organisations harden the first factor but leave the surrounding paths weak. Recovery abuse, session theft, and legacy authentication can bypass a well-designed MFA prompt entirely. That is why the control has to be judged across the full account lifecycle, not only at interactive sign-in.
Recovery is often the hidden weak point because attackers know it is designed to be forgiving. If a user can be re-enrolled through social engineering, a stolen email account, a compromised device, or a permissive help desk flow, the attacker may not need to defeat the main MFA method at all. Session token theft has a similar effect: the attacker sidesteps authentication after the fact.
Organisations should also watch for accounts that do not follow the modern path at all, such as dormant admins, test accounts, service-linked access, or old protocols that still accept credentials without strong challenge. Those gaps often explain why MFA appears broadly deployed but still fails to reduce actual compromise.
Risk and Threat Considerations
Weak recovery paths, legacy access, and session theft can undermine MFA even when the primary method is strong. Attackers usually target the easiest path into the account, so a narrow view of login prompts can miss the real exposure.
Failure mechanism: An attacker uses phishing, fatigue, token theft, or help desk social engineering to bypass or reuse an authenticated path, then keeps access through a weak recovery or session channel.
Impact: The organisation records MFA deployment but still suffers account takeover, privilege abuse, or silent re-entry after reset, which means the control reduced friction more than risk.
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 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Covers authenticator strength, phishing resistance, and recovery assurance for MFA outcomes. |
| Recommendation — Use NIST 800-63 to evaluate authenticator assurance and recovery strength, not just factor count. | ||
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Directly governs user authentication strength and MFA enforcement for workforce access. |
| IA-5 — Authenticator Management | Covers lifecycle controls for authenticators, which affects MFA recovery abuse and secret handling. | |
| IA-8 — Identification and Authentication (Non-Organizational Users) | Relevant where MFA protects external or customer access paths. | |
| Recommendation — Apply IA-2 to require strong authentication for organizational access. Use IA-5 to manage authenticator lifecycle, rotation, and recovery protections. Apply IA-8 when MFA protects external-user access paths. | ||
| NIST CSF 2.0 | PR.AA-05 — Identity Management, Authentication, and Access Control | Directly maps to proving that MFA is reducing access risk across authentication and step-up decisions. |
| Recommendation — Measure authentication outcomes under PR.AA-05, including step-up and resistance to takeover attempts. | ||
Practitioner Guidance
What to verify: Confirm that your telemetry distinguishes primary authentication success from recovery, reset, and step-up events. If you only measure enrollment or prompt volume, you are missing the part of MFA that attackers actually exploit.
Decision rule: If phishing-resistant methods are available but not enforced for sensitive roles or high-risk actions, treat the programme as partially effective rather than fully risk-reducing. Step-up should be reserved for meaningful risk changes, not used as a universal cosmetic layer.
What good looks like: The strongest sign is fewer successful attacks with a clear drop in account takeover, fewer recovery-driven exceptions, and visible friction for phishing and fatigue attempts without creating excessive user workarounds.
Practitioner takeaway: MFA reduces risk only when the strongest path is also the most common path, and when recovery, session handling, and legacy access are held to the same standard as the login prompt itself.
Related resources from NHI Mgmt Group
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