← Frameworks / ISO 27002:2022 / Coverage Analysis

ISO/IEC 27002:2022 โ€” SP 800-53 Coverage

How well do NIST SP 800-53 Rev 5 controls address each ISO 27002:2022 requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.

Clauses: 93
Avg Coverage: 78.5%
Publisher: ISO/IEC
Coverage Distribution
Full (85-100%): 49 Substantial (65-84%): 37 Partial (40-64%): 4 Weak (1-39%): 1 None (0%): 2

Clause-by-Clause Analysis

Sorted by clause
5.1 Setting information security policies, including topic-specific ones

Rationale

SP 800-53 has a policy and procedures control (-01) in each family, and nearly all of them are mapped here. PL-01 is the overarching planning policy, and PM-01 establishes the program plan. SR-01 adds supply chain policy. Together they cover ISO 27002's call for a coherent policy framework with topic-specific policies.

Gaps

Minimal gap. SP 800-53 policy requirements are more granular (per-family) while ISO 27002 expects a coherent hierarchical policy set with explicit review triggers and communication channels.

5.2 Defining and assigning information security roles

Rationale

PM-02 assigns the senior security role. PS-01 covers personnel security roles. PS-09 (Position Descriptions) explicitly requires incorporating security and privacy roles and responsibilities into organizational position descriptions, directly addressing ISO 27002's requirement that all information security responsibilities are defined and allocated. Each family's policy control also addresses roles and responsibilities, and PS-07 sets them for external providers.

Gaps

Minor: ISO 27002 provides specific implementation guidance on asset owner responsibilities. SP 800-53 addresses through system owner concept in PL-02 but 'asset owner' role is less defined.

5.3 Segregation of duties between conflicting roles

Rationale

AC-05 directly addresses separation of duties including identifying conflicting duties and implementing compensating controls. Comprehensive alignment with ISO 27002's requirement.

Gaps

Minor: ISO 27002 provides detailed guidance on identifying conflicting duties across business processes. AC-05 is focused on system-level duty separation.

Mapped Controls

5.4 Management responsibilities: requiring staff to follow security policies

Rationale

PS-07 covers third-party personnel management, and AT-01 establishes training policy. PL-04 has each person acknowledge the rules of behavior before getting access, and PS-06 has them sign access agreements. PM-01's program plan records management commitment and roles. OSA lowered this figure from 78% on 1 November 2026, when it dropped its earlier controls for management and leadership roles.

Gaps

ISO 27002 emphasizes management actively requiring all employees and contractors to apply security per policies, leading by example, and providing resources. SP 800-53 is less explicit on management behavioral expectations and enforcement responsibility.

5.5 Staying in contact with authorities such as regulators

Rationale

IR-06 covers reporting incidents to authorities. That is one part of keeping up relationships with relevant authorities. OSA lowered this figure from 80% on 1 November 2026, when it dropped its earlier controls for contact with outside security groups.

Gaps

ISO 27002 includes proactive relationship maintenance with authorities for prevention and intelligence, not just reactive incident reporting. Anticipatory contact with regulatory bodies is not explicitly required.

Mapped Controls

5.6 Joining special interest groups and security forums

Rationale

PM-15 directly covers contacts with security groups and associations, including sharing threat and vulnerability information with them. SI-05 receives security alerts and advisories from outside organizations. Good alignment with ISO 27002's requirement.

Gaps

Minor: ISO 27002 details benefits including improved knowledge, early warnings, and advisory access from professional forums. SP 800-53 is less specific about the breadth of groups to engage.

Mapped Controls

5.7 Gathering and analysing threat intelligence

Rationale

PM-16 sets up a threat awareness program that shares threat intelligence across organizations. RA-10 (Threat Hunting) adds proactive cyber threat hunting capability. OSA lowered this figure from 92% on 1 November 2026, when it dropped its earlier controls for security advisories, threat identification and risk response.

Gaps

ISO 27002 asks for threat intelligence to be collected, analysed and acted on. Gathering advisories, and using threat intelligence in risk assessment and risk response, are outside the controls mapped here.

Mapped Controls

5.8 Building security into project management

Rationale

SA-03 covers security in the system development life cycle. SA-04 addresses acquisition security requirements. PL-02 and PL-08 add the system's security plan and its security architecture, and SA-15 sets the development process.

Gaps

ISO 27002 specifies security integration into ALL project types regardless of nature (IT and non-IT). SP 800-53 SA controls focus on IT system development and acquisition projects specifically.

5.9 Inventory and ownership of information and related assets

Rationale

CM-08 directly covers the inventory of system components, at the detail needed for tracking, and keeps it reviewed and updated. OSA lowered this figure from 92% on 1 November 2026, when it dropped its earlier controls for the system inventory and the location of information.

Gaps

ISO 27002 includes 'associated assets' beyond information and system components, such as people, premises and cloud services. An inventory of the information itself, and of where it is held, is outside the control mapped here.

Mapped Controls

5.10 Acceptable use rules for information and related assets

Rationale

PL-04 directly covers rules of behavior and acceptable use policies. MP-07 covers media use restrictions, and MP-02, MP-04, MP-05 and MP-06 set rules for media access, storage, transport and sanitization. SC-08 and SC-28 protect information in transit and at rest.

Gaps

