# ISO 27001 to SOC 2 Control Mapping: All 93 Annex A Controls

Source: https://truvocyber.com/blog/iso-27001-to-soc-2-mapping
Published: 2026-10-10
Topic cluster: ISO 27001

> ISO 27001 to SOC 2 mapping for all 93 Annex A controls: 40 map to SOC 2 Security criteria, 53 are new work. Tables by theme plus a live mapping sheet.

In our experience, a SOC 2 program covers roughly 70 percent of the work for ISO 27001 certification. The policies carry over, and most controls need only small adjustments. By direct mapping, the SOC 2 Security criteria (CC1 to CC9) cover 40 of the 93 ISO 27001:2022 Annex A controls in our mapping spreadsheet, about 43 percent. The other 53 have no direct Security criterion and count as new work for a SOC 2 holder.

This post is the reverse of the [SOC 2 to ISO 27001 control mapping](/blog/iso-27001-soc-2-control-mapping), which starts from each SOC 2 criterion. Here every row starts from an Annex A control, in the same order the Statement of Applicability lists them, and shows the SOC 2 criteria that map to it, the coverage, and what a SOC 2 holder still has to build.

Key insight

**ISO 27001 vs ISO 27002 in this mapping**

ISO 27001 is the ISMS standard that organizations certify against. ISO 27002 is the implementation guide for the same 93 controls, with identical numbering (5.x, 6.x, 7.x, 8.x). The tables below use the ISO 27001:2022 Annex A numbers, which are the same in both documents.

Key insight

**Not sure where your ISO 27001 gaps are?**

Answer 20 questions and get a personalized readiness score based on your existing security posture. [Take the ISO 27001 Readiness Scorecard](/iso-27001-scorecard)

## How to Read These ISO 27001 to SOC 2 Mapping Tables

Each row maps one ISO 27001:2022 Annex A control to the SOC 2 Security criteria that map to it directly. The Coverage column uses three values from the mapping spreadsheet:

- **Full:** the evidence produced for at least one mapped SOC 2 criterion satisfies the ISO 27001 control without adaptation. The same log, policy, or record goes into both audit packages.
- **Partial:** every mapped SOC 2 criterion covers the intent of the control, but the evidence needs supplementing or reframing, typically by adding documented scope, extending a policy, or adding a step to an existing process.
- **Not covered:** no SOC 2 Security criterion maps to the control directly. The last column names what a SOC 2 holder still has to build.

The Full and Partial ratings come from the overlap type the spreadsheet assigns to each SOC 2 criterion. Of the 40 covered controls, 34 are Full and 6 are Partial.

Annex A controls are grouped by theme: A.5 (organizational), A.6 (people), A.7 (physical), and A.8 (technological). Each SOC 2 criterion links to its own post, and each Annex A control with a dedicated post links to it.

## Organizational Controls: A.5.1 to A.5.37

20 of the 37 ISO 27001 organizational controls map directly to a SOC 2 Security criterion. The 20 covered controls group as follows:

- **Policies, roles, and segregation of duties:** A.5.1 to A.5.3, mapped to CC1.2, CC1.3, CC2.2, CC3.1, CC5.1, CC5.3, and CC6.3
- **Access:** A.5.15, A.5.16, and A.5.18, mapped to CC6.1 to CC6.3
- **Suppliers:** A.5.19, A.5.20, and A.5.22, mapped to CC9.2
- **Incidents:** A.5.25 to A.5.27, mapped to CC7.3 to CC7.5
- **Continuity:** A.5.29 and A.5.30, mapped to CC7.5 and CC9.1
- **Independent review:** A.5.35, mapped to CC4.1 and CC4.2
- **Other organizational controls:** A.5.6 and A.5.31 (CC2.3), A.5.8 (CC3.4), A.5.11 (CC6.5), and A.5.37 (CC5.3)

