NIST SP 800-53 Rev 5
CM - Configuration Management

NIST SP 800-53 Rev 5 NIST800-CM-4: CM-4 Impact Analyses

Analyze changes to the system to determine potential security and privacy impacts prior to change implementation.

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

What else in your programme already covers this

This control maps to 105 controls across 58 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 · 5 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 12.5.3 12.5.3 Scope review after significant organisational change
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change
  • 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
  • ASD37-04 User application hardening (Essential)
  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)

BSI IT-Grundschutz · 3 controls

  • BSI-23 Baseline configuration establishment
  • BSI-24 Configuration change control
  • BSI-26 System component inventory

FedRAMP High · 3 controls

  • CM-3(2) Testing, Validation, and Documentation of Changes
  • CM-4 Impact Analyses
  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))

FedRAMP Moderate · 3 controls

  • CM-3(2) Testing, Validation, and Documentation of Changes
  • CM-4 Impact Analyses
  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))

API 1164 · 2 controls

  • API1164-14 Physical Security
  • API1164-22 Configuration management for OT systems
  • SEC01-BP07 Identify threats and prioritize mitigations using a threat model
  • SEC11-BP04 Conduct code reviews

CMMC 2.0 · 2 controls

FedRAMP Rev 5 · 2 controls

  • FEDRAMP-CM-1 Configuration Management Policy
  • FEDRAMP-CM-2 Baseline Configuration
  • IEC62304-4.1 Quality Management System
  • IEC62304-5.1 Software Development Planning

IEC 62443 · 2 controls

  • IEC62443-14 System security hardening
  • IEC62443-22 Configuration management for OT systems

ISO/IEC 27019:2024 · 2 controls

  • ISO27019-14 System security hardening
  • ISO27019-22 Configuration management for OT systems

ISO/IEC 42001:2023 · 2 controls

  • 6.1.4 AI system impact assessment
  • 8.2 AI risk assessment

NIST SP 1800-32 · 2 controls

NIST SP 800-190 · 2 controls

  • NISTSP82-1 OT Security Program Governance, Policy, Roles, and Safety-Security Integration
  • NISTSP82-5 OT Configuration Management, Patching, Vulnerability Management, and Malware Protection

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
  • CPS230-P26 Assessment of Business and Strategic Decisions on the Risk Profile
  • AS9100D-8.1 Operational Planning and Control
  • Clause 10 Change and configuration management
  • SUP.8 Configuration Management

C5 (Germany) · 1 control

  • C5-DEV-05 Risk assessment, categorisation and prioritisation of changes
  • CFTC-SS-32 Timely Advance Notice of Material Planned Changes

CIS Controls v8 · 1 control

  • CIS-16.8 Separate Production and Non-Production Systems
  • CA-ITSG33-SC-01 Security Control Catalogue

EU AI Act · 1 control

  • CJIS-7 Configuration Management
  • CAT-D3-3 Corrective controls
  • FFIEC-10 Secure configuration standards
  • ISO-26262-8-7 Configuration management

ISO 27001:2022 · 1 control

  • 8.32 Change management

ISO 27002:2022 · 1 control

  • 8.32 Change management

ISO 27701:2019 · 1 control

  • 7.2.5 Privacy impact assessment
  • ISO20000-10 Configuration management

ISO/IEC 27400:2022 · 1 control

  • 27400-6.4 Default Configuration Security

ITIL 4 · 1 control

  • ITIL4-10 Configuration management
  • NISTPF-8 Protect-P Information Protection Processes (PR.PO-P)

NIST SP 800-128 · 1 control

NIST SP 800-218 · 1 control

  • CM-4 CM-4 Impact Analyses
  • CM-4 CM-4 Impact Analyses
  • CM-4 CM-4 Impact Analyses

OSFI B-13 · 1 control

  • OSFIB13-3 Cyber Security: Identification, Protection, Detection, Response, Recovery
  • OMANCS-5 Network, Endpoint, System Development, and Configuration Security
  • OPENBANK-3 Mutual TLS, Token Binding, Request Signing (JWS), Key Management

PCI P2PE · 1 control

  • PCI-P2PE-10 Secure configuration standards

PCI PIN Security · 1 control

  • PCI-PIN-10 Secure configuration standards

PCI SSF · 1 control

  • PCI-SSF-10 Secure configuration standards

PSD2 SCA · 1 control

  • PSDTWO-2 SCA Exemptions and Risk-Based Authentication
  • CISABD-1 Take Ownership of Customer Security Outcomes

South Korea ISMS-P · 1 control

  • ISMSP-SYS-01 System Hardening and Patch Management

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

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-CM-4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 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. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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