Multi-Factor Authentication (MFA) is an access control that requires users to present two or more proofs of identity before gaining access. SOC 2 considers MFA a baseline control for any system holding sensitive data or production access. Audits expect MFA to be enforced on identity providers, administrative access to production systems, source control, cloud consoles, and any other sensitive applications. Modern MFA implementations favor phishing-resistant methods like hardware security keys or platform authenticators over SMS-based codes, which can be intercepted through SIM-swap attacks. Auditors test MFA by sampling user accounts, verifying MFA is enabled and required, reviewing authentication logs for any non-MFA logins to in-scope systems, and examining exception processes for accounts where MFA is not technically possible. MFA gaps are a common cause of breaches and a frequent finding in SOC 2 exception reports.
Multi-Factor Authentication (MFA)
Controls & Security · Last updated 2026-10-12
Related terms
Read more
- Guide: The Complete Guide to SOC 2 Compliance
- Guide: SOC 2 Compliance Checklist for Small Teams: What to Do First and What Auditors Actually Fail
- Compare: Vanta
- Compare: Drata
- Blog: SOC 2 Evidence Collection: What No One Tells You About the 12-Month Grind
- Blog: Your AI Agents Should Be Collecting Your SOC 2 Evidence