Four of the 20 are Partial: A.5.6, A.5.8, A.5.31, and A.5.35, because CC2.3, CC3.4, CC4.1, and CC4.2 each carry a Partial overlap rating.
Annex A controlControl nameSOC 2 criteria that map to itCoverageWhat a SOC 2 holder still has to buildA.5.1Policies for information security[CC3.1](/blog/soc-2-cc3-1-objectives), [CC5.1](/blog/soc-2-cc5-1-control-selection), [CC5.3](/blog/soc-2-cc5-3-policies-procedures)Full-A.5.2Information security roles and responsibilities[CC1.2](/blog/soc-2-cc1-2-board-oversight), [CC1.3](/blog/soc-2-cc1-3-structures-reporting-lines), [CC2.2](/blog/soc-2-cc2-2-internal-communication)Full-A.5.3Segregation of duties[CC6.3](/blog/soc-2-cc6-3-least-privilege-rbac)Full-A.5.4Management responsibilities-Not covered-A.5.5Contact with authorities-Not coveredRegister of regulator/authority contactsA.5.6Contact with special interest groups[CC2.3](/blog/soc-2-cc2-3-external-communication)Partial-[A.5.7](/blog/iso-27001-a-5-7-threat-intelligence)Threat intelligence-Not coveredDocumented threat intelligence processA.5.8Information security in project management[CC3.4](/blog/soc-2-cc3-4-change-assessment)Partial-A.5.9Inventory of information and other associated assets-Not coveredFormal asset inventory scoped to the ISMSA.5.10Acceptable use of information and other associated assets-Not coveredAcceptable use rules tied to the asset inventoryA.5.11Return of assets[CC6.5](/blog/soc-2-cc6-5-asset-disposal)Full-A.5.12Classification of information-Not coveredInformation classification schemeA.5.13Labelling of information-Not coveredLabelling scheme applied to classified informationA.5.14Information transfer-Not coveredInformation transfer procedures and agreements[A.5.15](/blog/iso-27001-a-5-15-access-control)Access control[CC6.1](/blog/soc-2-cc6-1-logical-access-security), [CC6.3](/blog/soc-2-cc6-3-least-privilege-rbac)Full-[A.5.16](/blog/iso-27001-a-5-16-identity-management)Identity management[CC6.2](/blog/soc-2-cc6-2-user-access-provisioning)Full-[A.5.17](/blog/iso-27001-a-5-17-authentication-information)Authentication information-Not coveredAuthentication information (secrets) management procedure[A.5.18](/blog/iso-27001-a-5-18-access-rights)Access rights[CC6.2](/blog/soc-2-cc6-2-user-access-provisioning)Full-A.5.19Information security in supplier relationships[CC9.2](/blog/soc-2-cc9-2-vendor-risk-management)Full-A.5.20Addressing information security within supplier agreements[CC9.2](/blog/soc-2-cc9-2-vendor-risk-management)Full-A.5.21Managing information security in the ICT supply chain-Not coveredICT supply chain security requirementsA.5.22Monitoring, review and change management of supplier services[CC9.2](/blog/soc-2-cc9-2-vendor-risk-management)Full-A.5.23Information security for use of cloud services-Not coveredCloud service security requirements and exit process[A.5.24](/blog/iso-27001-a-5-24-incident-management-planning)Information security incident management planning and preparation-Not coveredIncident management planning and preparation procedureA.5.25Assessment and decision on information security events[CC7.3](/blog/soc-2-cc7-3-security-event-evaluation)Full-A.5.26Response to information security incidents[CC7.4](/blog/soc-2-cc7-4-incident-response)Full-A.5.27Learning from information security incidents[CC7.5](/blog/soc-2-cc7-5-incident-recovery)Full-A.5.28Collection of evidence-Not coveredEvidence collection procedure for incidentsA.5.29Information security during disruption[CC7.5](/blog/soc-2-cc7-5-incident-recovery), [CC9.1](/blog/soc-2-cc9-1-business-disruption)Full-A.5.30ICT readiness for business continuity[CC7.5](/blog/soc-2-cc7-5-incident-recovery), [CC9.1](/blog/soc-2-cc9-1-business-disruption)Full-A.5.31Legal, statutory, regulatory and contractual requirements[CC2.3](/blog/soc-2-cc2-3-external-communication)Partial-A.5.32Intellectual property rights-Not coveredIntellectual property rights procedureA.5.33Protection of records-Not coveredRecords retention and protection scheduleA.5.34Privacy and protection of PII-Not coveredPrivacy and PII protection procedureA.5.35Independent review of information security[CC4.1](/blog/soc-2-cc4-1-monitoring-evaluations), [CC4.2](/blog/soc-2-cc4-2-deficiency-communication)Partial-A.5.36Compliance with policies, rules and standards for information security-Not coveredInternal compliance review against policies and standardsA.5.37Documented operating procedures[CC5.3](/blog/soc-2-cc5-3-policies-procedures)Full-

