FedRAMP High CM-3(2): Testing, Validation, and Documentation of Changes

What else in your programme already covers this

This control maps to 28 controls across 16 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 4 controls

NIST800-CM-3 CM-3 Configuration Change Control
NIST800-CM-4 CM-4 Impact Analyses
NIST800-SA-11 SA-11 Developer Testing and Evaluation
NIST800-SI-6 SI-6 Security and Privacy Function Verification

PCI DSS 4.0 · 4 controls

6.2.3 6.2.3 Code review before release
6.5.1 6.5.1 Change control procedure for production
6.5.2 6.5.2 Confirm PCI DSS controls after significant change
6.5.3 6.5.3 Separate pre-production from production

CIS Controls v8 · 3 controls

CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.12 Implement Code-Level Security Checks
CIS-16.8 Separate Production and Non-Production Systems

Azure Security Benchmark · 2 controls

ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-AIS-06 Automated Secure Application Deployment
CCM-CCC-02 Quality Testing

ISO 27001:2022 · 2 controls

8.29 Security testing in development and acceptance
8.32 Change management

ISO 27002:2022 · 2 controls

8.29 Security testing in development and acceptance
8.32 Change management

AWS Well-Architected Security Pillar · 1 control

SEC11-BP02 Automate testing throughout the development and release lifecycle

C5 (Germany) · 1 control

C5-DEV-06 Testing changes

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-5 Systems Development and Quality Assurance Category

CMMC 2.0 · 1 control

CM.L2-3.4.3 System Change Management

NIST SP 800-171 Rev 3 · 1 control

03.04.04 Impact Analyses

NIST SP 800-218 · 1 control

SP800-218-PW.8.2 Execute Security Testing

NIST SP 800-53 Rev 5 HIGH · 1 control

CM-3(2) CM-3(2) Configuration Change Control | Testing, Validation, and Documentation of Changes

NIST SP 800-53 Rev 5 MODERATE · 1 control

CM-3(2) CM-3(2) Configuration Change Control | Testing, Validation, and Documentation of Changes

SOC 2 · 1 control

SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High CM-3(2) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

If you hold C5 (Germany)29% covered · 291 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 6 were rejected on the C5 (Germany) pair alone.

See the released pairs, $299 each Browse the graph free