How to Read a SOC 2 Report in 30 Minutes — and the Gaps Most Firms Miss

At some point in every vendor diligence file there is a SOC 2 report: 80 pages of auditor prose that almost nobody reads, filed as proof that somebody did. A SOC 2 logo on a trust page does real work precisely because the report behind it so often goes unread. Here is how I work through one in half an hour, in the order that saves you the most time.

Minute 0–2: Type I or Type II?

Page one. A Type I report says the controls were designed sensibly on a single day. A Type II report says the controls operated over a period, usually six to twelve months. A vendor offering a Type I for a mature product is telling you something. Accept Type I from a young company once; ask when the Type II window closes.

Minute 2–5: The opinion, and the period

Find the auditor’s opinion letter. You are looking for two things: whether the opinion is unqualified (clean) or qualified (the auditor found something material enough to flag), and what period the report covers. A report whose period ended fourteen months ago is not current diligence; ask for the bridge letter covering the gap, which any serious vendor produces routinely.

Minute 5–10: Scope — where coverage quietly narrows

The system description defines what was audited. The two questions: which trust services criteria are in scope (Security is mandatory; Availability and Confidentiality are the ones an RIA usually cares about and the ones most often omitted), and which parts of the company are in scope. A report covering “the platform” may exclude the professional-services team that actually handles your data during onboarding. If the product you use isn’t named in the system description, the report may not cover it at all.

Minute 10–15: Subservice organizations — the dependency you inherit

Almost every vendor runs on someone else’s infrastructure. The report will treat those providers on a carve-out basis (their controls are excluded; the vendor relies on them) or an inclusive basis (rare). Carve-out is normal, but note who is carved out. Your vendor’s security now partially depends on a company you’ve never evaluated, and your diligence file should at least name that dependency.

Minute 15–25: Exceptions — read every one

The controls testing section lists each control and the result. Most rows say “no exceptions noted.” Read the ones that don’t. An exception like “for 3 of 25 terminated users sampled, access was not removed within the policy timeframe” is a finding about the exact risk you care about. Then check whether management’s response actually commits to remediation or just explains why it didn’t matter. A vendor’s posture toward its own exceptions tells you more than its marketing ever will.

Minute 25–30: CUECs — the homework they assigned you

Every SOC 2 lists complementary user entity controls: things the auditor assumed you do, like enforcing MFA on your accounts and deprovisioning your departed staff. The vendor’s clean opinion is conditional on your half of the bargain. Copy the CUEC list into your vendor file and confirm each one is actually true at your firm; this is the single most-skipped step in vendor diligence, and it converts the report from a filed PDF into an operating control.

Where this lands in your program

Reg S-P’s amended service-provider oversight expectations and Rule 206(4)-7’s risk coverage both assume your vendor diligence involves judgment, not collection. A SOC 2 on file demonstrates collection. A one-page memo noting the report type, period, scope gaps, exceptions, and CUEC confirmation demonstrates judgment, and takes exactly the thirty minutes described above.

BrainTrust members: the Vendor Due Diligence Questionnaire includes the SOC 2 follow-up questions, and the Vendor Contract Clause Rider carries the breach-notification and audit-rights language for when the report reveals gaps worth papering over.

The BrainTrust, free

This article is public. A free BrainTrust account opens every Insight, the 13 Sample Deliverables, the full Mock SEC Cyber Exam and the core compliance briefs. Name and email, no card.

Create Free Account →
Outside Testing

Want an outside test of your program? One-time engagements are available only to BrainTrust Premium members →