The full ISO 27001 to SOC 2 mapping, in both directions, is a live Google Sheet. When the mapping is updated, everyone with the link sees the current version.

Free · Google Sheet

SOC 2 & ISO 27001 Control Mapping

Every SOC 2 Common Criterion mapped to ISO 27001:2022 Annex A, all 93 Annex A controls mapped back to SOC 2 with what a SOC 2 holder still has to build, and two sample control sets, kept current in a shared Google Sheet. Enter your email to open it.

(function initLmMapping(){ 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(initLmMapping, 200); } })();

Key insight

**Notable gap in A.5.21**

Managing information security in the ICT supply chain goes further than SOC 2's vendor management requirements. It requires an inventory of ICT suppliers, security requirements embedded in procurement contracts, and procedures for managing supplier-induced security incidents throughout the supply chain.

## People Controls: A.6.1 to A.6.8

4 of the 8 ISO 27001 people controls map directly to a SOC 2 Security criterion. Screening, terms and conditions of employment, awareness training, and the disciplinary process (A.6.1 to A.6.4) map to CC1.1, CC1.4, CC1.5, and CC2.2. A.6.4 (disciplinary process) is Partial, because CC1.1 and CC1.5 each carry a Partial overlap rating.
Annex A controlControl nameSOC 2 criteria that map to itCoverageWhat a SOC 2 holder still has to buildA.6.1Screening[CC1.4](/blog/soc-2-cc1-4-commitment-to-competence)Full-A.6.2Terms and conditions of employment[CC1.4](/blog/soc-2-cc1-4-commitment-to-competence)Full-A.6.3Information security awareness, education and training[CC1.4](/blog/soc-2-cc1-4-commitment-to-competence), [CC2.2](/blog/soc-2-cc2-2-internal-communication)Full-A.6.4Disciplinary process[CC1.1](/blog/soc-2-cc1-1-integrity-ethical-values), [CC1.5](/blog/soc-2-cc1-5-accountability)Partial-A.6.5Responsibilities after termination or change of employment-Not coveredPost-termination responsibilities clauseA.6.6Confidentiality or non-disclosure agreements-Not coveredConfidentiality / NDA registerA.6.7Remote working-Not coveredRemote working policyA.6.8Information security event reporting-Not coveredInformation security event reporting channel

## Physical Controls: A.7.1 to A.7.14

4 of the 14 ISO 27001 physical controls map directly to a SOC 2 Security criterion. Perimeter, entry, storage media, and secure disposal (A.7.1, A.7.2, A.7.10, A.7.14) map to CC6.4 and CC6.5.
Annex A controlControl nameSOC 2 criteria that map to itCoverageWhat a SOC 2 holder still has to buildA.7.1Physical security perimeters[CC6.4](/blog/soc-2-cc6-4-physical-access)Full-A.7.2Physical entry[CC6.4](/blog/soc-2-cc6-4-physical-access)Full-A.7.3Securing offices, rooms and facilities-Not coveredSecure facilities and room designationA.7.4Physical security monitoring-Not coveredPhysical security monitoring (e.g. CCTV, alarms)A.7.5Protecting against physical and environmental threats-Not coveredEnvironmental threat protection assessmentA.7.6Working in secure areas-Not coveredSecure area working rulesA.7.7Clear desk and clear screen-Not coveredClear desk and clear screen policyA.7.8Equipment siting and protection-Not coveredEquipment siting and protection standardA.7.9Security of assets off-premises-Not coveredOff-premises asset security procedureA.7.10Storage media[CC6.5](/blog/soc-2-cc6-5-asset-disposal)Full-A.7.11Supporting utilities-Not coveredSupporting utilities resilience (power, HVAC)A.7.12Cabling security-Not coveredCabling security standardA.7.13Equipment maintenance-Not coveredEquipment maintenance schedule and recordsA.7.14Secure disposal or re-use of equipment[CC6.5](/blog/soc-2-cc6-5-asset-disposal)Full-

