← Frameworks / ISO 27001:2022 / Coverage Analysis

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

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

Clauses: 117
Avg Coverage: 76.1%
Publisher: ISO/IEC
Coverage Distribution
Full (85-100%): 54 Substantial (65-84%): 48 Partial (40-64%): 10 Weak (1-39%): 2 None (0%): 3

Clause-by-Clause Analysis

Sorted by clause
4.1 Organisational context: internal and external issues

Rationale

PM-11 defines mission and business processes and the protection needs that come from them. PM-01's program plan gives an overview of the program's requirements. Clause 4.1 asks for a broader analysis of the organization's context, including external and internal issues beyond security risk. OSA lowered this figure from 70% on 1 November 2026, when it dropped its earlier controls for risk context and critical infrastructure planning.

Gaps

No direct SP 800-53 control for analyzing external/internal issues (political, economic, social factors) affecting ISMS. Organizational context determination is broader than security risk assessment.

Mapped Controls

4.2 Identifying interested parties and their requirements

Rationale

PM-01's program plan sets out the program's requirements and how organizational entities coordinate on them. Clause 4.2 asks the organization to identify every interested party and their requirements. OSA lowered this figure from 55% on 1 November 2026, when it dropped its earlier controls for mission planning and supply chain relationships.

Gaps

SP 800-53 lacks explicit requirement to identify all interested parties (regulators, customers, partners) and their specific ISMS expectations. Stakeholder mapping and requirements analysis not directly covered. Mission partners and suppliers, as interested parties, are outside the control mapped here.

Mapped Controls

4.3 Defining the ISMS scope and boundaries

Rationale

PM-01's program plan describes what the security program must meet and the controls it uses. PM-09 sets one risk management strategy for the whole organization. PM-28 records the assumptions, constraints and risk tolerance behind it. OSA lowered this figure from 70% on 1 November 2026, when it dropped its earlier controls for authorization boundaries and enterprise architecture.

Gaps

SP 800-53 defines system boundaries per authorization but doesn't explicitly require ISMS scope statement. Multi-system/enterprise scope determination differs from individual system authorization boundaries. System boundaries and the enterprise architecture are outside the controls mapped here.

Mapped Controls

4.4 Establishing and continually improving the ISMS

Rationale

PM-01 sets the program plan and keeps it reviewed and updated. PM-09 sets the risk management strategy, and PM-31 the continuous monitoring strategy that tracks how well controls work. PM-30 adds a strategy for supply chain risk. OSA lowered this figure from 78% on 1 November 2026, when it dropped its earlier controls for program leadership and resources.

Gaps

SP 800-53 doesn't use PDCA/process approach terminology. Continuous improvement cycle and ISMS as a formal management system with documented processes is implicit rather than explicit.

5.1 Top management's leadership and commitment to the ISMS

Rationale

PM-02 appoints a senior information security officer with the mission and resources to run the program. PM-29 appoints a senior official accountable for risk management and sets up a risk executive function. PM-03 puts security and privacy resources into capital planning. Clause 5.1 asks top management to show its commitment more directly. OSA lowered this figure from 72% on 1 November 2026, when it dropped its earlier controls for management commitment and workforce development.

Gaps

SP 800-53 doesn't explicitly require top management to demonstrate commitment through resource allocation, communication of importance, or ensuring ISMS achieves intended outcomes.

Mapped Controls

5.2 Information security policy set by top management

Rationale

PL-01 directly requires security planning policy with management approval. PM-01 requires information security program plan. Policy establishment, approval, and communication well covered.

Gaps

Minor: ISO specifies policy must be 'appropriate to the purpose of the organization' and 'available as documented information' with specific distribution requirements.

5.3 Assigning ISMS roles with their responsibilities and authority

Rationale

PM-02 assigns the lead information security role, and PM-29 the senior risk management roles. PM-01's program plan identifies and assigns roles and responsibilities. Each family's policy control, such as PL-01, PS-01 and AC-01, addresses roles and responsibilities for its area. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for security roles in position descriptions.

Gaps

Minor gap. Plans and policies assign the roles here. Writing security roles into position descriptions is outside the controls mapped here.

6.1 Planning for risks and opportunities, including risk assessment

Rationale

