





The Trust Services Criteria (TSC) are the AICPA standards a SOC 2 examination measures your controls against. There are five categories: security, availability, processing integrity, confidentiality and privacy. Security is required in every SOC 2 report, and you add the other four when they match the commitments you make to customers.
The current version is the 2017 Trust Services Criteria with points of focus revised in 2022 (published by the AICPA as TSP section 100). The AICPA states that the 2022 revisions changed the points of focus, not the criteria.
Category | Criteria series | What it addresses | Consider adding it when |
Security | CC1 to CC9 (the Common Criteria) | Protecting information and systems against unauthorized access, disclosure and damage | Always required |
Availability | A1 | Systems are available for operation and use as committed, including capacity, backup and recovery | You commit to uptime, service levels or recovery targets |
Processing integrity | PI1 | Processing is complete, valid, accurate, timely and authorized | You process transactions or calculations on behalf of customers |
Confidentiality | C1 | Information designated as confidential is identified, protected and disposed of as committed | You hold customers' confidential business information under contract |
Privacy | P1 to P8 | Personal information is collected, used, retained, disclosed and disposed of as committed | You handle personal information and make privacy commitments |
The privacy series covers notice, choice and consent, collection, use and retention, access, disclosure and notification, quality, and monitoring and enforcement.
The security category is built from nine series of Common Criteria. CC1 to CC5 come from the COSO internal control framework, so they read like governance. CC6 to CC9 carry most of the technical weight.
Series | Name | What it looks at | Evidence auditors often request |
CC1 | Control Environment | Integrity and ethics, oversight, structure and authority, competence, accountability | Code of conduct, org chart, job descriptions, background check practice |
CC2 | Communication and Information | Quality of information and internal and external communication | Policies shared with staff, security responsibilities, customer-facing commitments |
CC3 | Risk Assessment | Objectives, identifying and analyzing risk, fraud risk, significant change | Risk assessment, risk register, review records |
CC4 | Monitoring Activities | Ongoing and separate evaluation of controls, reporting deficiencies | Monitoring results, internal reviews, remediation tracking |
CC5 | Control Activities | Selecting controls, technology controls, policies and procedures | Approved policies and procedures |
CC6 | Logical and Physical Access | Provisioning and removing access, authentication, least privilege, physical access, asset disposal, boundary protection, data in transit, malware prevention | Access lists and reviews, MFA settings, offboarding records, encryption settings, firewall rules |
CC7 | System Operations | Detecting vulnerabilities and anomalies, evaluating and responding to incidents, recovery | Vulnerability scans, alerts, incident tickets and reviews |
CC8 | Change Management | Authorizing, testing and approving changes | Change tickets, code reviews, approvals, test results |
CC9 | Risk Mitigation | Business disruption planning and vendor and business partner risk | Continuity and recovery plans, vendor reviews |
CC6 is the largest group, with eight criteria, and CC6 and CC7 typically generate a large share of evidence requests.
With Cstream: the control library maps controls to framework requirements, so you can see which control supports which criterion. Control tests span technology, people, process, vendor, policy, privacy and other, which matches how the Common Criteria reach beyond engineering into governance, vendors and people. The Audit Dashboard in Observe Pod shows coverage framework by framework, with evidence already mapped and attached.
Each criterion comes with points of focus, which are important characteristics that help management design controls and help auditors evaluate them. They are not requirements. The AICPA says using the criteria does not require an assessment of whether every point of focus is addressed, so you do not need a control for each one. They are best read as prompts for what a well-designed control tends to include.
Criterion. For example, access to systems is restricted to authorized users (CC6).
Control you design. For example, access to production requires manager approval, and access is removed within your stated timeframe when someone leaves.
Test the auditor runs. For example, inspect approval records and offboarding records for a sample of users.
Evidence you provide. Tickets, system exports and logs that show the control ran.
You write the control, so the wording and frequency are yours to choose. What matters is that you can show it operates as described.
Start with security, since every SOC 2 report includes it.
Review customer contracts, security questionnaires and marketing claims to see what you have promised.
Add a category only when you can support the promise with evidence. Each category adds criteria, controls and testing.
Revisit the choice each year as your product and customers change.
With Cstream: Multi-framework Mapping means adding a category, or a second framework such as ISO 27001 or HIPAA, builds on the controls you already run instead of starting a new spreadsheet.
The AICPA publishes the criteria and points of focus. See 2017 Trust Services Criteria with revised points of focus, 2022, which may require free registration.
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.

