Read a SOC 2 report in this order: who issued it, what system and period it covers, what the opinion says, what exceptions were found, which subservice organizations were carved out, and which controls the vendor expects you to operate. A clean opinion on the wrong scope tells you little.
Key takeaways
- A SOC 2 report is not pass or fail. It is an opinion with detail that you are expected to evaluate.
- Check scope before anything else. The product you buy must be inside the system described.
- Complementary user entity controls are your responsibility. If you do not perform them, the vendor’s controls may not protect you.
The sections of the report
| Section | What it is | What to look for |
|---|---|---|
| I. Independent service auditor’s report | The opinion | Issuer, type, period, categories, opinion wording |
| II. Management’s assertion | Management’s claim | Consistency with the opinion |
| III. Description of the system | Services, infrastructure, people, data, boundaries | Whether your product and region are in scope |
| IV. Criteria, controls, tests and results | The detail (Type 2) | Exceptions and management’s responses |
| V. Other information | Unaudited | Useful context, but not covered by the opinion |
A reviewer’s checklist
- Issuer. Is it a licensed CPA firm? See who can perform a SOC 2 audit.
- Type and period. Type 2 over a recent period is the stronger evidence. How old is the period end? Ask for a bridge letter if there is a gap.
- Categories. Security only, or others such as Availability? Do they match what you rely on?
- Scope. Does the description name the service, environments and locations you use?
- Opinion. Unmodified, or qualified? Read the basis paragraph if qualified. See qualified vs unqualified opinions.
- Exceptions. How many, in which areas, and what did management do about them? One late access removal differs from repeated failures in change approval.
- Subservice organizations. Which providers are carved out, and have you seen their reports? See subservice organizations.
- CUECs. List them and confirm someone on your side owns each. See CUECs and CSOCs explained.
What a report cannot tell you
It does not cover features outside the described system, events after the period, or whether the vendor meets a law such as HIPAA or GDPR. It reports on controls, not on the absence of vulnerabilities.
Frequently asked questions
Do I need an NDA to get a vendor’s report?
Usually yes. See are SOC 2 reports public.
Is a Type 1 report acceptable?
For a new vendor it can be a reasonable start, with a commitment to a Type 2.
Should I keep a record of my review?
Yes. Your own auditors may ask for it. See vendor management for SOC 2.
Sources & further reading
AICPA SOC 2 Guide; DC section 200, Description Criteria.
Related: What is SOC 2 Type 2, Glossary.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm enrolled in the AICPA Peer Review Program. See our published SOC 2 fees or book a scoping call.