CM-02 (03) Retention of Previous Configurationscm-2.3
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-02 (03). 4 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 recipes whose output is evidence for CM-02 (03). This mapping is this project’s opinion (overlay v3.0.0), versioned separately from the dataset — the upstream FedRAMP rules name none of these tools.
No authored recipe names CM-02 (03). The nearest authored work is below.
Nobody has assessed CM-02 (03) against AWS and pipeline yet. That is a gap in this project’s research — not a finding about the control, and not a claim that nothing collects it.
The KSIs that reach it are KSI-RPL-ABO, KSI-SVC-ACM — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not CM-02 (03)
These recipes prove a KSI that reaches it. None of them claims CM-02 (03) — treat them as neighbours worth reading, not as coverage.
- AWS Config compliance results proving system data is backed up on a defined schedule — RDS automated backups enabled with a minimum retention, and AWS Backup plans meeting a minimum frequency and retention via KSI-RPL-ABO
- Restore jobs that actually ran — the schedule they ran on, whether each one completed, how long it took, and what it produced — plus the point-in-time recovery window that makes transaction-level recovery possible via KSI-RPL-ABO
- AWS Config compliance results plus the State Manager association list proving a defined configuration is actually applied and re-applied to every managed node — instances are under SSM management, and the associations that carry your baseline report COMPLIANT on a schedule rather than drifting via KSI-SVC-ACM
- The machine-maintained component inventory — Config's recorder status and discovered-resource counts proving supported resources are tracked continuously and the list stays current without anyone editing a spreadsheet, plus Systems Manager Inventory's node and installed-application metadata for what runs inside them via KSI-SVC-ACM
What NIST requires of CM-02 (03)
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Retain [number] of previous versions of baseline configurations of the system to support rollback.
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 (2)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- RPLKSI-RPL-ABOAligning Backups with Objectives
The alignment of machine-based information resource backups with defined recovery objectives is persistently reviewed.
- SVCKSI-SVC-ACMAutomating Configuration Management
The configuration of machine-based information resources is managed using automation and persistently reviewed for drift.
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.