Tech

Explainer

Updated

What is multi-factor authentication?

Key facts

At NIST's second assurance level two distinct factors are required, and at least one option must be phishing-resistant.

Multi-factor authentication (MFA) is authentication that requires more than one distinct type of factor. NIST's glossary defines it as "authentication using two or more different factors to achieve authentication," and its authentication guideline names the three factor types.

The three types of factor

NIST's guideline says every authenticator has one or more authentication factors. The NIST glossary gives examples for each type.

Factor typeNIST's examples
Something you knowPIN, password
Something you haveCryptographic identification device, token
Something you areBiometric

How the factors combine

The glossary says that MFA "can be performed using a single authenticator that provides more than one factor or by a combination of authenticators that provide different factors." So one authenticator can supply two factors on its own, or two or more authenticators can each supply a different factor.

Assurance levels

NIST's guideline sorts authentication into levels called Authentication Assurance Levels (AAL), and each level sets its own factor count.

LevelWhat NIST requires
AAL1Single-factor authentication. NIST recommends that applications assessed at AAL1 offer multi-factor options.
AAL2Two distinct authentication factors. Applications assessed at AAL2 must offer a phishing-resistant option.
AAL3A phishing-resistant authenticator with a non-exportable authentication key, and two distinct authentication factors.

The summary of the levels in the NIST SP 800-63B-4 volume gives these requirements.

Which methods are phishing-resistant

NIST defines phishing resistance as the ability of an authentication protocol to keep authentication secrets and valid authenticator outputs away from an impostor verifier, without relying on the vigilance of the person signing in. The same volume lists the methods it does not count as phishing-resistant.

MethodWhat NIST saysSection
PasswordsPasswords are not phishing-resistant.3.1.1
Look-up secretsLook-up secrets are not phishing-resistant.3.1.2
Out-of-band authenticationOut-of-band authentication is not phishing-resistant.3.1.3
One-time password (OTP) authenticationOTP authentication is not phishing-resistant.3.1.4 and 3.1.5
Cryptographic authenticationCryptographic authentication is phishing-resistant if it meets the additional requirements in Section 3.2.5.3.1.6 and 3.1.7

The volume gives the reason for the manual-entry methods: authenticators that involve manual entry of an output "SHALL NOT be considered phishing-resistant because the manual entry does not bind the authenticator output to the specific session being authenticated." It also states that "phishing resistance requires single- or multi-factor cryptographic authentication."

What changed and when

In July 2025 NIST released the final version of SP 800-63, Revision 4, which the landing page for the suite describes as a comprehensive update from Revision 3. The authentication volume's list of changes includes, for Section 3.2.5, "Adds a definition and updates requirements for phishing-resistant authenticators."

Older text used other names for the same problem. The volume says that phishing was previously referred to in SP 800-63B as "verifier impersonation," and that some prior versions called phishing-resistant protocols "strongly MitM-resistant." A reader who finds those terms in an older document is reading the same subject under the earlier wording.

What a reader meets next

MFA and two-factor authentication. NIST's MFA definition asks for more than one distinct type of factor, and its AAL2 level asks for two distinct factors. The term two-factor authentication has its own page: What is two-factor authentication?

Phishing-resistant MFA. An authentication method can be MFA and still fall outside NIST's phishing-resistant list, as the table above shows. The volume describes a phishing attack as attempts by fraudulent verifiers "to fool an unwary claimant into presenting an authenticator to an impostor." For the attack itself, see What is phishing?

Have another question?