Quick answer
SOC 2 is an independent CPA report on a service organization's controls, measured against the AICPA Trust Services Criteria. A Type II report covers whether those controls operated effectively over a stated period; Type I covers a single date. It is a report, not a certification.
What SOC 2 and SOC 2 Type II mean
SOC 2 (System and Organization Controls 2) is a report, written by an independent licensed CPA firm, on the controls a service organization uses to protect the systems and data it runs for customers. The criteria come from the American Institute of CPAs (AICPA) and are called the Trust Services Criteria. A Type II report goes one step further than a Type I: it says whether those controls actually operated effectively over a stated period, not just whether they existed on one day.
Two points matter before anything else:
- It is a report, not a certificate. No body "certifies" a company as SOC 2. A CPA firm issues an opinion, and the company may share the report with customers, usually under a non-disclosure agreement. Be careful with a vendor page that says "SOC 2 certified"; the useful question is "can I read the report?"
- It is not a law and not a guarantee. The company chooses which categories are in scope and writes the description of its own system. The auditor tests what is described. The report tells you what was tested and what was found, and nothing more.
This page is a plain explanation, not legal or audit advice. It makes no claim about any specific company's audit status.
Type I vs Type II
| Type I | Type II | |
|---|---|---|
| What the auditor opines on | Whether controls are suitably designed and in place | Whether controls are suitably designed and operated effectively |
| Time covered | One specified date | A specified period |
| Evidence | Documents, configuration, walkthroughs | Samples taken across the period: tickets, logs, access reviews |
| What it tells a buyer | The company has set up controls | The company ran those controls consistently |
| Usual use | A first report, or a stopgap | What procurement and security teams ask for |
The AICPA does not set one required length for the Type II period; the company and auditor agree it, and it is stated in the report. Read the dates rather than assuming.
The five Trust Services Categories
| Category | What it covers | Example control |
|---|---|---|
| Security | Protection against unauthorized access and damage | Access is removed within a set time after someone leaves |
| Availability | The system is up and usable as committed | Backups are tested and restores are timed |
| Processing integrity | Processing is complete, valid, accurate and timely | Failed jobs raise an alert and are reviewed |
| Confidentiality | Information designated confidential is protected | Data is encrypted and retention is enforced |
| Privacy | Personal information is collected, used, kept and disposed of as committed | Deletion requests are handled and logged |
In practice Security is included in every SOC 2 report, and the company adds any of the other four that matter to its customers. A report that covers only Security says nothing about availability or privacy, so check which categories are in scope before you rely on it.
How to read a SOC 2 Type II report
Most reports follow the same structure. Read in this order:
- The auditor's opinion. An unqualified (clean) opinion means the controls were fairly described and effective. A qualified opinion means there was a significant problem; find the paragraph that explains why.
- Period and scope. Confirm the period dates, the categories in scope, and which products or services the report covers. A report on a back-office system does not cover the product you buy.
- The system description. Management's own account of the services, infrastructure, people, software and data flows.
- Controls, tests and results. The longest part. For each control, the auditor lists the test and any exception. Exceptions are not automatic failures; look at how many there were and what management said.
- Subservice organizations. If the company relies on a cloud host, the report either includes that provider's controls ("inclusive") or leaves them out and lists them ("carve-out"). With a carve-out you need that provider's report too.
- Complementary user entity controls. Things the customer must do for the controls to work, for example reviewing its own user accounts. These are your responsibilities, not the vendor's.
A worked example: reading the dates and exceptions
Sample data: a vendor sends a SOC 2 Type II report with a period of 1 July 2025 to 30 June 2026. Today is 19 November 2026.
| Check | What you see | Reading |
|---|---|---|
| Days since the period ended | 30 Jun 2026 to 19 Nov 2026 = 142 days | 142 days are not covered; ask for a bridge letter that says nothing material has changed since 30 June |
| Access-review control | 25 samples tested, 1 exception | 1 ÷ 25 = 4% deviation rate; read the exception and the management response |
| Categories in scope | Security and Availability only | Nothing is said about privacy; do not use this report for a privacy review |
| Subservice organization | Cloud host carved out | Request the host's own report |
Check: 1 ÷ 25 = 0.04, so 4%. None of these numbers is a pass or fail rule. The purpose is to turn "they have SOC 2" into four specific questions you can send to the vendor.
Common misconceptions
- "SOC 2 compliant" is not an official status. There is no pass mark. Ask for the report and read the opinion.
- Type I and Type II are not interchangeable. A Type I report cannot show that controls kept working.
- SOC 2 is not GDPR. It is a voluntary attestation against AICPA criteria; the GDPR is a regulation with legal duties. A SOC 2 report can support a vendor review, but it does not make a vendor GDPR compliant.
- A clean opinion does not mean no incidents. It says controls were described fairly and operated as described during the period.
- More categories is not always better. Pick the categories that match the risk you are buying: an analytics tool that handles visitor data should be read for Security, Confidentiality and Privacy.
For how this fits with internal policy, see data governance.
Using this when you evaluate an analytics tool
Imagine you are choosing a web analytics or live-chat provider and security asks for "SOC 2". The steps that carry over to any vendor, TapCub included:
- Ask the vendor for the report and its dates. TapCub's public security information is on the security page; this glossary page does not state TapCub's audit status, so confirm it there or by asking.
- Check the scope against what you will send. For analytics that means visitor events, IP handling and retention; for chat it means conversation content and attachments.
- Map your own responsibilities. A report covers the vendor's controls. What you configure is yours. In TapCub that includes Configuration › Privacy center (collection tier, consent rules, address truncation, retention, and export or delete requests for individual data subjects), roles in your project, and Configuration › Settings › API keys.
- Keep the evidence. Save the report, the date you reviewed it and who approved, so next year's review is a comparison, not a restart.
TapCub does not give legal advice, and a SOC 2 report is not a substitute for the privacy settings above. See compliance center for how those settings work.
Sources
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Analyst
Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.