Key insight

**Notable gap for SaaS organizations**

The ten [physical controls without a direct SOC 2 criterion](https://truvocyber.com/blog/soc-2-iso-27001-hipaa-infrastructure-providers) split into two situations.

- **Data center controls:** A.7.5, A.7.11, A.7.12, and A.7.13 apply to data center infrastructure. For SaaS organizations with no on-premises servers, these are typically marked as applicable in the Statement of Applicability, with the cloud provider's SOC 2 report or ISO 27001 certificate as supporting evidence, a justification statement, and a review of what the provider's controls cover.
- **Office and device controls:** A.7.7 (clear desk and clear screen) and A.7.8 (equipment siting and protection) apply to the organization's own office and employee devices. An ISO auditor will expect a clear desk policy and documented equipment handling procedures wherever the servers are hosted.

## Technological Controls: A.8.1 to A.8.34

12 of the 34 ISO 27001 technological controls map directly to a SOC 2 Security criterion: privileged access (A.8.2), malware protection (A.8.7), technical vulnerabilities (A.8.8), configuration management (A.8.9), data leakage prevention (A.8.12), logging and monitoring (A.8.15, A.8.16), software installation (A.8.19), network security and web filtering (A.8.20, A.8.23), cryptography (A.8.24), and change management (A.8.32). A.8.9 (configuration management) is Partial, because its only mapped criterion, CC5.2, carries a Partial overlap rating.
Annex A controlControl nameSOC 2 criteria that map to itCoverageWhat a SOC 2 holder still has to build[A.8.1](/blog/iso-27001-a-8-1-endpoint-devices)User endpoint devices-Not coveredUser endpoint device standard[A.8.2](/blog/iso-27001-a-8-2-privileged-access-rights)Privileged access rights[CC6.1](/blog/soc-2-cc6-1-logical-access-security), [CC6.3](/blog/soc-2-cc6-3-least-privilege-rbac)Full-[A.8.3](/blog/iso-27001-a-8-3-information-access-restriction)Information access restriction-Not covered-[A.8.4](/blog/iso-27001-a-8-4-access-to-source-code)Access to source code-Not coveredSource code access control procedure[A.8.5](/blog/iso-27001-a-8-5-secure-authentication)Secure authentication-Not coveredSecure authentication standardA.8.6Capacity management-Not coveredCapacity management plan[A.8.7](/blog/iso-27001-a-8-7-malware-protection)Protection against malware[CC6.6](/blog/soc-2-cc6-6-boundary-protection), [CC6.8](/blog/soc-2-cc6-8-malware-prevention)Full-[A.8.8](/blog/iso-27001-a-8-8-technical-vulnerabilities)Management of technical vulnerabilities[CC7.1](/blog/soc-2-cc7-1-vulnerability-management)Full-[A.8.9](/blog/iso-27001-a-8-9-configuration-management)Configuration management[CC5.2](/blog/soc-2-cc5-2-technology-general-controls)Partial-A.8.10Information deletion-Not coveredInformation deletion procedureA.8.11Data masking-Not coveredData masking standard[A.8.12](/blog/iso-27001-a-8-12-data-leakage-prevention)Data leakage prevention[CC6.7](/blog/soc-2-cc6-7-data-transmission)Full-[A.8.13](/blog/iso-27001-a-8-13-information-backup)Information backup-Not coveredInformation backup procedureA.8.14Redundancy of information processing facilities-Not coveredRedundancy design for processing facilities[A.8.15](/blog/iso-27001-a-8-15-logging)Logging[CC7.2](/blog/soc-2-cc7-2-security-monitoring)Full-[A.8.16](/blog/iso-27001-a-8-16-monitoring-activities)Monitoring activities[CC4.2](/blog/soc-2-cc4-2-deficiency-communication), [CC7.1](/blog/soc-2-cc7-1-vulnerability-management), [CC7.2](/blog/soc-2-cc7-2-security-monitoring)Full-A.8.17Clock synchronization-Not coveredClock synchronization standardA.8.18Use of privileged utility programs-Not coveredPrivileged utility program controlsA.8.19Installation of software on operational systems[CC6.8](/blog/soc-2-cc6-8-malware-prevention)Full-[A.8.20](/blog/iso-27001-a-8-20-network-security)Networks security[CC6.6](/blog/soc-2-cc6-6-boundary-protection)Full-A.8.21Security of network services-Not coveredNetwork services security requirementsA.8.22Segregation of networks-Not coveredNetwork segregation designA.8.23Web filtering[CC6.6](/blog/soc-2-cc6-6-boundary-protection)Full-[A.8.24](/blog/iso-27001-a-8-24-use-of-cryptography)Use of cryptography[CC6.1](/blog/soc-2-cc6-1-logical-access-security), [CC6.7](/blog/soc-2-cc6-7-data-transmission)Full-[A.8.25](/blog/iso-27001-a-8-25-secure-development-lifecycle)Secure development life cycle-Not coveredSecure development life cycle procedureA.8.26Application security requirements-Not coveredApplication security requirements specificationA.8.27Secure system architecture and engineering principles-Not coveredSecure system architecture and engineering principles[A.8.28](/blog/iso-27001-a-8-28-secure-coding)Secure coding-Not coveredSecure coding standardA.8.29Security testing in development and acceptance-Not coveredSecurity testing plan for development and acceptanceA.8.30Outsourced development-Not coveredOutsourced development security requirementsA.8.31Separation of development, test and production environments-Not coveredSeparation of development, test and production environments[A.8.32](/blog/iso-27001-a-8-32-change-management)Change management[CC8.1](/blog/soc-2-cc8-1-change-management)Full-A.8.33Test information-Not coveredTest data protection procedureA.8.34Protection of information systems during audit testing-Not coveredAudit testing protection procedure

## What Percentage of ISO 27001:2022 Annex A Does SOC 2 Cover?

In our mapping spreadsheet, the SOC 2 Security criteria (CC1 to CC9) map directly to 40 of the 93 Annex A controls, about 43 percent. The other 53 have no direct Security criterion and count as new work for a SOC 2 holder, alongside the ISMS clauses in the next section.
Annex A themeControlsCovered directly by SOC 2 Security criteriaFullPartialNo direct SOC 2 criterionOrganizational (A.5)3720 (54%)16417People (A.6)84 (50%)314Physical (A.7)144 (29%)4010Technological (A.8)3412 (35%)11122**Total****93****40 (43%)****34****6****53**

The 53 Annex A controls without a direct SOC 2 criterion, by theme:

- **Organizational (A.5), 17 controls:** A.5.4, A.5.5, A.5.7, A.5.9, A.5.10, A.5.12, A.5.13, A.5.14, A.5.17, A.5.21, A.5.23, A.5.24, A.5.28, A.5.32, A.5.33, A.5.34, and A.5.36
- **People (A.6), 4 controls:** A.6.5 (responsibilities after termination), A.6.6 (confidentiality agreements), A.6.7 (remote working), and A.6.8 (event reporting)
- **Physical (A.7), 10 controls:** A.7.3 to A.7.9 and A.7.11 to A.7.13
- **Technological (A.8), 22 controls:** A.8.1, A.8.3 to A.8.6, A.8.10, A.8.11, A.8.13, A.8.14, A.8.17, A.8.18, A.8.21, A.8.22, A.8.25 to A.8.31, A.8.33, and A.8.34

Key insight

**What covered means in the ISO 27001 to SOC 2 mapping**

The spreadsheet counts a control as covered only when a SOC 2 Security criterion maps to it directly. Many of the other 53 still benefit from SOC 2 work: Availability criteria produce evidence for capacity, backup, and redundancy (A.8.6, A.8.13, A.8.14), Confidentiality criteria for classification and labelling (A.5.12, A.5.13), and existing authentication and secure development controls often go a long way toward A.8.5 and A.8.25. Treat that as partial reuse, and confirm every control in the Statement of Applicability with your certification body.

## What ISO 27001 Adds Beyond the Annex A Controls

ISO 27001 also requires the ISMS management clauses, which have no SOC 2 equivalent:

- **Clause 6.1.3, Statement of Applicability:** lists all necessary controls, the justification for including each, whether each is implemented, and the justification for excluding any Annex A controls.
- **Clause 9.2, internal audit programme:** a documented programme with defined frequency, methods, responsibilities, planning requirements, and reporting.
- **Clause 9.3, management review:** documented reviews at planned intervals with required inputs and documented decisions on continual improvement.
- **Clause 10.2, nonconformity and corrective action:** a documented process for identifying nonconformities, determining causes, implementing corrective actions, and reviewing their effectiveness.

The [SOC 2 to ISO 27001 control mapping](/blog/iso-27001-soc-2-control-mapping) covers each clause in detail, including the required management review inputs.

Key insight

**ISO 27001 timeline for SOC 2 holders**

The typical timeline to [ISO 27001 certification](https://truvocyber.com/services/iso-27001-certification) is 4 to 6 months for organizations with a mature SOC 2 program, compared with 9 to 12 months from scratch. Most of that time goes to building the ISMS management artifacts, completing an internal audit cycle, and scheduling the Stage 1 and Stage 2 external audits. An independent [ISO 27001 internal auditor](/iso-internal-audit) can run that audit cycle and write the Clause 9.2 report.

The [SOC 2 vs ISO 27001 comparison](/blog/soc-2-vs.iso-27001-key-differences-shared-efficiencies) covers how the two frameworks relate, including audit mechanics, certification timelines, and what carries over.

For a customer or contract deadline, the [ISO 27001 Accelerator](https://truvocyber.com/iso-27001-accelerator) is a fixed-price program that aims for certification-ready in eight weeks.

### Adding ISO 27001 to SOC 2?

We map what transfers and build only the net-new work toward an effective security program.[Book Your Strategy Call](/contact-us)

## Frequently Asked Questions About ISO 27001 to SOC 2 Mapping

### How many ISO 27001 Annex A controls map to SOC 2?

In our mapping spreadsheet, the SOC 2 Security criteria (CC1 to CC9) map directly to 40 of the 93 ISO 27001:2022 Annex A controls, about 43 percent: 20 of 37 organizational, 4 of 8 people, 4 of 14 physical, and 12 of 34 technological. Of the 40, 34 are Full and 6 are Partial. The other 53 count as new work for a SOC 2 holder.

### Which ISO 27001 controls have no SOC 2 equivalent?

In our mapping spreadsheet, 53 of the 93 Annex A controls have no direct SOC 2 Security criterion: 17 organizational, 4 people, 10 physical, and 22 technological. The tables above list each one with what a SOC 2 holder still has to build, such as threat intelligence (A.5.7), classification and labelling (A.5.12, A.5.13), and secure coding (A.8.28).

### Can SOC 2 evidence be used for the ISO 27001 certification audit?

Yes, for the 40 Annex A controls a SOC 2 Security criterion maps to directly. Where the mapping is Full (34 controls), the same log or record goes into both audit packages. Where it is Partial (6 controls), existing evidence is a starting point that needs supplementing. The ISMS documents are ISO-specific and need to be built: the Statement of Applicability, internal audit reports, and management review records.

### What is the difference between ISO 27001 and ISO 27002 in a SOC 2 mapping?

ISO 27001 defines the requirements for an information security management system and is what organizations certify against. ISO 27002 is the companion implementation guide, using the same 93 controls and the same numbering (5.x through 8.x). A mapping of ISO 27002 controls to SOC 2 uses the same Annex A structure as this post.

### Does adding Availability or Confidentiality increase ISO 27001 overlap?

Yes. In our mapping spreadsheet, the Security criteria alone map directly to 40 of 93 Annex A controls. Availability criteria add evidence for capacity, backup, and redundancy (A.8.6, A.8.13, A.8.14), and Confidentiality criteria add evidence for classification and labelling (A.5.12, A.5.13) and partial coverage of data masking (A.8.11). Confirm each control in the Statement of Applicability.

### Is there a spreadsheet version of the ISO 27001 to SOC 2 mapping?

Yes. The full mapping is a live Google Sheet that covers both directions: SOC 2 criteria to Annex A, and all 93 Annex A controls back to SOC 2 with what a SOC 2 holder still has to build. Google Sheets can export it to Excel through File, Download, Microsoft Excel.

## Further Reading

- [SOC 2 to ISO 27001 Control Mapping: What Transfers](/blog/iso-27001-soc-2-control-mapping): the same mapping starting from each SOC 2 criterion, across all five Trust Services Criteria
- [SOC 2 vs ISO 27001: What Carries Over and How to Do Both](/blog/soc-2-vs.iso-27001-key-differences-shared-efficiencies): scope differences, certification mechanics, and sequencing decisions
- [SOC 2 Trust Services Criteria: A Practitioner's Guide](/blog/soc-2-trust-services-criteria-guide): what each criterion requires
- [Building SOC 2 Evidence Architecture](/blog/soc2-security-documentation): how to design evidence collection so the same records serve multiple frameworks

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How many ISO 27001 Annex A controls map to SOC 2?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "In our mapping spreadsheet, the SOC 2 Security criteria (CC1 to CC9) map directly to 40 of the 93 ISO 27001:2022 Annex A controls, about 43 percent: 20 of 37 organizational, 4 of 8 people, 4 of 14 physical, and 12 of 34 technological. Of the 40, 34 are Full and 6 are Partial. The other 53 count as new work for a SOC 2 holder."
      }
    },
    {
      "@type": "Question",
      "name": "Which ISO 27001 controls have no SOC 2 equivalent?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "In our mapping spreadsheet, 53 of the 93 Annex A controls have no direct SOC 2 Security criterion: 17 organizational, 4 people, 10 physical, and 22 technological. The tables above list each one with what a SOC 2 holder still has to build, such as threat intelligence (A.5.7), classification and labelling (A.5.12, A.5.13), and secure coding (A.8.28)."
      }
    },
    {
      "@type": "Question",
      "name": "Can SOC 2 evidence be used for the ISO 27001 certification audit?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, for the 40 Annex A controls a SOC 2 Security criterion maps to directly. Where the mapping is Full (34 controls), the same log or record goes into both audit packages. Where it is Partial (6 controls), existing evidence is a starting point that needs supplementing. The ISMS documents are ISO-specific and need to be built: the Statement of Applicability, internal audit reports, and management review records."
      }
    },
    {
      "@type": "Question",
      "name": "What is the difference between ISO 27001 and ISO 27002 in a SOC 2 mapping?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "ISO 27001 defines the requirements for an information security management system and is what organizations certify against. ISO 27002 is the companion implementation guide, using the same 93 controls and the same numbering (5.x through 8.x). A mapping of ISO 27002 controls to SOC 2 uses the same Annex A structure as this post."
      }
    },
    {
      "@type": "Question",
      "name": "Does adding Availability or Confidentiality increase ISO 27001 overlap?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. In our mapping spreadsheet, the Security criteria alone map directly to 40 of 93 Annex A controls. Availability criteria add evidence for capacity, backup, and redundancy (A.8.6, A.8.13, A.8.14), and Confidentiality criteria add evidence for classification and labelling (A.5.12, A.5.13) and partial coverage of data masking (A.8.11). Confirm each control in the Statement of Applicability."
      }
    },
    {
      "@type": "Question",
      "name": "Is there a spreadsheet version of the ISO 27001 to SOC 2 mapping?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. The full mapping is a live Google Sheet that covers both directions: SOC 2 criteria to Annex A, and all 93 Annex A controls back to SOC 2 with what a SOC 2 holder still has to build. Google Sheets can export it to Excel through File, Download, Microsoft Excel."
      }
    }
  ]
}
