SOC 2 to ISO 27001 mapping
Each of the 38 SOC 2 criteria this site maps, with the ISO/IEC 27001:2022 Annex A controls it shares a policy with. The mapping runs through the Policyseed policies: a criterion and a control are paired when one policy addresses both. It is not an official AICPA or ISO crosswalk, and every pair shows the policy that creates it.
Joined this way, the 38 criteria reach 91 of the 93 Annex A controls in 543 criterion-control pairs. 2 controls (7.6, 7.12) are not reached because no policy in the set documents them; they are explained below.
How to read this mapping
The two frameworks are organized differently. SOC 2 is a set of criteria a CPA firm reports against; ISO 27001 is a management system standard with a catalog of 93 reference controls in Annex A. There is no single correct way to line them up, which is why published comparisons quote different overlap figures. This page does not add another figure. It shows one concrete, checkable route between them: the documents you would actually write.
- A pair means a shared policy, not equivalence. If the Access Control Policy addresses CC6.2 and documents Annex A 5.18, the two are paired. The policy text you write for one helps with the other; the controls themselves are still assessed separately.
- Broad policies create broad links. The Information Security Policy touches many criteria and many controls, so it pairs all of them. Links that come only through a broad policy are weaker than links through a narrow one such as the Change Management Policy.
- Neither framework is covered by a document. Policies are where both start. Your auditor or certification body tests the controls and their evidence.
If you need an authoritative mapping, ask your auditor which one they use; the AICPA publishes its own mapping material for the Trust Services Criteria.
SOC 2 criteria to Annex A controls
For each criterion, the policies that address it and, after each policy, the Annex A controls that policy also documents. Criterion ids link to a plain-words explanation of the criterion; policy names link to the full policy text.
CC1 Control environment
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC1.1 Integrity and ethical values19 controls |
|
| CC1.2 Oversight by leadership8 controls |
|
| CC1.3 Structure, reporting lines and authority8 controls |
|
| CC1.4 Competent people8 controls |
|
| CC1.5 Accountability19 controls |
|
CC2 Communication and information
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC2.1 Quality information16 controls |
|
| CC2.2 Internal communication21 controls |
|
| CC2.3 External communication17 controls |
|
CC3 Risk assessment
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC3.1 Objectives for risk assessment8 controls |
|
| CC3.2 Identifying and analyzing risks9 controls |
|
| CC3.3 Fraud risk17 controls |
|
| CC3.4 Changes that affect risk10 controls |
|
CC4 Monitoring activities
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC4.1 Ongoing and separate evaluations11 controls |
|
| CC4.2 Communicating deficiencies15 controls |
|
CC5 Control activities
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC5.1 Selecting control activities8 controls |
|
| CC5.2 Technology controls21 controls |
|
| CC5.3 Policies and procedures14 controls |
|
CC6 Logical and physical access controls
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC6.1 Logical access security21 controls |
|
| CC6.2 User registration and deprovisioning15 controls |
|
| CC6.3 Role-based access and least privilege8 controls |
|
| CC6.4 Physical access10 controls |
|
| CC6.5 Disposal of physical assets18 controls |
|
| CC6.6 Protection from external threats22 controls |
|
| CC6.7 Data in transit and on removable media22 controls |
|
| CC6.8 Malicious software24 controls |
|
CC7 System operations
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC7.1 Detecting vulnerabilities and configuration changes20 controls |
|
| CC7.2 Monitoring for anomalies15 controls |
|
| CC7.3 Evaluating security events15 controls |
|
| CC7.4 Responding to incidents7 controls |
|
| CC7.5 Recovering from incidents13 controls |
|
CC8 Change management
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC8.1 Change management16 controls |
|
CC9 Risk mitigation
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| CC9.1 Mitigating business disruption risk8 controls |
|
| CC9.2 Vendor and business partner risk11 controls |
|
A1 Availability
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| A1.1 Capacity management21 controls |
|
| A1.2 Environmental protections, backups and recovery infrastructure15 controls |
|
| A1.3 Recovery testing6 controls |
|
C1 Confidentiality
| Criterion | Policy, then the Annex A controls it also documents |
|---|---|
| C1.1 Identifying and protecting confidential information16 controls |
|
| C1.2 Disposing of confidential information11 controls |
|
Annex A controls to SOC 2 criteria
The same pairs read from the ISO side, by Annex A theme. Use this view when you are building a Statement of Applicability and want to know which SOC 2 evidence you can point at for a control.
5. Organizational controls
| Control | Linking policies | SOC 2 criteria |
|---|---|---|
| 5.1 Policies for information security | P01 | CC1.1, CC1.2, CC1.3, CC1.5, CC2.2, CC3.1, CC4.1, CC4.2, CC5.1, CC5.3 |
| 5.2 Information security roles and responsibilities | P01 | CC1.1, CC1.2, CC1.3, CC1.5, CC2.2, CC3.1, CC4.1, CC4.2, CC5.1, CC5.3 |
| 5.3 Segregation of duties | P08, P09 | CC3.4, CC5.2, CC6.1, CC6.7, CC8.1 |
| 5.4 Management responsibilities | P01, P18 | CC1.1, CC1.2, CC1.3, CC1.4, CC1.5, CC2.2, CC3.1, CC3.3, CC4.1, CC4.2, CC5.1, CC5.3, CC6.2 |
| 5.5 Contact with authorities | P13, P22 | CC2.2, CC2.3, CC4.2, CC7.2, CC7.3, CC7.4, CC7.5, CC9.2, C1.1, C1.2 |
| 5.6 Contact with special interest groups | P01 | CC1.1, CC1.2, CC1.3, CC1.5, CC2.2, CC3.1, CC4.1, CC4.2, CC5.1, CC5.3 |
| 5.7 Threat intelligence | P11, P12 | CC2.1, CC4.1, CC6.8, CC7.1, CC7.2, CC7.3, A1.1 |
| 5.8 Information security in project management | P10, P22 | CC2.3, CC6.8, CC8.1, CC9.2, C1.1, C1.2 |
| 5.9 Inventory of information and other associated assets | P05, P06 | CC2.1, CC6.5, CC6.7, C1.1, C1.2 |
| 5.10 Acceptable use of information and other associated assets | P02, P06 | CC1.1, CC1.5, CC6.7, C1.1 |
| 5.11 Return of assets | P05, P18 | CC1.1, CC1.4, CC1.5, CC2.1, CC2.2, CC3.3, CC5.3, CC6.2, CC6.5, C1.2 |
| 5.12 Classification of information | P06 | CC6.7, C1.1 |
| 5.13 Labeling of information | P06 | CC6.7, C1.1 |
| 5.14 Information transfer | P06, P08 | CC6.1, CC6.7, C1.1 |
| 5.15 Access control | P03 | CC3.3, CC5.2, CC6.1, CC6.2, CC6.3 |
| 5.16 Identity management | P03, P04 | CC3.3, CC5.2, CC6.1, CC6.2, CC6.3, CC6.6 |
| 5.17 Authentication information | P04 | CC6.1, CC6.6 |
| 5.18 Access rights | P03 | CC3.3, CC5.2, CC6.1, CC6.2, CC6.3 |
| 5.19 Information security in supplier relationships | P16 | CC2.3, CC3.2, CC9.2 |
| 5.20 Addressing information security within supplier agreements | P16 | CC2.3, CC3.2, CC9.2 |
| 5.21 Managing information security in the ICT supply chain | P10, P16 | CC2.3, CC3.2, CC6.8, CC8.1, CC9.2 |
| 5.22 Monitoring, review and change management of supplier services | P16 | CC2.3, CC3.2, CC9.2 |
| 5.23 Information security for use of cloud services | P16, P20 | CC2.3, CC3.2, CC5.2, CC6.1, CC6.6, CC7.1, CC9.2, A1.1 |
| 5.24 Information security incident management planning and preparation | P13 | CC2.2, CC2.3, CC4.2, CC7.2, CC7.3, CC7.4, CC7.5 |
| 5.25 Assessment and decision on information security events | P12, P13 | CC2.1, CC2.2, CC2.3, CC4.2, CC7.1, CC7.2, CC7.3, CC7.4, CC7.5, A1.1 |
| 5.26 Response to information security incidents | P13 | CC2.2, CC2.3, CC4.2, CC7.2, CC7.3, CC7.4, CC7.5 |
| 5.27 Learning from information security incidents | P13 | CC2.2, CC2.3, CC4.2, CC7.2, CC7.3, CC7.4, CC7.5 |
| 5.28 Collection of evidence | P13 | CC2.2, CC2.3, CC4.2, CC7.2, CC7.3, CC7.4, CC7.5 |
| 5.29 Information security during disruption | P14 | CC7.5, CC9.1, A1.1, A1.2, A1.3 |
| 5.30 ICT readiness for business continuity | P14, P15 | CC7.5, CC9.1, A1.1, A1.2, A1.3 |
| 5.31 Legal, statutory, regulatory and contractual requirements | P01 | CC1.1, CC1.2, CC1.3, CC1.5, CC2.2, CC3.1, CC4.1, CC4.2, CC5.1, CC5.3 |
| 5.32 Intellectual property rights | P02, P05, P10 | CC1.1, CC1.5, CC2.1, CC6.5, CC6.8, CC8.1, C1.2 |
| 5.33 Protection of records | P07, P12 | CC2.1, CC6.5, CC7.1, CC7.2, CC7.3, A1.1, C1.1, C1.2 |
| 5.34 Privacy and protection of PII | P06, P22 | CC2.3, CC6.7, CC9.2, C1.1, C1.2 |
| 5.35 Independent review of information security | P01, P17 | CC1.1, CC1.2, CC1.3, CC1.5, CC2.1, CC2.2, CC3.1, CC3.2, CC3.3, CC3.4, CC4.1, CC4.2, CC5.1, CC5.3, CC9.1 |
| 5.36 Compliance with policies, rules and standards for information security | P01, P17 | CC1.1, CC1.2, CC1.3, CC1.5, CC2.1, CC2.2, CC3.1, CC3.2, CC3.3, CC3.4, CC4.1, CC4.2, CC5.1, CC5.3, CC9.1 |
| 5.37 Documented operating procedures | P12, P14 | CC2.1, CC7.1, CC7.2, CC7.3, CC7.5, CC9.1, A1.1, A1.2, A1.3 |
6. People controls
| Control | Linking policies | SOC 2 criteria |
|---|---|---|
| 6.1 Screening | P18 | CC1.1, CC1.4, CC1.5, CC2.2, CC3.3, CC5.3, CC6.2 |
| 6.2 Terms and conditions of employment | P18 | CC1.1, CC1.4, CC1.5, CC2.2, CC3.3, CC5.3, CC6.2 |
| 6.3 Information security awareness, education and training | P01, P18 | CC1.1, CC1.2, CC1.3, CC1.4, CC1.5, CC2.2, CC3.1, CC3.3, CC4.1, CC4.2, CC5.1, CC5.3, CC6.2 |
| 6.4 Disciplinary process | P18 | CC1.1, CC1.4, CC1.5, CC2.2, CC3.3, CC5.3, CC6.2 |
| 6.5 Responsibilities after termination or change of employment | P03, P18 | CC1.1, CC1.4, CC1.5, CC2.2, CC3.3, CC5.2, CC5.3, CC6.1, CC6.2, CC6.3 |
| 6.6 Confidentiality or non-disclosure agreements | P16, P18 | CC1.1, CC1.4, CC1.5, CC2.2, CC2.3, CC3.2, CC3.3, CC5.3, CC6.2, CC9.2 |
| 6.7 Remote working | P02, P21 | CC1.1, CC1.5, CC6.4, CC6.5, A1.2 |
| 6.8 Information security event reporting | P02, P13 | CC1.1, CC1.5, CC2.2, CC2.3, CC4.2, CC7.2, CC7.3, CC7.4, CC7.5 |
7. Physical controls
| Control | Linking policies | SOC 2 criteria |
|---|---|---|
| 7.1 Physical security perimeters | P21 | CC6.4, CC6.5, A1.2 |
| 7.2 Physical entry | P21 | CC6.4, CC6.5, A1.2 |
| 7.3 Securing offices, rooms and facilities | P21 | CC6.4, CC6.5, A1.2 |
| 7.4 Physical security monitoring | P21 | CC6.4, CC6.5, A1.2 |
| 7.5 Protecting against physical and environmental threats | P14, P21 | CC6.4, CC6.5, CC7.5, CC9.1, A1.1, A1.2, A1.3 |
| 7.6 Working in secure areas | None | Not reached |
| 7.7 Clear desk and clear screen | P19, P21 | CC6.4, CC6.5, CC6.6, CC6.7, CC6.8, A1.2 |
| 7.8 Equipment siting and protection | P21 | CC6.4, CC6.5, A1.2 |
| 7.9 Security of assets off-premises | P19, P21 | CC6.4, CC6.5, CC6.6, CC6.7, CC6.8, A1.2 |
| 7.10 Storage media | P05, P07, P19 | CC2.1, CC6.5, CC6.6, CC6.7, CC6.8, C1.1, C1.2 |
| 7.11 Supporting utilities | P21 | CC6.4, CC6.5, A1.2 |
| 7.12 Cabling security | None | Not reached |
| 7.13 Equipment maintenance | P19 | CC6.6, CC6.7, CC6.8 |
| 7.14 Secure disposal or re-use of equipment | P05, P07, P19 | CC2.1, CC6.5, CC6.6, CC6.7, CC6.8, C1.1, C1.2 |
8. Technological controls
| Control | Linking policies | SOC 2 criteria |
|---|---|---|
| 8.1 User endpoint devices | P19 | CC6.6, CC6.7, CC6.8 |
| 8.2 Privileged access rights | P03, P20 | CC3.3, CC5.2, CC6.1, CC6.2, CC6.3, CC6.6, CC7.1, A1.1 |
| 8.3 Information access restriction | P03, P06 | CC3.3, CC5.2, CC6.1, CC6.2, CC6.3, CC6.7, C1.1 |
| 8.4 Access to source code | P03, P09 | CC3.3, CC3.4, CC5.2, CC6.1, CC6.2, CC6.3, CC8.1 |
| 8.5 Secure authentication | P04 | CC6.1, CC6.6 |
| 8.6 Capacity management | P05, P12 | CC2.1, CC6.5, CC7.1, CC7.2, CC7.3, A1.1, C1.2 |
| 8.7 Protection against malware | P19 | CC6.6, CC6.7, CC6.8 |
| 8.8 Management of technical vulnerabilities | P11 | CC4.1, CC6.8, CC7.1 |
| 8.9 Configuration management | P09, P19, P20 | CC3.4, CC5.2, CC6.1, CC6.6, CC6.7, CC6.8, CC7.1, CC8.1, A1.1 |
| 8.10 Information deletion | P07, P22 | CC2.3, CC6.5, CC9.2, C1.1, C1.2 |
| 8.11 Data masking | P06, P12 | CC2.1, CC6.7, CC7.1, CC7.2, CC7.3, A1.1, C1.1 |
| 8.12 Data leakage prevention | P02, P06, P19 | CC1.1, CC1.5, CC6.6, CC6.7, CC6.8, C1.1 |
| 8.13 Information backup | P15 | CC7.5, CC9.1, A1.2, A1.3 |
| 8.14 Redundancy of information processing facilities | P14, P20 | CC5.2, CC6.1, CC6.6, CC7.1, CC7.5, CC9.1, A1.1, A1.2, A1.3 |
| 8.15 Logging | P12 | CC2.1, CC7.1, CC7.2, CC7.3, A1.1 |
| 8.16 Monitoring activities | P12 | CC2.1, CC7.1, CC7.2, CC7.3, A1.1 |
| 8.17 Clock synchronization | P12 | CC2.1, CC7.1, CC7.2, CC7.3, A1.1 |
| 8.18 Use of privileged utility programs | P03 | CC3.3, CC5.2, CC6.1, CC6.2, CC6.3 |
| 8.19 Installation of software on operational systems | P09, P19 | CC3.4, CC5.2, CC6.6, CC6.7, CC6.8, CC8.1 |
| 8.20 Networks security | P20 | CC5.2, CC6.1, CC6.6, CC7.1, A1.1 |
| 8.21 Security of network services | P20 | CC5.2, CC6.1, CC6.6, CC7.1, A1.1 |
| 8.22 Segregation of networks | P20 | CC5.2, CC6.1, CC6.6, CC7.1, A1.1 |
| 8.23 Web filtering | P19 | CC6.6, CC6.7, CC6.8 |
| 8.24 Use of cryptography | P08 | CC6.1, CC6.7 |
| 8.25 Secure development life cycle | P10 | CC6.8, CC8.1 |
| 8.26 Application security requirements | P10 | CC6.8, CC8.1 |
| 8.27 Secure system architecture and engineering principles | P10, P20 | CC5.2, CC6.1, CC6.6, CC6.8, CC7.1, CC8.1, A1.1 |
| 8.28 Secure coding | P10 | CC6.8, CC8.1 |
| 8.29 Security testing in development and acceptance | P09, P10 | CC3.4, CC5.2, CC6.8, CC8.1 |
| 8.30 Outsourced development | P09, P16 | CC2.3, CC3.2, CC3.4, CC5.2, CC8.1, CC9.2 |
| 8.31 Separation of development, test and production environments | P09, P10, P20 | CC3.4, CC5.2, CC6.1, CC6.6, CC6.8, CC7.1, CC8.1, A1.1 |
| 8.32 Change management | P09 | CC3.4, CC5.2, CC8.1 |
| 8.33 Test information | P06, P10 | CC6.7, CC6.8, CC8.1, C1.1 |
| 8.34 Protection of information systems during audit testing | P11 | CC4.1, CC6.8, CC7.1 |
Controls the mapping does not reach
- 7.6 Working in secure areas. The policies assume no company-operated secure areas (no server rooms or data centers); the secure areas that hold production systems are the hosting provider's. If you operate one, add rules for working in it; otherwise record it as not applicable in your Statement of Applicability.
- 7.12 Cabling security. Not covered. For a cloud-hosted company, cabling that carries production traffic belongs to the hosting provider, and office cabling usually to the landlord; record it as such in your Statement of Applicability, or add a line if you run your own office network cabling.
What the mapping leaves out
Annex A is only part of ISO 27001. Clauses 4 to 10 of the standard describe the management system: the scope of the ISMS, how risks are assessed and treated, the Statement of Applicability, objectives, internal audit, management review and continual improvement. A SOC 2 program produces some of the raw material, such as a risk assessment and a review cycle, but not those records in the form a certification auditor expects. The ISO 27001 policy templates page lists what to add.
On the SOC 2 side, the report also needs a system description written by management, which ISO 27001 does not ask for. See the free SOC 2 system description template. For the policies behind every row above, see the SOC 2 policies list; for the controls between policy and evidence, the SOC 2 controls list.
Frequently asked questions
- Is this an official SOC 2 to ISO 27001 crosswalk?
- No. The pairs on this page come from joining two Policyseed data sets: which policies address each Trust Services criterion, and which policies document each Annex A control. A pair means one policy appears on both sides. It is useful for reusing documents and evidence across the two frameworks, but it is not a mapping published by the AICPA or ISO, and your auditor or certification body may draw the lines differently.
- If we have SOC 2, are we most of the way to ISO 27001?
- Often a good part of the way on controls, because the same access reviews, change records, incident logs and vendor reviews serve both. The bigger gap is usually the management system itself: ISO 27001 clauses 4 to 10 ask for an ISMS scope, a risk treatment process, a Statement of Applicability, internal audit and management review, which a SOC 2 report does not require in that form.
- Why does one criterion map to so many Annex A controls?
- Because the join is at policy level. A broad policy such as the Information Security Policy addresses several criteria and documents several controls, so every criterion it addresses is paired with every control it documents. Read the per-policy lines in the table to see which policy creates each link, and treat links that come only through a broad policy as weaker than links through a narrow one.
- Which Annex A controls are not reached?
- Only controls that no Policyseed policy documents. They are physical controls a cloud-hosted company usually treats as the hosting provider's or the landlord's responsibility; the page lists them with the reason, and you record your decision for each in your Statement of Applicability.
ISO and ISO/IEC 27001 are standards published by the International Organization for Standardization and the International Electrotechnical Commission; the Trust Services Criteria are published by the AICPA. Policyseed is not affiliated with any of them. Control and criterion names are cited for reference; the mapping is our own.
Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.