CM-02 Baseline Configuration
Configuration Management
Description
a. Develop, document, and maintain under configuration control, a current baseline configuration of the system; and b. Review and update the baseline configuration of the system: 1. [Assignment: organization-defined frequency]; 2. When required due to [Assignment: organization-defined circumstances]; and 3. When system components are installed or upgraded.
Supplemental Guidance
Baseline configurations for systems and system components include connectivity, operational, and communications aspects of systems. Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, or changes to systems and include security and privacy control implementations, operational procedures, information about system components, network topology, and logical placement of components in the system architecture. Maintaining baseline configurations requires creating new baselines as organizational systems change over time. Baseline configurations of systems reflect the current enterprise architecture.
Changes from Rev 4
Adds requirement to update baseline configuration document at organizationally-defined frequencies and for organizationally-defined circumstances (in addition to when changes are made) Incorporates withdrawn control CM-02(1)
Enhancements (4)
What NIST adds to this control. Select one to read its statement.
CM-02(02) Automation Support for Accuracy and Currency ModerateHigh
Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using [Assignment: organization-defined automated mechanisms].
CM-02(03) Retention of Previous Configurations ModerateHigh
Retain [Assignment: organization-defined number] of previous versions of baseline configurations of the system to support rollback.
CM-02(06) Development and Test Environments
Maintain a baseline configuration for system development and test environments that is managed separately from the operational baseline configuration.
CM-02(07) Configure Systems and Components for High-risk Areas ModerateHigh
a. Issue [Assignment: organization-defined systems or system components] with [Assignment: organization-defined configurations] to individuals traveling to locations that the organization deems to be of significant risk; and b. Apply the following controls to the systems or components when the individuals return from travel: [Assignment: organization-defined controls].
Patterns that use this control (23)
Grouped by the emphasis each pattern gives it.
Critical (11)
- SP-001 Client Module
- SP-002 Server Module
- SP-008 Public Web Server Pattern
- SP-011 Cloud Computing Pattern
- SP-015 Secure Remote Working
- SP-023 Industrial Control Systems
- SP-025 Advanced Monitoring and Detection
- SP-026 PCI Full Environment
- SP-028 Secure DevOps Pipeline Pattern
- SP-045 AI Governance and Responsible AI
- SP-049 AI in Security Operations (draft)
Important (10)
- SP-012 Secure Software Development Lifecycle
- SP-017 Secure Network Zone Module
- SP-029 Zero Trust Architecture
- SP-030 API Security
- SP-036 Incident Response
- SP-037 Privileged User Management
- SP-038 Vulnerability Management and Patching
- SP-046 External Attack Surface Management
- SP-047 Secure Agentic AI Frameworks
- SP-054 CBDC and Digital Currency Infrastructure (draft)
MITRE ATT&CK Techniques (287)
ATT&CK v16.1Techniques mitigated by this control, mapped via CTID.