Minor: ISO 27002 specifies 'return of assets' as part of the acceptable use lifecycle and covers acceptable use of cloud services. SP 800-53 separates asset return into PS-04.

5.11 Return of assets when people leave or change roles

Rationale

PS-04 covers personnel termination including return of organizational assets and information. PS-05 covers personnel transfer with similar asset handling requirements.

Gaps

Minimal gap. ISO 27002 includes return of both physical and electronic assets, which PS-04/PS-05 address.

Mapped Controls

5.12 Classification of information by security needs

Rationale

RA-02 covers security categorization of information and systems using FIPS 199 methodology.

Gaps

ISO 27002 uses multi-tier classification schemes; SP 800-53 uses FIPS 199 categorization (C/I/A impact levels). Conceptually similar but terminology and methodology differ. ISO 27002 classification applies to all information forms.

Mapped Controls

5.13 Labelling of information to show its classification

Rationale

MP-03 covers media marking and labeling. PE-22 marks hardware components with the impact or classification level of the information they may handle. OSA lowered this figure from 80% on 1 November 2026, when it dropped its earlier controls for security attributes on digital information and its categorization.

Gaps

ISO 27002 requires labeling procedures for all information formats including physical, electronic, and verbal. SP 800-53 focuses primarily on media marking; comprehensive cross-format labeling is less prescribed.

Mapped Controls

5.14 Rules and agreements for information transfer

Rationale

SC-07 boundary protection; SC-08 transmission confidentiality/integrity; AC-04 information flow enforcement; AC-17 remote access. CA-03 sets agreements for exchanging information with other systems, and PS-06 sets access agreements for individuals.

Gaps

ISO 27002 includes transfer agreements and procedures for all forms (electronic, physical, verbal). SP 800-53 focuses on electronic and physical transfer; verbal transfer procedures are a gap.

5.15 Access control policy and rules

Rationale

AC-01 sets the access control policy and procedures. AC-03 enforces approved authorizations in line with that policy, and AC-06 applies least privilege. Together they set and enforce access rules based on business and security needs. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for account management, session controls and remote access.

Gaps

Minimal gap. SP 800-53 AC family is more detailed than ISO 27002's requirement.

Mapped Controls

5.16 Identity management from creation to removal

Rationale

IA-02 identification and authentication; IA-04 identifier management; IA-05 authenticator management; IA-08 non-organizational users. AC-02 manages accounts from creation to removal. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for identity proofing.

Gaps

Minimal gap. SP 800-53 IA family provides comprehensive identity lifecycle management.

5.17 Issuing and managing authentication information such as passwords

Rationale

IA-05 directly covers authenticator management (passwords, tokens, certificates), from first issue to protection, change and revocation.

Gaps

Minimal gap. ISO 27002's authentication information management requirements are comprehensively addressed.

Mapped Controls

5.18 Managing access rights, including regular reviews

Rationale

AC-02 covers account management, including provisioning, periodic review and revocation. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for least privilege.

Gaps

Minimal gap. Access right lifecycle (request, approve, review, revoke) is well covered.

Mapped Controls

5.19 Managing security risks in supplier relationships

Rationale

SR-01 sets the supply chain risk management policy and procedures. SR-02 adds a plan for managing supply chain risks across the life of a system, component or service, and keeps it up to date. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for acquisition contracts and the controls on suppliers and external service providers.

Gaps

ISO 27002 emphasizes ongoing supplier relationship management with periodic review and risk reassessment. The controls here set policy and a plan, so contract terms and the oversight of service providers fall outside this mapping.

Mapped Controls

5.20 Security requirements in supplier agreements

Rationale

SA-04 directly requires security requirements in acquisition contracts, including contracts for services. SR-03 covers supply chain controls and processes specified in agreements. SR-05 adds contract tools and procurement methods, and SR-02 a supply chain risk management plan.

Gaps

Minor: ISO 27002 requires specific agreement terms for information access, processing, handling, and return. SA-04 is comprehensive but agreement format requirements differ.

5.21 Managing ICT supply chain security risks

Rationale

SR-02 sets a supply chain risk management plan, and SR-03 the processes and controls that address weaknesses in the ICT supply chain. SR-04 keeps the provenance of components, and SR-05 covers acquisition strategies. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for supplier assessments and checks that components are genuine and untampered.

Gaps

The SR controls mapped here align well with ISO 27002's ICT supply chain requirements. Supplier assessments, and checks that components are genuine and untampered, fall outside this mapping.

5.22 Monitoring supplier services and managing their changes

Rationale

SA-09 includes requirements to monitor external service providers' control compliance on an ongoing basis. SR-06 covers supplier assessments and reviews.

Gaps

ISO 27002 requires regular monitoring and review of supplier service delivery, performance measurement, and change management of supplier services. SP 800-53 is less prescriptive about ongoing supplier service monitoring cadence and performance tracking.

5.23 Security of cloud services from adoption to exit

Rationale

SA-09 covers external system services, including cloud services, with oversight roles and ongoing monitoring of providers. SA-04 puts security requirements and the split of responsibilities into the acquisition contract, and SR-05 adds acquisition strategies. SA-01 sets the system and services acquisition policy.

Gaps

ISO 27002:2022 added cloud-specific controls covering shared responsibility models, cloud exit strategy, multi-tenancy isolation, and cloud-specific risk assessment. SP 800-53 addresses cloud through general external service controls but lacks cloud-specific implementation requirements. FedRAMP supplements this for federal use.

