Crossfoot / Crosswalks / NIST CSF 2.0 to SOC 2
Draft v0.1.029 of 29 objectives have a direct match
NIST CSF 2.0 to SOC 2 crosswalk
29 control objectives in NIST Cybersecurity Framework are mapped here to SOC 2 Trust Services Criteria. Every one has a requirement on the other side. Each row is one shared objective, with the requirement ids on both sides.
| Control objective | NIST CSF 2.0 | SOC 2 |
|---|---|---|
| Security governance and policies | GV.POPolicyGV.OVOversight | CC1.1Demonstrates commitment to integrity and ethical valuesCC1.2Board exercises oversight responsibilityCC5.3Deploys control activities through policies and procedures |
| Security roles and accountability | GV.RRRoles, responsibilities and authorities | CC1.3Establishes structure, authority and responsibilityCC1.5Enforces accountability |
| Risk assessment and treatment | GV.RMRisk management strategyID.RARisk assessment | CC3.1Specifies suitable objectivesCC3.2Identifies and analyzes riskCC3.3Considers potential for fraudCC3.4Identifies and assesses significant changes |
| Asset and system inventory | ID.AMAsset management | CC6.1Logical access security (inventory of information assets is a point of focus) |
| Data classification and handling | ID.AM-07Inventories of data and corresponding metadata are maintainedPR.DSData security | C1.1Identifies and maintains confidential information |
| Access provisioning, review and removal | PR.AA-05Access permissions, entitlements and authorizations are defined and managed (least privilege, separation of duties) | CC6.2Registers and authorizes new users prior to issuing credentialsCC6.3Authorizes, modifies or removes access based on roles |
| Least privilege and privileged access | PR.AA-05Access permissions managed incorporating least privilege | CC6.3Role-based access and least privilege |
| Authentication, unique IDs and multi-factor authentication | PR.AA-03Users, services and hardware are authenticated | CC6.1Logical access security software, infrastructure and architectures |
| Encryption at rest and key management | PR.DS-01The confidentiality, integrity and availability of data-at-rest are protected | CC6.1Logical access security (encryption of data at rest) |
| Encryption in transit | PR.DS-02The confidentiality, integrity and availability of data-in-transit are protected | CC6.7Restricts transmission, movement and removal of information |
| Network security and segmentation | PR.IR-01Networks and environments are protected from unauthorized logical access and usage | CC6.6Implements logical access security measures against threats from outside system boundaries |
| Secure configuration and hardening | PR.PS-01Configuration management practices are established and applied | CC7.1Uses detection and monitoring procedures to identify changes to configurations |
| Vulnerability scanning and patching | ID.RARisk assessment (vulnerability identification, ID.RA-01)PR.PS-02Software is maintained, replaced and removed commensurate with risk | CC7.1Detection and monitoring procedures identify vulnerabilities |
| Penetration testing and independent assessment | ID.IMImprovement (incl. ID.IM-02, improvements from tests and exercises) | CC4.1Selects, develops and performs ongoing and/or separate evaluationsCC7.1Detection and monitoring procedures |
| Logging, log review and monitoring | DE.CMContinuous monitoringPR.PS-04Log records are generated and made available for continuous monitoring | CC7.2Monitors system components for anomalies indicative of malicious acts, natural disasters and errors |
| Intrusion detection and integrity monitoring | DE.CMContinuous monitoringDE.AEAdverse event analysis | CC7.2Monitors system components for anomaliesCC6.8Prevents or detects unauthorized or malicious software |
| Malware protection | PR.PS-05Installation and execution of unauthorized software are preventedDE.CMContinuous monitoring | CC6.8Implements controls to prevent or detect and act upon the introduction of unauthorized or malicious software |
| Incident response and breach notification | RS.MAIncident managementRS.ANIncident analysisRS.COIncident response reporting and communicationRS.MIIncident mitigationDE.AEAdverse event analysis | CC7.3Evaluates security events to determine whether they are incidentsCC7.4Responds to identified security incidentsCC7.5Identifies, develops and implements activities to recover from incidents |
| Change management | PR.PS-01Configuration management practices are established and applied | CC8.1Authorizes, designs, develops, configures, documents, tests, approves and implements changes |
| Secure software development | PR.PS-06Secure software development practices are integrated and their performance monitored | CC8.1Changes are developed, tested and approved |
| Third-party and vendor risk management | GV.SCCybersecurity supply chain risk management | CC9.2Assesses and manages risks associated with vendors and business partners |
| Business continuity and disaster recovery | PR.IR-03Mechanisms are implemented to achieve resilience requirementsRC.RPIncident recovery plan execution | CC9.1Identifies, selects and develops risk mitigation activities for business disruptionsA1.2Environmental protections, software, data backup processes and recovery infrastructureA1.3Tests recovery plan procedures |
| Backup and redundancy | PR.DS-11Backups of data are created, protected, maintained and tested | A1.2Data backup processes and recovery infrastructure |
| Capacity and availability management | PR.IR-04Adequate resource capacity to ensure availability is maintained | A1.1Maintains, monitors and evaluates current processing capacity |
| Security awareness and training | PR.ATAwareness and training | CC1.4Demonstrates commitment to attract, develop and retain competent individualsCC2.2Internally communicates information necessary to support internal control |
| Personnel screening, terms and sanctions | GV.RR-04Cybersecurity is included in human resources practices | CC1.4Hiring and competence practicesCC6.3Removes access on termination |
| Physical access and facility security | PR.AA-06Physical access to assets is managed, monitored and enforced commensurate with risk | CC6.4Restricts physical access to facilities and protected information assets |
| Data retention, media handling and secure disposal | ID.AM-08Systems, hardware, software, services and data are managed throughout their life cycles | CC6.5Discontinues logical and physical protections over assets only after the ability to read or recover data is diminishedC1.2Disposes of confidential information |
| Ongoing control monitoring and internal audit | ID.IMImprovementGV.OVOversight | CC4.1Selects, develops and performs ongoing and/or separate evaluationsCC4.2Evaluates and communicates internal control deficiencies |
Open a control objective for the evidence checklist.SOC 2 to NIST CSF 2.0 →
Scope: Mapped at category level (e.g. PR.AA) or subcategory where one is clearly the match (e.g. PR.AA-05). Security (CC series), Availability (A1) and Confidentiality (C1). Processing Integrity and Privacy are not covered in this dataset version. 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.