Language

Multi-Factor Authentication (MFA)

What is Multi-Factor Authentication (MFA)?

Multi-factor authentication (MFA) is a method of confirming a user’s access to an account or service with at least two distinct types of authentication factor. A person might enter a password and then approve the login using a device linked to their account.
Authentication factors are usually grouped into three categories:
  • Something you know: a password or PIN.
  • Something you have: a registered device, security key, or hardware token, or device containing a cryptographic credential.
  • Something you are: a biometric characteristic, such as a face or fingerprint.
The factors must come from different categories. A password followed by a security question still relies entirely on something the user knows and therefore does not constitute MFA. NIST defines MFA as an authentication system requiring more than one distinct type of authentication factor.

How does MFA work?

An MFA process checks the factors required by the service before granting access. For example, a banking application may ask for a password and then require the customer to use a registered authenticator. Another service may use a passkey stored on a device and require a fingerprint or face check to activate it.
The service may require all factors at every login or request additional authentication when risk increases. This step-up authentication may be triggered when a user signs in from a new device, recovers an account, changes payment details, or accesses sensitive information.
The strength of MFA depends on the authenticators and protocols used. A password combined with an OTP can help protect an account when the password has been stolen, but an attacker may still intercept the code or persuade the user to reveal it. A passkey using an appropriate cryptographic authentication protocol can provide phishing-resistant authentication because it binds authentication to the legitimate service. MFA is therefore a category of methods, not a guarantee that every combination provides the same level of protection.

Where does biometric verification fit?

Biometrics can contribute to MFA when they are used with a physical authenticator. For example, a fingerprint or facial biometric may activate a passkey or cryptographic credential stored on a user’s device. In this case, MFA combines possession of the device or credential with the biometric factor.
Remote biometric verification serves a different purpose. Comparing a current facial capture with a portrait from a verified identity document or account record can help establish or reconfirm who the person is during onboarding, account recovery, or reverification. This type of identity check is not automatically an MFA factor and should not be confused with using biometrics to activate an authenticator.
The reliability of remote face verification depends on the quality of the reference image and the controls used during enrollment. Liveness detection can help identify photographs, masks, replayed videos, and other presentation attacks. Organizations should also protect the capture process against injection attacks and provide a secure recovery method for users who cannot complete the biometric check.

How can Regula help with MFA?

Regula supports identity verification and facial biometric checks that can complement an MFA system.
Regula Document Reader SDK can verify an identity document and extract its data and portrait during enrollment, account recovery, or reverification. Regula Face SDK can compare a current facial capture with a verified reference and perform liveness checks.
These capabilities can provide stronger identity evidence when an organization enrolls a user, restores access, or approves a sensitive account change.

FAQ

Are a password and a security question considered MFA?

No. Both are knowledge factors: they test information a person knows. MFA requires factors from at least two distinct categories, such as a password and a registered device. Adding more questions from the same category does not change that distinction.

Does a One-Time Password (OTP) automatically make a login multi-factor?

No. An OTP commonly acts as a possession factor because it demonstrates control of the authenticator or device that generates or receives it. It creates MFA when combined with a different factor, such as a password. Manually entered OTPs may still be intercepted or obtained through phishing, so they do not provide the same protection as phishing-resistant cryptographic authentication.

Is a face scan on its own MFA?

No. A facial biometric check by itself represents one factor. It can form part of MFA when combined with an independent factor, such as possession of a trusted device. The service also needs a reliable reference to determine whose face is being checked.

Can MFA prevent every account takeover?

No. MFA makes unauthorized access harder, but attackers may still steal authenticated sessions, exploit account-recovery procedures, compromise devices, or trick users into approving fraudulent requests. The level of protection depends on the authenticators selected and how they are enrolled, used, replaced, and recovered. Sensitive actions may require phishing-resistant authentication or additional identity verification.

Is MFA the same as Two-Factor Authentication (2FA)?

Two-factor authentication is a form of MFA that uses exactly two distinct factor types. MFA is the broader term and can require two or more factors. The terms are sometimes used interchangeably, but 2FA is technically a subset of MFA.

On our website, we use cookies to collect technical information. In particular, we process the IP address of your location to personalize the content of the site

Cookie Policy rules