RA-03 covers risk assessment. PM-09 sets the risk management strategy, and PM-28 frames risk with its assumptions, constraints and risk tolerance. PM-04 tracks the remedial actions that respond to risk, and PM-06 measures performance. PM-01's program plan brings these together. OSA lowered this figure from 82% on 1 November 2026, when it dropped its earlier controls for risk response and baseline selection.

Gaps

ISO explicitly requires considering 'opportunities' alongside risks. SP 800-53 is risk-focused but doesn't explicitly address opportunities for improvement. Risk acceptance criteria less formalized.

6.1.3 Risk treatment planning and the Statement of Applicability

Rationale

RA-07 responds to findings from assessments, monitoring and audits within the organization's risk tolerance. Its options of mitigating, accepting, sharing or avoiding a risk match ISO's risk treatment options. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for treatment plans and control selection.

Gaps

ISO requires explicit Statement of Applicability (SoA) document. SP 800-53 doesn't have a direct SoA equivalent, though system security plans and baseline tailoring serve a similar purpose. The risk treatment plan, the choice of controls and the risk owners' approval are outside the control mapped here.

Mapped Controls

6.2 Setting information security objectives with plans to reach them

Rationale

PM-01 includes program objectives; PM-03 addresses resource planning; PM-06 covers security measures of performance. Objective-setting partially covered.

Gaps

ISO requires measurable security objectives at relevant functions/levels with explicit plans (what, resources, responsible, completion, evaluation). SP 800-53 is less prescriptive about objective-setting methodology.

6.3 Planning changes to the ISMS
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 configuration change control and impact analysis.

Gaps

ISO 6.3 is about planned changes to the ISMS itself (management system changes), not just technical changes. Organizational/process changes to the ISMS are not directly covered. OSA maps no control here, so the whole clause is a gap.

7.1 Providing the resources the ISMS needs

Rationale

PM-03 directly addresses information security and privacy resources. It puts them into capital planning and investment requests and makes the planned resources available. OSA lowered this figure from 78% on 1 November 2026, when it dropped its earlier controls for resources for systems and their development life cycle.

Gaps

ISO requirement is broader - all resources needed for ISMS establishment, implementation, maintenance, and continual improvement. Budget allocation and resource planning less prescriptive in SP 800-53.

Mapped Controls

7.2 Competence of people whose work affects security

Rationale

PM-13 sets up a workforce development program for security and privacy roles. It defines the knowledge and skills each role needs, provides role-based training and sets standards for measuring qualifications. OSA lowered this figure from 88% on 1 November 2026, when it dropped its earlier controls for security training and training feedback.

Gaps

ISO requires retaining documented evidence of competence, such as training records and certifications. Training for staff outside security and privacy roles, and the evaluation of training, are outside the control mapped here.

Mapped Controls

7.3 Staff awareness of security policy and their role

Rationale

AT-02 directly covers security awareness training, including awareness of policy, roles and responsibilities, and consequences. PS-08 sets a formal sanctions process for people who don't follow security policy. This aligns closely with the clause.

Gaps

Minimal gap. AT-02 covers awareness of policy, contribution to ISMS effectiveness, and implications of non-conformance.

Mapped Controls

7.4 Planning ISMS communication inside and outside the organisation

Rationale

PM-01 disseminates the program plan across the organization. PM-31 reports security and privacy status to named roles at a set frequency, and PM-28 shares the results of risk framing. PM-15 keeps contact with security and privacy groups outside the organization.

Gaps

ISO requires determining what, when, with whom, and how to communicate regarding ISMS. SP 800-53 lacks a systematic communication planning control. Internal/external communication strategy not explicitly required.

7.5 Creating and controlling documented information for the ISMS

Rationale

PL-02 (system security plan) and PM-01 (program plan) address documentation, and each protects its plan from unauthorized disclosure and change. Each family's policy control, such as AC-01 and AU-01, documents policy and procedures and keeps them reviewed and updated. SA-05 adds system documentation, and CP-02 and IR-08 document the contingency and incident response plans. Documentation requirements are partially met. OSA lowered this figure from 75% on 1 November 2026, when it dropped its earlier controls for audit records and their retention.

Gaps

ISO has specific requirements for documented information control (creation, updating, version control, distribution, access, storage, disposal). SP 800-53 doesn't have a unified document management control.

8.1 Planning and controlling ISMS operations, including outsourced processes

Rationale

