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.
The full answer
SOC 2 does expect security awareness training, but the requirement is outcome-based. The AICPA's Trust Services Criteria call for personnel to understand their security responsibilities; they do not state 'annual' or set a specific curriculum. So there is no formal annual mandate — just a control you must show is operating.
The market convention fills the gap. Auditors generally expect training when someone is hired and then on a recurring cadence, and annually is the frequency almost everyone lands on because it is easy to evidence and matches customer expectations. Some regulated environments push for more frequent refreshers or role-specific training for engineers and privileged users.
What auditors actually sample is evidence that training happened. Expect to provide completion records, dates, the content or provider used, and coverage showing every in-scope employee finished it during the period. For a Type 2 report, which covers an observation window of three to twelve months, gaps in completion across that window are a common finding.
Make it easy to prove. GRC platforms such as Vanta, Drata, and Secureframe track training completion automatically and flag anyone overdue, and auditors with confirmed integrations pull those records directly. Set a yearly cadence, enroll new hires at onboarding, and keep the completion logs so the control is easy to attest.
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 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.