





SOC 2 has no fixed list of controls to implement. Its formal requirements are the Trust Services Criteria you choose, a system description prepared against the AICPA's description criteria, management's assertion, and an examination by an independent CPA firm. Inside that frame, you design the controls and the auditor tests them.
Lists called "SOC 2 requirements" often mix three different things: criteria the AICPA publishes, example controls that vendors suggest, and expectations that individual auditors or buyers add. Keeping them apart helps you plan.
The Security category. Every report covers the Common Criteria, CC1 to CC9.
A system description. Management describes the system against the description criteria in DC section 200: the services, principal service commitments and system requirements, system components, and related disclosures.
Management's assertion. A written statement that the description is fairly presented and that the controls meet the criteria (and, for a Type 2, operated effectively).
An independent examination. Performed by a licensed CPA firm under AICPA attestation standards.
An observation window, for a Type 2.
Whether to include availability, processing integrity, confidentiality and privacy
Type 1 or Type 2
The scope: which services, systems and locations
The controls themselves, their owners and their frequency
The controls in this table are examples of what companies commonly design, not a mandated list.
Area | Criteria | Examples of controls companies design | Typical evidence |
Governance and ownership | CC1 | Code of conduct, defined roles, management oversight, performance and accountability | Org chart, approved code of conduct, job descriptions |
Communication | CC2 | Policies shared with staff, channels for reporting concerns, customer communication of commitments | Distribution and acknowledgment records |
Risk assessment | CC3 | Annual risk assessment, risk register, review of significant changes | Assessment document, register, review notes |
Monitoring | CC4 | Ongoing control monitoring, tracking and fixing deficiencies | Test results, remediation tickets |
Policies and control activities | CC5 | Approved policies and procedures, technology controls | Policy versions, approvals |
Access | CC6 | Approval before access, multi-factor authentication, least privilege, timely removal, encryption, network protection, physical access, secure disposal | Access lists, review records, configuration exports |
System operations | CC7 | Vulnerability management, logging and alerting, incident response and recovery | Scan results, alerts, incident records |
Change management | CC8 | Review, testing and approval before release | Change tickets, review and test records |
Vendors and continuity | CC9 | Business disruption planning, vendor risk reviews | Continuity plan, vendor review records |
Optional categories | A1, PI1, C1, P1 to P8 | Capacity and recovery testing, data accuracy checks, confidential data handling, privacy notices and consent | Depends on commitments made |
With Cstream: the control library maps controls to framework requirements, so you can see which control satisfies which requirement. Control tests cover technology, people, process, vendor, policy, privacy and other, so the areas above are tested together rather than tracked in separate tools.
System description and management's assertion
Information security and supporting policies, approved and versioned
Risk assessment and risk register
Asset and application inventory, and vendor list
Incident response plan and business continuity and disaster recovery plans
Evidence that each control operated
Some expectations are common practice rather than AICPA rules. Penetration tests, background checks, annual policy reviews and a report period covering roughly the last twelve months are examples. The criteria do not name each of these, but many auditors and customers expect them, so confirm with your audit firm and your key customers.
Write down your service commitments to customers, including contracts, SLAs and marketing claims.
Choose the Trust Services categories that match those commitments.
For each criterion in scope, list the controls you already run and the gaps.
Assign an owner, frequency and evidence source to every control.
Review the result with your auditor before the window or audit starts.
With Cstream: Projects turn your requirements list into assigned tasks with due dates and real-time readiness tracking. Vendor Management and Risk Registry keep third-party risk and organizational risk in the same program, so CC3 and CC9 evidence is not kept elsewhere.
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.

