How it typically works?
- User login: the user enters their standard username and password.
- Second factor request: the system prompts for another verification factor such as a one-time code.
- Verification: the system validates the second factor, confirming the user’s identity.
- Access granted: only after all factors are validated is access provided.
Common techniques
- SMS codes: one-time codes sent by text message. Convenient but vulnerable to SIM swapping.
- Authenticator apps: mobile apps like Google Authenticator or Microsoft Authenticator generate rotating codes.
- Push notifications: apps that require the user to approve or deny login attempts in real time.
- Hardware tokens: physical devices such as YubiKeys or smart cards that generate or store secure codes.
- Biometric factors: fingerprint, facial recognition, or iris scanning as additional layers of assurance.
- Adaptive MFA: systems that adjust the required factor depending on risk context, such as unusual location or device.
Impact
MFA significantly reduces the risk of unauthorized access. Industry reports indicate that MFA can block the vast majority of automated credential-based attacks. For organizations, deploying MFA is often the single most effective step in improving security posture.
However, implementation challenges exist. Users may find MFA inconvenient, and poorly designed systems can create login fatigue. Attackers are also adapting with MFA fatigue attacks, where they flood users with repeated push requests until approval is mistakenly granted. Despite these issues, MFA remains a core element of Zero Trust strategies and compliance requirements.