Why Your Current Multi-Factor Authentication is Failing Against Modern Adversary-in-the-Middle Attacks
Standard push notifications and SMS codes are no longer enough to stop sophisticated phishing kits. Learn why phishing-resistant MFA is the only viable path forward for modern enterprise defense.

The Illusion of MFA Security
For years, security leaders treated Multi-Factor Authentication (MFA) as the ultimate silver bullet against credential theft. We told our boards that if we turned on MFA, we were safe from 99% of bulk attacks. That era is over. The rise of sophisticated Adversary-in-the-Middle (AiTM) phishing kits like Evilginx, Muraena, and Modlishka has commoditized the bypass of standard MFA.
Traditional MFA methods—SMS codes, voice calls, and simple push notifications—rely on shared secrets or one-time codes that are easily intercepted. In an AiTM attack, the victim lands on a proxy page that looks identical to the legitimate login portal. When the user enters their credentials and MFA code, the attacker captures them in real-time, along with the session cookie. The attacker then injects that cookie into their own browser, bypassing the authentication flow entirely.
The Definition of Phishing-Resistant MFA
To be truly "phishing-resistant," the authentication mechanism must cryptographically bind the user's session to the specific origin (URL) they are logging into. Currently, there are only two widely recognized standards that achieve this: FIDO2/WebAuthn (security keys and Passkeys) and Certificate-Based Authentication (CBA), typically via PIV/CAC cards.
FIDO2 works because the private key never leaves the hardware device (or the TPM of a laptop). During authentication, the browser sends the website's origin to the authenticator. If the origin doesn't match the one stored during registration, the authenticator refuses to sign the challenge. This makes it mathematically impossible for a proxy site to trick the user into authenticating to the wrong server.
Implementation Reality: The Push-to-FIDO Migration
Transitioning an entire workforce to phishing-resistant MFA is a logistical hurdle, but it is no longer optional. The approach should be tiered based on user risk and technical capability.
1. Identify Your High-Value Targets
Start with administrators (Global Admins, AWS Root users, DevOps engineers) and users with access to sensitive financial or PII data. These users should be issued physical hardware keys (e.g., YubiKeys) immediately. If a physical key is lost, the fallback must not be a vulnerable SMS code; it should be a highly vetted manual identity verification process or a pre-provisioned backup key.
2. Leverage Platform Authenticators (Passkeys)
For the general workforce, physical keys might be cost-prohibitive. This is where Passkeys (FIDO2 credentials stored in the OS or browser) come in. Modern Windows (Windows Hello), macOS/iOS (iCloud Keychain), and Android devices support these natively. By leveraging the hardware already in your users' pockets and on their desks, you can achieve phishing resistance without the overhead of shipping hardware.
3. Disable the Weakest Links
The most critical step in a rollout is the removal of legacy options. Attackers will always target the weakest link. If your policy allows a user to choose between a FIDO2 key and an SMS code, the attacker will simply trigger the SMS flow. Once FIDO2 is enrolled, you must explicitly disable SMS, Voice, and basic Push as valid factors for those accounts.
Handling Technical Debt and Legacy Apps
Not every application supports WebAuthn. Legacy on-premises apps or older SaaS products may only understand SAML or OIDC without supporting modern extensions. In these cases, the resistance must happen at the Identity Provider (IdP) level. Ensure your IdP (Okta, Entra ID, Duo) is configured to require a phishing-resistant factor for the initial session establishment.
If an application is so old it doesn't support modern federation, it should be placed behind an identity-aware proxy (IAP) that enforces phishing-resistant MFA before granting access to the network segment.
The Strategic Shift
Security operators must stop viewing MFA as a checkbox. We are in an arms race where the cost of attacking traditional MFA has dropped to nearly zero. The move to phishing-resistant MFA is a move from "something you know and something you have" to "something you have and a cryptographic proof of where you are using it." Without that proof of origin, your MFA is just a speed bump, not a barrier.