Multi-factor authentication (MFA) has become one of cybersecurity’s most important controls. Roughly 70% of enterprise workforce users are now protected by it. But its success has created an unintended problem. Organizations increasingly treat successful authentication as proof of identity.
They assume that because someone passed MFA, they have verified who that person is. They may also assume that the identity itself has not been compromised.
Neither is it necessarily true.
Attackers increasingly target the processes surrounding authentication. These include enrollment, account recovery, help desks, device registration, and session management. An attacker may bind an authenticator to the wrong person or hijack an authenticated session. In either case, MFA may work exactly as designed while granting access to an impostor.
The question therefore needs to evolve from “Did this user pass MFA?” to “How confident are we that this is still the legitimate person behind the identity?”
Authentication Is Not Identity Verification
Authentication establishes that someone controls the authenticators associated with an account. Identity verification, or identity proofing, establishes whether that person corresponds to the claimed real-world identity.
The NIST Digital Identity Guidelines explicitly distinguish the two.
Suppose an attacker social-engineers a help desk into resetting an employee’s MFA and then enrolls a device under the attacker’s control. The next login may satisfy every authentication requirement. The credentials are correct, and the registered second factor is successfully completed.
The authentication succeeded. The identity assurance failed.
This is why identity verification matters during password resets, MFA re-enrollment, account recovery, device replacement, and privileged-access elevation. Weak verification at any of these points can turn MFA into part of the attacker’s infrastructure.
When the Attacker Passes MFA
Organizations often picture attackers outside the authentication boundary trying to break through it. Increasingly, that is the wrong model.
Attackers can use phishing, social engineering, SIM swapping, session theft and account recovery attacks to circumvent authentication controls. The uncomfortable reality is that the attacker may not fail authentication. The attacker may pass it.
Even phishing-resistant MFA does not eliminate every identity risk. Authentication still depends on how authenticators were originally bound to identities. It also depends on how they can be replaced and what happens during recovery.
An organization can deploy sophisticated authentication at the front door while leaving a side entrance less protected. An attacker may exploit weaker identity verification processes to reset those protections.
MFA Is Not Identity Threat Detection
There is another category error. Successful MFA does not necessarily mean an identity remains trustworthy.
Authentication establishes confidence at a point in time. Identity threat detection asks what is happening to and through that identity afterward.
An employee might legitimately authenticate at 8:02 a.m. The session could be hijacked minutes later. The compromised identity might then escalate privileges or access sensitive data the employee has never previously touched. The successful MFA event provides little assurance that this later activity is legitimate.
Identity risk is dynamic. A trustworthy identity at login can become compromised minutes later.
Three Different Questions
Organizations need to distinguish between three questions:
- Who is this person? Identity verification establishes confidence in the person behind the identity.
- Can this person demonstrate control of the required authenticators? Authentication answers this question. MFA is extremely valuable here.
- Is this identity continuing to behave legitimately? Identity threat detection uses signals and behavior over time to answer this question.
These are complementary controls, not substitutes.
Identity Confidence Should Have a Lifecycle
Confusing these functions creates significant blind spots. Organizations may assign excessive trust to MFA-authenticated sessions. At the same time, they may leave recovery processes weak or fail to detect compromise after login.
A better approach treats identity confidence as dynamic rather than binary.
At enrollment, organizations establish confidence that an identity belongs to a particular person. At authentication, they establish control of the required authenticators. After login, new risk signals should continue to inform confidence. These can include device changes, unusual access, privilege escalation, and recovery events.
High-risk interactions may require identity assurance to be established again. Examples include resetting credentials, enrolling a new authenticator, or granting administrative access. Identity confidence should therefore be established, authenticated, and monitored. When risk warrants it, that confidence should be re-established.
MFA Has a Job Description
None of this diminishes MFA’s importance. Strong, phishing-resistant authentication remains essential.
The problem begins when organizations ask MFA to answer questions it cannot.
MFA cannot determine whether an attacker manipulated account recovery. It cannot determine whether the person enrolling an authenticator was properly identity-proofed. It also cannot determine whether an authenticated session was subsequently hijacked.
And it cannot replace identity threat detection.
Identity verification establishes who you are. Authentication establishes control of the required authenticators. Identity threat detection determines whether that identity remains trustworthy over time.
MFA is critical to the second question.
Mistaking it for the answer to all three could leave organizations confidently authenticating the very attackers they are trying to keep out.
