CM-2(3)—Baseline Configuration | Retention of Previous Configurations
IL4 Mod
IL4 High
IL5
IL6
>Control Description
Retain ⚙organization-defined number of previous versions of baseline configurations of the system to support rollback.
>DoD Impact Level Requirements
FedRAMP Parameter Values
CM-2 (3) [organization-defined number of previous versions of baseline configurations of the previously approved baseline configuration of IS components]
>Discussion
Retaining previous versions of baseline configurations to support rollback include hardware, software, firmware, configuration files, configuration records, and associated documentation.
>Programmatic Queries
Beta
Related Services
AWS Config
Amazon S3
CLI Commands
Describe Config snapshots for historical baselines
aws configservice describe-configuration-snapshots --region us-east-1Get Config timeline for resource changes
aws configservice get-resource-config-history --resource-type AWS::EC2::Instance --resource-id i-1234567890abcdef0 --region us-east-1Enable S3 versioning for config storage
aws s3api put-bucket-versioning --bucket config-bucket-name --versioning-configuration Status=EnabledList object versions in S3 config bucket
aws s3api list-object-versions --bucket config-bucket-name>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of CM-2(3) (Retention Of Previous Configurations)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring CM-2(3)?
- •How frequently is the CM-2(3) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to CM-2(3)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce CM-2(3) requirements.
- •What automated tools, systems, or technologies are deployed to implement CM-2(3)?
- •How is CM-2(3) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce CM-2(3) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of CM-2(3)?
- •What audit logs, records, reports, or monitoring data validate CM-2(3) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of CM-2(3) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate CM-2(3) compliance?
Ask AI
Configure your API key to use AI features.