ISO 27002:2022
Organizational controls – ISO 27002:2022

ISO 27002:2022 5.36: Compliance with policies, rules and standards for information security

Requires compliance with the organisation's own information security policy, topic specific policies, rules and standards to be reviewed regularly.

What else in your programme already covers this

This control maps to 147 controls across 35 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 16 controls

  • NIST800-AU-1 Policy and procedures for audit and accountability
  • NIST800-AU-6 Audit record review, analysis, and reporting
  • NIST800-CA-2 Control assessments
  • NIST800-CA-5 Plan of action and milestones
  • NIST800-CA-7 Continuous monitoring
  • NIST800-CM-13 Data Action Mapping. Develop and document a map of system data actions
  • NIST800-PM-1 Information Security Program Plan. Develop and disseminate an organization-wide information security program plan that: Provides an overview of the requirements for the security program and a description of the security program management controls and
  • NIST800-PM-14 Testing, Training, and Monitoring. Implement a process for ensuring that organizational plans for conducting security and privacy testing, training, and monitoring activities associated with organizational systems: Are developed and maintained; and Continue to be
  • NIST800-PM-27 Privacy Reporting. Develop [organization-defined] and disseminate to: [organization-defined] to demonstrate accountability with statutory, regulatory, and policy privacy mandates; and [organization-defined] and other personnel with responsibility for monitoring privacy program compliance; and Review and update
  • NIST800-PM-32 Purposing. Analyze [organization-defined] supporting mission essential services or functions to ensure that the information resources are being used consistent with their intended purpose
  • NIST800-PM-4 Plan of Action and Milestones Process. Implement a process to ensure that plans of action and milestones for the information security, privacy, and supply chain risk management programs and associated organizational systems: Are developed
  • NIST800-PM-6 Measures of Performance. Develop, monitor, and report on the results of information security and privacy measures of performance
  • NIST800-PT-1 Policy and Procedures. Develop, document, and disseminate to [organization-defined]: [organization-defined] personally identifiable information processing and transparency policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent
  • NIST800-PT-8 Computer Matching Requirements. When a system or organization processes information for the purpose of conducting a matching program: Obtain approval from the Data Integrity Board to conduct the matching program; Develop and enter into
  • NIST800-RA-3 Risk assessment
  • SP800-53-PL Planning Family

ISO 22301:2019 · 13 controls

  • 10.1 Nonconformity and corrective action
  • 10.2 Continual improvement
  • 4.4 Business continuity management system
  • 5.2.1 Establishing the business continuity policy
  • 6.1.1 Determining risks and opportunities
  • 6.2 Business continuity objectives and planning to achieve them
  • 7.5.3 Control of documented information
  • 8.3.1 General
  • 8.4.1 General
  • 8.6 Evaluation of business continuity documentation and capabilities
  • 9.1 Monitoring, measurement, analysis and evaluation
  • 9.2.2 Audit programme(s)
  • 9.3.2 Management review input

ISO 27701:2019 · 13 controls

  • 5.2.4 Information security management system
  • 5.4 Planning
  • 5.5 Support
  • 5.6 Operation
  • 5.6.3 Information security risk treatment
  • 5.7 Performance evaluation
  • 5.8 Improvement
  • 5.8.1 Nonconformity and corrective action
  • 5.8.2 Continual improvement
  • 6.15 Compliance
  • 6.15.2 Information security reviews
  • 6.6.3 User responsibilities
  • 8.5.4 Notification of PII disclosure requests

PCI DSS 4.0 · 11 controls

  • 12.1.1 An overall information security policy is: • Established. • Published. • Maintained. • Disseminated to all relevant personnel, as well as to relevant vendors and business partners
  • 12.1.2 The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment
  • 12.3.2 TRA for customized approach
  • 12.4.2 Quarterly PCI compliance reviews (SP)
  • 12.4.2.1 Documentation of quarterly reviews (SP)
  • 2.1.1 All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 5.1.1 All security policies and operational procedures that are identified in Requirement 5 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 6.1.1 All security policies and operational procedures that are identified in Requirement 6 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 9.1.1 All security policies and operational procedures that are identified in Requirement 9 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 3.1.1 All security policies and operational procedures that are identified in Requirement 3 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
  • 6.5.2 Upon completion of a significant change, all applicable PCI DSS requirements are confirmed to be in place on all new or changed systems and networks, and documentation is updated as applicable

