CM-2 Baseline configuration
What the standard requires
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. [frequency]; 2. When required due to [circumstances] ; and 3. When system components are installed or upgraded.
Quoted verbatim from NIST SP 800-53 Rev 5 (OSCAL catalog), which is in the public domain.
Maps to 2 controls in 2 other frameworks
| Framework | Control |
|---|---|
| HITRUST CSF v11 | 09.b.03 Development, test and production environments are separated |
| NIST Cybersecurity Framework (1.1, legacy) | PR.IP-1 Baseline configuration created and maintained |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to FedRAMP Moderate’s Configuration Management family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.