Identity & Security

Phishing-Resistant MFA Explained: What NIST and WebAuthn Require

What makes multi-factor authentication phishing-resistant under NIST SP 800-63B-4, how WebAuthn and passkeys fit, and how to plan a rollout.

By Devacon LtdPublished 5 min read

Multi-factor authentication stops many account takeovers, but not all MFA is equal. A one-time code typed into a convincing fake login page can be relayed to the real site within seconds. Phishing-resistant MFA closes that gap by making the authentication itself useless anywhere except the genuine site.

This article explains what “phishing-resistant” means in the current NIST guidance, which authenticators qualify, how WebAuthn and passkeys fit in, and how to plan a rollout without locking users out.

The standard behind the term

NIST Special Publication 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management, was published as a final document in July 2025. It supersedes the earlier SP 800-63B from March 2020. It is written for US federal systems, but its definitions are a useful, precise vocabulary for any team designing authentication.

The guideline defines phishing resistance as the ability of the authentication protocol to stop authentication secrets from being disclosed to an impostor verifier, without relying on the user to spot the fake. That last part is the point: training helps, but a phishing-resistant method still protects a user who has been fooled.

Two ways to achieve it

NIST recognizes two mechanisms, both of which require cryptographic authentication:

  • Channel binding. The authenticator’s output is tied to the secure channel itself, for example with client-authenticated TLS as used by government PIV and CAC smart cards. NIST describes this as the stronger of the two.
  • Verifier name binding. The authenticator only produces output for the verifier it was registered with. WebAuthn is NIST’s example of this approach.

What does not qualify

NIST states that authenticators requiring the user to manually enter an output, such as one-time passwords and out-of-band codes, are not phishing-resistant. Typing does nothing to bind the code to the real session, so a relay attack still works. Passwords and look-up secrets are not phishing-resistant either.

The guidance also treats out-of-band verification over the public telephone network, such as SMS or voice codes, as a restricted authenticator. Verifiers that use it must offer alternatives and should consider risk signals such as a recent SIM change or number port. Email is not permitted as an out-of-band authenticator.

Where assurance levels come in

SP 800-63B-4 defines three authenticator assurance levels (AALs):

Level Confidence Phishing resistance
AAL1 Basic Not required
AAL2 High Verifiers must offer at least one phishing-resistant option
AAL3 Very high Required, with a non-exportable private key

The AAL2 rule is easy to miss. Even if most users still sign in with a less resistant method, a system operating at AAL2 must make a phishing-resistant option available.

How WebAuthn delivers verifier name binding

The W3C Web Authentication specification defines a browser API for creating and using public key credentials. Level 3 became a W3C Recommendation on 25 August 2026.

In WebAuthn, each credential is scoped to a Relying Party, which is your application. The specification says a credential can only be used by origins that belong to that Relying Party, and browsers and authenticators enforce this together. A look-alike domain is a different origin, so the browser will not use the real site’s credential there. That is the phishing resistance NIST refers to.

During sign-in, the authenticator signs a challenge from your server with its private key, and your server checks the signature with the public key it stored at registration. Because the server holds a public key rather than a shared secret, there is no password-like value in your database for an attacker to replay.

Passkeys, synced and device-bound

The WebAuthn Level 3 specification uses the term passkey and distinguishes two kinds of credential:

  • Multi-device credentials (synced passkeys), which a credential manager can back up and sync across a user’s devices.
  • Single-device credentials, which stay on one authenticator, such as a hardware security key.

Two flags tell your server which kind it is dealing with. Backup Eligibility is set when the credential is created and never changes. Backup State shows whether the credential is currently backed up and can change over time.

This distinction matters for assurance. NIST calls credentials that copy their secret to other devices syncable authenticators. Because their keys are exportable, they are not allowed at AAL3, but they are permitted at AAL2. For most consumer and workforce applications, synced passkeys are a practical phishing-resistant option. For the highest-risk roles, device-bound credentials remain the requirement.

Planning a rollout

Moving users to phishing-resistant MFA is as much a change-management task as a technical one. A staged plan reduces support load and lockouts.

Technical checklist

  • Add WebAuthn registration and sign-in to your application, or enable it in your identity provider if sign-in is federated.
  • Record the Backup Eligibility and Backup State flags at registration so you can apply different policies to synced and device-bound credentials.
  • Let users register more than one authenticator, so that losing a device does not mean losing access.
  • Design recovery carefully. If account recovery falls back to an SMS code or email link, an attacker will target the recovery path instead. Recovery should be at least as strong as the authenticator it replaces.
  • Keep restricted methods as fallbacks only, with the alternatives and risk checks NIST expects.
  • Log enrollment and use of each authenticator type, so you can measure adoption and spot anomalies.

Rollout sequence

  1. Start with privileged users. Administrators, finance approvers and anyone with production access benefit most and are usually the smallest group.
  2. Offer, then encourage. Make phishing-resistant sign-in available to everyone, prompt users to enroll, and explain the benefit in plain language.
  3. Enforce by risk. Require it for sensitive actions and roles first, then widen enforcement as enrollment grows.
  4. Retire weaker methods gradually, keeping a supported path for users who genuinely cannot use the new method.

Common misunderstandings

  • “An authenticator app is phishing-resistant.” A six-digit code from an app is still typed by the user, so NIST does not treat it as phishing-resistant. Push approvals are out-of-band authenticators, which NIST does not count as phishing-resistant either.
  • “Passkeys are only for consumers.” Synced passkeys can serve as the phishing-resistant option at AAL2 when they meet NIST’s requirements for syncable authenticators, and device-bound credentials with non-exportable keys are the route to AAL3.
  • “We have MFA, so we are done.” The recovery flow, session handling and the help desk’s identity checks are all part of the authentication system.

How Devacon can help

We design and implement authentication flows that include phishing-resistant options, from WebAuthn and passkey support in your own application to policy configuration in identity providers such as Microsoft Entra ID and Okta. A typical engagement covers enrollment, recovery design and a staged rollout plan. Learn more about our identity and access management services.

Sources

  1. NIST SP 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management (CSRC publication page)
  2. NIST SP 800-63B-4 (online version)
  3. W3C Web Authentication: An API for accessing Public Key Credentials, Level 3

Facts in this article were checked against the sources above on November 17, 2026. Standards and products change, so check the source before relying on a detail. Related service: Identity & Access Management.

More insights

Let's build something great together

Ready to talk about custom software? Tell us about your project requirements and we will get back to you.