The SOC 2 Trust Services Criteria (TSC) are the control requirements the AICPA sets for a SOC 2 audit. Older guides call them the SOC 2 trust principles or Trust Services Principles. The criteria have two parts:
In the audits we support, access reviews (CC6.2 and CC6.3) are the most common evidence gap: the review happens, but nobody keeps a dated record of the review (Truvo Cyber, 2026).
Watch: how to build a SOC 2 program from scratch (12 min)
Quick facts
16 questions mapped to Common Criteria. See your strengths, find your gaps, get a prioritized action plan.
The SOC 2 Trust Services Criteria have two layers: 33 Common Criteria that apply to every SOC 2 report, and extra criteria series that apply only when you add Availability, Processing Integrity, Confidentiality, or Privacy to scope. The Common Criteria follow the 17 principles of the COSO 2013 framework, with AICPA supplemental criteria for areas such as logical access and change management. The official source is the AICPA's TSP Section 100, the 2017 Trust Services Criteria with revised points of focus (2022).
1. Common Criteria (CC1 to CC9) apply to every SOC 2 engagement. The AICPA based them on the 17 principles of the COSO Internal Control Integrated Framework (2013). The AICPA also added supplemental criteria for logical access, system operations, and change management. The nine series:
2. Category-specific criteria apply only when you add a category beyond Security:
What your audit covers:
To choose categories, see the SOC 2 scoping guide and the five Trust Services Categories breakdown.
The SOC 2 Common Criteria are the 33 criteria, CC1.1 through CC9.2, that apply to every SOC 2 report regardless of which categories are in scope. Together they make up the Security category, grouped into nine series from CC1 Control Environment to CC9 Risk Mitigation.
Each criterion below links to a detailed implementation guide.
To browse the criteria alongside ISO 27001 and other frameworks, open them in the Framework Explorer (FEX).
| Series | Criteria |
| CC1 Control Environment | CC1.1 integrity and ethical values CC1.2 board independence and oversight CC1.3 structures, reporting lines, and authorities CC1.4 commitment to competence CC1.5 accountability for internal control |
| CC2 Communication and Information | CC2.1 quality information supporting controls CC2.2 internal communication of objectives and responsibilities CC2.3 external communication |
| CC3 Risk Assessment | CC3.1 specifies suitable objectives CC3.2 identifies and analyzes risk CC3.3 considers potential for fraud CC3.4 identifies and assesses significant changes |
| CC4 Monitoring Activities | CC4.1 ongoing and separate evaluations CC4.2 evaluates and communicates deficiencies |
| CC5 Control Activities | CC5.1 selects and develops control activities CC5.2 general controls over technology CC5.3 deploys through policies and procedures |
| CC6 Logical and Physical Access Controls | CC6.1 logical access security software, infrastructure, and architectures CC6.2 registers, authorizes, and administers user access CC6.3 role-based access, least privilege, segregation of duties CC6.4 restricts physical access CC6.5 discontinues protections over disposed assets CC6.6 protects against threats from outside system boundaries CC6.7 restricts transmission, movement, and removal of information CC6.8 prevents or detects unauthorized or malicious software |
| CC7 System Operations | CC7.1 detects configuration changes and new vulnerabilities CC7.2 monitors system components for anomalies CC7.3 evaluates security events CC7.4 responds to security incidents CC7.5 recovers from identified security incidents |
| CC8 Change Management | CC8.1 authorizes, designs, tests, approves, and implements changes |
| CC9 Risk Mitigation | CC9.1 risk mitigation for business disruptions CC9.2 assesses and manages vendor and business partner risks |
Free · Google Sheet
SOC 2 Common Criteria CC1 to CC9, Mapped to ISO 27001 (Spreadsheet)
Every Common Criteria point with the ISO 27001:2022 Annex A controls each point maps to and the SOC 2 evidence that carries over, plus two sample control sets, kept current in a shared Google Sheet. Enter your email to open it.
COSO Principles 1 to 5 · Integrity, oversight, accountability, competence, and enforcement.
Commitment to Integrity and Ethical Values
Requirement: The entity demonstrates a commitment to integrity and ethical values.
In practice: a code of conduct or acceptable use policy that employees acknowledge at onboarding, plus a way to report violations. Contractors and vendor staff follow the same standards.
Typical Evidence
Board Independence and Oversight
Requirement: The board is independent from management and oversees internal controls.
In practice: without a formal board, auditors accept advisory board minutes, investor board updates, or another documented oversight structure. Someone outside day-to-day operations reviews security on a schedule.
Typical Evidence
Management Structures and Reporting Lines
Requirement: Management sets structures, reporting lines, authorities, and responsibilities, with board oversight.
In practice: an org chart, role definitions, delegated authority, and segregation of duties. The AICPA supplemental criteria also ask management to consider external parties and security requirements.
Typical Evidence
Requirement: The entity attracts, develops, and retains competent people.
In practice: background checks, job descriptions with security duties, security awareness training with completion records, and competency checks. The supplemental points of focus extend to contractors and vendor staff.
Typical Evidence
Accountability for Internal Control
Requirement: The entity holds people accountable for their internal control duties.
In practice: security duties in job descriptions and performance reviews, plus a process for handling non-compliance.
Typical Evidence
COSO Principles 13 to 15 · How the organization gets and shares the information controls depend on.
Requirement: The entity obtains or generates relevant, quality information to support internal controls.
In practice: logs, vulnerability data, and threat intelligence that feed security decisions. See security logging and monitoring architecture.
Typical Evidence
Requirement: The entity communicates internal control objectives and responsibilities to personnel.
In practice: security awareness training, documented system boundaries, and a way for employees to report incidents.
Typical Evidence
Requirement: The entity communicates with external parties about matters affecting internal controls.
In practice: a trust center, external incident notification procedures, and security expectations shared with vendors and partners.
Typical Evidence
COSO Principles 6 to 9 · How the organization identifies and analyzes risk.
Requirement: The entity sets objectives clearly enough to identify risks against them.
In practice: documented security objectives and risk appetite, with sub-objectives for each category in scope.
Typical Evidence
Risk Identification and Analysis
Requirement: The entity identifies and analyzes risks to decide how to manage them.
In practice: an asset inventory, a threat and vulnerability assessment (vendors included), and a treatment decision for each risk. Auditors expect the assessment repeated on a schedule, not done once.
Typical Evidence
Requirement: The entity considers the potential for fraud when assessing risk.
In practice: fraud scenarios such as insider threats, privileged access abuse, unauthorized data access, and unauthorized code changes.
Typical Evidence
Requirement: The entity assesses changes that could affect internal controls.
In practice: impact reviews when technology, vendors, leadership, or regulations change.
Typical Evidence
COSO Principles 16 and 17 · How the organization checks that controls work.
Ongoing and Separate Evaluations
Requirement: The entity runs ongoing and periodic evaluations of controls.
In practice: GRC platform checks, internal audits, vulnerability scans, and penetration tests. The AICPA points of focus also list compliance assessments and third-party assessments.
Typical Evidence
Requirement: The entity reports control deficiencies in a timely manner to the people responsible for corrective action, including senior management and the board.
In practice: deficiency tickets with owners and due dates. See ticketing, SLA, and incident response processes.
Typical Evidence
COSO Principles 10 to 12 · How the organization selects and deploys controls.
Control Selection and Development
Requirement: The entity selects and develops control activities that reduce risks to acceptable levels.
In practice: a mapping from the risks found in CC3 to controls, with a mix of manual and automated, preventive and detective controls, plus a segregation of duties matrix. Controls follow risk, not a framework checklist.
Typical Evidence
Requirement: The entity develops general controls over technology.
In practice: controls over infrastructure, security management, and technology acquisition and maintenance.
Typical Evidence
Requirement: The entity deploys controls through policies and procedures.
In practice: policies, signed acknowledgments, and proof that teams follow them: access reviews on schedule, incidents handled per procedure, and changes through the documented process.
Typical Evidence
AICPA supplemental · The largest series, with 8 criteria.
Security Software, Infrastructure, and Architectures
Requirement: The entity implements logical access security software, infrastructure, and architectures to protect information assets.
In practice: SSO/IdP, MFA, network segmentation, encryption at rest and in transit, key management, firewall rules, and an asset inventory. CC6.1 usually maps to more controls than any other CC6 criterion.
Typical Evidence
User Registration and Authorization
Requirement: The entity registers and authorizes new users before issuing credentials, and removes access when users are no longer authorized.
In practice: onboarding and offboarding tickets or provisioning logs, plus access reviews on a defined schedule. Most teams run the review but keep no dated record.
Typical Evidence
Role-Based Access and Least Privilege
Requirement: The entity grants, changes, or removes access based on roles, least privilege, and segregation of duties.
In practice: RBAC, documented roles, periodic role reviews, and an approval record for each access change. When someone changes teams, review that person's access.
Typical Evidence
Requirement: The entity restricts physical access to facilities, data centers, backup media, and other sensitive locations.
In practice:
Typical Evidence
Requirement: The entity removes protections from physical assets only after data can no longer be read or recovered.
In practice: a disposal procedure and sanitization records for retired hardware and storage media.
Typical Evidence
Requirement: The entity protects against threats from outside the system boundary.
In practice: firewalls, IDS/IPS, VPN or zero-trust access for remote connections, and MFA on external-facing systems.
Typical Evidence
Requirement: The entity restricts how information is transmitted, moved, and removed, and protects information along the way.
In practice: TLS for data in transit, DLP where needed, removable media controls, and MDM. Scope depends on your data flows and customer agreements.
Typical Evidence
Requirement: The entity prevents, detects, and acts on unauthorized or malicious software.
In practice: EDR or antivirus, software installation restrictions, change detection, and scanning of assets from external sources.
Typical Evidence
AICPA supplemental · Vulnerability management, monitoring, incident response, and recovery.
Vulnerability and Configuration Management
Requirement: The entity detects configuration changes that introduce vulnerabilities, and newly discovered vulnerabilities.
In practice: regular vulnerability scans, configuration baselines, file integrity monitoring, and detection of unauthorized changes. Your vulnerability management program sits here.
Typical Evidence
Requirement: The entity monitors systems for anomalies that indicate malicious acts, natural disasters, and errors.
In practice: a SIEM or log aggregation, tuned alert rules, and a process to analyze anomalies. Detection covers compromise attempts, unauthorized access, credential misuse, and unauthorized hardware or software.
Typical Evidence
Requirement: The entity evaluates security events to decide whether they are incidents.
In practice: a triage process for severity, impact, and response. Privacy-scoped audits also check whether personal data was exposed.
Typical Evidence
Requirement: The entity responds to security incidents through a defined incident response program.
In practice: an incident response plan with roles, containment steps, communication templates, and post-incident reviews. Auditors want proof of testing (tabletop exercises count) and proof that real incidents followed the plan.
Typical Evidence
Requirement: The entity recovers from security incidents.
In practice: tested BCP/DR procedures and root cause analysis with corrective actions. The AICPA expects test scenarios where key people are unavailable and several systems fail at once.
Typical Evidence
One criterion · The heaviest evidence load for most software companies.
Requirement: The entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures.
In practice: pull request approvals, test results, and deployment logs from the CI/CD pipeline, plus baseline configurations and an emergency change process. Auditors check that each change is approved before deployment and that emergency changes get a review afterwards.
Typical Evidence
Two criteria · Business disruption and vendor risk.
Business Disruption Risk Mitigation
Requirement: The entity identifies and develops risk mitigation activities for business disruptions.
In practice: BCP/DR plans, recovery procedures for security events, and cyber liability or E&O insurance.
Typical Evidence
Vendor and Business Partner Risk
Requirement: The entity assesses and manages risks from vendors and business partners.
In practice: a vendor inventory, risk assessments on a defined schedule, and security terms in contracts. Breaches involving a third party doubled from 15% to 30% in Verizon's 2025 DBIR, so auditors look closely here.
Typical Evidence
The five SOC 2 trust principles, now called Trust Services Categories, are Security, Availability, Processing Integrity, Confidentiality, and Privacy. Security is required in every SOC 2 report, and the other four are optional.
The "five trust principles" are the old name for the five Trust Services Categories. The AICPA renamed the Trust Services Principles and Criteria to the Trust Services Criteria in 2017. SOC 2 reports issued on or after December 15, 2018 use the 2017 criteria.
Every SOC 2 report includes Security. You add the other four based on the commitments you make to customers:
| Category | Criteria | Include when |
| Security | CC1 to CC9 (Common Criteria) | Always |
| Availability | A series | You promise uptime in contracts, SLAs, or a public status page |
| Processing Integrity | PI series | Customers rely on your output for business decisions |
| Confidentiality | C series | You commit to how customer or proprietary data is classified, kept, or protected |
| Privacy | P series | You collect personal information directly from individuals |
For a first SOC 2, Security only is often the right starting scope.
Not sure which categories to add? Ali explains how to scope your first report, and which optional categories are easiest to add, in under a minute.
Most teams do the security work. The gaps show up when an auditor asks for proof. In our engagements, gaps cluster in four areas.
1. Policies (CC1 and CC5)
2. Access reviews (CC6.2 and CC6.3)
3. Incident response and monitoring (CC7)
4. Change management (CC8.1)
Next steps
Our vCISO assessment shows you exactly where your controls stand today.
The SOC 2 Trust Services Criteria are the AICPA's control criteria for SOC 2 audits. They include 33 Common Criteria (CC1 to CC9) that every SOC 2 covers, plus extra criteria for Availability, Processing Integrity, Confidentiality, and Privacy. Older guides call them the SOC 2 trust principles.
Security is required in every SOC 2. Security is made up of the 33 Common Criteria (CC1 to CC9). Availability, Processing Integrity, Confidentiality, and Privacy are optional.
Common Criteria are the 33 baseline criteria in every SOC 2 audit. Trust Services Categories set the audit scope. Security uses only the Common Criteria, and each added category adds a separate criteria series (A, PI, C, or P).
Start from the commitments you make to customers:
Many companies start with Security only. See the SOC 2 scoping guide.
If you are in Canada and want help making that scoping call, the top SOC 2 consultants in Canada are compared side by side, with typical readiness costs.
There are 33 Common Criteria in total:
The AICPA publishes the 2017 Trust Services Criteria (With Revised Points of Focus, 2022) on aicpa-cima.com. You need to log in to an AICPA & CIMA account to download the PDF.
The AICPA released an exposure draft of proposed 2027 SOC 2 Trust Services Criteria on October 28, 2026. The draft is a proposal, not a final standard.
Until the AICPA approves a final version, the 2017 criteria with the 2022 revised points of focus listed on this page stay in use. (Updated October 31, 2026.)
CC6.2 requires you to register and authorize users before issuing credentials, and to remove credentials when access is no longer authorized. The AICPA points of focus add a periodic review of access credentials. Auditors want dated review records that show who was reviewed, who approved continued access, and what changed.
CC8.1 requires that changes to infrastructure, data, software, and procedures are authorized, designed, documented, tested, approved, and implemented in a controlled way. Auditors usually sample changes from the observation period and look for a ticket, an approval or peer review, and test evidence for each one.
CC1.1, CC1.2, and CC1.4 are three Control Environment criteria:
CC1.4 maps to COSO Principle 4: the entity demonstrates a commitment to attract, develop, and retain competent individuals. Auditors look for background checks, security training records, job descriptions with security duties, and succession plans for key roles.