5.24 Setting up incident management plans and roles

Rationale

IR-08 sets the incident response plan, which describes the response capability and names who is responsible for it. The organization distributes the plan to incident response staff and keeps it up to date. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for incident response procedures and the training and testing of responders.

Gaps

IR-08 provides the core of incident management planning. Incident response procedures fall outside this mapping, along with the training and testing of responders.

Mapped Controls

5.25 Assessing whether security events are incidents

Rationale

IR-04 incident handling includes event assessment and triage, as part of detection and analysis. AU-06 reviews and analyzes audit records for unusual activity, which supports event identification and initial assessment. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for incident tracking and reporting, and system monitoring.

Gaps

Minimal gap. Event classification and decision-making processes are well addressed.

Mapped Controls

5.26 Incident response following documented procedures

Rationale

IR-04 comprehensively covers incident response, including containment, eradication, and recovery. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for incident reporting and spillage response.

Gaps

Minimal gap. Specific incident types, such as information spillage, rest on IR-04's general handling capability.

Mapped Controls

5.27 Lessons learned from security incidents

Rationale

IR-04 includes incident analysis and post-incident activities. It feeds lessons learned from incident handling into the response procedures and training, which supports ISO 27002's requirement to use incident knowledge to improve security.

Gaps

Minor: ISO 27002 emphasizes structured knowledge management from incidents to reduce future likelihood and impact. SP 800-53 supports this through post-incident review but formal knowledge base management is less prescribed.

Mapped Controls

5.28 Collecting and preserving evidence of security events

Rationale

AU-03 sets what audit records contain, which gives them value as evidence. AU-11 retains audit records long enough to support investigations of incidents after the fact. AU-10 provides irrefutable evidence of who performed an action, and through its enhancement AU-10(03) on chain of custody it keeps reviewer and releaser credentials within the chain of custody. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for evidence collection in incident handling and the review and protection of audit records.

Gaps

ISO 27002 provides specific evidence handling guidance, including chain of custody and forensic admissibility. The controls here cover the content, retention and non-repudiation of audit records. Procedures to identify, collect and preserve evidence after an incident fall outside this mapping.

Mapped Controls

5.29 Keeping security in place during disruption

Rationale

The CP controls mapped here cover continuity planning, testing, and recovery. CP-11 provides alternate communications protocols, and CP-13 alternative security mechanisms. Strong alignment with maintaining security during disruption.

Gaps

Minimal gap. SP 800-53 CP family is comprehensive for maintaining security during disruption scenarios.

5.30 ICT readiness to support business continuity

Rationale

CP-02 sets the contingency plan, with essential functions, recovery objectives and restoration priorities. Through its enhancements CP-02(01) and CP-02(08), it coordinates that plan with related plans, such as business continuity plans, and identifies the critical assets behind essential functions. CP-04 tests the plan to check that it works and that the organization is ready to carry it out. CA-02 assesses whether controls are implemented correctly and work as intended. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for alternate processing and telecommunications, backup and system recovery.

Gaps

ISO 27002 specifically addresses Business Impact Analysis for ICT services and ICT readiness as a distinct concept. CP-02 plans for essential functions and recovery objectives, and CP-04 tests the plan. The capabilities that deliver readiness, such as alternate processing sites, backup and system recovery, fall outside this mapping.

Mapped Controls

5.31 Identifying legal and regulatory requirements, including contractual ones

Rationale

PM-01 sets the information security program plan. The policy controls mapped here, such as AC-01 and SR-01, require each policy to be consistent with applicable laws, regulations and standards. OSA lowered this figure from 60% on 1 November 2026, when it dropped its earlier controls for contractual requirements and rules of behavior.

Gaps

ISO 27002 requires explicit identification, documentation, and maintenance of all applicable legal, regulatory, and contractual requirements. SP 800-53 lacks a dedicated legal compliance identification control; FISMA context assumes federal requirements rather than requiring systematic identification.

5.32 Intellectual property rights and software licence compliance

Rationale

No direct SP 800-53 control addresses intellectual property management, software licensing compliance, or copyright protection.

Gaps

Significant gap. SP 800-53 does not address software licensing compliance, copyright management, proprietary data protection, or IP rights enforcement. Requires supplementary organizational controls outside SP 800-53.

Mapped Controls

5.33 Protection of records against loss and misuse

Rationale

AU-09 protects audit information against unauthorized modification or deletion. AC-03 enforces approved access to records, and CP-09 backs information up. SC-08 and SC-28 protect confidentiality and integrity in transit and at rest. OSA lowered this figure from 70% on 1 November 2026, when it dropped its earlier controls for the retention of records and audit logs.

Gaps

ISO 27002 asks that all records be kept safe from loss, tampering and unauthorized access or release, as legal and business requirements demand. Retention schedules and broader records management, such as classification and disposal, fall outside this mapping.

5.34 Protecting PII and meeting privacy requirements

Rationale

PM-18 sets the privacy program plan, and PT-01 a policy for processing PII in line with applicable laws. PT-03 limits processing to stated purposes and describes them in privacy notices. PT-07 sets conditions for specific categories of PII, and PL-02 adds privacy plans for systems. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for consent and privacy impact assessments, among other privacy duties.

Gaps

