Join our Newsletter — 33% off our NHI Course

Why do passkey deployments fail when MFA fallbacks stay on?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Passkey deployments still fail when MFA fallbacks remain, because WorkOS says attackers can route around cryptographic domain binding through SMS, push, email reset, or QR-code paths. Authentication stacks need governing as a whole, since recovery and reset flows can reopen the phishing route the primary factor closed.

Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “Passkeys stop phishing. Your MFA fallbacks undo it.”.

Key questions

Q: Why do passkeys still leave organisations exposed to phishing attacks?

A: Passkeys reduce phishing risk only when they are the sole usable method.

Q: How should security teams decide whether QR-based passkey flows are acceptable?

A: They should decide based on the threat model, not convenience.

Q: What breaks when passkeys are used alongside weak fallback authentication?

A: The programme becomes only as strong as the fallback path.

Practitioner guidance

  • Audit the fallback surface Inventory every active authentication and recovery path in each identity provider and application, including SMS, push, email codes, backup codes, password reset, and "try another way" options.
  • Make phishing-resistant methods mandatory for privileged users Require passkeys or hardware security keys for administrators, finance roles, and production access, rather than offering them as optional enrollment choices.
  • Remove phishable recovery routes Redesign account recovery so it cannot bypass the phishing-resistant method through email or SMS, and require stronger identity proofing or pre-enrolled recovery codes instead.

Bottom line: Passkeys reduce proxy phishing risk, but only when the identity stack stops offering weaker alternate routes.

Glossary terms: Passkey, FIDO2, Mfa Downgrade Surface, Cryptographic binding

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 3 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Phishing resistance is a property of the entire authentication chain, not the strongest factor in it. Passkeys stop proxy phishing only when weaker branches are removed, because attackers do not need to defeat the cryptographic method if they can downgrade the session into a recoverable or alternative path. That makes fallback governance part of the control surface, not an implementation detail. Practitioners should judge authentication by the weakest surviving route.

A few things that frame the scale:

  • 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.

A question worth separating out:

Q: What is the difference between passkey security and MFA strength?

A: Passkey security is protocol-enforced phishing resistance through cryptographic domain binding. MFA strength is broader and can still include phishable methods such as SMS, push, or email reset. A system can use a strong factor and still be weak overall if it leaves alternate paths that attackers can exploit.

👉 Read our full editorial: Passkeys fail when MFA fallbacks remain in place



   
ReplyQuote
Share:

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.