





A SOC 2 audit is an attestation examination performed by an independent, licensed CPA firm. Management prepares a description of the system and an assertion about it, the auditor tests both against the Trust Services Criteria, and the process ends with a signed report and an opinion. Knowing the stages in advance removes most of the surprises.
Management writes the system description, signs the assertion, designs and operates the controls, and provides evidence.
The audit firm plans the engagement, tests the description and controls, and forms an opinion.
Control owners across engineering, IT, HR, security and operations answer questions and supply evidence.
Stage | What happens | Your role | Output |
1. Plan and scope | Confirm systems, criteria, report type and period | Decide scope and commitments | Agreed scope |
2. Select the audit firm | Compare licensed CPA firms with SOC 2 experience | Request proposals, check experience with companies like yours | Signed engagement letter |
3. Kick off | Agree timeline, evidence request list, contacts and tooling | Name a point of contact and control owners | Project plan |
4. Describe the system | Draft the system description against DC section 200 | Write and review it with the auditor | Draft description |
5. Walkthroughs | The auditor learns how each control works | Explain and demonstrate controls | Design assessment |
6. Fieldwork | The auditor requests evidence and tests controls | Provide populations and evidence on time | Test results |
7. Exceptions and clarifications | The auditor shares anything that did not meet expectations | Explain, fix and respond | Management responses |
8. Draft report | The auditor shares the draft | Check wording and facts, sign the assertion and representation letter | Approved draft |
9. Final report | The auditor issues the signed report | Share under NDA, plan renewal | Final SOC 2 report |
For a Type 1 the auditor tests design as of a date. For a Type 2 the auditor also tests operating effectiveness across the whole observation window.
With Cstream: Projects track these stages, owners and due dates on your side, and Cstream works directly with your audit firm to speed up review cycles and reduce friction during the examination.
Auditors use four standard techniques:
Inquiry: asking control owners how a control works
Observation: watching a control being performed
Inspection: reviewing documents, configurations and records
Reperformance: repeating a control to see whether the same result occurs
For a Type 2, the auditor asks for populations, such as every new hire, every leaver or every production change in the period, then selects samples from them. If a sample shows a failure, the auditor may select more samples and evaluate whether the control is operating effectively.
Evidence area | Examples |
Governance | Org chart, roles, management meeting records |
Policies | Approved and versioned policies, acknowledgments |
Risk | Risk assessment and register |
People | Training records, onboarding and offboarding records, background check records where applicable |
Access | User lists, approvals, review records, authentication settings |
Operations | Vulnerability scans, monitoring alerts, incident tickets |
Change | Change tickets, code review and approval records |
Vendors | Vendor inventory and review records, third-party SOC reports |
Resilience | Continuity and recovery plans, backup and restore test results |
With Cstream: Evidence Management keeps audit evidence organized against controls and requirements, so requests are answered from one place. The Audit Dashboard in Observe Pod shows a framework-by-framework view with evidence already mapped and attached, ready for review.
Name one point of contact and give every control an owner and a backup.
Answer evidence requests quickly and in the format asked.
Share system, staff and vendor changes with the auditor early.
Do not hide an exception. Explain it, show what you did about it and add a management response.
Keep populations easy to produce.
Read the draft report carefully, since your name is on the assertion.
Starting fieldwork before gaps are fixed
Evidence scattered across personal drives
Unclear scope that changes during the audit
Surprise changes to systems or vendors during the window
Slow responses that push report dates back
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.

