practiceEngineering & architecture

Multi-Factor Authentication (MFA)

An authentication approach requiring proof from at least two distinct factor categories to increase confidence in the claimant.

Download Markdown (.md)

01What it means

Multi-factor authentication (MFA) requires distinct authentication factors, commonly something known, possessed, or inherent to the claimant. Two passwords are not two factors. A multi-factor authenticator may combine possession of a device with local activation such as a PIN or biometric comparison.[1][2]

Independent proof factors Verify distinct factor types before issuing a session at the achieved assurance
  1. 01Assurance + threatsAccount and action risk
  2. 02Enroll factorsKnowledge, possession, or inherence
  3. 03Verify distinct proofsIndependent factors, intended service
  4. 04Create sessionBind achieved assurance
  5. 05Recover + revokeBackup authenticators and suspicious activity

Two passwords are not two factors. Enrollment, factor replacement, and recovery must be protected at least as strongly as ordinary authentication.

02Why it matters

MFA reduces reliance on one stolen or guessed secret and can materially limit password compromise. Phishing resistance, enrollment, recovery, and factor independence matter more than simply displaying a second prompt.

03When to use it

Offer MFA broadly and require it for privileged access, sensitive data, high-impact actions, and risk levels needing stronger assurance. Prefer phishing-resistant cryptographic authenticators where practical and provide accessible, securely governed recovery.

04How it works

  1. Select an assurance target and threats for the account and action.
  2. Enroll two independent factors through an authenticated process and notify the account owner.
  3. During authentication, verify proof of control from the required distinct factors.
  4. Bind the result to the intended service and create a session at the achieved assurance.
  5. Protect factor replacement and recovery at least as strongly as normal authentication.
  6. Support revocation, backup authenticators, and monitoring for suspicious prompts or enrollment.

05A practical example

Example

An administrator signs in with a password and a hardware security key bound to the service origin. A stolen password alone is insufficient, and replacing the key requires a separately protected recovery process.

06Where it breaks

MFA does not stop session theft, malicious endpoints, unsafe recovery, or authorization flaws. SMS and approval prompts can be phished or abused, biometrics have privacy and recovery constraints, and inaccessible factor choices can lock users out.

Common mistakes

  • Calling two knowledge questions multi-factor authentication.
  • Using a weak recovery flow that bypasses both factors.
  • Treating any second factor as phishing-resistant.
  • Sending repeated approval prompts that train users to accept attacks.

07Sources

  1. Digital Identity Guidelines: Authentication and Authenticator ManagementNIST · Government standardDigital Identity Guidelines: Authentication and Authenticator Management
  2. Implementing Phishing-Resistant MFACISA · Government security guidanceImplementing Phishing-Resistant MFA
View saved topics

Start typing to search titles, definitions, categories, and frameworks.