Crossfoot
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 objectiveNIST CSF 2.0ISO 27001:2022
Security governance and policies
GV.POPolicy
GV.OVOversight
A.5.1Policies for information security
A.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 responsibilities
A.5.3Segregation of duties
Risk assessment and treatment
GV.RMRisk management strategy
ID.RARisk assessment
Clause 6.1.2Information security risk assessment
Clause 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 maintained
PR.DSData security
A.5.12Classification of information
A.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 control
A.5.16Identity management
A.5.18Access rights
Least privilege and privileged access
PR.AA-05Access permissions managed incorporating least privilege
A.8.2Privileged access rights
A.8.3Information access restriction
Authentication, unique IDs and multi-factor authentication
PR.AA-03Users, services and hardware are authenticated
A.5.17Authentication information
A.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 transfer
A.8.24Use of cryptography
Network security and segmentation
PR.IR-01Networks and environments are protected from unauthorized logical access and usage
A.8.20Networks security
A.8.21Security of network services
A.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 acceptance
A.5.35Independent review of information security
Logging, log review and monitoring
DE.CMContinuous monitoring
PR.PS-04Log records are generated and made available for continuous monitoring
A.8.15Logging
A.8.16Monitoring activities
A.8.17Clock synchronization
Intrusion detection and integrity monitoring
DE.CMContinuous monitoring
DE.AEAdverse event analysis
A.8.16Monitoring activities
Malware protection
PR.PS-05Installation and execution of unauthorized software are prevented
DE.CMContinuous monitoring
A.8.7Protection against malware
Incident response and breach notification
RS.MAIncident management
RS.ANIncident analysis
RS.COIncident response reporting and communication
RS.MIIncident mitigation
DE.AEAdverse event analysis
A.5.24Information security incident management planning and preparation
A.5.25Assessment and decision on information security events
A.5.26Response to information security incidents
A.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 cycle
A.8.26Application security requirements
A.8.28Secure coding
A.8.29Security testing in development and acceptance
A.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 relationships
A.5.20Addressing information security within supplier agreements
A.5.21Managing information security in the ICT supply chain
A.5.22Monitoring, review and change management of supplier services
A.5.23Information security for use of cloud services
Business continuity and disaster recovery
PR.IR-03Mechanisms are implemented to achieve resilience requirements
RC.RPIncident recovery plan execution
A.5.29Information security during disruption
A.5.30ICT readiness for business continuity
Backup and redundancy
PR.DS-11Backups of data are created, protected, maintained and tested
A.8.13Information backup
A.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.1Screening
A.6.2Terms and conditions of employment
A.6.4Disciplinary process
A.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 perimeters
A.7.2Physical entry
A.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 media
A.7.14Secure disposal or re-use of equipment
A.8.10Information deletion
Ongoing control monitoring and internal audit
ID.IMImprovement
GV.OVOversight
Clause 9.2Internal audit
Clause 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.

More from NIST CSF 2.0