SOC 2 · 9 controls

  • SOC2-CC1.1 COSO principle 1: Demonstrates commitment to integrity and ethical values
  • SOC2-CC2.2 COSO principle 14: Internally communicates information including objectives and responsibilities
  • SOC2-CC4.1 COSO principle 16: Selects and develops ongoing and separate evaluations
  • SOC2-CC4.2 COSO principle 17: Evaluates and communicates deficiencies in a timely manner
  • SOC2-CC5.3 COSO principle 12: Deploys control activities through policies and procedures
  • SOC2-CC6.3 Role-based access and least privilege are enforced
  • SOC2-PI1.2 System inputs are complete, accurate, and processed in a timely manner
  • SOC2-PI1.3 System processing is complete, valid, accurate, timely, and authorized
  • SOC2-PI1.4 System outputs are complete, valid, accurate, timely, and distributed

CIS Controls v8 · 6 controls

  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-18.4 Validate Security Measures
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-2.3 Address Unauthorized Software
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure

FedRAMP High · 5 controls

  • CA-2 Control Assessments
  • CA-5 Plan of Action and Milestones
  • CA-7 Continuous Monitoring
  • CA-7(4) Continuous Monitoring | Risk Monitoring. Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following: (a) Effectiveness monitoring; (b) Compliance monitoring; and (c) Change monitoring
  • SI-11 Error Handling

FedRAMP Moderate · 5 controls

  • CA-2 Control Assessments
  • CA-5 Plan of Action and Milestones
  • CA-7 Continuous Monitoring
  • CA-7(4) Continuous Monitoring | Risk Monitoring. Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following: (a) Effectiveness monitoring; (b) Compliance monitoring; and (c) Change monitoring
  • SI-11 Error Handling

ISO/IEC 42001:2023 · 5 controls

  • 10.1 Continual improvement
  • 6.1.3 Risk treatment
  • 9.1 Monitoring, measurement, analysis and evaluation
  • A.6.2.4 AI system verification and validation
  • A.9.4 Intended use of the AI system
  • CA-2 Control Assessments
  • CA-5 Plan of Action and Milestones
  • CA-7 Continuous Monitoring
  • CA-7(4) Continuous Monitoring | Risk Monitoring. Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following: (a) Effectiveness monitoring; (b) Compliance monitoring; and (c) Change monitoring
  • SI-11 Error Handling
  • CA-2 Control Assessments
  • CA-5 Plan of Action and Milestones
  • CA-7 Continuous Monitoring
  • CA-7(4) Continuous Monitoring | Risk Monitoring. Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following: (a) Effectiveness monitoring; (b) Compliance monitoring; and (c) Change monitoring
  • SI-11 Error Handling

APRA CPS 234 · 4 controls

  • CPS234-21 Implementation of Information Security Controls
  • CPS234-22 Systematic Control Testing Program
  • CPS234-25 Internal Audit Review of Information Security Controls
  • CPS234-28 Escalation of Unremediated Testing Deficiencies
  • NIST-CSF-GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
  • NIST-CSF-GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes
  • NIST-CSF-ID.RA-08 Processes for receiving, analyzing, and responding to vulnerability disclosures are established
  • CA-2 Control Assessments
  • CA-5 Plan of Action and Milestones
  • CA-7 Continuous Monitoring
  • CA-7(4) Continuous Monitoring | Risk Monitoring. Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following: (a) Effectiveness monitoring; (b) Compliance monitoring; and (c) Change monitoring
  • CPS230-24 Design and Embedding of Internal Controls
  • CPS230-P30 Monitoring, Review and Testing of Control Effectiveness
  • CPS230-P31 Remediation of Material Operational Risk Weaknesses
  • ISM-1478 The CISO oversees their organisation's cyber security program and ensures their organisati
  • ISM-1526 System owners continuously monitor the security of each system, and manage associated cybe
  • ISM-1587 System owners report the security status of each system to its authorising officer at leas
  • ASBv3-GS-5 Define and implement security posture management strategy
  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources
  • PV-2 Audit and enforce secure configurations

CMMC 2.0 · 3 controls

ISO 27001:2022 · 3 controls

  • 5.35 Independent review of information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.4 Management responsibilities

C5 (Germany) · 2 controls

  • C5-COM-03 Internal audits of the information security management system
  • C5-SP-03 Exceptions from Existing Policies and Instructions

DORA · 2 controls

HIPAA Security Rule · 2 controls

NIS2 Directive · 2 controls

  • Art.21.2.f Policies and procedures to assess the effectiveness of the cybersecurity risk-management measures
  • Art.21.4 Take corrective measures without undue delay on finding that the measures are not met

NIST SP 800-171 Rev 3 · 2 controls

  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions
  • SEC04-BP04 Initiate remediation for non-compliant resources
  • AUCDR-IS-STEP4 Step 4 - Implement a formal controls assessment program
  • AEO-13 Measurement, Analyses and Improvement

GDPR · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Organizational controls – ISO 27002:2022

You are reading one control. How much of ISO 27002:2022 have you already done?

ISO 27002:2022 5.36 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 147 it maps to, and the evidence behind each claim, over MCP and REST.