CM-2: Develop, document, and maintain a current baseline configuration of the system
Vallum evidence mapping for NIST SP 800-53 CM-2 — develop, document, and maintain a current baseline configuration of the system. This page documents what evidence Vallum produces, what it does not produce, and what remains the customer's responsibility.
Source Attribution
- Framework
- NIST SP 800-53 Rev 5
- Control ID
- CM-2
- Source Organization
- NIST
- Official Source
- NIST SP 800-53 Rev 5 ↗
- Control Objective
- Develop, document, and maintain a current baseline configuration of the system
Evidence Vallum Produces
Configuration-change receipts, inventory attestation records, and baseline-comparison evidence
Evidence Vallum Does NOT Produce
Infrastructure configuration state, OS-level patch status, or hardware inventory records
Known Limitations
Vallum produces evidence relevant to this control but does not enforce the control at the infrastructure, network, or operating-system level. Evidence covers Vallum-managed operations only. Customer systems, third-party integrations, and infrastructure controls require separate evidence sources.
Your Responsibilities
Maintain infrastructure baselines, manage OS and application patches, document configuration standards, and perform drift detection
External Controls Required
Identity provider (IdP), network firewall and segmentation, infrastructure monitoring, endpoint protection, and organizational security policies
Residual Risk
Vallum evidence covers authorization and evidence-layer operations. Gaps exist at infrastructure, network, and physical layers that require complementary controls. Time-of-check to time-of-use windows exist between evidence capture and verification.
Relevant Titan Components
Related Content
Related Threats
Related Architectures
Need a detailed evidence mapping for your specific compliance program?
Request a Control Evidence Mapping