FedRAMP Moderate CM-4(2): Impact Analyses | Verification of Controls. After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements

What else in your programme already covers this

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

CIS Controls v8 · 2 controls

CIS-16.8 Separate Production and Non-Production Systems
CIS-18.4 Validate Security Measures

ISO 27001:2022 · 2 controls

8.31 Separation of development, test and production environments
8.32 Change management

ISO 27002:2022 · 2 controls

8.31 Separation of development, test and production environments
8.32 Change management

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

AWS Well-Architected Security Pillar · 1 control

SEC01-BP06 Automate deployment of standard security controls

Azure Security Benchmark · 1 control

PV-2 Audit and enforce secure configurations

CMMC 2.0 · 1 control

CM.L2-3.4.4 Security Impact Analysis

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-CCC-07 Detection of Baseline Deviation

NIST SP 800-171 Rev 3 · 1 control

03.12.01 Security Assessment

NIST SP 800-172 · 1 control

3.14.7e Verify Correctness of Security Functions

NIST SP 800-53 Rev 5 · 1 control

NIST800-CM-4 Impact analyses

PCI DSS 4.0 · 1 control

6.5.2 Upon completion of a significant change, all applicable PCI DSS requirements are confirmed to be in place on all new or changed systems and networks, and documentation is updated as applicable

SOC 2 · 1 control

SOC2-CC8.1 Change management processes are in place

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 Moderate have you already done?

FedRAMP Moderate CM-4(2) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If you hold CMMC 2.035% covered · 210 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. 348 were rejected on the ISO 27002:2022 pair alone.

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