CM-1 Policy and procedures
Configuration management policy and procedures: documenting, distributing, owning and periodically reviewing the policy and procedures behind baselines, change control and secure settings.

Configuration management (CM) family of NIST SP 800-53 Rev. 5: baseline configurations, change control, impact analysis, secure settings, least functionality, component inventory, software restrictions and signed components.
Configuration management policy and procedures: documenting, distributing, owning and periodically reviewing the policy and procedures behind baselines, change control and secure settings.
Developing and keeping a current baseline configuration of the system under configuration control and updating it periodically and when components change, plus enhancements for automation, keeping previous configurations and configuring components used in high-risk areas.
Configuration change control: which changes are controlled, review and approval with security and privacy impact analysis, documenting decisions, implementing approved changes, keeping change records and oversight by a defined change control body.
Analyzing proposed system changes for potential security and privacy impacts before implementation, plus enhancements for separate test environments and verifying controls after a change.
Defining, approving and enforcing physical and logical access restrictions on who can change the system, plus enhancements for automated enforcement with audit records, dual authorization and limiting production privileges.
Secure configuration settings: documenting the most restrictive settings consistent with operations using common secure configurations, applying them, approving deviations and controlling changes, plus automated management and response to unauthorized changes.
Least functionality: configuring systems to provide only mission-essential capabilities and restricting unneeded functions, ports, protocols, software and services, plus periodic review and allow-listing enhancements.
Building and maintaining an accurate inventory of system components at a useful level of detail without duplicates, reviewed at a defined frequency, plus enhancements for updates on installation, automated maintenance and unauthorized component detection.
The configuration management plan: roles and processes, identifying and managing configuration items through the life cycle, approval of the plan and protecting it from unauthorized disclosure and change.
Using software and documentation in line with contracts and copyright law, tracking quantity-licensed software and controlling peer-to-peer file sharing, plus the open-source software enhancement.
Governing software that users install: setting installation policies, enforcing them through defined methods and monitoring compliance, plus enhancements for privileged installation and automated enforcement.
Information location: documenting where defined information is processed and stored, on which components, who has access there, and changes to location, plus the automated tools enhancement in the moderate and high baselines.
Data action mapping: documenting a map of the system operations that process personally identifiable information across its life cycle, a privacy-focused control outside the SP 800-53B baselines.
Blocking installation of defined software and firmware components unless their digital signature is verified against a certificate the organization recognizes and approves; not in any SP 800-53B baseline.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.