NIST SP 800-53 Rev 5
CM - Configuration Management

NIST SP 800-53 Rev 5 NIST800-CM-1: CM-1 Policy and Procedures

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): organization-level; mission/business process-level; system-level] configuration management policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the configuration management policy and procedures; and c. Review and update the current configuration management: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

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

What else in your programme already covers this

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

CMMC 2.0 · 4 controls

ISO 22301:2019 · 4 controls

  • 5.2.1 Establishing the business continuity policy
  • 6.1.2 Addressing risks and opportunities
  • 7.5.3 Control of documented information
  • 8.1 Operational planning and control

PCI DSS 4.0 · 4 controls

  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs
  • 1.2.8 1.2.8 NSC configuration files secured and consistent
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • 2.2.1 2.2.1 System configuration standards maintained

ISO 27001:2022 · 2 controls

  • 5.37 Documented operating procedures
  • 8.9 Configuration management
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied

NIST SP 800-128 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • ASBv3-GS-5 Define and implement security posture management strategy

C5 (Germany) · 1 control

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

CIS Controls v8 · 1 control

  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • ITSG33-CM Configuration Management (CM)
  • CCM-CCC-01 Change Management Policy and Procedures

FedRAMP High · 1 control

  • CM-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • CM-1 Policy and Procedures

ISO 27002:2022 · 1 control

  • 8.9 Configuration management

ISO 27701:2019 · 1 control

  • 6.2.1 Management direction for information security
  • CM-1 CM-1 Policy and Procedures
  • CM-1 CM-1 Policy and Procedures
  • CM-1 CM-1 Policy and Procedures

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-1 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 37 it maps to, and the evidence behind each claim, over MCP and REST.