ISO 27002 defers to ISO 27701 for a full privacy management system. SP 800-53's privacy controls focus on the US federal context. Consent and the authority to process PII fall outside this mapping.

5.35 Independent review of how security is managed

Rationale

CA-02 assesses the controls against a plan with a set scope and reports the results. Through its enhancement CA-02(01) on independent assessors, it has independent assessors or assessment teams carry out those assessments. OSA lowered this figure from 80% on 1 November 2026, when it dropped its earlier controls for continuous monitoring and performance measures.

Gaps

ISO 27002 requires independent review of the organization's approach to managing information security, beyond technical control assessment. CA-02 covers independent assessment of controls. Review of the management approach as a whole is less explicit in SP 800-53.

Mapped Controls

5.36 Regularly checking compliance with security policies and standards

Rationale

CA-02 assesses compliance with security requirements. CA-07 continuous monitoring detects deviations. The policy controls mapped here, such as AC-01, require regular review of each policy and its procedures.

Gaps

Minor: ISO 27002 requires regular review that information processing and procedures comply with security policies and standards. SP 800-53 assessment approach differs from ISO's compliance checking methodology.

5.37 Documented operating procedures for IT systems

Rationale

SA-05 provides administrator and user documentation, including how to configure and operate the system securely. The policy controls mapped here, such as CM-01 and MA-01, each require documented procedures for their family's controls.

Gaps

ISO 27002 requires documented operating procedures for information processing facilities made available to all personnel who need them. SP 800-53 distributes procedures across families rather than requiring unified operating procedures documentation.

6.1 Background screening before joining and during employment

Rationale

PS-03 directly covers personnel screening including background verification checks before access is granted. Covers initial and ongoing screening requirements.

Gaps

Minimal gap. ISO 27002 provides guidance on screening depth varying by role sensitivity, which aligns with PS-03's risk-based approach.

Mapped Controls

6.2 Security responsibilities in employment contracts

Rationale

PS-06 covers access agreements, including confidentiality requirements, that individuals sign before they get access. PL-04 sets rules of behavior that users acknowledge, describing their responsibilities for security and privacy. OSA lowered this figure from 88% on 1 November 2026, when it dropped its earlier controls for security duties in position descriptions and the security of external personnel.

Gaps

ISO 27002 includes security responsibilities in employment contracts. The controls here cover access agreements and rules of behavior, which users sign or acknowledge. Security duties in position descriptions and the terms for external personnel fall outside this mapping.

Mapped Controls

6.3 Security awareness training and education for staff

Rationale

AT-02 covers literacy training and awareness, and AT-03 role-based training. PM-13 sets up a security and privacy workforce program. CP-03 and IR-02 add training for contingency and incident response roles. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for training records and feedback on training.

Gaps

Minimal gap. Training records, and the feedback that ISO 27002 uses to improve training, fall outside this mapping.

6.4 Disciplinary process for security policy breaches

Rationale

PS-08 covers personnel sanctions for security violations including formal and informal sanctions. OSA raised this figure from 75% on 1 November 2026, when it set one figure for this control and its twin in ISO/IEC 27001:2022, which has the same controls.

Gaps

ISO 27002 requires a formal, communicated disciplinary process with graduated responses. PS-08 addresses sanctions but is less prescriptive about process stages, communication to personnel, and consideration of mitigating circumstances.

Mapped Controls

6.5 Security duties that continue after termination or role change

Rationale

PS-04 covers personnel termination, from revoking access to an exit interview on security topics. PS-05 covers personnel transfer.

Gaps

Minimal gap. PS-04/PS-05 address access revocation, asset return, and ongoing confidentiality obligations.

Mapped Controls

6.6 Non-disclosure agreements to protect confidential information

Rationale

PS-06 covers access agreements, which include confidentiality requirements, for everyone who needs access to the organization's information and systems.

Gaps

ISO 27002 specifically requires NDAs reflecting organizational needs with regular review and updates. PS-06 is broader (access agreements) and NDA-specific requirements (jurisdiction, post-contract duration) are less detailed.

Mapped Controls

6.7 Protecting information during remote working

Rationale

AC-17 directly covers remote access controls and monitoring. PE-17 covers alternate work site security.

Gaps

Minor: ISO 27002 includes physical security at remote locations, clean desk for remote workers, and remote working-specific risk considerations beyond technical access controls.

Mapped Controls

6.8 Security event reporting by staff through agreed channels

Rationale

IR-06 directly covers incident reporting requirements, with a set time for personnel to report suspected incidents. AU-06 reports findings from audit record review, and SI-02 covers reporting system flaws.

Gaps

Minimal gap. ISO 27002 emphasizes employee obligation to report events; SP 800-53 addresses through policy and reporting procedures.

Mapped Controls

7.1 Physical security perimeters around sensitive areas

Rationale

PE-03 covers physical access control including perimeter barriers, entry points, and access mechanisms.

Gaps

Minimal gap. ISO 27002 includes guidance on perimeter strength proportional to assets; PE-03 addresses this through risk-based physical access controls.

Mapped Controls

7.2 Controlling physical entry to secure areas

Rationale

PE-02 physical access authorizations; PE-03 physical access control mechanisms, which keep access logs at entry points and escort visitors. PE-16 controls system components entering and leaving the facility, as at delivery points. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for monitoring physical access, visitor control and visitor records.

