SOC 2 exists because companies hand their data to other companies. A bank uses a payroll SaaS, a hospital uses a scheduling tool, a retailer uses a cloud analytics product. Each customer wants to know the service is run securely, and they cannot all audit it themselves. So the service company hires one CPA firm to examine it once, and shares that report with everyone.
What it covers
The report is measured against the Trust Services Criteria. There are five categories:
- Security (the Common Criteria, CC1 to CC9). Always included.
- Availability, Confidentiality, Processing Integrity and Privacy. Optional, added when they matter to customers.
Most first reports cover Security only.
Type I and Type II
- Type I checks the controls are designed properly at one point in time.
- Type II checks they actually operated over a period, usually 3 to 12 months. This is the one customers really want.
Who needs it
SaaS, cloud and service companies selling to businesses, especially in the US. It usually appears as a line in a security questionnaire or contract: "Please provide your most recent SOC 2 Type II report." Without it, deals stall.
What is changing
In October 2026 the AICPA published an exposure draft of updated criteria. If adopted, they would apply to examinations starting on or after 31 December 2027. Until then, reports use the 2017 criteria.
SOC 2 is not a certificate. It is a CPA's report on your controls, read by your customers.
1. Who issues a SOC 2 report?
2. Which SOC 2 category is always included?
3. A customer wants proof controls worked across the year. Which report?