Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
CCC - Change Control & Configuration Management

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CCC-01: Change Management Policy and Procedures

Keep approved change management policies and procedures covering the risk of changing applications, systems, infrastructure and configuration, whether the asset is run in-house or by a supplier, and review them at least annually.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

FedRAMP High · 4 controls

  • CM-1 Policy and Procedures
  • CM-3 Configuration Change Control
  • CM-9 Configuration Management Plan
  • SA-10 Developer Configuration Management

FedRAMP Moderate · 4 controls

  • CM-1 Policy and Procedures
  • CM-3 Configuration Change Control
  • CM-9 Configuration Management Plan
  • SA-10 Developer Configuration Management

NIST SP 800-161 Rev 1 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

C5 (Germany) · 3 controls

PCI DSS 4.0 · 3 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • 6.5.1 6.5.1 Change control procedure for production

ISO 27001:2022 · 2 controls

  • 8.19 Installation of software on operational systems
  • 8.32 Change management

ISO 27002:2022 · 2 controls

  • 8.19 Installation of software on operational systems
  • 8.32 Change management
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

SOC 2 · 2 controls

  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • CPS230-9 Management of the Full Range of Operational Risks
  • ASBv3-GS-5 Define and implement security posture management strategy
  • CFTC-SS-5 Systems Development and Quality Assurance Category

CIS Controls v8 · 1 control

  • CIS-4.1 Establish and Maintain a Secure Configuration Process

CMMC 2.0 · 1 control

  • CCC-01 Change Management Policy and Procedures

DORA · 1 control

EU AI Act · 1 control

ISO 22301:2019 · 1 control

  • 6.3 Planning changes to the business continuity management system

ISO 27018:2019 · 1 control

  • 12.1.2 Change management

ISO 27701:2019 · 1 control

  • 6.9.1 Operational procedures and responsibilities

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST SP 800-218 · 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 CCC - Change Control & Configuration Management

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CCC-01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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