What a SOC 2 Report Actually Is
Lesson 1: What a SOC 2 Report Actually Is
An enterprise prospect sends over a 200-row security questionnaire, then asks the only question their security team really cares about: “Can you send your SOC 2?” What arrives is not a certificate, not a badge, and not a score. It is a CPA's written opinion on a PDF that your company wrote about itself.
That sentence is the whole course in miniature. SOC 2 (properly SOC 2®, a registered AICPA trademark) is an attestation report, produced under AICPA attestation standards by an independent licensed CPA firm, examining whether a service organization's controls were suitably designed and operating effectively against the AICPA Trust Services Criteria. Understanding the words “attestation”, “described”, and “operating effectively” is what separates people who pass cleanly from people who spend nine months and six figures learning the hard way.
The SOC family: pick the right report
AICPA's SOC suite grew out of the old SAS 70 report, which was retired when SSAE 16 (now SSAE 18) replaced it around 2011. Today the family looks like this:
| Report | What it covers | Who reads it |
|---|---|---|
| SOC 1 | Controls at a service organization relevant to user entities' internal control over financial reporting (ICFR). Payroll processors, claims processors, fund administrators, payment rails. | Your customers' CFO and their financial-statement auditors. |
| SOC 2 | Controls relevant to security, availability, processing integrity, confidentiality, and privacy — the Trust Services Criteria. The general-purpose “is your shop secure” report. | Customers' security and procurement teams, under NDA. |
| SOC 3 | Same criteria as SOC 2, but a short public-facing seal-style report with no control detail and no test results. | Anyone. Marketing-friendly, evidentiary-light. |
| SOC for Cybersecurity | An entity's entire cybersecurity risk-management program (not a service system). | Boards, insurers, regulators. |
| SOC for Supply Chain | Controls in a production, manufacturing or distribution system. | Manufacturers and their customers. |
Most SaaS companies need SOC 2 and nothing else. If you touch money movement or financial statement numbers, expect SOC 1 to be requested too — often by the customer's auditors rather than the customer.
Type I vs Type II: the distinction that defines the project
Both SOC 1 and SOC 2 come in two flavors, and the difference is not cosmetic:
| Type I | Type II | |
|---|---|---|
| Question answered | Were the controls suitably designed as of a single date? | Were they designed and did they operate effectively throughout a period? |
| Coverage | Point in time (e.g. “as of 30 September”) | A window, typically 3–12 months |
| Effort | Weeks; mostly documentation | Fieldwork plus a full period of accumulating evidence |
| Evidence risk | Low | High — you cannot retroactively create evidence |
| Market perception | “They've documented something.” | The default expectation of enterprise buyers. |
Type I is a bridge, not a destination. It is genuinely useful when a deal closes in six weeks and the buyer will accept design assurance, but plenty of buyers now reject Type I outright, so an increasing number of companies skip straight to Type II. The trap: a Type I report gives you false comfort about the hard part, which is consistency over time.
Who is actually grading you
The engagement is performed by a licensed CPA firm under SSAE 18, with AT-C section 320 covering service-organization examinations. Three consequences follow from that, and they explain most of the friction people experience:
- The auditor attests; management asserts. You write the system description and the assertion (“we designed and operated these controls”). The CPA tests and opines. Every weak sentence in your description becomes a finding, because the auditor is opining on whether your description is fairly presented as well as whether the controls worked.
- Criteria are outcomes, not a checklist. The AICPA publishes criteria and “points of focus” — examples of how you might meet them — but never mandates a specific control. Your auditor judges suitability. This is why two companies with identical stacks produce different reports.
- The report is restricted-use. It is written for entities with “sufficient understanding” of the system, distributed under NDA, and it carries a date. A 14-month-old report is a negotiating liability, which is what bridge letters exist to paper over.
What changed in October 2026
Two AICPA developments matter if you are starting now rather than reading a 2019 blog post:
Proposed 2027 Trust Services Criteria (exposure draft, 26 October 2026). The AICPA's Assurance Services Executive Committee released proposed revisions to both the TSC and the Description Criteria, aimed at “relevance, clarity, and usability” in a changed technology and third-party risk landscape, including a redlined version for comparison. While these are drafts out for comment, not effective standards, they signal direction — and any program you build in 2026 should not be architected around soon-to-be-revised language. Build to the principles, not to a point of focus's exact wording.
Joint SOC 2 + AIUC-1 offering (19 October 2026). The AICPA partnered with the Artificial Intelligence Underwriting Company to deliver a single CPA-led engagement combining a SOC 2 report with AIUC-1, a certification for AI agent safety, security and reliability. The distinguishing feature is live adversarial testing of agent behaviour — hallucinations, data leakage, manipulative requests, prompt injection — rather than a policy review. Full launch was expected in early 2027, with multiple CPA firms already delivering engagements. Both SOC 2 and AIUC-1 renew annually; AIUC-1 additionally requires quarterly technical retesting. If you ship AI agents to enterprises, this is the shape your buyers' questions are heading toward.
🧠 Knowledge Check
1. A prospect asks for your SOC 2. What is the deliverable?
2. Which statement about Type I versus Type II is correct?
3. Which report would a customer's financial-statement auditors most likely request from a payroll processor?