Gaps

Minimal gap. Physical entry controls are comprehensive.

7.3 Physical security of offices and other facilities

Rationale

PE-03 physical access control for offices and rooms. PE-05 access control for output devices.

Gaps

Minor: ISO 27002 addresses office-specific risks including sound insulation, door locks, window protection, and facility design. SP 800-53 is less specific about office-level security design.

Mapped Controls

7.4 Physical security monitoring of premises, such as CCTV

Rationale

PE-06 directly covers monitoring physical access including CCTV, intrusion alarms, and guard patrols. PE-03 keeps the physical access logs for review. AU-06, through its enhancement AU-06(06) on correlation with physical monitoring, ties audit records to physical access monitoring to spot unusual activity.

Gaps

Minimal gap. ISO 27002 monitoring requirements are well addressed by PE-06's comprehensive monitoring provisions.

Mapped Controls

7.5 Protecting sites from physical and environmental hazards

Rationale

PE controls cover the main environmental protections: power equipment (PE-09), fire protection (PE-13), temperature and humidity (PE-14) and water damage (PE-15). PE-23 (Facility Location) adds planning facility location considering physical and environmental hazards, natural disasters, and man-made threats. PE-18 positions system components to limit damage from those hazards. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for emergency shutoff, emergency power, emergency lighting and electromagnetic pulse protection.

Gaps

Minimal gap. PE-23 strengthens coverage through facility location planning that considers hazards.

7.6 Rules for work inside secure areas
0%

Rationale

NIST's crosswalk pairs no SP 800-53 control with this clause, so OSA maps none. OSA lowered this figure from 80% on 1 November 2026, when it dropped its earlier controls for physical access and visitor control in secure areas.

Gaps

ISO 27002 includes specific rules for working in secure areas such as photography restrictions, supervised access, empty area verification, and prohibition of recording equipment. The whole clause is a gap here.

7.7 Rules for a clear desk and a clear screen

Rationale

AC-11 covers session lock (clear screen). MP-04 covers media storage requirements. PE-05 covers access control for output devices to prevent unauthorized viewing.

Gaps

Minor: ISO 27002 explicitly addresses clear desk policy as a formal requirement. AC-11 covers screen lock; desk policy is implied through MP controls but not explicitly stated as a standalone requirement.

7.8 Siting equipment securely and protecting it from hazards

Rationale

PE-14 environmental controls for equipment. PE-18 location of information system components. PE-23 (Facility Location) addresses planning facility and equipment location considering physical and environmental hazards, supporting equipment siting decisions at the site level.

Gaps

ISO 27002 includes equipment placement to minimize unauthorized access, environmental hazards, and electromagnetic interference. SP 800-53 is less specific about equipment siting methodology but PE-23 adds site-level considerations.

7.9 Protecting assets used off-premises, such as laptops

Rationale

MP-05 media transport protection; AC-19 access control for mobile devices, including outside controlled areas. PE-17 sets the controls for alternate work sites, and AC-20 sets the terms for using external systems. OSA lowered this figure from 80% on 1 November 2026, when it dropped its earlier controls for remote access and the protection of stored information.

Gaps

ISO 27002 covers all off-premises assets including laptops, paper documents, and portable equipment with physical and logical protection. SP 800-53 covers media and mobile devices well but holistic physical asset protection off-site is less comprehensive.

7.10 Managing storage media from acquisition to disposal

Rationale

The MP family covers the media protection lifecycle: access (MP-02), storage (MP-04), transport (MP-05), sanitization (MP-06), use restrictions (MP-07). PE-16 controls media entering and leaving the facility, and MA-02 sanitizes media before equipment leaves for off-site maintenance. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for media policy, media marking and media downgrading.

Gaps

Minimal gap.

7.11 Reliable supporting utilities, such as power and cooling

Rationale

PE-09 power equipment and cabling protection. PE-10 emergency shutoff capabilities. PE-11 emergency power supply. PE-12 emergency lighting. Comprehensive supporting utility protection.

Gaps

Minimal gap. ISO 27002 includes water supply and sewage considerations which are partially addressed through general facility controls.

7.12 Security of power and data cabling

Rationale

PE-04 covers access control for transmission medium including cable routing protection. PE-09 covers power equipment and cabling protection.

Gaps

ISO 27002 provides specific cabling security measures including protected routing, electromagnetic shielding, fiber optic preference for sensitive links, and separation of power/telecommunications. SP 800-53 PE-04 is more general about transmission medium protection.

Mapped Controls

7.13 Secure and timely equipment maintenance

Rationale

MA-02 controlled maintenance schedules, approves and monitors all maintenance, on site or remote, including the removal of equipment for off-site repair. MA-06 timely maintenance gets support and spare parts within a set time of a failure. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for maintenance policy, maintenance tools and personnel, and remote and field maintenance.

Gaps

Minor: maintenance personnel, maintenance tools and remote maintenance rest on MA-02's general approval and monitoring of maintenance.

Mapped Controls

7.14 Removing data and software before equipment disposal or reuse

Rationale

MP-06 covers media sanitization with methods appropriate to classification (clear, purge, destroy), before disposal, release or re-use. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for downgrading media before re-use.

Gaps

Minor: ISO 27002 includes all equipment disposal beyond just media. Equipment-level sanitization (checking for embedded storage) is less explicitly addressed; SP 800-53 focuses on media sanitization.