PM-01 covers program implementation through the program plan. PL-07 describes how the organization intends to operate each system securely. CM-03 controls planned changes to systems. SA-01 and SA-04 set security requirements for acquired systems and services. OSA lowered this figure from 75% on 1 November 2026, when it dropped its earlier controls for system security plans and control assessment.

Gaps

ISO requires organizations to plan, implement, and control processes needed to meet requirements. Outsourced process control and documented evidence of process execution are gaps.

8.2 Carrying out risk assessments regularly and for major changes

Rationale

RA-03 directly covers risk assessment at planned intervals or when significant changes occur, and documents the results. OSA lowered this figure from 92% on 1 November 2026, when it dropped its earlier controls for vulnerability scanning and criticality analysis.

Gaps

Minimal gap. RA-03 comprehensively covers risk assessment execution. ISO emphasizes retaining documented results.

Mapped Controls

8.3 Carrying out the risk treatment plan

Rationale

CA-05 (plan of action and milestones) addresses risk treatment plans, and PM-04 tracks those plans across the organization. RA-07 (Risk Response) explicitly addresses risk treatment with options for mitigation, acceptance, sharing or avoidance, closely aligning with ISO risk treatment concepts. OSA lowered this figure from 88% on 1 November 2026, when it dropped its earlier controls for risk assessment.

Gaps

Minor: ISO requires retaining documented results of risk treatment. POA&M process is close but doesn't perfectly map to ISO risk treatment plan format.

Mapped Controls

9.1 Monitoring ISMS performance and evaluating its effectiveness

Rationale

CA-07 (continuous monitoring) and PM-06 (measures of performance) directly address monitoring and measurement. PM-31 sets the organization-wide metrics and how often controls are monitored and assessed. OSA lowered this figure from 82% on 1 November 2026, when it dropped its earlier controls for system monitoring and testing plans.

Gaps

ISO requires determining what to monitor, methods, when, who analyzes results. PM-06 is less prescriptive about evaluation methods and timing.

Mapped Controls

9.2 Planned internal audits of the ISMS

Rationale

CA-02 covers control assessments, which work much like internal audits: it selects assessors, plans the scope and reports the results. CA-01 sets the assessment policy and procedures, and PM-31 sets how often controls are assessed. CA-07, through its enhancement CA-07(01) on independent assessment, has independent assessors monitor the controls on an ongoing basis.

Gaps

ISO requires formal internal audit program with defined criteria, scope, frequency, methods, and auditor independence. CA-02 covers assessments but doesn't use audit terminology or require audit program management.

9.3 Regular top management review of the ISMS

Rationale

PM-01 requires periodic review of the program plan. CA-07 reports security and privacy status to named roles, and CA-06 has a senior official authorize each system. PM-29 gives senior leaders an accountable role in risk management. These partially address management review.

Gaps

ISO specifies detailed management review inputs (audit results, stakeholder feedback, risk assessment changes, opportunities for improvement) and outputs (decisions, resource changes). SP 800-53 lacks formal management review structure.

10.1 Continual improvement of the ISMS

Rationale

PM-31 sets organization-wide metrics and acts on what monitoring finds, which supports improvement. PM-01 and PM-09 keep the program plan and the risk management strategy reviewed and updated.

Gaps

ISO requires explicit continual improvement processes for ISMS suitability, adequacy, and effectiveness. SP 800-53 supports continuous monitoring but doesn't explicitly require PDCA-style continual improvement methodology.

Mapped Controls

10.2 Corrective action on nonconformities and their root causes

Rationale

CA-05 (POA&M) addresses remediation of identified weaknesses. PM-04 tracks remediation plans. RA-07 (Risk Response) addresses responding to findings from assessments and audits, aligning with corrective action requirements.

Gaps

ISO requires formal nonconformity management including root cause analysis, corrective action implementation, and effectiveness review. POA&M process is close but lacks formal nonconformity management structure.

A.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, new in Rev 5, adds supply chain policy to a comprehensive policy framework.

Gaps

Minimal gap. SP 800-53 policy requirements are more granular (per-family) while ISO expects a coherent policy set.

A.5.2 Defining and assigning information security roles

Rationale

PM-02 directly assigns senior information security role. PS-01 covers personnel security roles. PS-09 (Position Descriptions) explicitly requires incorporating security and privacy roles into organizational position descriptions, strengthening role definition coverage. OSA lowered this figure from 92% on 1 November 2026, when it set one figure for this control and its twin in ISO/IEC 27002:2022, which has the same controls.

