The Situation

Every user has MFA. The audit passed. Then a finance manager clicks a link to a fake Microsoft 365 login page, types her password, and approves the push notification on her phone because it looks normal. The phishing kit relays both to the real login page and captures her session. The attacker is in, and MFA did exactly what it was told.

This is adversary-in-the-middle (AiTM) phishing. It's why "MFA is on" and "MFA is phishing-resistant" are two different statements.

What's Really Going On

Most MFA asks the user to prove something: type a code, tap approve. A person can be tricked into doing that on a fake site. Phishing-resistant methods take the user out of that decision. The credential is cryptographically tied to the real website's domain, so it simply won't work on a look-alike page.

CISA's 2022 fact sheet "Implementing Phishing-Resistant MFA" calls phishing-resistant MFA the gold standard. It names two forms: FIDO/WebAuthn authenticators and PKI-based methods such as smart cards. It treats app push, one-time codes and SMS as weaker options.

In practice, that means:

  • Passkeys (FIDO2 credentials stored on a phone, laptop or password manager)
  • FIDO2 security keys (hardware keys such as YubiKeys)
  • Windows Hello for Business and similar platform credentials
  • Certificate-based authentication with smart cards

Both major identity platforms support this now. Microsoft Entra ID has a built-in "Phishing-resistant MFA" authentication strength you can require in Conditional Access. In Okta Identity Engine, Okta FastPass and passkeys (FIDO2 WebAuthn) are the phishing-resistant authenticators, and you can require them in app sign-in policies.

One detail worth knowing: passkeys come in two kinds. Device-bound passkeys stay on one device or security key. Synced passkeys copy across a user's devices through Apple, Google or a password manager. Synced passkeys are easier for users. Device-bound passkeys give you more control. Entra ID now lets admins allow one type or both, by group, through passkey profiles.

Where Teams Go Wrong

Turning on enforcement before enrollment. If you require phishing-resistant MFA before people have registered a passkey, they get locked out. Enroll first, enforce later.

Leaving the old methods in place. If SMS or push is still allowed as a fallback, an attacker will just pick the weaker option. The goal is to remove those methods for protected groups, not just add a new one.

Forgetting recovery. Lost phones and new laptops are the help desk's biggest risk. If recovery means "call us and we'll reset your MFA," your attacker can call too.

Ignoring legacy apps. Older apps that use basic authentication, LDAP or their own logins can't use passkeys. They need to sit behind your identity provider or be listed as known exceptions.

A Staged Rollout: Six Steps

1. Start With the People Attackers Want Most

Admins first, then executives, finance, HR and IT support. These groups are small, high-value and usually willing to accept a little friction. Give admins hardware security keys, with two keys each.

2. Inventory Your Sign-In Paths

List how people actually sign in: browsers, Office desktop apps, mobile apps, VPN, VDI and shared devices. Test passkeys on each one before the rollout, not after.

3. Make Enrollment Easy

Use a registration campaign or a guided first sign-in. In Entra ID, a Temporary Access Pass lets new or recovering users register a passkey without falling back on SMS. Write a one-page guide with screenshots.

4. Fix Recovery Before You Need It

Define how a user proves who they are when their device is gone: video call with ID check, manager confirmation, or an in-person visit. Train the help desk to never reset MFA based on a phone call alone.

5. Enforce in Rings

Require phishing-resistant MFA through Conditional Access or Okta policy for the first group. Watch sign-in logs for failures for two weeks. Then expand group by group.

6. Remove the Weak Methods

Once a group is enforced, disable SMS, voice and plain push for that group. Keep a small, monitored break-glass account setup with security keys stored safely.

Choosing Methods by User Type

User group Good fit Why
Global and privileged admins Hardware FIDO2 keys (two per person) Device-bound, hard to copy, easy to audit
Knowledge workers on managed laptops Windows Hello for Business or platform passkeys No extra hardware, smooth daily sign-in
Mobile-heavy staff Passkeys on the phone (or Okta FastPass) Works where they already work
Shared or kiosk devices Security keys or smart cards No personal phone needed
Contractors Passkeys with a time-limited policy Avoids issuing hardware to short-term users

What to Do Next

Pull your sign-in logs and count how many users still rely on SMS or push. Then pick your admin group and get them on security keys this month. It's the smallest group with the biggest payoff, and it will show you where the rollout will snag before you reach everyone else.


Want a second set of eyes on your setup? Stackcurve advisors help IT leaders review their security stack and compare options at no cost to you. Talk to an advisor → or get your free Cyber-Ready Score →


← Back to Blog

Stackcurve is independent. No vendor pays for placement or editorial influence on this blog.