CMMC 2.0
Configuration Management

CMMC 2.0 CM.L2-3.4.3: System Change Management

Track changes to systems, review them, approve or reject them, and log the decision together with the change.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

PCI DSS 4.0 · 9 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 10.2.1.5 10.2.1.5 Logs capture changes to identification and authentication credentials
  • 10.3.4 10.3.4 File integrity monitoring on audit logs
  • 11.3.1.3 11.3.1.3 Internal scans after significant change
  • 11.5.2 11.5.2 Change detection on critical files
  • 4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change

CIS Controls v8 · 6 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure
  • CIS-6.1 Establish an Access Granting Process
  • CIS-7.3 Perform Automated Operating System Patch Management
  • CIS-8.5 Collect Detailed Audit Logs

NIST SP 800-53 Rev 5 · 5 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 4 controls

C5 (Germany) · 3 controls

  • C5-DEV-03 Policies for changes to information systems
  • C5-DEV-07 Logging of changes
  • C5-DEV-09 Approvals for provision in the production environment

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.32 Change management
  • 8.9 Configuration management

NIST Cybersecurity Framework 2.0 · 3 controls

  • 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
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied

AWS Well-Architected Security Pillar · 2 controls

Azure Security Benchmark · 2 controls

  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources
  • DS-6 Enforce security of workload throughout DevOps lifecycle

FedRAMP High · 2 controls

  • CM-3 Configuration Change Control
  • CM-3(2) Testing, Validation, and Documentation of Changes

FedRAMP Moderate · 2 controls

  • CM-3 Configuration Change Control
  • CM-3(2) Testing, Validation, and Documentation of Changes

ISO 27002:2022 · 2 controls

  • 8.32 Change management
  • 8.9 Configuration management

ISO 27701:2019 · 2 controls

  • 6.11.2 Security in development and support processes
  • 6.9.1 Operational procedures and responsibilities

NIST SP 800-218 · 2 controls

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-5 Systems Development and Quality Assurance Category

DISA Security Technical Implementation Guides (STIGs) · 1 control

  • STIG-PGM-3 Change control and configuration-drift prevention

ISO 22301:2019 · 1 control

  • 6.3 Planning changes to the business continuity management system

ISO/IEC 42001:2023 · 1 control

NIS2 Directive · 1 control

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

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

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 Configuration Management

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 CM.L2-3.4.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gapsIf you hold NIST SP 800-171 Rev 394.5% covered · 6 gapsIf you hold NIST SP 800-53 Rev 585.5% covered · 16 gapsIf you hold ISO 27001:202279.1% covered · 23 gapsIf you hold ISO 27002:202267.3% covered · 36 gapsIf you hold CIS Controls v864.5% covered · 39 gaps

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. 1 were rejected on the FedRAMP Moderate pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll CMMC 2.0 controls