A SOC 2 report is written by an independent auditor about the controls at a service organization. If you are reviewing a vendor's report, it can be long and dense. This guide explains the usual sections, what to look for, and what questions to ask. Report layouts vary by audit firm, so treat this as a common pattern, not a standard.
For the basics, see SOC 2 Type 1 vs Type 2 and the Trust Services Criteria.
The Usual Sections
| Section | What it tells you |
|---|---|
| Management's assertion | What management states about the system and controls, see management assertion |
| Independent auditor's report | The auditor's opinion on the description and the controls |
| System description | Services, infrastructure, people, data, and boundaries, see system description |
| Criteria and controls | Which controls map to which criteria |
| Tests and results | What the auditor tested and what was found (Type 2 reports) |
| Other information | Optional management responses or extra context |
Start With the Opinion
The auditor's opinion states whether the description is fairly presented and the controls were designed, and for Type 2, operated effectively. A qualified opinion means the auditor found an issue serious enough to limit the conclusion. Read the basis for the qualification closely.
Check the Scope and Period
- Confirm the report covers the service you actually use
- Check which Trust Services Criteria categories are included
- Review the audit period and how recent it is
- Ask for a bridge letter if there is a gap since the period ended
Review Tests and Exceptions
In a Type 2 report, test results show how the auditor checked each control. Look for noted control deviations and management's response. An exception does not automatically mean a vendor is unsuitable. Consider what the control does and whether it affects your data.
Look at Subservice Organizations and User Controls
- Find any subservice organizations and whether they are carved out or included
- Read the complementary user entity controls, which are controls you are expected to run on your side
- Map each one to an owner in your company
Common Mistakes
- Reading only the cover page or the opinion
- Ignoring the period dates or the system scope
- Skipping the user entity controls
- Filing the report without recording who reviewed it and what was concluded
Review Checklist
- Report type and period noted
- Opinion type recorded
- In-scope services match your use
- Exceptions reviewed with a written conclusion
- User entity controls assigned to owners
- Follow-ups sent to the vendor
How AuditFlo.co Helps
AuditFlo.co helps teams keep audit-period evidence collection records, which can include records of vendor reviews you perform. It does not interpret a report for you, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors. See also vendor management for SOC 2.
Sources
- AICPA, SOC 2 Reporting on an Examination of Controls at a Service Organization, Guide
- AICPA, Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy