NIST SP 800-53 Rev 5
CM - Configuration Management

NIST SP 800-53 Rev 5 NIST800-CM-9: CM-9 Configuration Management Plan

Develop, document, and implement a configuration management plan for the system that: a. Addresses roles, responsibilities, and configuration management processes and procedures; b. Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items; c. Defines the configuration items for the system and places the configuration items under configuration management; d. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; and e. Protects the configuration management plan from unauthorized disclosure and modification.

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 56 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.1 1.2.1 Ruleset configuration standards for NSCs
  • 10.3.3 10.3.3 Audit logs promptly backed up to central secure storage
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • 2.2.1 2.2.1 System configuration standards maintained
  • 6.5.1 6.5.1 Change control procedure for production
  • 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-2(3) Retention of Previous Configurations
  • CM-8(1) Updates During Installation and Removal
  • CM-9 Configuration Management Plan

FedRAMP Moderate · 3 controls

  • CM-2(3) Retention of Previous Configurations
  • CM-8(1) Updates During Installation and Removal
  • CM-9 Configuration Management Plan

ISO 27001:2022 · 3 controls

  • 5.37 Documented operating procedures
  • 8.32 Change management
  • 8.9 Configuration management

ISO 27002:2022 · 3 controls

  • 5.37 Documented operating procedures
  • 8.32 Change management
  • 8.9 Configuration management

NIST SP 800-128 · 3 controls

API 1164 · 2 controls

  • API1164-14 Physical Security
  • API1164-22 Configuration management for OT systems

CIS Controls v8 · 2 controls

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

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 22301:2019 · 2 controls

  • 7.5 Documented information
  • 7.5.2 Creating and updating

ISO/IEC 27019:2024 · 2 controls

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

ISO/IEC 42001:2023 · 2 controls

  • 7.5.2 Creating and updating documented information
  • 8.1 Operational planning and control

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
  • AS9100D-8.1 Operational Planning and Control
  • Clause 10 Change and configuration management
  • SUP.8 Configuration Management
  • ASBv3-GS-5 Define and implement security posture management strategy

C5 (Germany) · 1 control

  • C5-DEV-03 Policies for changes to information systems

CMMC 2.0 · 1 control

  • CA-ITSG33-SC-01 Security Control Catalogue
  • CCM-CCC-01 Change Management Policy and Procedures

EU AI Act · 1 control

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

HIPAA Security Rule · 1 control

  • ISO-26262-8-7 Configuration management
  • 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-218 · 1 control

  • CM-9 CM-9 Configuration Management Plan
  • CM-9 CM-9 Configuration Management Plan

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

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • 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-9 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.