Gaps

Minimal gap. With PS-09, ISO's requirement for defined security roles and responsibilities is comprehensively addressed.

A.5.3 Segregation of duties between conflicting roles

Rationale

AC-05 directly addresses separation of duties. Comprehensive coverage. OSA lowered this figure from 95% on 1 November 2026, when it set one figure for this control and its twin in ISO/IEC 27002:2022, which has the same controls.

Gaps

Minimal gap.

Mapped Controls

A.5.4 Management responsibilities: requiring staff to follow security policies

Rationale

PS-01 sets personnel security policy. PL-04 has each person acknowledge the rules of behavior before getting access, and PS-06 has them sign access agreements. PS-07 requires external providers to follow the organization's personnel security policies. PM-01's program plan records management commitment and roles. OSA lowered this figure from 82% on 1 November 2026, when it dropped its earlier controls for management and leadership roles.

Gaps

ISO emphasizes management requiring personnel to apply security per policies. SP 800-53 is less explicit about management enforcement responsibility.

A.5.5 Staying in contact with authorities such as regulators

Rationale

IR-06 covers incident reporting to authorities. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for contact with outside security groups.

Gaps

ISO also asks for standing contact with authorities, beyond incident reporting. IR-06, the one control mapped here, covers incident reporting.

Mapped Controls

A.5.6 Joining special interest groups and security forums

Rationale

PM-15 directly covers contacts with security groups and associations. SI-05 receives security alerts and advisories from outside organizations. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for the threat awareness program and its information sharing.

Gaps

Minimal gap.

Mapped Controls

A.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 to search for indicators of compromise and detect advanced threats. OSA lowered this figure from 92% on 1 November 2026, when it dropped its earlier controls for security advisories and threat identification in risk assessment.

Gaps

RA-10 adds proactive threat hunting. Gathering advisories, and using threat intelligence in risk assessment, are outside the controls mapped here.

Mapped Controls

A.5.8 Building security into project management

Rationale

SA-03 covers security in the system development life cycle, and SA-04 sets security requirements for acquisitions. PL-08 adds the security architecture, and SA-15 the development process and standards.

Gaps

ISO specifically requires security in ALL project management regardless of project type. SA controls focus on system/software projects specifically.

A.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 includes 'associated assets' beyond information and system components. An inventory of the information itself, and of where it is held, is outside the control mapped here.

Mapped Controls

A.5.10 Acceptable use rules for information and related assets

Rationale

PL-04 directly covers rules of behavior and acceptable use. MP-02, MP-04, MP-05, MP-06 and MP-07 set rules for media access, storage, transport, sanitization and use. PE-16 and PE-20 control and track assets as they move. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for the use of external systems.

Gaps

Minimal gap.

A.5.11 Return of assets when people leave or change roles

Rationale

PS-04 covers personnel termination including return of organizational assets.

Gaps

Minimal gap.

Mapped Controls

A.5.12 Classification of information by security needs

Rationale

RA-02 covers security categorization of information and systems. Well aligned.

Gaps

Minor: ISO uses classification levels; SP 800-53 uses FIPS 199 categorization. Conceptually similar but terminology/methodology differs.

Mapped Controls

A.5.13 Labelling of information to show its classification

Rationale

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

Gaps

ISO covers labeling of all information forms. MP-03 and PE-22 mark media and hardware. Labels on digital information itself are outside the controls mapped here.

Mapped Controls

A.5.14 Rules and agreements for information transfer

Rationale

SC-07 boundary protection; SC-08 transmission confidentiality/integrity; AC-04 information flow enforcement; AC-20 external system use. CA-03 (Information Exchange) addresses information exchange agreements with external systems. AC-17, AC-18 and AC-19 cover remote, wireless and mobile connections, and PS-06 covers access agreements. OSA lowered this figure from 88% on 1 November 2026, when it dropped its earlier controls for cryptographic key management.

Gaps

Minor: ISO includes transfer agreements and policies for all forms (electronic, physical, verbal). SP 800-53 focuses on technical controls but CA-03 adds exchange agreements.

A.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. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for account management and remote access.

Gaps

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

Mapped Controls

A.5.16 Identity management from creation to removal

Rationale

IA-02 and IA-08 identify and authenticate organizational and non-organizational users. IA-04 manages identifiers, and IA-05 manages authenticators. 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.

