CMMC 2.0
Configuration Management

CMMC 2.0 CM.L2-3.4.4: Security Impact Analysis

Analyze the security impact of a proposed change before it is implemented.

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

What else in your programme already covers this

This control maps to 42 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.

  • NIST-CSF-DE.AE-04 The estimated impact and scope of adverse events are understood
  • NIST-CSF-ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded
  • 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
  • NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated

PCI DSS 4.0 · 5 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 11.3.1.3 11.3.1.3 Internal scans after significant change
  • 12.5.3 12.5.3 Scope review after significant organisational change
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change

ISO 27001:2022 · 4 controls

  • 5.8 Information security in project management
  • 8.27 Secure system architecture and engineering principles
  • 8.29 Security testing in development and acceptance
  • 8.32 Change management
  • SEC01-BP07 Identify threats and prioritize mitigations using a threat model
  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP04 Conduct code reviews

C5 (Germany) · 2 controls

  • C5-DEV-05 Risk assessment, categorisation and prioritisation of changes
  • C5-DEV-06 Testing changes

FedRAMP High · 2 controls

  • CM-4 Impact Analyses
  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))

FedRAMP Moderate · 2 controls

  • CM-4 Impact Analyses
  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))

ISO 27002:2022 · 2 controls

  • 8.26 Application security requirements
  • 8.32 Change management

ISO 27701:2019 · 2 controls

  • 6.11.2 Security in development and support processes
  • 7.2.5 Privacy impact assessment

ISO/IEC 42001:2023 · 2 controls

  • 6.1.2 AI risk assessment
  • 8.2 AI risk assessment

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

APRA CPS 234 · 1 control

  • CPS234-P31 Annual Review of Testing Program Sufficiency
  • CFTC-SS-32 Timely Advance Notice of Material Planned Changes

CIS Controls v8 · 1 control

  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure

HIPAA Security Rule · 1 control

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

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

CMMC 2.0 CM.L2-3.4.4 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.

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.

Query this from an agent

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