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.
The full answer
There is no SOC 2 control that literally says 'run a background check.' The framework's Trust Services Criteria, published by the AICPA, expect organizations to hire competent, trustworthy people and to define personnel security responsibilities. Background screening is how most companies demonstrate they take that seriously, not a separately mandated rule.
Because of that, auditors commonly look for pre-employment background checks as evidence for the hiring and personnel controls. What counts as reasonable varies by role and jurisdiction — criminal and identity checks are typical, and some employers add credit or education verification for sensitive positions. The point is a consistent, documented process rather than a specific check.
Watch the edges. Background-check laws differ by country and state, so you scope screening to what is lawful where you hire; contractors and offshore staff often need an equivalent process. Auditors generally accept a documented policy plus proof it was applied to the people in scope during the period.
Evidence is straightforward: your HR or personnel security policy, plus records showing checks were completed for employees hired in the audit window. For a Type 2 report, which covers an observation window of three to twelve months, expect the auditor to sample new hires from that period, so keep completion records organized as you onboard.
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 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.
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.
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.