Mapped Controls

8.1 Protecting information on user endpoint devices

Rationale

AC-19 sets configuration and connection requirements for mobile devices such as phones and tablets. AC-11 locks any device after inactivity until the user signs in again. OSA lowered this figure from 82% on 1 November 2026, when it dropped its earlier controls for least functionality, encryption of stored information, the component inventory and port restrictions.

Gaps

ISO 27002 provides holistic endpoint management guidance including BYOD policies, MDM, containerization, and endpoint-specific risk assessment. AC-19 covers mobile devices such as phones and tablets, so laptops and desktops rest on AC-11 alone. Endpoint hardening, storage encryption and port control are uncovered.

Mapped Controls

8.2 Limiting and controlling privileged access rights

Rationale

AC-06 least privilege with specific privileged access restrictions, authorization, and review. AC-02 account management including privileged account lifecycle. CM-05 restricts access for making changes to the system.

Gaps

Minimal gap. SP 800-53 privileged access controls are comprehensive.

Mapped Controls

8.3 Restricting access to information under access control rules

Rationale

AC-03 access enforcement; AC-24 access control decisions applied to each access request before enforcement. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for information flow control and least privilege.

Gaps

Minimal gap. SP 800-53 access restriction controls exceed ISO 27002 requirements.

Mapped Controls

8.4 Controlling who can read and change source code

Rationale

CM-05 covers access restrictions for change including source code and software libraries. AC-03 access enforcement. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for developer configuration management of source code.

Gaps

ISO 27002 specifically addresses source code repositories, read/write access separation, and source code library management. SP 800-53 addresses these through general access and change restriction controls. Version control of the source code repository is uncovered.

Mapped Controls

8.5 Secure authentication methods, such as multi-factor sign-in

Rationale

AC-07 limits unsuccessful logon attempts, AC-08 shows a notice before logon, AC-09 reports the last logon, and IA-06 obscures authentication feedback. Together they cover a secure logon procedure. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for identifying and authenticating users, managing authenticators and re-authentication.

Gaps

The controls here cover the logon procedure. The authentication mechanism itself, such as multi-factor authentication suited to the information's sensitivity, is uncovered.

8.6 Capacity management to meet current and future demand

Rationale

CP-02, through its enhancement CP-02(02) on capacity planning, plans for the processing, telecommunications and environmental capacity needed during contingency operations. SC-05, through its enhancement SC-05(02), manages capacity, bandwidth and redundancy to limit the effects of flooding attacks. AU-04 allocates audit log storage capacity.

Gaps

ISO 27002 requires proactive capacity management for all IT resources with monitoring, forecasting, and right-sizing. The controls here cover capacity for contingency operations, resilience to denial of service and audit log storage. Day-to-day monitoring, forecasting and right-sizing fall outside this mapping.

Mapped Controls

8.7 Malware protection backed by user awareness

Rationale

SI-03 directly covers malicious code protection with detection, eradication, and prevention. AT-02 builds the user awareness the control also asks for.

Gaps

Minimal gap.

Mapped Controls

8.8 Technical vulnerability management, including patching

Rationale

RA-05 vulnerability monitoring and scanning. SI-02 flaw remediation with patching. SI-05 security alerts, advisories, and directives for vulnerability notifications.

Gaps

Minimal gap. SP 800-53 vulnerability management controls are comprehensive.

8.9 Secure configuration management for systems and networks

Rationale

The CM family covers configuration management: policy (CM-01), baselines (CM-02), change control (CM-03), impact analysis (CM-04), access restrictions (CM-05), settings (CM-06), inventory (CM-08) and the configuration management plan (CM-09). SA-10 extends configuration management to the system's developers. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for least functionality and signed components.

Gaps

Minimal gap.

8.10 Deleting information once the need for it ends

Rationale

MP-06 media sanitization covers secure deletion methods. SI-21 deletes information when it's no longer needed, and MA-02 sanitizes equipment before off-site maintenance. MP-04 protects media until they are sanitized or destroyed. NIST also names enhancements that sanitize in particular cases. AC-04, through AC-04(25), sanitizes data that moves between security domains. AC-07, through AC-07(02), wipes a mobile device after repeated failed logons. MA-03, through MA-03(03), and MA-04, through MA-04(03), sanitize equipment and components used in maintenance.

Gaps

ISO 27002 specifically addresses deletion when information is no longer required, based on retention policies and legal requirements. SP 800-53 covers sanitization methods but proactive information deletion based on business need is less explicitly addressed.

8.11 Data masking, such as pseudonymisation and anonymisation

Rationale

SI-19 removes chosen elements of personally identifiable information from datasets and checks that de-identification works. Through its enhancement SI-19(04), it removes, masks, encrypts, hashes or replaces direct identifiers. AC-04, through its enhancement AC-04(23), modifies information that may not be released when it moves between security domains. OSA lowered this figure from 78% on 1 November 2026, when it dropped its earlier controls for the handling of personal data, protection of data at rest and data tainting.

Gaps

ISO 27002 gives specific guidance on data masking techniques, including pseudonymization, anonymization and dynamic masking rules. SI-19 applies them to personal data, and AC-04 to information that moves between security domains. Dynamic masking rules for other sensitive data are less explicit.

Mapped Controls

8.12 Data leakage prevention for sensitive information

