Skip to content
Start with Identity
Concept

MFA

MFA (multi-factor authentication) is sign-in that requires two or more factors from different categories: something you know (a password or PIN), something you have (an MFA device such as a phone or security key) or something you are (a biometric). NIST SP 800-63B-4 grades MFA by Authenticator Assurance Level (AAL) and requires verifiers to offer at least one phishing-resistant option at AAL2.

MFA method Phishing-resistant?
SMS or voice code (a NIST "restricted" authenticator) No
Authenticator app code (TOTP) No
Push approval, even with number matching No
Passkey or FIDO2 security key Yes
PIV or CAC smart card Yes

The word MFA now covers methods with a security gap of several orders of magnitude, which is why policies that just say "require MFA" keep failing. SMS codes, app-generated codes, and push approvals are all relayed by commodity phishing kits in real time. Origin-bound credentials are not. When you write a policy or a compliance control, name the method class, not the acronym.

See also: phishing-resistant MFA, passkey, AAL, MFA vendors, two-factor authentication (2FA)

Related terms
Last reviewed By SWI Community TeamSuggest a correctionHow we research