





A SOC 2 report reads like a structured file: the auditor's opinion first, then management's assertion, the system description and the controls with their test results. This page walks through a typical Type 2 layout using an invented company, Example Co, so you know what each part looks like. Everything below is illustrative and is not taken from a real report. Real reports are written by audit firms in their own wording and formats.
Item | Example |
Company | Example Co (fictional) |
Service | Example Platform, a cloud application |
Report type | SOC 2 Type 2 |
Categories | Security and availability |
Period | A twelve-month period chosen by Example Co and its auditor |
This section states what the auditor examined and what they concluded. In substance it says that the auditor examined Example Co's description of Example Platform and the suitability of its controls for the period, that management and the auditor each have defined responsibilities, that every system of controls has inherent limitations, and then gives the opinion.
What to notice: the period, the categories covered and the opinion type. An unqualified opinion is the standard result, and it can coexist with exceptions listed later.
Example Co's management states that its description is fairly presented and that its controls were suitably designed and operated effectively to meet the criteria in scope. It is signed by management and covers the same period as the opinion.
What to notice: the scope, period and categories should match Section 1 exactly.
Example Co's description would typically be organized under headings such as these:
Services provided and how customers use them
Principal service commitments and system requirements
System components: infrastructure, software, people, procedures and data
Boundaries of the system and what is out of scope
Subservice organizations, such as the cloud provider, and how they are treated
Complementary user entity controls expected of customers
Significant incidents and significant changes during the period, where applicable
What to notice: whether the description matches the product you buy, and which vendors sit behind it.
With Cstream: the system description is easier to write and keep accurate when your assets, applications, people and vendors are already in one inventory. Asset Management, Application Management, Tech Store and Vendor Management hold that inventory in one data model.
This is the core of a Type 2 report. The table below shows invented rows in the usual format.
Criterion | Control (Example Co) | Test performed by the auditor | Result |
CC1.4 | New employees complete security awareness training after joining | Inspected training records for a sample of new hires | No exceptions noted |
CC6.2 | Access for departing employees is removed after they leave | Inspected offboarding records for a sample of leavers | Exception noted: one sampled account was removed later than the stated timeframe |
CC8.1 | Production changes are reviewed and approved before release | Inspected change records for a sample of releases | No exceptions noted |
CC9.2 | Vendors that handle customer data are reviewed each year | Inspected vendor review records | No exceptions noted |
A1.2 | Backups run on a schedule and failures are followed up | Inspected backup logs and tickets for a sample of days | No exceptions noted |
What to notice: each row names the criterion, the control, the test and the result. The exception shows how a single sampled item can be recorded.
An optional, unaudited section. Example Co might use it to explain the exception: the cause, what changed and the date the fix was in place.
What to notice: a clear response that names the cause and the fix is a sign of a mature program. This section is not covered by the auditor's opinion.
No exceptions noted means the tested samples met the control as described.
Exceptions noted is followed by a description of what the auditor found.
An exception on a low-risk control is different from a cluster of exceptions in access or change management.
For each row in Section 4, ask what evidence you would hand the auditor. The training row needs completion records. The offboarding row needs a list of leavers and the removal dates. The change row needs approvals. Building that evidence list early makes fieldwork straightforward.
With Cstream: Evidence Management organizes proof against each control, so the right records are ready for every sample. Control tests run continuously, so a late removal like the one in the example appears on your worklist and is fixed before it becomes an exception, and the Audit Dashboard lets your team see coverage framework by framework, much as an auditor will.
Cstream is the trusted GRC platform that supports startups through every stage of the SOC 2 journey, from planning and control implementation to audit preparation and ongoing compliance. Cstream keeps one data model for IT operations and compliance, so the assets, people, vendors, policies and control test results you use every day are the same ones that support your audit.
Cstream's SOC 2 capabilities include key features supporting preparation and audit, such as:
Cstream works directly with your audit firm to keep reviews moving. Multi-framework Mapping also lets the same controls support ISO 27001, HIPAA and other frameworks later.
Schedule a demo to see how Cstream supports your SOC 2 journey.

