A SOC 2 report is an independent auditor's examination of a service organisation's controls against the AICPA Trust Services Criteria. A Type II report tests whether controls operated over a period, and is the most common evidence vendors send.
Who it applies to
Service organisations that hold or process customer data, most often SaaS and cloud providers. It is voluntary, but customers and their regulators widely expect it.
Key dates
- 2017Trust Services Criteria published
- 2022Points of focus revised
- Every 12 monthsTypical cycle for a Type II report
What SOC 2 asks of third-party risk management
Control environment, communication, risk assessment, monitoring, control activities, logical and physical access, system operations, change management and risk mitigation, including vendor management (CC9.2). Always in scope.
Capacity, backup, recovery and recovery testing. Optional.
Identifying, protecting and disposing of confidential information. Optional.
Complete, valid, accurate and timely processing. Optional.
Notice, choice, collection, use, access, disclosure, quality and monitoring of personal information. Optional.
Documents to request from vendors
- SOC 2 Type II report for the service you buy
- Bridge letter if the period ended more than three months ago
- Reports for carved-out subservice organisations
- The list of complementary user entity controls, mapped to your team
- Management responses to any exceptions
In ProcureCortex
ProcureCortex reads the whole SOC 2 report: period, opinion, scope, subservice organisations, user entity controls and every exception in section 4. Each finding cites the page, and a stale period or a carved-out host becomes a finding automatically.
How an assessment worksSources
- AICPA: SOC 2 for service organizationswww.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2
Summarised for practitioners, not legal advice. Check the source text for your own obligations.