Rationale

SC-07, through its enhancement SC-07(10) on preventing exfiltration, stops information leaving through the system boundary and tests for exfiltration. PE-03, through its enhancement PE-03(02), checks the physical perimeter for information or components being taken out. SI-20 embeds data or capabilities that reveal exfiltration, and AU-13 monitors open sources for signs that information has been disclosed. PE-19 protects against leakage through electromagnetic emanations. OSA lowered this figure from 82% on 1 November 2026, when it dropped its earlier controls for information flow enforcement, system monitoring and covert channel analysis.

Gaps

ISO 27002 specifically addresses DLP tools. The controls here block and detect exfiltration at the boundary, at the perimeter and in open sources. Rules that decide which data may flow where, and monitoring of endpoints and email, fall outside this mapping.

8.13 Information backup with regular restore tests

Rationale

CP-09 directly covers information system backup, including backup frequency and the protection of backup integrity. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for alternate storage sites for off-site backup.

Gaps

Minimal gap. SP 800-53 backup controls are comprehensive.

Mapped Controls

8.14 Redundancy in IT systems to keep services available

Rationale

CP-06 sets up an alternate storage site and CP-07 an alternate processing site. CP-02 sets the contingency plan that these sites serve. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for alternate telecommunications services and distributed processing.

Gaps

ISO 27002 focuses on redundancy for availability requirements. CP controls focus on contingency, which includes redundancy. Redundant telecommunications links are now a gap.

Mapped Controls

8.15 Event logging, with logs kept safe and reviewed

Rationale

AU controls cover logging: auditable events (AU-02), record content (AU-03), review and analysis (AU-06), protection (AU-09), retention (AU-11), record generation (AU-12) and session audit (AU-14). OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for log storage capacity, logging failures, report generation and time stamps.

Gaps

Minimal gap. SP 800-53 AU family is comprehensive for logging requirements.

8.16 Monitoring networks and systems for unusual behaviour

Rationale

SI-04 directly covers system monitoring, including the analysis of detected events and anomalies. IR-04, through its enhancement IR-04(13) on behavior analysis, analyzes anomalous or suspected adversarial behavior. AC-02, through AC-02(12), monitors accounts for atypical use. AC-17, through AC-17(01), monitors and controls remote access, and MA-04, through MA-04(01), logs and reviews remote maintenance sessions. SC-07 monitors communications at the system boundary, PE-06 monitors physical access, and AU-13 watches for disclosure of organizational information. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for audit record review and continuous monitoring.

Gaps

Minimal gap. SP 800-53 monitoring controls are comprehensive.

8.17 Clock synchronisation to a trusted time source

Rationale

AU-08 time stamps audit records from the system's internal clocks, in UTC or with a stated offset. The organization sets how closely those clocks must match reference clocks. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for synchronizing system clocks to an authoritative time source.

Gaps

Synchronizing clocks to approved time sources, the core of this clause, is now a gap. AU-08 covers the time stamps themselves.

Mapped Controls

8.18 Restricting privileged utility programs able to bypass controls

Rationale

AC-06 least privilege restricts access to privileged utilities. AC-03 enforces approved authorizations for access to them. OSA lowered this figure from 80% on 1 November 2026, when it dropped its earlier controls for restricting unneeded programs and user-installed software.

Gaps

ISO 27002 specifically addresses privileged utility programs that can override system and application controls. SP 800-53 addresses them through general access and privilege controls rather than utility-specific ones. Removing or disabling utilities that aren't needed is now a gap.

Mapped Controls

8.19 Controlling what software is installed on operational systems

Rationale

CM-05 restricts who can install software. CM-07 least functionality limits what can be installed. CM-11 controls user-installed software. OSA lowered this figure from 92% on 1 November 2026, when it dropped its earlier controls for signed components and unsupported system components.

Gaps

Small gaps remain: verifying software signatures before installation, and keeping installed software at a supported version.

Mapped Controls

8.20 Network security and management of network devices

Rationale

SC-07 protects the boundary and SC-08 protects the confidentiality and integrity of transmissions. AC-18 governs wireless access, AC-20 the use of external systems, and SC-10 ends network connections after a session or a period of inactivity. AC-03 enforces approved access. OSA lowered this figure from 92% on 1 November 2026, when it dropped its earlier controls for information flow enforcement and internal system connections.

Gaps

SC-07 focuses on the perimeter. Small gaps remain: controlling information flows within the network, and authorizing and documenting internal system connections.

8.21 Security features and service levels for network services

Rationale

SA-09 covers external system services, including network services, with security requirements and ongoing monitoring. CA-03 approves and manages information exchanges through agreements, such as service level agreements, that document security requirements. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for boundary protection and transmission confidentiality and integrity.

Gaps

ISO 27002 requires security features, service levels and management requirements for network services, including service level agreements. These are less detailed in SP 800-53. The technical protection of the services themselves, such as boundary protection and encryption in transit, is now a gap.

Mapped Controls

8.22 Network segregation into separate security zones

Rationale

SC-07 boundary protection includes network segmentation. AC-04 enforces approved information flows within the system and between connected systems. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for system partitioning.

Gaps

Minimal gap. SP 800-53 network segmentation controls are comprehensive.

Mapped Controls

8.23 Web filtering to block harmful websites

Rationale

