Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Multi-factor authentication requires users to prove their identity with two or more independent factors, such as a password and a security key, before access is granted.

What Is Multi-Factor Authentication (MFA)?
Multi-factor authentication (MFA) is a login process that asks for two or more independent pieces of evidence before granting access. A password alone proves only that someone knows a secret, and secrets leak. Adding a second factor means that a stolen or guessed password is no longer enough on its own to break in.
Two-factor authentication (2FA) is simply MFA with exactly two factors, and it is by far the most common form. The terms are often used interchangeably.
Authentication factors fall into three categories:
The key word is independent. Two passwords are still one factor, because the same phishing page can capture both. Genuine MFA combines factors from different categories, so that compromising one does not automatically compromise the other.
Not all second factors offer the same protection.
MFA dramatically reduces account takeover, but it is not invulnerable. Attackers use adversary-in-the-middle phishing kits that relay credentials and codes to the real site in real time and steal the resulting session cookie. They bombard users with push prompts, call help desks pretending to be locked-out staff, and steal session tokens directly from compromised devices.
Gaps in coverage are just as dangerous. Legacy protocols such as IMAP or older Exchange authentication may not support MFA at all, leaving a back door that password spraying can exploit. Service accounts and break-glass accounts are frequently exempted and then forgotten.
A strong rollout starts with the accounts that matter most: administrators, remote access, email, and cloud consoles. Privileged access should always require phishing-resistant methods. From there, coverage should extend to every user and every application, ideally through a central identity provider and single sign-on so that policies are enforced consistently.
Other good practices include:
In a Zero Trust architecture, strong authentication is checked continuously rather than once at the perimeter. MFA becomes one signal among many, combined with device health, location, and behaviour, to decide whether each request should be allowed. This shift is why phishing-resistant MFA is now a baseline expectation in guidance from bodies such as the UK’s National Cyber Security Centre.
A rollout is only as good as its coverage. Track the percentage of users and applications enforcing MFA, the share of sign-ins using phishing-resistant methods, and the number of exemptions, each with a named owner and an expiry date. Review sign-in logs for accounts that still authenticate with a password alone. These figures are easy to report to the board and quickly show where the remaining gaps lie.
At Privia Security, we offer Multi-Factor Authentication (2FA) Solutions and test your identity controls for bypass weaknesses as part of our Penetration Test Services.
2FA uses exactly two factors, while MFA means two or more. In practice, most MFA deployments use exactly two factors, typically a password plus an app, key, or biometric, so the terms are often used interchangeably. What matters more than the number is that the factors are genuinely independent and that at least one of them resists phishing.
SMS codes are much safer than a password alone, but they are the weakest MFA option because messages can be intercepted through SIM swapping, malware on the phone, or weaknesses in mobile networks. Authenticator apps or FIDO2 security keys are recommended wherever possible, and SMS should be treated as a fallback rather than the default for staff accounts.
Phishing-resistant MFA, such as FIDO2 security keys, passkeys, and certificate-based smart cards, cryptographically binds the login to the genuine website’s domain. A fake site cannot obtain a valid response, even if the user is completely fooled and tries to sign in. This is why it defeats real-time relay phishing kits that easily capture SMS and app codes.
Interactive MFA is often impractical for service accounts because no person is present to approve a prompt. They should instead be protected with long random secrets or certificates, restricted sign-in locations, managed identities where your cloud platform offers them, the narrowest possible permissions, and close monitoring for any interactive or unusual sign-in activity.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.