A.5.17 Issuing and managing authentication information such as passwords

Rationale

IA-05 directly covers authenticator management (passwords, tokens, etc.), including how people must protect their authenticators.

Gaps

Minimal gap.

Mapped Controls

A.5.18 Managing access rights, including regular reviews

Rationale

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

Gaps

Minimal gap.

Mapped Controls

A.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 emphasizes ongoing supplier relationship management and periodic review. The controls here set policy and a plan, so contract terms and the oversight of service providers fall outside this mapping.

Mapped Controls

A.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 in agreements, and SR-05 adds contract tools and procurement methods.

Gaps

Minor: ISO requires specific agreement terms for information protection. SA-04 is comprehensive but format differs.

A.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 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.

Gaps

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

A.5.22 Monitoring supplier services and managing their changes

Rationale

SA-09 includes ongoing monitoring of external service providers' control compliance. SR-06 covers supplier assessments and reviews.

Gaps

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

A.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 27001:2022 added cloud-specific control. SP 800-53 addresses cloud through general external service controls but lacks cloud-specific acquisition, use, management, and exit requirements. FedRAMP supplements this.

A.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

Incident response procedures fall outside this mapping, along with the training and testing of responders.

Mapped Controls

A.5.25 Assessing whether security events are incidents

Rationale

IR-04 incident handling includes the detection and analysis of events. AU-06 reviews and analyzes audit records for unusual activity and reports what it finds. OSA lowered this figure from 90% on 1 November 2026, when it dropped its earlier controls for incident tracking and reporting.

Gaps

Minimal gap.

Mapped Controls

A.5.26 Incident response following documented procedures

Rationale

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

Gaps

Minimal gap.

Mapped Controls

A.5.27 Lessons learned from security incidents

Rationale

IR-04 includes incident analysis and feeds lessons learned from incident handling into the response procedures and training. This addresses post-incident review.

Gaps

Minor: ISO emphasizes using incident knowledge to reduce future likelihood/impact systematically. SP 800-53 less prescriptive on knowledge management from incidents.

Mapped Controls

A.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 audit record review.

Gaps

ISO focuses on digital forensics evidence handling for legal proceedings. 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

A.5.29 Keeping security in place during disruption

Rationale

The CP controls mapped here cover continuity planning and testing, alternate sites, backup and recovery. CP-13 adds alternative security mechanisms for when the primary ones are unavailable or compromised. Strong alignment.

Gaps

Minimal gap.

A.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, system recovery and alternative security mechanisms.

Gaps

ISO emphasizes ICT readiness specifically supporting business continuity plans. The controls here plan, test and assess that readiness. The capabilities that deliver it, such as alternate processing sites, backup and system recovery, fall outside this mapping.

Mapped Controls

A.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 requires explicit identification and documentation of all legal/regulatory/contractual requirements. SP 800-53 lacks a dedicated legal compliance identification control. FISMA context assumes federal requirements.

A.5.32 Intellectual property rights and software licence compliance

Rationale

No direct SP 800-53 control for intellectual property management.

Gaps

Significant gap. SP 800-53 does not address software licensing, copyright compliance, or IP protection. Requires supplementary organizational controls.

Mapped Controls

A.5.33 Protection of records against loss and misuse

Rationale

AC-03 enforces approved access to records. AU-09 protects audit information from unauthorized change or deletion, 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 asks that records be kept safe from loss, tampering and unauthorized access, as legal and regulatory requirements demand. Retention periods and broader records management, such as classification and disposal schedules, fall outside this mapping.

A.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 85% on 1 November 2026, when it dropped its earlier controls for consent and the authority to process PII, among other privacy duties.

Gaps

ISO defers to ISO 27701 for full privacy coverage. Consent and the authority to process PII fall outside this mapping.

A.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 requires independent review of the ISMS approach at planned intervals and after significant changes, beyond technical control assessment. CA-02 covers independent assessment of controls. Review of the management system as a whole is less explicit in SP 800-53.

Mapped Controls

A.5.36 Regularly checking compliance with security policies and standards

Rationale

CA-02 assesses compliance with security requirements, and CA-07 monitors control effectiveness on an ongoing basis. The policy controls mapped here, such as AC-01, require regular review of each policy and its procedures.

Gaps

Minor: ISO requires regular review that information processing complies with policies. SP 800-53 assessment approach differs from compliance checking methodology.

