
SOC 2 Type II: What It Is, How the Audit Works and Why Customers Ask for It
SOC 2 Type II is an independent audit report that proves a service provider’s security controls do not just exist on paper — they actually worked, consistently, over a period of months. If you sell software, hosting, or any service that stores customer data, you have probably seen it on a procurement checklist: “Please provide your SOC 2 Type II report.” This guide explains what SOC 2 Type II means, how it differs from Type I, what auditors test, and how a company prepares for one.
What Is SOC 2?
SOC 2 (System and Organization Controls 2) is a reporting framework developed by the American Institute of CPAs (AICPA). It is built around five Trust Services Criteria:
- Security — the system is protected against unauthorised access, both physical and logical. This is the only mandatory criterion; every SOC 2 report covers it.
- Availability — the system is available for operation and use as agreed.
- Processing integrity — processing is complete, valid, accurate, timely and authorised.
- Confidentiality — information designated as confidential is protected as agreed.
- Privacy — personal information is collected, used, retained, disclosed and disposed of in line with commitments.
Unlike a certification such as ISO 27001, SOC 2 is not a pass/fail certificate. A licensed CPA firm audits the company and issues a report describing the controls, the tests performed and the results — including any exceptions. Customers then read that report and judge for themselves.
SOC 2 Type I vs SOC 2 Type II
| Feature | Type I | Type II |
|---|---|---|
| What it tests | Controls are suitably designed at a point in time | Controls operated effectively over a period (usually 3–12 months) |
| Evidence needed | Policies, diagrams and descriptions | Months of logs, tickets, reviews and records proving the controls ran |
| Time to obtain | Weeks | Months, including the observation period |
| What customers trust | Useful for early-stage vendors | Much stronger — it proves sustained operation |
| Typical use | First step, or a stopgap while Type II is in progress | The standard request in enterprise procurement |
The difference matters. A Type I report can be earned by a company that wrote good policies last month. A SOC 2 Type II report can only be earned by a company that followed them for months — which is why enterprise buyers insist on it.
How a SOC 2 Type II Audit Works
1. Scoping
The company and auditor agree which systems and criteria are in scope. A SaaS provider, for example, scopes in its production environment, customer data stores and the teams that run them, and picks the relevant criteria beyond mandatory security.
2. Readiness and gap assessment
Before the observation period starts, the company documents its controls and fixes gaps — missing access reviews, unencrypted backups, no incident-response plan. Starting the clock with known gaps wastes the whole period.
3. The observation period
Over typically 6–12 months, the company operates its controls and keeps evidence: access-review sign-offs, change tickets, vulnerability scan results, training records, incident logs. This discipline is the hardest part — much like preparing for an information security audit, the audit is won in the daily routine, not in the final week.
4. Testing
The auditor samples the evidence and tests each control: re-performing a sample of access reviews, inspecting configurations, interviewing staff, checking that exceptions were handled. Findings are recorded as exceptions in the report.
5. The report
The auditor issues one of two opinions: unqualified (controls operated effectively, aside from any disclosed exceptions) or qualified (material exceptions). The report is then shared under NDA with customers and prospects.
Practical Example: A Small SaaS Company Wins an Enterprise Deal
A 40-person SaaS company kept losing enterprise deals at the security questionnaire stage. It scoped a SOC 2 Type II audit around security, availability and confidentiality, spent two months fixing gaps — introducing quarterly access reviews, encrypting backups and formalising incident response — then ran a six-month observation period. The resulting unqualified report did not just satisfy the next enterprise customer’s checklist; the sales team could answer security questions with a single document instead of weeks of back-and-forth, and the discipline improved their own enterprise data security posture in the process.
Common SOC 2 Type II Pitfalls
- Starting the clock too early: beginning the observation period before controls are actually running produces a report full of exceptions.
- Evidence gaps: a control performed but not documented is, for audit purposes, a control not performed.
- Scope creep: adding systems mid-period that were not monitored from the start.
- Treating it as a one-off: SOC 2 is annual. Companies that relax after the report struggle the next year.
- Over-sharing: the full report contains sensitive detail, so it is shared under NDA — never posted publicly.
How to Prepare: A Short Checklist
- Pick your criteria and define the system boundary in writing.
- Document every control: owner, frequency, and what evidence it produces.
- Automate evidence collection where possible (access logs, scan reports, ticket exports).
- Run a readiness assessment at least a quarter before the observation period.
- Train staff on the controls they own — auditors interview people, not just documents.
- For smaller teams, the same discipline applies at a smaller scale; see our guide to cloud security for small business.
Frequently Asked Questions
What does SOC 2 Type II mean in simple terms?
It means an independent auditor has verified that a company’s security controls actually worked over a period of several months — not just that good policies were written.
How long does a SOC 2 Type II audit take?
The observation period is usually 6–12 months, plus preparation and audit fieldwork. A first-time Type II typically takes 9–15 months from decision to report.
Is SOC 2 Type II a certification?
No. It is an audit report with an auditor’s opinion, not a certificate. Companies are sometimes said to be “SOC 2 compliant” as shorthand, but the deliverable is the report itself.
What is the difference between SOC 2 and ISO 27001?
ISO 27001 is a certifiable management-system standard with a pass/fail certificate; SOC 2 is an attestation report describing controls and test results against the Trust Services Criteria. Many companies hold both.
Do small companies need SOC 2 Type II?
Only if customers demand it — but for B2B SaaS and cloud providers, enterprise customers increasingly do. Smaller firms often start with Type I, then progress to Type II once their controls are mature.



[…] similar principles. To understand how independent audits evidence security controls, read about SOC 2 Type II audits and why customers ask for them. Infrastructure choices also affect assessment outcomes, as explained in this overview of what data […]
[…] audit covers. To understand how audit reports evidence controls at service providers, read about SOC 2 Type II audits. And for a comparable government approval process, see this guide to the Certificate of […]
[…] response plan. For a broader view of how assurance programs are structured, see our guide to SOC 2 Type II, which covers a related but distinct framework for security […]
[…] ISO 27001 and SOC 2 are complementary, not competing. Many companies get both, because ISO 27001 shows they have a management system, and SOC 2 shows their controls operated effectively over a period. If you are choosing between them, ask your customers which one they require, and start with that one. For more on the US attestation route, see our guide to SOC 2 Type II Compliance: What It Is, Why It Matters, and How to Get Certified. […]