SC-07 monitors and controls communications at the boundary, where web filtering takes place. AC-04 enforces information flow policies, such as limiting web requests to those that pass through an approved proxy. OSA lowered this figure from 70% on 1 November 2026, when it dropped its earlier controls for malicious code protection.

Gaps

ISO 27002 specifically addresses URL filtering, web content filtering, and restricting access to unsafe websites. No dedicated SP 800-53 web filtering control exists; addressed through general boundary and content controls.

Mapped Controls

8.24 Using cryptography, including encryption and key management

Rationale

SC-12 cryptographic key establishment and management. SC-13 cryptographic protection with algorithm requirements. SC-17 public key infrastructure certificates.

Gaps

Minimal gap. SP 800-53 cryptography controls are comprehensive including key management lifecycle.

Mapped Controls

8.25 Security built into the development life cycle

Rationale

SA-03 system development life cycle with security integration. SA-15 development process, standards, and tools. SA-17 developer security and privacy architecture and design. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for security engineering principles, developer configuration management and developer testing.

Gaps

Minimal gap. SP 800-53 SA family is comprehensive for secure development lifecycle.

Mapped Controls

8.26 Application security requirements when building or buying software

Rationale

AC-03 enforces approved access authorizations. SC-08 protects information in transit, and SC-13 sets the cryptography to use. These cover security functions that application requirements commonly specify. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for security requirements in acquisitions, security engineering principles and developer testing.

Gaps

The controls here cover specific security functions. Identifying, specifying and approving an application's security requirements during development or acquisition is now a gap.

Mapped Controls

8.27 Applying secure engineering principles to system architecture

Rationale

SA-08 security and privacy engineering principles. SA-17 developer security and privacy architecture and design.

Gaps

Minimal gap. SP 800-53 architecture and engineering controls are comprehensive.

Mapped Controls

8.28 Secure coding practices in software development

Rationale

SA-15 has developers follow a documented development process with set standards and tools, and through its enhancement SA-15(05) reduce attack surfaces. SA-11 requires developer testing and flaw remediation, and through SA-11(01) static code analysis. SA-04, through SA-04(03), requires developers to show the development methods and practices they use. SA-08 applies security and privacy engineering principles, and SA-10 manages changes to source code under configuration management. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for developer training.

Gaps

ISO 27002 gives specific secure coding guidance, including input validation, error handling and code review. The controls here set the development process, its standards, static analysis and testing. Training developers in secure coding falls outside this mapping.

8.29 Security and acceptance testing of new or changed systems

Rationale

SA-11 directly covers developer security testing and evaluation. CA-02 security assessments for acceptance testing. SA-04 includes testing requirements in acquisition. SR-05, through its enhancement SR-05(02), assesses a system, component or service before it is selected, accepted, modified or updated.

Gaps

Minimal gap. SP 800-53 security testing controls are comprehensive.

8.30 Overseeing outsourced development from contract to acceptance

Rationale

SA-04 acquisition requirements for outsourced development. SA-10/SA-11 developer requirements apply to outsourced developers. SA-15 has the developer follow a documented process that the organization reviews. SR-02 and SR-04 add supply chain risk planning and provenance. OSA lowered this figure from 88% on 1 November 2026, when it dropped its earlier controls for external service oversight and developer screening.

Gaps

Minor: ISO 27002 details outsourced development supervision, intellectual property rights and acceptance testing. SP 800-53 covers these through general acquisition and developer controls.

8.31 Separating development and test environments from production

Rationale

CM-04, through its enhancement CM-04(01) on separate test environments, analyzes changes in a separate test environment before they reach the operational one. CM-05 limits who can make changes to the system, through access restrictions, software libraries and change windows. SA-03 manages the system through a development life cycle that builds in security. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for developer testing, system partitioning and baseline configurations.

Gaps

ISO 27002 explicitly requires development, testing and production environments to be kept apart. The controls here keep testing apart from production and restrict who changes production. Keeping development apart from both is less explicit.

Mapped Controls

8.32 Change management for IT systems and services

Rationale

CM-03 configuration change control with documented approval processes. CM-05 access restrictions for change. SA-10 developer configuration management for development changes. SI-02 tests flaw remediation updates before installation. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for security impact analysis before changes.

Gaps

Minimal gap. SP 800-53 change management controls are comprehensive.

8.33 Choosing and protecting test data

Rationale

SA-03 manages the system through a development life cycle that builds in security. Through its enhancement SA-03(02) on the use of live or operational data, it approves, documents and controls the use of live data in preproduction environments, and protects those environments at the level of the live data.

Gaps

ISO 27002 specifically addresses the protection of test data, including anonymization, controlled use of production data for testing and the disposal of test data. SA-03 controls the use of live data in testing. Anonymizing test data and disposing of it after testing are less explicit.

Mapped Controls

8.34 Planning audit testing to protect live systems
0%

Rationale

NIST's crosswalk pairs no SP 800-53 control with this clause, so OSA maps none. OSA lowered this figure from 75% on 1 November 2026, when it dropped its earlier controls for control assessments, audit record review and penetration testing.

Gaps

ISO 27002 asks that audit testing be planned and agreed with management to keep business disruption low, and that access to audit tools be controlled. With no control mapped, the whole clause is a gap.

Methodology and Disclaimer

This coverage analysis maps from ISO 27002:2022 clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.

Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.

This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.