A.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 requires documented operating procedures for information processing facilities. SP 800-53 has family-specific procedures but no unified operating procedures control.

A.6.1 Background screening before joining and during employment

Rationale

PS-03 directly covers personnel screening before access is granted.

Gaps

Minimal gap.

Mapped Controls

A.6.2 Security responsibilities in employment contracts

Rationale

PS-06 covers access agreements 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 responsibilities in position descriptions.

Gaps

ISO 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 fall outside this mapping.

Mapped Controls

A.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 feedback on training results fall outside this mapping.

A.6.4 Disciplinary process for security policy breaches

Rationale

PS-08 covers personnel sanctions for security violations.

Gaps

ISO requires formal disciplinary process communicated to employees. PS-08 addresses sanctions but formal process establishment less detailed.

Mapped Controls

A.6.5 Security duties that continue after termination or role change

Rationale

PS-04 covers personnel termination; PS-05 covers personnel transfer. Both address ongoing responsibilities.

Gaps

Minimal gap. PS-04/PS-05 address access revocation and ongoing obligations.

Mapped Controls

A.6.6 Non-disclosure agreements to protect confidential information

Rationale

PS-06 covers access agreements which include confidentiality requirements.

Gaps

ISO specifically requires NDAs reflecting organizational needs. PS-06 is broader (access agreements) and NDA specifics are less detailed.

Mapped Controls

A.6.7 Protecting information during remote working

Rationale

AC-17 directly covers remote access controls. PE-17 covers alternate work sites.

Gaps

Minor: ISO includes remote working security policies and risk considerations beyond technical access controls (physical environment, clean desk at home).

Mapped Controls

A.6.8 Security event reporting by staff through agreed channels

Rationale

IR-06 directly covers incident reporting, 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. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for incident response assistance.

Gaps

Minimal gap.

Mapped Controls

A.7.1 Physical security perimeters around sensitive areas

Rationale

PE-03 covers physical access control, enforcing access at the facility's entry and exit points with access control devices or guards.

Gaps

Minimal gap.

Mapped Controls

A.7.2 Controlling physical entry to secure areas

Rationale

PE-02 physical access authorizations; PE-03 physical access control, which keeps access logs at entry points and escorts visitors. PE-16 controls the delivery and removal of system components. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for monitoring physical access and keeping visitor records.

Gaps

Minimal gap. Comprehensive physical entry controls.

A.7.3 Physical security of offices and other facilities

Rationale

PE-03 physical access control; PE-05 access control for output devices.

Gaps

Minor: ISO includes broader facility security design considerations.

Mapped Controls

A.7.4 Physical security monitoring of premises, such as CCTV

Rationale

PE-06 directly covers monitoring physical access. PE-03 keeps the physical access logs it reviews. 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.

Mapped Controls

A.7.5 Protecting sites from physical and environmental hazards

Rationale

PE controls cover the main environmental protections: power equipment (PE-09), fire (PE-13), temperature and humidity (PE-14) and water (PE-15). PE-23 (Facility Location) adds planning facility location considering physical and environmental hazards, directly addressing threat protection at the site selection level. 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 and emergency lighting.

Gaps

Minimal gap. PE-23 strengthens coverage by addressing hazard considerations in facility location planning.

A.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 85% on 1 November 2026, when it dropped its earlier controls for physical access and visitor control in secure areas.

Gaps

ISO includes rules for working in secure areas, such as no cameras and supervised work. The whole clause is a gap here.

A.7.7 Rules for a clear desk and a clear screen

Rationale

AC-11 covers session lock (clear screen). MP-04 covers media storage.

Gaps

Minor: ISO explicitly addresses clear desk policy. AC-11 covers screen; desk policy is implied through MP controls but not explicitly stated.

A.7.8 Siting equipment securely and protecting it from hazards

Rationale

PE-14 covers environmental controls; PE-18 location of components. PE-23 (Facility Location) addresses planning facility/site location considering physical and environmental hazards, supporting equipment siting decisions.

Gaps

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

A.7.9 Protecting assets used off-premises, such as laptops

Rationale

MP-05 protects media in transport. AC-19 sets configuration and connection requirements 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 covers all off-premises assets (laptops, paper, etc.). SP 800-53 covers media and mobile devices but physical asset protection off-site less comprehensive.

A.7.10 Managing storage media from acquisition to disposal

Rationale

