What makes MFA phishing-resistant, and how NIST grades authenticators
Reviewed 2026-11-10 · Editorial assessment by the editors
By the editors · 3 min read
MFA is phishing-resistant when the credential is bound to the real site or device, so a fake sign-in page cannot relay it. Passkeys, FIDO2 security keys, Windows Hello for Business and certificate-based authentication are on Microsoft's phishing-resistant list; a code typed from a phone is not. NIST sets out three authenticator assurance levels in SP 800-63B-4.
Why can ordinary MFA be phished?
A one-time code or a push approval proves that the user has the phone, but not which website they are signing in to. A fake page can ask for the code and pass it to the real site straight away, which is called an adversary-in-the-middle attack. The second factor worked; it was given to the wrong party.
What makes a credential phishing-resistant?
With FIDO2 and WebAuthn, the device holds a private key and proves possession to the site, and the credential is bound to the real site, so there is no shared secret to type into a fake page. Microsoft lists these phishing-resistant methods for Entra ID: Windows Hello for Business, Platform Credential for macOS, synced passkeys, FIDO2 security keys, passkeys in Microsoft Authenticator and certificate-based authentication.
Okta describes FastPass as passwordless sign-in with device trust and biometrics and supports FIDO2 WebAuthn and PIV/CAC. NewCore lists phishing-resistant MFA, device-bound passkeys and VisualMFA.
Device-bound or synced passkeys?
Device-bound passkeys stay on one device or security key. Synced passkeys are backed up across a user's devices by a passkey provider. Microsoft lists synced passkeys in Entra ID as generally available in March 2026, managed alongside device-bound passkeys through passkey profiles in the authentication methods policy.
Which to allow is a policy decision. Synced passkeys are easier to recover when a device is lost; device-bound passkeys never leave the hardware they were created on.
What are NIST's authenticator assurance levels?
NIST SP 800-63B-4, "Digital Identity Guidelines: Authentication and Authenticator Management", was published on 31 July 2025 and sets technical requirements for each of three authenticator assurance levels, AAL1 to AAL3. Vendors map their products to these levels: Okta states that FastPass meets FedRAMP High and NIST requirements for AAL3 on properly configured devices, and NewCore scores authenticator strength from 1 to 10 mapped to NIST levels. Read the configuration conditions that come with any such claim.
The MFA and passwordless comparison calls Okta and Entra ID on these methods.
Where do most rollouts start?
Usually with a method already on the device. In Microsoft estates that means Windows Hello for Business and Platform Credential for macOS; where Okta is the identity provider, FastPass. Security keys and PIV or CAC smart cards cover shared devices and high-assurance roles. In Entra ID the allowed methods are set in the authentication methods policy, and passkey profiles, generally available since March 2026, manage synced and device-bound passkeys side by side.