RSA 2026Come see what your attackers already know→
GhostEye
PLATFORMCOMPANYRESOURCES
SCHEDULE DEMO

Find out who in your company is exposed.

PLATFORM

Overview

RESOURCES

BlogResearchEventsNewsProductGlossary

COMPANY

About
GhostEye
22 Vanderbilt Suite 7C
New York, NY 10017
founders@ghosteye.ai
Trust CenterHelp CenterSchedule DemoTerms of UsePrivacy Policy

© 2026 GhostEye, Inc. All rights reserved.

  1. ← Glossary
  2. /
  3. Multi-Factor Authentication (MFA)

Multi-Factor Authentication (MFA)

INFRASTRUCTURE
·4 min read·Updated Mar 2026

Multi-factor authentication (MFA) is a security mechanism that requires users to provide two or more verification factors - something they know (password), something they have (phone, security key), or something they are (biometrics) - before accessing a system or application..

What is Multi-Factor Authentication?

Multi-factor authentication (MFA) is a security mechanism that requires users to provide two or more verification factors - something they know (password), something they have (phone, security key), or something they are (biometrics) - before accessing a system or application.

Types of MFA

MethodMechanismStrengthsWeaknesses
**TOTP (Time-based One-Time Password)**Time-synchronized code generator (Google Authenticator, Authy)Not dependent on phone service or emailEasily bypassed by phishing, social engineering, or malware
**Push Notification**Mobile app approves/denies login attemptUser can detect unusual requests in real timeVulnerable to MFA fatigue attacks (prompt bombing)
**SMS (Text Message)**One-time code sent via textWidely supported, works on basic phonesVulnerable to SIM swapping, SMS interception, phishing
**FIDO2 Security Keys**Physical USB or NFC device (YubiKey, Titan)Phishing-resistant, cannot be remotely compromisedHigher cost, requires hardware, can be lost or forgotten
**Biometric**Fingerprint, face recognition, iris scanPhishing-resistant, cannot be sharedDevice-dependent, may fail in edge cases, privacy concerns

MFA Deployment Patterns

Organizations typically implement MFA in layers. Tier 1 (lowest sensitivity): No MFA or optional MFA. Tier 2 (moderate): TOTP or push notification required for email and VPN access. Tier 3 (high sensitivity): FIDO2 security keys required for admin panels and financial systems. Tier 4 (critical): Multi-factor approval required (two security keys or biometric plus hardware key). This tiered approach balances security with usability - not all access requires the same level of protection.

MFA Bypass Attacks

Attackers have developed sophisticated methods to bypass MFA. MFA fatigue (or prompt bombing) floods targets with push notifications until they approve one by mistake. SIM swapping involves contacting the carrier to transfer a victim's phone number to an attacker's device, allowing them to receive SMS codes and reset passwords. Social engineering targets help desk agents to disable MFA or reset credentials. Man-in-the-middle (MITM) attacks intercept credentials during the login process. Adversary-in-the-Middle (AitM) phishing tools harvest both credentials and MFA codes in real time.

Limitations of MFA

MFA is not a complete defense against account compromise. A study by CISA found that roughly 15% of enterprise MFA implementations could be bypassed. Limitations include: MFA only protects the login process, not post-authentication actions; once logged in, an attacker has full access to the account; MFA doesn't address social engineering of non-technical actions (wire transfers, data requests); and MFA implementation varies widely - weak implementations (SMS or TOTP without rate limiting) are vulnerable to attack. Users often disable or bypass MFA when it's inconvenient, and help desk pressure to reset MFA makes it a human vulnerability.

Why MFA Alone Isn't Enough

MFA significantly reduces credential-based attack risk, but it's not a complete defense. Attackers have developed techniques to bypass MFA, including MFA fatigue attacks (flooding the target with push notifications until they approve one), SIM swapping (taking over the target's phone number), and social engineering (convincing the target or help desk to disable MFA). Scattered Spider regularly bypasses MFA by calling help desks and requesting resets. Defense requires layering MFA with phishing-resistant authentication (FIDO2), social engineering simulations, and limiting help desk override capabilities.

On this pageWhat is Multi-Factor Authentication?Types of MFAMFA Deployment PatternsMFA Bypass AttacksLimitations of MFAWhy MFA Alone Isn't EnoughFAQ

Frequently Asked Questions

What's the most secure type of MFA?

FIDO2 security keys (like YubiKey) are phishing-resistant and cannot be remotely compromised. They're immune to SIM swapping, social engineering, and most known MFA bypass attacks. However, they cost more and can be lost or forgotten.

Can attackers bypass MFA?

Yes. Common bypass methods include MFA fatigue (flooding users with push notifications until they approve), SIM swapping (taking over the phone number), social engineering help desk agents to reset MFA, and intercepting TOTP or SMS codes. Phishing-resistant methods like FIDO2 are much harder to bypass.

Why do some organizations still use SMS for MFA?

SMS is cheap, widely supported, and requires no additional software. However, it's vulnerable to SIM swapping and interception. Organizations typically use SMS for non-critical systems while requiring FIDO2 or push notifications for sensitive access.

What should I do if an attacker has my MFA device?

Contact your organization immediately and disable all active sessions. Change your password from a different device. Most organizations can revoke MFA codes and force a re-authentication. If your FIDO2 key is lost, it cannot be used remotely to compromise your account - only to authenticate new logins if someone gains access to the system.

Related Terms
Zero TrustPhishingHelp Desk VishingCredential StuffingAccess Control