Illustrative example — fictional company, real structure
What is a SOC 2 report?
A SOC 2 report is the document a licensed CPA firm issues after examining a service organization’s controls. It has five parts: the auditor’s opinion, management’s assertion, the system description, the controls mapped to the criteria (with the auditor’s tests and results in a Type 2), and optional other information.
Real SOC 2 reports live under NDA — so here is one you can dissect. Every numbered marker is pinned to a real element of a Type II report. Click it to see what that element means, what an experienced reviewer checks, and when it should worry you.
ASHFORD & GRAY, CPAs LLP (fictional)
Independent Service Auditor’s Report
To the Management of Meridian Cloud Technologies Pvt. Ltd.
Scope. We have examined Meridian Cloud Technologies’ description of its customer-data platform system for processing user entities’ transactions throughout the period 1 April 2025 to 31 March 2026, based on the criteria for a description of a service organization’s system in DC section 200, and the suitability of the design and operating effectiveness of controls stated in the description to provide reasonable assurance that service commitments and system requirements were achieved based on the trust services criteria relevant to Security, Availability, and Confidentiality.
Inherent limitations. Because of their nature, controls at a service organization may not prevent, or detect and correct, all misstatements… projections of any evaluation of effectiveness to future periods are subject to risk.
Opinion. In our opinion, in all material respects, (a) the description presents the system as designed and implemented throughout the period, (b) the controls were suitably designed, and (c) the controls operated effectively throughout the period.
Restricted use. This report is intended solely for the information and use of Meridian Cloud Technologies, user entities of the system during some or all of the period, and prospective user entities…
Ashford & Gray
Certified Public Accountants · 12 May 2026
SOC 2® Type II
Section II — Assertion of Meridian Cloud Technologies Management
We have prepared the accompanying description of Meridian’s customer-data platform system… We confirm, to the best of our knowledge and belief, that:
- the description fairly presents the system as designed and implemented throughout the period,
- the controls stated in the description were suitably designed throughout the period, and
- the controls operated effectively throughout the period to achieve our service commitments and system requirements.
…based on the criteria in DC section 200 and the trust services criteria for Security, Availability, and Confidentiality set forth in TSP section 100.
Section III — Description of the System (excerpt)
Components of the system
Infrastructure. Production workloads on a public cloud provider (Mumbai & Singapore regions)…
Software. Multi-tenant web application, REST APIs, CI/CD pipeline…
People. Engineering, security, support, and compliance functions (142 personnel)…
Data. Customer PII and transaction records, classified per the data-classification policy…
Principal service commitments
Meridian commits to 99.9% monthly availability, encryption of customer data in transit and at rest, and confidentiality handling per master service agreements…
Subservice organizations
Meridian uses a cloud infrastructure provider for hosting. The description excludes the controls of the subservice organization (carve-out method). The trust services criteria are achieved only if complementary subservice organization controls (CSOCs) operate effectively…
Complementary user entity controls
- User entities are responsible for provisioning and deprovisioning their own users…
- User entities are responsible for configuring single sign-on and MFA for their tenant…
- User entities are responsible for reviewing user access on a periodic basis…
Section IV — Trust Services Criteria, Controls, Tests and Results (excerpt)
Criteria related to the Security (Common Criteria) category
| Criteria | Controls specified by Meridian | Tests performed by Ashford & Gray | Results |
|---|---|---|---|
| CC6.1 | Multi-factor authentication is enforced for all production and identity-provider access. | Inspected IdP configuration, observed authentication for a sample of 25 users, and inquired of the Head of Security. | No exceptions noted. |
| CC6.2 | Access of terminated personnel is revoked within one business day of separation. | Selected a sample of 25 terminations and compared HRIS separation dates to access-revocation timestamps. | Exception noted. For 1 of 25 sampled terminations, revocation occurred after three business days. See Section V. |
| CC8.1 | Production changes require peer review and passing CI checks prior to deployment. | Reperformed pipeline gating for a sample of 40 changes and inspected branch-protection settings. | No exceptions noted. |
Section V — Other Information Provided by Management (unaudited)
Management response — CC6.2 exception. The delayed revocation involved a contractor account outside the automated HRIS integration. Effective July 2025, contractor accounts are provisioned through the same integration, and a weekly reconciliation of active accounts against the personnel register was implemented. No unauthorized activity was identified for the affected account.
The information in this section has not been subjected to the procedures applied in the examination and, accordingly, the service auditor expresses no opinion on it.
Want the full illustrative report as a PDF?
We’ll email you the complete Meridian example, with every section laid out like a real Type II report from a licensed CPA firm, along with Tranquility Cybersecurity’s profile. It is clearly watermarked as illustrative, with no real client data.
Why we built a report you can click
Real SOC 2 reports are restricted-use documents — they travel under NDA, so almost nobody sees one before they need to read one. Meridian Cloud Technologies is fictional, but every element above sits exactly where it sits in a real Type II report, phrased the way real reports phrase it. The 18 markers cover the things experienced reviewers actually stop on: the opinion wording, the period, the boundary, the carve-out, the CUECs, and how exceptions are written and answered.
When you are ready to go deeper: the full reviewer’s guide walks all five sections with an 8-step checklist, the opinions & exceptions guide decodes the four opinion types, and the SOC 2 Simulator shows how a scope like Meridian’s gets chosen in the first place. If you are preparing for your own examination, Tranquility Cybersecurity runs the readiness and coordinates the audit through independent, US-licensed CPA firms — 1,000+ audits delivered.
Report anatomy — common questions
Is this a real SOC 2 report?
What are the sections of a SOC 2 report?
Which part of the report should I read first?
How long is a real SOC 2 report?
Can I download a full example report?
Want your report to read this cleanly?
A 30-minute call with an auditor: your scope, your likely control set, and what your first Type II should cover.
Related Reading
How to Read a SOC 2 Report
All five sections annotated, an 8-step reviewer checklist, and the red flags.
Read moreSOC 2 Opinions & Exceptions
Unmodified, qualified, adverse, disclaimer — and why exceptions are not qualification.
Read moreCUECs & CSOCs Explained
The controls a SOC report assumes of you and of carved-out vendors.
Read moreSubservice Organizations
Carve-out vs inclusive — how your vendors' vendors appear in the report.
Read moreType 1 vs Type 2
Which report to get first, and when to go straight to Type 2.
Read moreSOC 2 Knowledge Hub
Type 1 vs Type 2, criteria, timelines and audit prep — all guides.
Read more
