# CM-1 — Policy and Procedures

- **Control ID:** CM-1
- **Family:** [CM](/md/families/CM.md)
- **Baselines:** low, moderate, high
- **Enhancement of:** No content available.

## Description

Develop, document, and disseminate to \[assignment\]: \[assignment\] configuration management policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls; Designate an \[assignment\] to manage the development, documentation, and dissemination of the configuration management policy and procedures; and Review and update the current configuration management: Policy \[assignment\] and following \[assignment\] ; and Procedures \[assignment\] and following \[assignment\].

## Discussion

Configuration management policy and procedures address the controls in the CM family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of configuration management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to configuration management policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.

## Implementation guidance

No content available.

## CSF 2.0 subcategories

- [GV.OC-03](/md/csf/GV.OC-03.md) — Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
- [GV.OV-01](/md/csf/GV.OV-01.md) — Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
- [GV.PO-01](/md/csf/GV.PO-01.md) — Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
- [GV.PO-02](/md/csf/GV.PO-02.md) — Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
- [GV.SC-03](/md/csf/GV.SC-03.md) — Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes
- [ID.IM-01](/md/csf/ID.IM-01.md) — Improvements are identified from evaluations
- [ID.IM-02](/md/csf/ID.IM-02.md) — ID.IM-02
- [ID.IM-03](/md/csf/ID.IM-03.md) — Improvements are identified from execution of operational processes, procedures, and activities
- [PR.PS-01](/md/csf/PR.PS-01.md) — PR.PS-01

## Related controls

- [PM-9](/md/controls/PM-9.md)
- [PS-8](/md/controls/PS-8.md)
- [SA-8](/md/controls/SA-8.md)
- [SI-12](/md/controls/SI-12.md)

---

Derived from official NIST publications (NIST SP 800-53 Rev 5 and NIST CSF 2.0). nistcontrols.com is not affiliated with NIST.