Crossfoot / Crosswalks / ISO 27001:2022 to NIST 800-53 r5
Draft v0.1.029 of 29 objectives have a direct match
ISO 27001:2022 to NIST 800-53 r5 crosswalk
29 control objectives in ISO/IEC 27001 (Annex A controls and management clauses) are mapped here to NIST SP 800-53 Security and Privacy Controls. Every one has a requirement on the other side. Each row is one shared objective, with the requirement ids on both sides.
| Control objective | ISO 27001:2022 | NIST 800-53 r5 |
|---|---|---|
| Security governance and policies | A.5.1Policies for information securityA.5.36Compliance with policies, rules and standards for information security | PM-1Information security program planPL-1Policy and procedures (planning) |
| Security roles and accountability | A.5.2Information security roles and responsibilitiesA.5.3Segregation of duties | PM-2Information security program leadership roleAC-5Separation of duties |
| Risk assessment and treatment | Clause 6.1.2Information security risk assessmentClause 6.1.3Information security risk treatment | RA-3Risk assessmentPM-9Risk management strategy |
| Asset and system inventory | A.5.9Inventory of information and other associated assets | CM-8System component inventory |
| Data classification and handling | A.5.12Classification of informationA.5.13Labelling of information | RA-2Security categorization |
| Access provisioning, review and removal | A.5.15Access controlA.5.16Identity managementA.5.18Access rights | AC-2Account managementAC-3Access enforcementPS-4Personnel terminationPS-5Personnel transfer |
| Least privilege and privileged access | A.8.2Privileged access rightsA.8.3Information access restriction | AC-6Least privilegeAC-5Separation of duties |
| Authentication, unique IDs and multi-factor authentication | A.5.17Authentication informationA.8.5Secure authentication | IA-2Identification and authentication (organizational users)IA-5Authenticator management |
| Encryption at rest and key management | A.8.24Use of cryptography | SC-28Protection of information at restSC-12Cryptographic key establishment and managementSC-13Cryptographic protection |
| Encryption in transit | A.5.14Information transferA.8.24Use of cryptography | SC-8Transmission confidentiality and integritySC-13Cryptographic protection |
| Network security and segmentation | A.8.20Networks securityA.8.21Security of network servicesA.8.22Segregation of networks | SC-7Boundary protectionAC-4Information flow enforcement |
| Secure configuration and hardening | A.8.9Configuration management | CM-2Baseline configurationCM-6Configuration settingsCM-7Least functionality |
| Vulnerability scanning and patching | A.8.8Management of technical vulnerabilities | RA-5Vulnerability monitoring and scanningSI-2Flaw remediation |
| Penetration testing and independent assessment | A.8.29Security testing in development and acceptanceA.5.35Independent review of information security | CA-8Penetration testingCA-2Control assessments |
| Logging, log review and monitoring | A.8.15LoggingA.8.16Monitoring activitiesA.8.17Clock synchronization | AU-2Event loggingAU-6Audit record review, analysis and reportingAU-11Audit record retentionSI-4System monitoring |
| Intrusion detection and integrity monitoring | A.8.16Monitoring activities | SI-4System monitoringSI-7Software, firmware and information integrity |
| Malware protection | A.8.7Protection against malware | SI-3Malicious code protection |
| Incident response and breach notification | 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 | IR-4Incident handlingIR-8Incident response planIR-6Incident reportingIR-3Incident response testing |
| Change management | A.8.32Change management | CM-3Configuration change controlCM-4Impact analysesCM-5Access restrictions for change |
| Secure software development | 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 | SA-3System development life cycleSA-8Security and privacy engineering principlesSA-11Developer testing and evaluation |
| Third-party and vendor 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 | SR-3Supply chain controls and processesSR-6Supplier assessments and reviewsSA-9External system services |
| Business continuity and disaster recovery | A.5.29Information security during disruptionA.5.30ICT readiness for business continuity | CP-2Contingency planCP-4Contingency plan testingCP-10System recovery and reconstitution |
| Backup and redundancy | A.8.13Information backupA.8.14Redundancy of information processing facilities | CP-9System backup |
| Capacity and availability management | A.8.6Capacity management | SC-5Denial-of-service protection |
| Security awareness and training | A.6.3Information security awareness, education and training | AT-2Literacy training and awarenessAT-3Role-based training |
| Personnel screening, terms and sanctions | A.6.1ScreeningA.6.2Terms and conditions of employmentA.6.4Disciplinary processA.6.5Responsibilities after termination or change of employment | PS-3Personnel screeningPS-4Personnel terminationPS-8Personnel sanctions |
| Physical access and facility security | A.7.1Physical security perimetersA.7.2Physical entryA.7.4Physical security monitoring | PE-2Physical access authorizationsPE-3Physical access controlPE-6Monitoring physical access |
| Data retention, media handling and secure disposal | A.7.10Storage mediaA.7.14Secure disposal or re-use of equipmentA.8.10Information deletion | MP-6Media sanitizationSI-12Information management and retention |
| Ongoing control monitoring and internal audit | Clause 9.2Internal auditClause 9.3Management review | CA-2Control assessmentsCA-7Continuous monitoring |
Open a control objective for the evidence checklist.NIST 800-53 r5 to ISO 27001:2022 →
Scope: Annex A controls are prefixed 'A.'; management-system clauses are prefixed 'Clause'. Base controls only (no enhancements). FedRAMP, TX-RAMP and StateRAMP baselines are built on 800-53, but baseline membership and parameters are not included here. 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.