SOC 2
SOC 2 examinations evaluate a service organisation's controls against the AICPA 2017 Trust Services Criteria: 61 criteria across security (the common criteria CC1 to CC9, built on the COSO 2013 principles), availability, confidentiality, processing integrity and privacy, each with points of focus revised in 2022.
SOC 2 is a compliance framework from International (AICPA attestation standard, used worldwide) with 5 domains and 61 controls that map to 182 other frameworks. The largest domains are CC - Common Criteria (Security) (33 controls), P - Privacy (18 controls), PI - Processing Integrity (5 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, 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 (5)
A - Availability
Systems are available for operation and use as committed or agreed
C - Confidentiality
Information designated as confidential is protected as committed or agreed
CC - Common Criteria (Security)
Control criteria applicable to all trust service categories
| Code | Title |
|---|---|
| SOC2-CC1.1 | CC1.1 Commitment to integrity and ethical values (COSO principle 1) |
| SOC2-CC1.2 | CC1.2 Board independence and oversight of internal control (COSO principle 2) |
| SOC2-CC1.3 | CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3) |
| SOC2-CC1.4 | CC1.4 Attracting, developing and retaining competent people (COSO principle 4) |
| SOC2-CC1.5 | CC1.5 Accountability for internal control responsibilities (COSO principle 5) |
| SOC2-CC2.1 | CC2.1 Relevant, quality information to support internal control (COSO principle 13) |
| SOC2-CC2.2 | CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14) |
| SOC2-CC2.3 | CC2.3 Communication with external parties about internal control (COSO principle 15) |
| SOC2-CC3.1 | CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6) |
| SOC2-CC3.2 | CC3.2 Identifying and analysing risks to objectives (COSO principle 7) |
| SOC2-CC3.3 | CC3.3 Considering fraud risk (COSO principle 8) |
| SOC2-CC3.4 | CC3.4 Identifying and assessing significant changes (COSO principle 9) |
| SOC2-CC4.1 | CC4.1 Ongoing and separate evaluations of control (COSO principle 16) |
| SOC2-CC4.2 | CC4.2 Evaluating and communicating control deficiencies (COSO principle 17) |
| SOC2-CC5.1 | CC5.1 Selecting control activities that mitigate risk (COSO principle 10) |
| SOC2-CC5.2 | CC5.2 General controls over technology (COSO principle 11) |
| SOC2-CC5.3 | CC5.3 Deploying controls through policies and procedures (COSO principle 12) |
| SOC2-CC6.1 | CC6.1 Logical access security over protected information assets |
| SOC2-CC6.2 | CC6.2 Registering and authorising users before issuing credentials |
| SOC2-CC6.3 | CC6.3 Role-based access, least privilege and segregation of duties |
| SOC2-CC6.4 | CC6.4 Restricting physical access to facilities and assets |
| SOC2-CC6.5 | CC6.5 Protecting data on assets until disposal |
| SOC2-CC6.6 | CC6.6 Protection against threats from outside the system boundary |
| SOC2-CC6.7 | CC6.7 Restricting and protecting information in transmission, movement and removal |
| SOC2-CC6.8 | CC6.8 Preventing and detecting unauthorised or malicious software |
| SOC2-CC7.1 | CC7.1 Detecting configuration changes and new vulnerabilities |
| SOC2-CC7.2 | CC7.2 Monitoring system components for anomalies |
| SOC2-CC7.3 | CC7.3 Evaluating security events to identify incidents |
| SOC2-CC7.4 | CC7.4 Responding to security incidents |
| SOC2-CC7.5 | CC7.5 Recovering from security incidents |
| SOC2-CC8.1 | CC8.1 Managing changes to procedures, software, data and infrastructure |
| SOC2-CC9.1 | CC9.1 Mitigating risks of business disruption |
| SOC2-CC9.2 | CC9.2 Assessing and managing vendor and business partner risk |
P - Privacy
Personal information is collected, used, retained, disclosed, and disposed according to commitments
| Code | Title |
|---|---|
| SOC2-P1.1 | P1.1 Privacy notice to data subjects |
| SOC2-P2.1 | P2.1 Choice and consent |
| SOC2-P3.1 | P3.1 Collecting personal information consistent with objectives |
| SOC2-P3.2 | P3.2 Explicit consent before collecting information that requires it |
| SOC2-P4.1 | P4.1 Limiting use to identified purposes |
| SOC2-P4.2 | P4.2 Retaining personal information |
| SOC2-P4.3 | P4.3 Securely disposing of personal information |
| SOC2-P5.1 | P5.1 Data subject access |
| SOC2-P5.2 | P5.2 Correction of personal information |
| SOC2-P6.1 | P6.1 Disclosure to third parties with consent |
| SOC2-P6.2 | P6.2 Record of authorised disclosures |
| SOC2-P6.3 | P6.3 Record of unauthorised disclosures and breaches |
| SOC2-P6.4 | P6.4 Privacy commitments from vendors and third parties |
| SOC2-P6.5 | P6.5 Vendor commitments to report unauthorised disclosures |
| SOC2-P6.6 | P6.6 Notifying breaches and incidents |
| SOC2-P6.7 | P6.7 Accounting of personal information held and disclosed |
| SOC2-P7.1 | P7.1 Quality of personal information |
| SOC2-P8.1 | P8.1 Inquiries, complaints, disputes and compliance monitoring |
PI - Processing Integrity
System processing is complete, valid, accurate, timely, and authorized
| Code | Title |
|---|---|
| SOC2-PI1.1 | PI1.1 Quality information about processing objectives, data definitions and specifications |
| SOC2-PI1.2 | PI1.2 Controls over system inputs |
| SOC2-PI1.3 | PI1.3 Controls over system processing |
| SOC2-PI1.4 | PI1.4 Controls over output delivery |
| SOC2-PI1.5 | PI1.5 Controls over stored inputs, work in process and outputs |
Your Compliance Coverage
If you comply with SOC 2, you already cover:
Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
100%
61 controls mapped
Compare →NIST SP 800-53 Rev 5
100%
61 controls mapped
Compare →ISO 27001:2022
98%
60 controls mapped
Compare →+ 179 more: ISO 27701:2019 (97%), ISO 27002:2022 (97%)
See all 182 mapped frameworks ↓Maps to 182 other frameworks
Coverage is not the same as your position
This page shows what SOC 2 overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is SOC 2 and who does it apply to?
SOC 2 is a compliance framework from International (AICPA attestation standard, used worldwide) with 5 domains and 61 controls. SOC 2 examinations evaluate a service organisation's controls against the AICPA 2017 Trust Services Criteria: 61 criteria across security (the common criteria CC1 to CC9, built on the COSO 2013 principles), availability, confidentiality, processing integrity and privacy, each with points of focus revised in 2022. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does SOC 2 actually require?
SOC 2 has 61 controls organised across 5 domains. The largest domains are CC - Common Criteria (Security) (33 controls), P - Privacy (18 controls), PI - Processing Integrity (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of SOC 2 do I already cover?
SOC 2 maps to 182 other compliance frameworks. The top mapping partners are Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 (100% coverage), NIST SP 800-53 Rev 5 (100% coverage), ISO 27001:2022 (98% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement SOC 2?
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 61 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 1,121 frameworks.
Get Started Free →Free forever, no credit card required