Crossfoot / Crosswalks / SOC 2 to ISO 27001:2022
Draft v0.1.029 of 29 objectives have a direct match
SOC 2 to ISO 27001:2022 crosswalk
29 control objectives in SOC 2 Trust Services Criteria are mapped here to ISO/IEC 27001 (Annex A controls and management clauses). Every one has a requirement on the other side. Each row is one shared objective, with the requirement ids on both sides.
| Control objective | SOC 2 | ISO 27001:2022 |
|---|---|---|
| Security governance and policies | CC1.1Demonstrates commitment to integrity and ethical valuesCC1.2Board exercises oversight responsibilityCC5.3Deploys control activities through policies and procedures | A.5.1Policies for information securityA.5.36Compliance with policies, rules and standards for information security |
| Security roles and accountability | CC1.3Establishes structure, authority and responsibilityCC1.5Enforces accountability | A.5.2Information security roles and responsibilitiesA.5.3Segregation of duties |
| Risk assessment and treatment | CC3.1Specifies suitable objectivesCC3.2Identifies and analyzes riskCC3.3Considers potential for fraudCC3.4Identifies and assesses significant changes | Clause 6.1.2Information security risk assessmentClause 6.1.3Information security risk treatment |
| Asset and system inventory | CC6.1Logical access security (inventory of information assets is a point of focus) | A.5.9Inventory of information and other associated assets |
| Data classification and handling | C1.1Identifies and maintains confidential information | A.5.12Classification of informationA.5.13Labelling of information |
| Access provisioning, review and removal | CC6.2Registers and authorizes new users prior to issuing credentialsCC6.3Authorizes, modifies or removes access based on roles | A.5.15Access controlA.5.16Identity managementA.5.18Access rights |
| Least privilege and privileged access | CC6.3Role-based access and least privilege | A.8.2Privileged access rightsA.8.3Information access restriction |
| Authentication, unique IDs and multi-factor authentication | CC6.1Logical access security software, infrastructure and architectures | A.5.17Authentication informationA.8.5Secure authentication |
| Encryption at rest and key management | CC6.1Logical access security (encryption of data at rest) | A.8.24Use of cryptography |
| Encryption in transit | CC6.7Restricts transmission, movement and removal of information | A.5.14Information transferA.8.24Use of cryptography |
| Network security and segmentation | CC6.6Implements logical access security measures against threats from outside system boundaries | A.8.20Networks securityA.8.21Security of network servicesA.8.22Segregation of networks |
| Secure configuration and hardening | CC7.1Uses detection and monitoring procedures to identify changes to configurations | A.8.9Configuration management |
| Vulnerability scanning and patching | CC7.1Detection and monitoring procedures identify vulnerabilities | A.8.8Management of technical vulnerabilities |
| Penetration testing and independent assessment | CC4.1Selects, develops and performs ongoing and/or separate evaluationsCC7.1Detection and monitoring procedures | A.8.29Security testing in development and acceptanceA.5.35Independent review of information security |
| Logging, log review and monitoring | CC7.2Monitors system components for anomalies indicative of malicious acts, natural disasters and errors | A.8.15LoggingA.8.16Monitoring activitiesA.8.17Clock synchronization |
| Intrusion detection and integrity monitoring | CC7.2Monitors system components for anomaliesCC6.8Prevents or detects unauthorized or malicious software | A.8.16Monitoring activities |
| Malware protection | CC6.8Implements controls to prevent or detect and act upon the introduction of unauthorized or malicious software | A.8.7Protection against malware |
| Incident response and breach notification | CC7.3Evaluates security events to determine whether they are incidentsCC7.4Responds to identified security incidentsCC7.5Identifies, develops and implements activities to recover from incidents | A.5.24Information security incident management planning and preparationA.5.25Assessment and decision on information security eventsA.5.26Response to information security incidentsA.5.27Learning from information security incidents |
| Change management | CC8.1Authorizes, designs, develops, configures, documents, tests, approves and implements changes | A.8.32Change management |
| Secure software development | CC8.1Changes are developed, tested and approved | A.8.25Secure development life cycleA.8.26Application security requirementsA.8.28Secure codingA.8.29Security testing in development and acceptanceA.8.31Separation of development, test and production environments |
| Third-party and vendor risk management | CC9.2Assesses and manages risks associated with vendors and business partners | A.5.19Information security in supplier relationshipsA.5.20Addressing information security within supplier agreementsA.5.21Managing information security in the ICT supply chainA.5.22Monitoring, review and change management of supplier servicesA.5.23Information security for use of cloud services |
| Business continuity and disaster recovery | CC9.1Identifies, selects and develops risk mitigation activities for business disruptionsA1.2Environmental protections, software, data backup processes and recovery infrastructureA1.3Tests recovery plan procedures | A.5.29Information security during disruptionA.5.30ICT readiness for business continuity |
| Backup and redundancy | A1.2Data backup processes and recovery infrastructure | A.8.13Information backupA.8.14Redundancy of information processing facilities |
| Capacity and availability management | A1.1Maintains, monitors and evaluates current processing capacity | A.8.6Capacity management |
| Security awareness and training | CC1.4Demonstrates commitment to attract, develop and retain competent individualsCC2.2Internally communicates information necessary to support internal control | A.6.3Information security awareness, education and training |
| Personnel screening, terms and sanctions | CC1.4Hiring and competence practicesCC6.3Removes access on termination | A.6.1ScreeningA.6.2Terms and conditions of employmentA.6.4Disciplinary processA.6.5Responsibilities after termination or change of employment |
| Physical access and facility security | CC6.4Restricts physical access to facilities and protected information assets | A.7.1Physical security perimetersA.7.2Physical entryA.7.4Physical security monitoring |
| Data retention, media handling and secure disposal | CC6.5Discontinues logical and physical protections over assets only after the ability to read or recover data is diminishedC1.2Disposes of confidential information | A.7.10Storage mediaA.7.14Secure disposal or re-use of equipmentA.8.10Information deletion |
| Ongoing control monitoring and internal audit | CC4.1Selects, develops and performs ongoing and/or separate evaluationsCC4.2Evaluates and communicates internal control deficiencies | Clause 9.2Internal auditClause 9.3Management review |
Open a control objective for the evidence checklist.ISO 27001:2022 to SOC 2 →
Scope: Security (CC series), Availability (A1) and Confidentiality (C1). Processing Integrity and Privacy are not covered in this dataset version. Annex A controls are prefixed 'A.'; management-system clauses are prefixed 'Clause'. A mapping means the requirements address the same objective. It does not mean satisfying one satisfies the other, because scope, frequency and evidence rules differ.