Contact Us Latest Security Reports → 中文
Blog / Technical Guide
TECHNICAL GUIDE

MFA & Identity Security: From OTP to Passwordless — A Complete Enterprise Strategy

Passwords are dead, but their successors are not equally secure. This guide breaks down MFA technology strengths, attacker bypass techniques, and how enterprises can choose the right authentication strategy to defend against modern threats.

Hexion Networks Security Research Team · 2025-08-18 · 7 min read
MFA STRENGTH SPECTRUM Lower Security Phishing-Resistant SMS OTP Usability: ★★★★★ Risk: SIM Swap Risk: SS7 Interception Risk: AiTM Phishing Bypassable TOTP APP Usability: ★★★★ Risk: AiTM Phishing Risk: MFA Fatigue Pro: No SIM risk Partially Bypassable PUSH NOTIFY (Number Match) Usability: ★★★★ Risk: MFA Fatigue Pro: Context display Pro: Number match Harder to Bypass HW SECURITY KEY Usability: ★★★ Pro: Phishing-resistant Pro: FIDO2 standard Cost: Higher Phishing-Resistant PASSKEY (FIDO2/WebAuthn) Usability: ★★★★★ Pro: Passwordless Pro: Phishing-resistant Pro: Biometric Highest Security

Microsoft telemetry shows that accounts with MFA enabled are 99.9% less likely to be compromised than those without. That number makes MFA look like a silver bullet — but attackers have long developed multiple techniques to bypass MFA, creating a critical gap between "has MFA" and "MFA actually works."

The core logic of authentication is combining at least two of three factors: something you know (password), something you have (phone/hardware key), and something you are (biometrics). But various implementations differ wildly in security strength — choosing the wrong MFA method may give your enterprise a false sense of security.

How Attackers Bypass MFA: Four Techniques You Need to Know

Understanding attack methods is the first step to choosing the right defensive tools:

  • ① AiTM (Adversary-in-the-Middle) Phishing

    Attackers set up a proxy phishing site that relays credentials and OTP codes to the real site in real time, stealing the authenticated session cookie. SMS OTP and TOTP apps cannot defend against this technique. Microsoft and Google accounts have been targeted at scale using this method.

  • ② MFA Fatigue Attack (Push Bombing)

    After obtaining a password, attackers repeatedly trigger push authentication notifications until the target approves out of frustration or confusion. The Uber breach in 2022 was executed via this technique. Enabling Number Match significantly reduces this risk.

  • ③ SIM Swapping

    Attackers use social engineering to convince a carrier to transfer the victim's phone number to an attacker-controlled SIM card, allowing them to receive all SMS OTPs. This is the fundamental weakness of SMS-based MFA, with documented cases in Taiwan as well.

  • ④ Social Engineering the MFA Reset Process

    Attackers impersonate IT support staff, tricking targets into completing "account verification" via phone or email, triggering an MFA reset and account takeover. Both Twilio and Cloudflare faced this attack in 2022 — Cloudflare successfully defended because they had deployed hardware security keys.

FIDO2 / Passkey: The Truly Phishing-Resistant Authentication Standard

The FIDO2 (Fast Identity Online 2.0) standard combined with the WebAuthn protocol provides the strongest phishing-resistant authentication available today. Its core principle is "domain binding" — the authentication process uses a cryptographic signature from the device that includes the legitimate domain. Even if an attacker creates a visually identical phishing site, authentication cannot be completed on the wrong domain.

Three Forms of Passkey
Platform Passkey

Stored in the device's secure chip (iPhone Face ID, Android fingerprint, Windows Hello) — free, convenient, and the future mainstream option.

Hardware Security Key

Physical USB/NFC devices like YubiKey — highest security, ideal for privileged accounts and high-risk scenarios.

Cross-Device

Use your phone to scan a QR code to confirm a desktop login — balances security and convenience without needing extra hardware.

Google Internal Case Study

After Google required all employees to use hardware security keys in 2017, account takeover incidents dropped to zero. Even when employees were tricked by phishing emails and entered their passwords on malicious sites, the hardware key's domain binding mechanism prevented any unauthorized logins.

Enterprise MFA Tiered Deployment Strategy

Not all accounts need the same level of protection. A risk-based tiered strategy is the pragmatic approach:

CRITICAL
Admins, domain controllers, cloud root accounts
Hardware security keys (FIDO2) + conditional access policies (managed devices only, specific IP ranges)
HIGH
Executives, Finance, HR, Developers
Passkey or hardware key preferred; TOTP app as backup; SMS OTP disabled
STANDARD
General employee accounts
Push notifications with Number Match enabled, or TOTP app; progressively migrate to Passkey
MFA FIDO2 Passkey Identity Security AiTM Attack Zero Trust
Need Expert Security Advice?

Contact Hexion Networks to assess your organization's identity security posture and plan the right MFA upgrade path.

Free Consultation
ALL ARTICLES View All →
Threat Report
2026 Cybersecurity Threat Trends Analysis
2026-01-15
Technical Guide
Zero Trust Architecture Implementation Roadmap
2025-12-10
Threat Analysis
Ransomware Defense Strategy 2026
2025-11-28
Compliance
SEMI E187 Semiconductor Security Compliance Guide
2025-11-05
Threat Analysis
Social Engineering Attacks: From Phishing to AI Deepfake
2025-10-20
Technical Guide
OT/ICS Industrial Security: Purdue Model to Zero Trust
2025-10-08
Technical Guide
Enterprise IoT Security Challenges & Defense
2025-09-15
Threat Analysis
Software Supply Chain Attacks: SolarWinds to XZ Utils
2025-09-02
Technical Guide
MFA & Identity Security: OTP to Passwordless
2025-08-18
Technical Guide
Cloud Security Misconfigurations: Prevention Guide
2025-08-05