Crossfoot / Crosswalks / NIST CSF 2.0 to ISO 27001:2022
Draft v0.1.029 of 29 objectives have a direct match
NIST CSF 2.0 to ISO 27001:2022 crosswalk
29 control objectives in NIST Cybersecurity Framework 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 | NIST CSF 2.0 | ISO 27001:2022 |
|---|---|---|
| Security governance and policies | GV.POPolicyGV.OVOversight | A.5.1Policies for information securityA.5.36Compliance with policies, rules and standards for information security |
| Security roles and accountability | GV.RRRoles, responsibilities and authorities | A.5.2Information security roles and responsibilitiesA.5.3Segregation of duties |
| Risk assessment and treatment | GV.RMRisk management strategyID.RARisk assessment | Clause 6.1.2Information security risk assessmentClause 6.1.3Information security risk treatment |
| Asset and system inventory | ID.AMAsset management | A.5.9Inventory of information and other associated assets |
| Data classification and handling | ID.AM-07Inventories of data and corresponding metadata are maintainedPR.DSData security | A.5.12Classification of informationA.5.13Labelling of information |
| Access provisioning, review and removal | PR.AA-05Access permissions, entitlements and authorizations are defined and managed (least privilege, separation of duties) | A.5.15Access controlA.5.16Identity managementA.5.18Access rights |
| Least privilege and privileged access | PR.AA-05Access permissions managed incorporating least privilege | A.8.2Privileged access rightsA.8.3Information access restriction |
| Authentication, unique IDs and multi-factor authentication | PR.AA-03Users, services and hardware are authenticated | A.5.17Authentication informationA.8.5Secure authentication |
| Encryption at rest and key management | PR.DS-01The confidentiality, integrity and availability of data-at-rest are protected | A.8.24Use of cryptography |
| Encryption in transit | PR.DS-02The confidentiality, integrity and availability of data-in-transit are protected | A.5.14Information transferA.8.24Use of cryptography |
| Network security and segmentation | PR.IR-01Networks and environments are protected from unauthorized logical access and usage | A.8.20Networks securityA.8.21Security of network servicesA.8.22Segregation of networks |
| Secure configuration and hardening | PR.PS-01Configuration management practices are established and applied | A.8.9Configuration management |
| Vulnerability scanning and patching | ID.RARisk assessment (vulnerability identification, ID.RA-01)PR.PS-02Software is maintained, replaced and removed commensurate with risk | A.8.8Management of technical vulnerabilities |
| Penetration testing and independent assessment | ID.IMImprovement (incl. ID.IM-02, improvements from tests and exercises) | A.8.29Security testing in development and acceptanceA.5.35Independent review of information security |
| Logging, log review and monitoring | DE.CMContinuous monitoringPR.PS-04Log records are generated and made available for continuous monitoring | A.8.15LoggingA.8.16Monitoring activitiesA.8.17Clock synchronization |
| Intrusion detection and integrity monitoring | DE.CMContinuous monitoringDE.AEAdverse event analysis | A.8.16Monitoring activities |
| Malware protection | PR.PS-05Installation and execution of unauthorized software are preventedDE.CMContinuous monitoring | A.8.7Protection against malware |
| Incident response and breach notification | RS.MAIncident managementRS.ANIncident analysisRS.COIncident response reporting and communicationRS.MIIncident mitigationDE.AEAdverse event analysis | 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 | PR.PS-01Configuration management practices are established and applied | A.8.32Change management |
| Secure software development | PR.PS-06Secure software development practices are integrated and their performance monitored | 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 | GV.SCCybersecurity supply chain risk management | 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 | PR.IR-03Mechanisms are implemented to achieve resilience requirementsRC.RPIncident recovery plan execution | A.5.29Information security during disruptionA.5.30ICT readiness for business continuity |
| Backup and redundancy | PR.DS-11Backups of data are created, protected, maintained and tested | A.8.13Information backupA.8.14Redundancy of information processing facilities |
| Capacity and availability management | PR.IR-04Adequate resource capacity to ensure availability is maintained | A.8.6Capacity management |
| Security awareness and training | PR.ATAwareness and training | A.6.3Information security awareness, education and training |
| Personnel screening, terms and sanctions | GV.RR-04Cybersecurity is included in human resources practices | 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 | PR.AA-06Physical access to assets is managed, monitored and enforced commensurate with risk | A.7.1Physical security perimetersA.7.2Physical entryA.7.4Physical security monitoring |
| Data retention, media handling and secure disposal | ID.AM-08Systems, hardware, software, services and data are managed throughout their life cycles | A.7.10Storage mediaA.7.14Secure disposal or re-use of equipmentA.8.10Information deletion |
| Ongoing control monitoring and internal audit | ID.IMImprovementGV.OVOversight | Clause 9.2Internal auditClause 9.3Management review |
Open a control objective for the evidence checklist.ISO 27001:2022 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). 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.