Does SOC 2 require MFA?
Effectively yes, though not by name. SOC 2's Trust Services Criteria require strong logical access controls without naming MFA, but auditors and customers treat multi-factor authentication as the baseline, so nearly every SOC 2 program enables it.
The full answer
SOC 2 does not contain a rule that spells out 'multi-factor authentication.' It is built on the AICPA's Trust Services Criteria, which require you to restrict logical access to authorized users and protect credentials. MFA is the most widely accepted way to meet that objective, so while it is not named, it is functionally the expected control.
In real audits, missing MFA is one of the fastest ways to draw an exception. Auditors expect it on anything that guards sensitive systems — identity providers, email, cloud consoles, production infrastructure, VPNs, and admin accounts. Enterprise customers reviewing your report also look for it, so weak authentication can hurt sales as much as your audit.
Scope and consistency matter more than the specific factor. Auditors want to see MFA enforced across in-scope systems rather than enabled for a few users, and they will note privileged accounts that lack it. Document where MFA is required and why any narrow exceptions exist.
Evidence is easy to produce. GRC platforms such as Vanta, Drata, and Secureframe continuously check MFA settings against your identity provider, and auditors with confirmed integrations pull that configuration directly. For a Type 2, which covers an observation window of three to twelve months, enforce MFA before the window opens so it holds across the whole period.
Go deeper
Short answer not enough? These pages cover the full picture:
Get matched with the right auditor
Answer a few questions about your scope and see transparent, comparable pricing from vetted audit firms — no sales calls.
Get instant pricing →Talk to auditors who handle this every week
Every firm on AuditNex is listed on identical terms — placement cannot be bought, and credentials are independently checked.
Related questions
Can a two-person startup get SOC 2?
Yes. SOC 2 has no minimum headcount; a two-person startup can earn a report. Controls simply scale to your size — the auditor assesses whether your controls fit your operations, not whether you have a large team.
Do I need a penetration test for SOC 2?
Not strictly. The AICPA's SOC 2 framework never names a penetration test as a required control, but most auditors and enterprise buyers expect one as evidence of vulnerability management, so in practice it is nearly standard.
Does SOC 2 cover remote work and BYOD?
Yes. SOC 2's Security criteria apply wherever your team works, so remote work and BYOD fall in scope. Auditors expect controls like endpoint protection, encryption, MDM or access policies, and secure authentication regardless of device location.
Does SOC 2 require a vendor management program?
Yes, in practice. SOC 2's Common Criteria include managing risks from vendors and subservice organizations, so auditors expect a vendor management process — inventory, risk-based due diligence, and monitoring — even though no single rule dictates its exact form.
Does SOC 2 require annual security training?
Not by a named rule. SOC 2's Trust Services Criteria require security awareness training but never specify a frequency; auditors and customers treat training at onboarding plus at least annually as the standard, so most companies run it yearly.
Does SOC 2 require background checks?
Not by name. SOC 2's Trust Services Criteria expect you to hire and retain trustworthy personnel but never mandate background checks specifically; auditors treat pre-employment screening as the standard way to evidence that control, so most companies run them.
Sources: AICPA Trust Services Criteria (2017, rev. 2022); AICPA SSAE No. 18 attestation standards. Answer written and maintained by the AuditNex research team; last reviewed July 26, 2026. AuditNex is a marketplace — accredited firms price and scope engagements independently.