# SOC 2 Trust Services Criteria: All 33 Criteria Listed

Source: https://truvocyber.com/blog/soc-2-trust-services-criteria-guide
Published: 2025-10-21
Topic cluster: SOC 2

> The AICPA SOC 2 Trust Services Criteria in one place: the five categories, all 33 common criteria (CC1 to CC9), and the common gaps auditors flag.

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:

- **Common Criteria (CC1 to CC9):** 33 criteria that every [SOC 2 report](https://truvocyber.com/blog/what-is-a-soc-2-type-2-report-and-why-is-it-important) covers. Together they make up the Security category.

- **Category-specific criteria:** extra criteria for Availability, Confidentiality, Processing Integrity, and Privacy. You add these only when you make those commitments to customers.

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**

- **Source:** [AICPA 2017 Trust Services Criteria, with the 2022 revised points of focus](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022) (the edition auditors use today)

- **Basis:** the 17 COSO 2013 internal control principles, plus AICPA supplemental criteria for logical access, system operations, and change management

- **Required in every SOC 2:** Security (the Common Criteria)

- **Optional:** Availability, Confidentiality, Processing Integrity, Privacy

  

?
  SOC 2 Scorecard

### Score Your SOC 2 Security Program

16 questions mapped to Common Criteria. See your strengths, find your gaps, get a prioritized action plan.
[Take the Scorecard](/soc-2-scorecard)Under 5 min · Free

## SOC 2 Trust Services Criteria Overview: How Are They Organized?

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:

- CC1: Control Environment

- CC2: Communication and Information

- CC3: Risk Assessment

- CC4: Monitoring Activities

- CC5: Control Activities

- CC6: Logical and Physical Access Controls

- CC7: System Operations

- CC8: Change Management

- CC9: Risk Mitigation

**2. Category-specific criteria** apply only when you add a category beyond Security:

- **A series:** Availability

- **PI series:** Processing Integrity

- **C series:** Confidentiality

- **P series:** Privacy

**What your audit covers:**

- **Security only:** the Common Criteria

- **Security plus another category:** the Common Criteria plus that category's series

To choose categories, see the [SOC 2 scoping guide](/blog/soc-2-scoping) and the [five Trust Services Categories breakdown](/blog/soc-2-trust-services-categories).

## SOC 2 Common Criteria: What Are All 33?

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)](https://fex.truvocyber.com/browse/soc2).

Series
Criteria

**CC1** Control Environment
[CC1.1](/blog/soc-2-cc1-1-integrity-ethical-values) integrity and ethical values
[CC1.2](/blog/soc-2-cc1-2-board-oversight) board independence and oversight
[CC1.3](/blog/soc-2-cc1-3-structures-reporting-lines) structures, reporting lines, and authorities
[CC1.4](/blog/soc-2-cc1-4-commitment-to-competence) commitment to competence
[CC1.5](/blog/soc-2-cc1-5-accountability) accountability for internal control

**CC2** Communication and Information
[CC2.1](/blog/soc-2-cc2-1-information-quality) quality information supporting controls
[CC2.2](/blog/soc-2-cc2-2-internal-communication) internal communication of objectives and responsibilities
[CC2.3](/blog/soc-2-cc2-3-external-communication) external communication

**CC3** Risk Assessment
[CC3.1](/blog/soc-2-cc3-1-objectives) specifies suitable objectives
[CC3.2](/blog/soc-2-cc3-2-risk-identification) identifies and analyzes risk
[CC3.3](/blog/soc-2-cc3-3-fraud-risk) considers potential for fraud
[CC3.4](/blog/soc-2-cc3-4-change-assessment) identifies and assesses significant changes

**CC4** Monitoring Activities
[CC4.1](/blog/soc-2-cc4-1-monitoring-evaluations) ongoing and separate evaluations
[CC4.2](/blog/soc-2-cc4-2-deficiency-communication) evaluates and communicates deficiencies

**CC5** Control Activities
[CC5.1](/blog/soc-2-cc5-1-control-selection) selects and develops control activities
[CC5.2](/blog/soc-2-cc5-2-technology-general-controls) general controls over technology
[CC5.3](/blog/soc-2-cc5-3-policies-procedures) deploys through policies and procedures

**CC6** Logical and Physical Access Controls
[CC6.1](/blog/soc-2-cc6-1-logical-access-security) logical access security software, infrastructure, and architectures
[CC6.2](/blog/soc-2-cc6-2-user-access-provisioning) registers, authorizes, and administers user access
[CC6.3](/blog/soc-2-cc6-3-least-privilege-rbac) role-based access, least privilege, segregation of duties
[CC6.4](/blog/soc-2-cc6-4-physical-access) restricts physical access
[CC6.5](/blog/soc-2-cc6-5-asset-disposal) discontinues protections over disposed assets
[CC6.6](/blog/soc-2-cc6-6-boundary-protection) protects against threats from outside system boundaries
[CC6.7](/blog/soc-2-cc6-7-data-transmission) restricts transmission, movement, and removal of information
[CC6.8](/blog/soc-2-cc6-8-malware-prevention) prevents or detects unauthorized or malicious software

**CC7** System Operations
[CC7.1](/blog/soc-2-cc7-1-vulnerability-management) detects configuration changes and new vulnerabilities
[CC7.2](/blog/soc-2-cc7-2-security-monitoring) monitors system components for anomalies
[CC7.3](/blog/soc-2-cc7-3-security-event-evaluation) evaluates security events
[CC7.4](/blog/soc-2-cc7-4-incident-response) responds to security incidents
[CC7.5](/blog/soc-2-cc7-5-incident-recovery) recovers from identified security incidents

**CC8** Change Management
[CC8.1](/blog/soc-2-cc8-1-change-management) authorizes, designs, tests, approves, and implements changes

**CC9** Risk Mitigation
[CC9.1](/blog/soc-2-cc9-1-business-disruption) risk mitigation for business disruptions
[CC9.2](/blog/soc-2-cc9-2-vendor-risk-management) assesses and manages vendor and business partner risks

  
 

SERIES CC1
 

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.
 

(function initLmlmsoc2isomapping(){ if (window.hbspt && window.hbspt.forms) { window.hbspt.forms.create({ region: "na3", portalId: "341945322", formId: "760ef504-5a85-46c1-b4c3-5c526bd65f3b", target: "#lm-soc2-iso-mapping-form", css: "" }); } else { setTimeout(initLmlmsoc2isomapping, 200); } })();

## CC1 Control Environment

COSO Principles 1 to 5 · Integrity, oversight, accountability, competence, and enforcement.

1.1

[Commitment to Integrity and Ethical Values](/blog/soc-2-cc1-1-integrity-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
Code of conduct Employee acknowledgments Violation reporting Contractor standards

1.2

[Board Independence and Oversight](/blog/soc-2-cc1-2-board-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
Advisory board minutes Independent oversight Investor board updates

1.3

[Management Structures and Reporting Lines](/blog/soc-2-cc1-3-structures-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
Org chart Role definitions Authority levels Duty segregation

1.4

[Commitment to Competence](/blog/soc-2-cc1-4-commitment-to-competence)

**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
Background checks Security training Contractor competency Succession planning

1.5

[Accountability for Internal Control](/blog/soc-2-cc1-5-accountability)

**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
Performance measures Security in job descriptions Corrective action process

  
 

SERIES CC2
 

## CC2 Communication and Information

COSO Principles 13 to 15 · How the organization gets and shares the information controls depend on.

2.1

[Information Quality](/blog/soc-2-cc2-1-information-quality)

**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](/blog/security-logging-and-monitoring-architecture-guide).

Typical Evidence
Security logs Threat intelligence feeds Vulnerability data

2.2

[Internal Communication](/blog/soc-2-cc2-2-internal-communication)

**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
Security awareness training System boundary docs Incident reporting process

2.3

[External Communication](/blog/soc-2-cc2-3-external-communication)

**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
Trust center Incident notification procedures Vendor communications

  
 

SERIES CC3
 

## CC3 Risk Assessment

COSO Principles 6 to 9 · How the organization identifies and analyzes risk.

3.1

[Objective Clarity](/blog/soc-2-cc3-1-objectives)

**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
Security objectives Risk appetite statement TSC sub-objectives

3.2

[Risk Identification and Analysis](/blog/soc-2-cc3-2-risk-identification)

**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
Asset inventory Risk assessment Vendor risk analysis

3.3

[Fraud Risk Assessment](/blog/soc-2-cc3-3-fraud-risk)

**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
Fraud risk scenarios Insider threat assessment Access abuse evaluation

3.4

[Change Assessment](/blog/soc-2-cc3-4-change-assessment)

**Requirement:** The entity assesses changes that could affect internal controls.

**In practice:** impact reviews when technology, vendors, leadership, or regulations change.

Typical Evidence
Change impact assessments Vendor change reviews Technology change log

  
 

SERIES CC4
 

## CC4 Monitoring Activities

COSO Principles 16 and 17 · How the organization checks that controls work.

4.1

[Ongoing and Separate Evaluations](/blog/soc-2-cc4-1-monitoring-evaluations)

**Requirement:** The entity runs ongoing and periodic evaluations of controls.

**In practice:** GRC platform checks, internal audits, vulnerability scans, and [penetration tests](/blog/soc2-pen-testing-on-prem). The AICPA points of focus also list compliance assessments and third-party assessments.

Typical Evidence
Penetration test reports Internal audits GRC platform checks

4.2

[Deficiency Communication](/blog/soc-2-cc4-2-deficiency-communication)

**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](/blog/soc2-ticketing-sla-vulnerability-incident-response).

Typical Evidence
Deficiency tickets Remediation tracking Corrective action records

  
 

SERIES CC5
 

## CC5 Control Activities

COSO Principles 10 to 12 · How the organization selects and deploys controls.

5.1

[Control Selection and Development](/blog/soc-2-cc5-1-control-selection)

**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
Risk-to-control mapping Control mix documentation Segregation of duties matrix

5.2

[Technology General Controls](/blog/soc-2-cc5-2-technology-general-controls)

**Requirement:** The entity develops general controls over technology.

**In practice:** controls over infrastructure, security management, and technology acquisition and maintenance.

Typical Evidence
Infrastructure hardening docs Technology access controls Acquisition procedures

5.3

[Policy Deployment](/blog/soc-2-cc5-3-policies-procedures)

**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
Policy documents Policy acknowledgments Procedure execution evidence

  
 

SERIES CC6
 

## CC6 Logical and Physical Access Controls

AICPA supplemental · The largest series, with 8 criteria.

6.1

[Security Software, Infrastructure, and Architectures](/blog/soc-2-cc6-1-logical-access-security)

**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
SSO/IdP configuration MFA enforcement Network segmentation Encryption Asset inventory

6.2

[User Registration and Authorization](/blog/soc-2-cc6-2-user-access-provisioning)

**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
Onboarding procedures Offboarding procedures Periodic access reviews Provisioning logs

6.3

[Role-Based Access and Least Privilege](/blog/soc-2-cc6-3-least-privilege-rbac)

**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
RBAC implementation Role definitions Access change authorization

6.4

[Physical Access Restrictions](/blog/soc-2-cc6-4-physical-access)

**Requirement:** The entity restricts physical access to facilities, data centers, backup media, and other sensitive locations.

**In practice:**

- **Cloud-native:** your cloud provider's SOC 2 report ([CSOCs](/blog/soc-2-csocs-inclusive-method)) covers the data center.

- **[On-premises](/blog/soc2-readiness-bare-metal-saas):** visitor logs, badge access, cameras, and documented access approvals.

Typical Evidence
Cloud provider SOC 2 (CSOCs) Visitor logs Badge access Security cameras

6.5

[Asset Disposal](/blog/soc-2-cc6-5-asset-disposal)

**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
Data sanitization records Asset disposal procedures

6.6

[Boundary Protection](/blog/soc-2-cc6-6-boundary-protection)

**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
Firewall configurations IDS/IPS VPN/zero-trust access MFA for external access

6.7

[Data Transmission Controls](/blog/soc-2-cc6-7-data-transmission)

**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
TLS/encryption in transit DLP policies Removable media controls MDM

6.8

[Malware Prevention](/blog/soc-2-cc6-8-malware-prevention)

**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
EDR/antivirus Software installation restrictions Change detection

  
 

SERIES CC7
 

## CC7 System Operations

AICPA supplemental · Vulnerability management, monitoring, incident response, and recovery.

7.1

[Vulnerability and Configuration Management](/blog/soc-2-cc7-1-vulnerability-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
Vulnerability scan reports Configuration baselines File integrity monitoring

7.2

[Security Event Monitoring](/blog/soc-2-cc7-2-security-monitoring)

**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
SIEM/log aggregation Alerting rules Anomaly analysis

7.3

[Security Event Evaluation](/blog/soc-2-cc7-3-security-event-evaluation)

**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
Event triage process Severity classification Impact assessment

7.4

[Incident Response](/blog/soc-2-cc7-4-incident-response)

**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
Incident response plan Tabletop exercise results Post-incident reviews

7.5

[Incident Recovery](/blog/soc-2-cc7-5-incident-recovery)

**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
DR/BCP procedures DR test results Root cause analyses

  
 

SERIES CC8
 

## CC8 Change Management

One criterion · The heaviest evidence load for most software companies.

8.1

[Change Management Process](/blog/soc-2-cc8-1-change-management)

**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
Pull request workflows Deployment logs Approval records Test results Emergency change process Baseline configurations

  
 

SERIES CC9
 

## CC9 Risk Mitigation

Two criteria · Business disruption and vendor risk.

9.1

[Business Disruption Risk Mitigation](/blog/soc-2-cc9-1-business-disruption)

**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
BCP/DR plans DR test results Cyber insurance policy

9.2

[Vendor and Business Partner Risk](/blog/soc-2-cc9-2-vendor-risk-management)

**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](https://www.verizon.com/business/resources/reports/2025-dbir-executive-summary.pdf), so auditors look closely here.

Typical Evidence
Vendor inventory Vendor risk assessments Vendor SOC reports Contract security terms

  
 

## SOC 2 Trust Principles: What Are the Five Categories?

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](/blog/soc-2-type-1-vs-type-2-why-type-1-first), 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.*

  
 

## SOC 2 Evidence Gaps: Where Do Most Audits Fall Short?

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)

- **Gap:** generic template policies that don't match how the team works. Auditors compare policy wording with observed controls and flag every mismatch.

- **Fix:** write policies from your real process.

2. Access reviews (CC6.2 and CC6.3)

- **Gap:** the review happens, but nobody keeps a dated record of who approved continued access or what changed.

- **Fix:** capture evidence inside the existing review, on a defined schedule.

- **Why auditors push here:** credential abuse was the most common initial access vector in breaches, at 22%, per [Verizon's 2025 Data Breach Investigations Report](https://www.verizon.com/business/resources/reports/2025-dbir-executive-summary.pdf).

3. Incident response and monitoring (CC7)

- **Gap:** the incident response plan was never tested, or the tabletop results were never written down. Alert rules were never tuned, so the team drowns in noise or misses real signals.

- **Fix:** run tabletop exercises on a schedule and keep the notes. Tune the alert rules in your [monitoring architecture](/blog/security-logging-and-monitoring-architecture-guide).

- **Why auditors push here:** [IBM's 2025 Cost of a Data Breach Report](https://newsroom.ibm.com/2025-07-30-ibm-report-13-of-organizations-reported-breaches-of-ai-models-or-applications,-97-of-which-reported-lacking-proper-ai-access-controls) puts the average breach lifecycle at 241 days, at an average cost of USD 4.44 million.

4. Change management (CC8.1)

- **Gap:** a mature CI/CD pipeline with no documented approval step, or emergency changes that skip every control with no review afterwards.

- **Fix:** require approval before deployment and review each emergency change after the fact.

**Next steps**

- First audit coming up? A [SOC 2 readiness assessment](https://truvocyber.com/services/soc-2-compliance) finds these gaps before an auditor does.

- Planning the timeline: [automated roadmap to SOC 2 compliance](/blog/automated-roadmap-to-soc-2-compliance)

- Automating evidence: [SOC 2 compliance automation guide](/blog/soc-2-compliance-automation)

- Staying [continuously audit-ready](/blog/soc-2-renewal-hidden-challenges-saas) between audit cycles

  

### Build an Effective Security Program That Makes SOC 2 a Byproduct

Our vCISO assessment shows you exactly where your controls stand today.

[Book Your Strategy Call](/contact-us)

  

## Frequently Asked Questions

### What are the SOC 2 Trust Services Criteria?

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.

### Which Trust Services Criteria are required for every SOC 2?

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.

### What is the difference between Common Criteria and Trust Services Categories?

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).

### How do I decide which Trust Services Categories apply to my business?

Start from the commitments you make to customers:

- Uptime promises in contracts or SLAs: add Availability

- Customers rely on your output for business decisions: add Processing Integrity

- Commitments on how you handle confidential data: add Confidentiality

- You collect personal information directly from individuals: add Privacy

Many companies start with Security only. See the [SOC 2 scoping guide](/blog/soc-2-scoping).

If you are in Canada and want help making that scoping call, the [top SOC 2 consultants in Canada](https://truvocyber.com/blog/top-soc-2-consultants-canada) are compared side by side, with typical readiness costs.

### How many criteria are in each CC series?

There are 33 Common Criteria in total:

- CC1 Control Environment: 5

- CC2 Communication and Information: 3

- CC3 Risk Assessment: 4

- CC4 Monitoring Activities: 2

- CC5 Control Activities: 3

- CC6 Logical and Physical Access Controls: 8

- CC7 System Operations: 5

- CC8 Change Management: 1

- CC9 Risk Mitigation: 2

### Where can I get the official AICPA Trust Services Criteria PDF?

The AICPA publishes the [2017 Trust Services Criteria (With Revised Points of Focus, 2022)](https://www.aicpa-cima.com/resources/download/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.

### Is the AICPA changing the Trust Services Criteria?

The AICPA released an [exposure draft of proposed 2027 SOC 2 Trust Services Criteria](https://www.aicpa-cima.com/news/article/aicpa-proposes-update-of-soc-2-r-trust-services-criteria-to-enhance-the-relevance-usability-and-value-of-cpas-reports) on October 28, 2026. The draft is a proposal, not a final standard.

- Public comment runs through January 15, 2027.

- If approved, the 2027 criteria apply to engagements beginning on or after December 31, 2027, with early adoption permitted.

- The draft restructures the criteria and adds points of focus on AI governance, model monitoring, prompt manipulation, data poisoning and training data management.

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.)

### What does CC6.2 require for access reviews?

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.

### What does SOC 2 CC8.1 require for change management?

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.

### What are SOC 2 CC1.1, CC1.2, and CC1.4?

CC1.1, CC1.2, and CC1.4 are three Control Environment criteria:

- **CC1.1:** commitment to integrity and ethical values (code of conduct, employee acknowledgments, violation reporting)

- **CC1.2:** board independence and oversight of internal control

- **CC1.4:** attracting, developing, and retaining competent people (background checks, training, succession planning)

### What is CC1.4 commitment to competence?

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.