The MP family covers media protection: access (MP-02), storage (MP-04), transport (MP-05), sanitization (MP-06), use (MP-07). PE-16 controls media and other components 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.

A.7.11 Reliable supporting utilities, such as power and cooling

Rationale

PE-09 power equipment protection; PE-10 emergency shutoff; PE-11 emergency power; PE-12 emergency lighting.

Gaps

Minimal gap.

A.7.12 Security of power and data cabling

Rationale

PE-04 covers access control for transmission medium. PE-09 covers power equipment/cabling protection. OSA lowered this figure from 85% on 1 November 2026, when it set one figure for this control and its twin in ISO/IEC 27002:2022, which has the same controls.

Gaps

ISO includes specific cabling security measures, such as protected routing and shielding. PE-04 is more general.

Mapped Controls

A.7.13 Secure and timely equipment maintenance

Rationale

MA-02 covers controlled maintenance: it schedules, approves and monitors all maintenance, on site or remote, and checks the controls afterwards. MA-06 gets maintenance 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

A.7.14 Removing data and software before equipment disposal or reuse

Rationale

MP-06 covers media sanitization before disposal, release or re-use. OSA lowered this figure from 92% on 1 November 2026, when it dropped its earlier controls for media use and assessing equipment for re-use.

Gaps

Minor: ISO includes all equipment disposal, while SP 800-53 focuses on media.

Mapped Controls

A.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 80% on 1 November 2026, when it dropped its earlier controls for least functionality and the encryption of stored information.

Gaps

ISO covers all user endpoint devices holistically (BYOD, MDM, containerization). AC-19 covers mobile devices such as phones and tablets, so laptops and desktops rest on AC-11 alone. Endpoint hardening and storage encryption are uncovered.

Mapped Controls

A.8.2 Limiting and controlling privileged access rights

Rationale

AC-06 directly covers least privilege including privileged access restriction, review, and authorization. Comprehensive coverage.

Gaps

Minimal gap.

Mapped Controls

A.8.3 Restricting access to information under access control rules

Rationale

AC-03 enforces approved authorizations for logical access. AC-24 applies access control decisions 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.

Mapped Controls

A.8.4 Controlling who can read and change source code

Rationale

CM-05 covers access restrictions for change, including 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 specifically addresses source code access restrictions. Here they rest on access restrictions for change and access enforcement. Version control of the source code repository is uncovered.

Mapped Controls

A.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.

A.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. OSA lowered this figure from 72% on 1 November 2026, when it dropped its earlier controls for resource availability.

Gaps

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

Mapped Controls

A.8.7 Malware protection backed by user awareness

Rationale

SI-03 directly covers malicious code protection. AT-02 builds the user awareness the clause also asks for.

Gaps

Minimal gap.

Mapped Controls

A.8.8 Technical vulnerability management, including patching

Rationale

RA-05 vulnerability monitoring and scanning; SI-02 flaw remediation; SI-05 security alerts.

Gaps

Minimal gap.

A.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, software usage restrictions, user-installed software and signed components.

Gaps

Minimal gap.

A.8.10 Deleting information once the need for it ends

Rationale

MP-06 sanitizes media before disposal, release or reuse. SI-21 deletes information when it's no longer needed, and MA-02 sanitizes equipment before it leaves for 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. OSA lowered this figure from 80% on 1 November 2026, when it dropped its earlier controls for information retention and component disposal.

Gaps

ISO specifically addresses information deletion when no longer required. SP 800-53 covers sanitization, and SI-21 deletes refreshed information when it's no longer needed. Retention schedules are uncovered here.

A.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 80% on 1 November 2026, when it dropped its earlier controls for the handling of personal data.

Gaps

ISO specifically addresses data masking techniques, such as pseudonymization, anonymization and masking. SI-19 applies them to personal data. Masking other sensitive data, in line with access policy, is less explicit.

Mapped Controls

A.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 80% on 1 November 2026, when it dropped its earlier controls for information flow enforcement and system monitoring.

Gaps

ISO specifically addresses DLP. 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.

A.8.13 Information backup with regular restore tests

Rationale

CP-09 directly covers information system backup. It sets how often to back up user and system information, in line with recovery objectives, and protects the backups. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for alternate storage sites for backups.

Gaps

Minimal gap.

Mapped Controls

A.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.

Gaps

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

Mapped Controls

A.8.15 Event logging, with logs kept safe and reviewed

