CM-02 Baseline Configurationcm-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.
Partial1 of 1 recipe reaches CM-02, and none is rated full — the output narrows the question, a human judgement closes it.
AWS Config · AWS Systems Manager1 recipe · 3 calls
Collect evidence (1)
Authored AWS recipes whose output is evidence for CM-02. 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.
What NIST requires of CM-02
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
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.
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 (5)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- CMTKSI-CMT-RMVRedeploying vs Modifying
Changes to machine-based information resources are executed through the redeployment of version controlled resources rather than direct modification wherever reasonable.
- CNAKSI-CNA-DFPDefining Functionality and Privileges
The functionality and privileges for infrastructure and services are strictly defined.
- CNAKSI-CNA-IBPImplementing Best Practices
The use and configuration of third-party machine-based information resources is persistently compared against the original provider's best practices and guidance.
- MLAKSI-MLA-EVCEvaluating Configurations
The configuration of machine-based information resources, especially infrastructure as code, is persistently evaluated and tested.
- 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.