Lion Cipher Lab

Read a vendor's SOC 2 Type II report like a risk reviewer: opinion, scope, CUECs, and the exceptions that matter

Why it matters

A vendor hands you a 60-page SOC 2 report, and the single most common thing that happens next is: someone skims the cover, sees the auditor's logo and the word 'unqualified,' files the PDF, and marks the vendor 'approved.' That is not a review -- it is a filing. A SOC 2 report is one of the richest risk documents a vendor will ever voluntarily give you, and almost all of its value lives in the parts people never read: which Trust Services Criteria are actually in scope (and whether they match what you need), whether the reporting period ended eight months ago (leaving a gap you own), which…

What you'll learn

Steps in this lab

  1. What a SOC 2 report actually is -- and what it is not
  2. Type I vs Type II -- a photo versus a movie (and why it changes your review)
  3. Read the opinion first -- unqualified, qualified, adverse, or disclaimer
  4. Read the scope -- which criteria, which system, and which period
  5. Find the subservice organizations -- carved-out means more work for you
  6. Extract the CUECs -- the controls the report assumes YOU perform
  7. Read Section 4 -- the tests of controls, exceptions, and management responses
  8. A clean SOC 2 is not a security guarantee -- the reviewer's mindset
  9. Write the one-page vendor SOC 2 review memo

Open the full interactive lab →