Skip to content
Start with Identity
Authentication

MFA Device

An MFA device is the physical thing a user has (a phone running an authenticator app, a hardware security key, a smart card, or an OTP token) that supplies the "something you have" factor in multi-factor authentication. NIST SP 800-63B-4 calls these authenticators and classifies them by how they prove possession, not by brand.

MFA device NIST 800-63B-4 type Phishing-resistant?
Phone receiving an SMS or voice code Out-of-band device over the PSTN, a "restricted" authenticator No
Phone with a push app, such as Microsoft Authenticator or Duo Out-of-band device No, even with number matching
Phone or token showing a 6-digit TOTP code Single-factor OTP No
Hardware security key, such as a YubiKey Single- or multi-factor cryptographic authenticator (FIDO2) Yes
Phone or laptop holding a passkey Multi-factor cryptographic authenticator Yes
PIV or CAC smart card Multi-factor cryptographic authenticator Yes

The distinction that matters is the last column. A device that displays or receives a code the user types can be relayed by a phishing proxy; a device that signs a challenge bound to the website's origin cannot. NIST SP 800-63B-4 requires that verifiers "SHALL offer at least one phishing-resistant authentication option at AAL2", and it bars syncable authenticators, such as synced passkeys, at AAL3 because their keys can be exported.

When choosing MFA devices, plan for loss as carefully as for issuance: register at least two devices per user, decide how a lost device is replaced (a Temporary Access Pass after re-verification, not an SMS code), and remove the old device from the account.

See also: phishing-resistant MFA, phishable MFA, AAL, MFA matrix, best MFA solutions, MFA implementation best practices

Last reviewed By SWI Community TeamSuggest a correctionHow we research