How the concept is used

A password and an additional secret answer are both knowledge factors. They therefore do not automatically provide the independence sought from MFA. An authenticator on a device can instead be combined with local user verification, depending on the design. The documented method, rather than the number of screens, determines which factors support the check.

A practical example

Imagine a shop owner accessing an order system with a password and approval on a registered phone. If the phone is lost, recovery becomes important: an attacker should not be able to replace the additional factor through a weakly protected email request. The owner also needs a realistic way to regain access. Backup access and support should therefore be designed alongside everyday login.

Important distinctions

MFA does not guarantee protection against every phishing attempt or misuse. Some methods can expose users to code theft or approval of the wrong request, while others bind authentication to the intended service. Compare the factor types, phishing resistance and recovery process together. A biometric unlock on a phone also does not necessarily mean that the online shop receives a fingerprint or facial image. Where biometric information is processed depends on the architecture, and should be checked rather than inferred from the customer’s experience.

Sources

  1. NIST: NIST SP 800-63B-4: Authentication and Authenticator Management Checked

These explanations were prepared with AI assistance and draw on the sources listed.