Rationale

AU controls cover logging: the events to log (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 logging policy, log storage capacity, logging failures, report generation, time stamps and non-repudiation.

Gaps

Minimal gap.

A.8.16 Monitoring networks and systems for unusual behaviour

Rationale

SI-04 directly covers system monitoring. 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.

A.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 set one figure for this control and its twin in ISO/IEC 27002:2022, which has the same controls.

Gaps

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

Mapped Controls

A.8.18 Restricting privileged utility programs able to bypass controls

Rationale

AC-06 applies least privilege, so only authorized users can reach privileged utilities. AC-03 enforces approved authorizations for access. OSA lowered this figure from 85% on 1 November 2026, when it dropped its earlier controls for restricting unneeded programs and user-installed software.

Gaps

ISO specifically addresses privileged utility programs. SP 800-53 addresses them through general access controls. Removing or disabling utilities that aren't needed is now a gap.

Mapped Controls

A.8.19 Controlling what software is installed on operational systems

Rationale

CM-05 restricts access for changes, including software installation. CM-07 applies least functionality. CM-11 governs 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

A.8.20 Network security and management of network devices

Rationale

SC-07 protects the boundary and SC-08 protects 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

Small gaps remain: controlling information flows within the network, and authorizing and documenting internal system connections.

A.8.21 Security features and service levels for network services

Rationale

SA-09 requires providers of external services, including network services, to meet security requirements, and monitors their compliance. 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 requires security features, service levels and management requirements for network services. Service level specifics 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

A.8.22 Network segregation into separate security zones

Rationale

SC-07 boundary protection with segmentation. AC-04 controls information flows between segments. OSA lowered this figure from 95% on 1 November 2026, when it dropped its earlier controls for system partitioning.

Gaps

Minimal gap.

Mapped Controls

A.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 75% on 1 November 2026, when it dropped its earlier controls for malicious code protection.

Gaps

ISO specifically addresses web filtering. SP 800-53 doesn't have a dedicated web filtering control; addressed through general boundary and content controls.

Mapped Controls

A.8.24 Using cryptography, including encryption and key management

Rationale

SC-12 cryptographic key management; SC-13 cryptographic protection; SC-17 public key infrastructure certificates.

Gaps

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

Mapped Controls

A.8.25 Security built into the development life cycle

Rationale

SA-03 system development life cycle; SA-15 development process, standards and tools; SA-17 developer security 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.

Mapped Controls

A.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 and security engineering principles.

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

A.8.27 Applying secure engineering principles to system architecture

Rationale

SA-08 security engineering principles; SA-17 developer security architecture.

Gaps

Minimal gap.

Mapped Controls

A.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 and security architecture.

Gaps

ISO specifically addresses secure coding practices. The controls here set the development process, its standards, static analysis and testing. Training developers in secure coding falls outside this mapping.

A.8.29 Security and acceptance testing of new or changed systems

Rationale

SA-11 directly covers developer security testing. CA-02 security assessments. SA-04 includes testing requirements. 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.

A.8.30 Overseeing outsourced development from contract to acceptance

Rationale

SA-04 acquisition requirements; SA-10/SA-11 developer requirements apply to outsourced development. 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.

Gaps

Minor: ISO specifically addresses outsourced development supervision and acceptance. SP 800-53 covers through general acquisition controls.

A.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 and system partitioning.

Gaps

ISO explicitly requires environment separation. The controls here keep testing apart from production and restrict who changes production. Keeping development apart from both is less explicit.

Mapped Controls

A.8.32 Change management for IT systems and services

Rationale

CM-03 configuration change control, with approval that weighs security impact; CM-05 access restrictions for change; SA-10 developer configuration management. 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.

Gaps

Minimal gap.

A.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. OSA lowered this figure from 70% on 1 November 2026, when it dropped its earlier controls for developer testing and development process standards.

Gaps

ISO specifically addresses the protection of test data, such as anonymizing it and controlling the use of production data in testing. SA-03 controls the use of live data in testing. Choosing and anonymizing test data are less explicit.

Mapped Controls

A.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 78% on 1 November 2026, when it dropped its earlier controls for control assessments, audit record review and penetration testing.

Gaps

ISO requires that audit testing be planned and agreed to keep business disruption low. With no control mapped, the whole clause is a gap.

Methodology and Disclaimer

This coverage analysis maps from ISO 27001: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.