EvidenceSheet
FedRAMP High (NIST SP 800-53 Rev 5 baseline) · CM - Configuration Management

CM-1 Policy and Procedures

Develop, document, disseminate and review the policy for configuration management, and its procedures, on the FedRAMP-defined cadence: policy at least annually under High and at least every three years under Moderate, procedures at least annually and after significant changes under both.

Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), CM-1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open FedRAMP High (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

6
artefacts
4
held by a system
0
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • SSP CM-1 statement naming the configuration management policy owner, its review cadence (policy yearly for High, at least every three years for Moderate; procedures yearly for both) and the change procedure it governs · Cloud console / configuration management
  • Software inventory generated from authoritative discovery tooling · Cloud console / configuration management
  • Emergency change records with retroactive approvals · Cloud console / configuration management
  • Approved baseline configurations for each platform family · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Configuration management policy with review signatures and version history · Policy repository / GRC workspace
  • Configuration management policy and change control procedure · Policy repository / GRC workspace

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CA-9 Internal System Connections · CM-2 Baseline Configuration