NIST SP 800-171 Rev 3
03.04 CM (Configuration Management)

NIST SP 800-171 Rev 3 03.04.03: Configuration Change Control

Define and document types of changes that require configuration change control; review proposed changes; approve or disapprove with explicit consideration of security impact.

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

What else in your programme already covers this

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

C5 (Germany) · 4 controls

  • C5-AM-03 Commissioning of Hardware
  • 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
  • ASBv3-DS-3 Secure DevOps infrastructure
  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources
  • DS-6 Enforce security of workload throughout DevOps lifecycle
  • CFTC-SS-32 Timely Advance Notice of Material Planned Changes
  • CFTC-SS-4 Systems Operations Category
  • CFTC-SS-5 Systems Development and Quality Assurance Category

ISO 27001:2022 · 3 controls

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

NIST SP 800-218 · 3 controls

  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP06 Deploy software programmatically

FedRAMP High · 2 controls

  • CM-3 Configuration Change Control
  • CM-9 Configuration Management Plan

FedRAMP Moderate · 2 controls

  • CM-3 Configuration Change Control
  • CM-9 Configuration Management Plan

NIST SP 800-53 Rev 5 · 2 controls

PCI DSS 4.0 · 2 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 6.5.1 6.5.1 Change control procedure for production
  • ANSSI-HYG-34 Define an Update Policy for Information System Components

CMMC 2.0 · 1 control

ISO 27002:2022 · 1 control

  • 8.32 Change management

ISO 27701:2019 · 1 control

  • 6.9.1 Operational procedures and responsibilities

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-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

  • CE-FW.4 Approve and Document Inbound Rules

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 03.04 CM (Configuration Management)

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

NIST SP 800-171 Rev 3 03.04.03 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 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. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

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