SOC 2
Trust Service Criteria for service organizations covering security, availability, processing integrity, confidentiality, and privacy
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (17)
A - Availability
Systems are available for operation and use as committed or agreed
| Code | Title |
|---|---|
| SOC2-A1.1 | Maintains capacity to meet availability commitments |
| SOC2-A1.2 | Environmental protections, data backups, and recovery infrastructure support availability |
| SOC2-A1.3 | Recovery plan procedures support system recovery from failures |
Additional Criteria for Availability
| Code | Title |
|---|---|
| A1.1 | Availability Capacity Management |
| A1.2 | Environmental Protections and Backups |
Additional Criteria for Confidentiality
| Code | Title |
|---|---|
| C1.1 | Confidential Information Identification |
Additional Criteria for Privacy
| Code | Title |
|---|---|
| P3.1 | Personal Information Collection Consent |
C - Confidentiality
Information designated as confidential is protected as committed or agreed
| Code | Title |
|---|---|
| SOC2-C1.1 | Confidential information is identified and protected during receipt, processing, storage |
| SOC2-C1.2 | Confidential information is disposed of securely |
CC - Common Criteria (Security)
Control criteria applicable to all trust service categories
| Code | Title |
|---|---|
| SOC2-CC1.1 | COSO principle 1: Demonstrates commitment to integrity and ethical values |
| SOC2-CC1.2 | COSO principle 2: Board exercises oversight responsibility |
| SOC2-CC1.3 | COSO principle 3: Management establishes structures, reporting lines, and authorities |
| SOC2-CC1.4 | COSO principle 4: Demonstrates commitment to attract and retain competent individuals |
| SOC2-CC1.5 | COSO principle 5: Holds individuals accountable for internal control responsibilities |
| SOC2-CC2.1 | COSO principle 13: Obtains and generates relevant, quality information |
| SOC2-CC2.2 | COSO principle 14: Internally communicates information including objectives and responsibilities |
| SOC2-CC2.3 | COSO principle 15: Communicates with external parties regarding matters affecting controls |
| SOC2-CC3.1 | COSO principle 6: Specifies objectives to identify and assess risks |
| SOC2-CC3.2 | COSO principle 7: Identifies risks and analyzes to determine how managed |
| SOC2-CC3.3 | COSO principle 8: Considers potential for fraud |
| SOC2-CC3.4 | COSO principle 9: Identifies and assesses changes that could impact internal controls |
| SOC2-CC4.1 | COSO principle 16: Selects and develops ongoing and separate evaluations |
| SOC2-CC4.2 | COSO principle 17: Evaluates and communicates deficiencies in a timely manner |
| SOC2-CC5.1 | COSO principle 10: Selects and develops control activities to mitigate risks |
| SOC2-CC5.2 | COSO principle 11: Selects and develops general controls over technology |
| SOC2-CC5.3 | COSO principle 12: Deploys control activities through policies and procedures |
| SOC2-CC6.1 | Logical and physical access security for information and assets |
| SOC2-CC6.2 | Prior to granting access, registration and authorization processes are established |
| SOC2-CC6.3 | Role-based access and least privilege are enforced |
| SOC2-CC6.6 | Measures against threats outside system boundaries are implemented |
| SOC2-CC6.7 | Transmission of data is restricted to authorized users |
| SOC2-CC6.8 | Controls to prevent or detect unauthorized or malicious software |
| SOC2-CC7.1 | Detection and monitoring procedures for security events are in place |
| SOC2-CC7.2 | Monitors system components for anomalies indicating malicious acts |
| SOC2-CC7.3 | Evaluates security events to determine incident status |
| SOC2-CC7.4 | Responds to identified security incidents through defined procedures |
| SOC2-CC7.5 | Identifies the root cause of security incidents |
| SOC2-CC8.1 | Change management processes are in place |
| SOC2-CC9.1 | Identifies, selects and develops risk mitigation activities |
| SOC2-CC9.2 | Risk mitigation activities include assessment of vendor and business partner controls |
Common Criteria Change Management
| Code | Title |
|---|---|
| CC8.1 | Change Management |
Common Criteria Communication
| Code | Title |
|---|---|
| CC2.1 | Information Quality for Internal Communication |
Common Criteria Control Activities
| Code | Title |
|---|---|
| CC5.1 | Control Activities Selection and Development |
Common Criteria Control Environment
| Code | Title |
|---|---|
| CC1.1 | Commitment to Integrity and Ethical Values |
Common Criteria Logical and Physical Access
| Code | Title |
|---|---|
| CC6.1 | Logical Access Security Controls |
| CC6.2 | User Access Provisioning and Removal |
| CC6.3 | Access Reviews and Least Privilege |
| CC6.6 | Network Boundary Protection |
| CC6.7 | Data in Transit and Endpoint Protection |
| CC6.8 | Prevention and Detection of Unauthorized Software |
Common Criteria Monitoring Activities
| Code | Title |
|---|---|
| CC4.1 | Ongoing and Separate Evaluations |
Common Criteria Risk Assessment
| Code | Title |
|---|---|
| CC3.2 | Risk Identification and Analysis |
Common Criteria Risk Mitigation
| Code | Title |
|---|---|
| CC9.1 | Risk Mitigation Activities |
| CC9.2 | Vendor and Third Party Risk Management |
Common Criteria System Operations
| Code | Title |
|---|---|
| CC7.1 | Vulnerability Detection and Configuration Monitoring |
| CC7.2 | Security Event Monitoring |
| CC7.3 | Security Incident Response |
| CC7.4 | Incident Recovery |
P - Privacy
Personal information is collected, used, retained, disclosed, and disposed according to commitments
| Code | Title |
|---|---|
| SOC2-P1.1 | Privacy notice provides clear notice about privacy practices |
| SOC2-P2.1 | Consent is obtained for the collection, use, and disclosure of personal information |
| SOC2-P3.1 | Personal information is collected consistent with privacy commitments |
| SOC2-P3.2 | Explicit consent is obtained for sensitive personal information |
| SOC2-P4.1 | Personal information is used for purposes identified in privacy commitments |
| SOC2-P4.2 | Personal information is retained for only as long as needed |
| SOC2-P4.3 | Personal information is securely disposed of |
| SOC2-P5.1 | Personal information is accessed only by authorized personnel |
| SOC2-P5.2 | Corrections to personal information are processed timely |
| SOC2-P6.1 | Personal information is disclosed to third parties only as committed |
| SOC2-P6.2 | Records of personal information disclosures are maintained |
| SOC2-P7.1 | Personal information collected is limited to what is necessary and relevant |
| SOC2-P8.1 | Inquiries, complaints, and disputes regarding personal information are addressed |
PI - Processing Integrity
System processing is complete, valid, accurate, timely, and authorized
| Code | Title |
|---|---|
| SOC2-PI1.1 | Obtains or generates and uses relevant quality information to support processing integrity |
| SOC2-PI1.2 | System inputs are complete, accurate, and processed in a timely manner |
| SOC2-PI1.3 | System processing is complete, valid, accurate, timely, and authorized |
| SOC2-PI1.4 | System outputs are complete, valid, accurate, timely, and distributed |
| SOC2-PI1.5 | Inputs are processed completely, accurately, and timely for stored data |
Your Compliance Coverage
If you comply with SOC 2, you already cover:
ISO 27001:2022
51%
39 controls mapped
Compare →TISAX — Trusted Information Security Assessment Exchange
17%
13 controls mapped
Compare →SSAE 18 — Attestation Standards (SOC Reporting)
17%
13 controls mapped
Compare →+ 628 more: South Korea Cloud Security Assurance Program (CSAP) (16%), CSA CCM v4 (14%)
See all 631 mapped frameworks ↓Maps to 631 other frameworks
Frequently Asked Questions
What is SOC 2?
SOC 2 is a compliance framework from United States with 17 domains and 76 controls. Trust Service Criteria for service organizations covering security, availability, processing integrity, confidentiality, and privacy It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does SOC 2 have?
SOC 2 has 76 controls organised across 17 domains. The largest domains are CC - Common Criteria (Security) (31 controls), P - Privacy (13 controls), Common Criteria Logical and Physical Access (6 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does SOC 2 map to?
SOC 2 maps to 631 other compliance frameworks. The top mapping partners are ISO 27001:2022 (51% coverage), TISAX — Trusted Information Security Assessment Exchange (17% coverage), SSAE 18 — Attestation Standards (SOC Reporting) (17% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with SOC 2 compliance?
Start your SOC 2 compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about SOC 2 requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 76 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 700 frameworks.
Get Started Free →Free forever — no credit card required