CM-03 (02) Testing, Validation, and Documentation of Changescm-3.2
Whether an AWS call fetches evidence for this control, and what to run. Its Rev5 baselines, the indicators that reach it and the FedRAMP guidance attached to it open below.
Nothing names itNo recipe names CM-03 (02). 5 reach an indicator it shares, which is adjacency and not coverage — worth reading, not worth recording as evidence for this control.
Collect evidence (0)
Authored AWS and pipeline recipes whose output is evidence for CM-03 (02). This mapping is this project’s opinion (AWS overlay v3.0.0, pipeline overlay v0.8.0), versioned separately from the dataset — the upstream FedRAMP rules name none of these tools.
No authored recipe names CM-03 (02). The nearest authored work is below.
Three collectible artifacts line up with the three verbs: a CloudFormation change set is the validated preview of what a change would do, a pipeline execution record shows the test stage that gated the deployment and whether it passed, and an approval action on that pipeline carries who signed the change off. Change Manager would carry the approval and the runbook together, but it is one of the Systems Manager capabilities AWS lists as unavailable in the GovCloud (US) Regions, so a recipe leading with it is undeliverable for a FedRAMP estate — build on the change set and the pipeline, which exist in both partitions. Whether the tests were ADEQUATE to the change is the reviewer's judgement, and a green stage cannot report it.
A recipe would call:
This project’s assessment (automation register v0.9.0, reviewed 2026-08-11), versioned separately from the dataset and from the evidence overlays. It is an opinion about the AWS surface on that date, and the surface moves.
The KSIs that reach it are KSI-CMT-LMC, KSI-CMT-RVP, KSI-CMT-VTD — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not CM-03 (02)
These recipes prove a KSI that reaches it. None of them claims CM-03 (02) — treat them as neighbours worth reading, not as coverage.
- Who changed what, when, and from which state to which — CloudTrail's record of every mutating API call and Config's per-resource configuration history, plus, where Change Manager is in use, the change-request executions that carry the approval via KSI-CMT-LMC KSI-CMT-RVP KSI-CMT-VTDaws
- Every running instance built from an image you never approved and every node carrying denylisted software, together with proof that an automated action was configured for those findings and a record of what it did when one fired via KSI-CMT-LMCaws
- For every change that reached the assessed branch, the automated verification that ran against it — which workflows ran, on which commit, and what each concluded — together with the two things that decide whether those runs were a condition of the change or merely adjacent to it: the rule that made the checks required, and the platform's own per-push record of whether that rule held, failed, or was bypassed. The runs alone are activity; the rule and the per-push record are what make them a gate. via KSI-CMT-LMC KSI-CMT-VTDpipeline
- The rule requiring the designated owners of the changed code to approve before it merges, the file that names who those owners are, the platform's own report of whether that file actually parses — and, per change, who approved, on which commit, and when. via KSI-CMT-RVPpipeline
- Patch Manager compliance state plus Amazon Inspector scan status and coverage — proving flaws are being found continuously (Inspector enabled and actually covering your resources) and that the fixes landed (per-node missing/failed patch counts and the time of the last scan or install) via KSI-CMT-VTDaws
What NIST requires of CM-03 (02)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Test, validate, and document changes to the system before finalizing the implementation of the changes.
NIST SP 800-53 Rev5 catalog 5.2.0, from usnistgov/oscal-content at 78650f0. The FedRAMP dataset carries no control text; this is borrowed and pinned.
Rev5 baseline membership
Membership is the whole relationship — a baseline is a set of control ids. Class A carries no baseline at all. The Low/Moderate/High labels are an interpretation from control counts, not a dataset fact.
KSI indicators reaching this control (3)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- CMTKSI-CMT-LMCLogging Changes
Modifications to the cloud service offering are logged and monitored.
- CMTKSI-CMT-RVPReviewing Change Procedures
The effectiveness of documented change management procedures is persistently reviewed.
- CMTKSI-CMT-VTDValidating Throughout Deployment
Persistent testing and validation of changes throughout deployment is automated.
Pages exist for the 209 controls reached by at least one KSI. Baseline-only controls are the orphans on /coverage. Control titles and full text live in the NIST catalog, not this dataset.