FedRAMP Moderate CM-4: Impact Analyses

What else in your programme already covers this

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

PCI DSS 4.0 · 5 controls

1.2.2 Changes to NSC reviewed and approved
11.3.1.3 Internal scans after significant changes
12.5.3 Impact analysis on org structure changes (SP)
6.5.1 Changes to all system components in the production environment are made according to established procedures that include: • Reason for, and description of, the change. • Documentation of security impact. • Documented change approval
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

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP07 Identify threats and prioritize mitigations using a threat model
SEC11-BP04 Conduct code reviews

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

CFTC-SS-12 Capacity and Performance Planning Category
CFTC-SS-32 Timely Advance Notice of Material Planned Changes

SOC 2 · 2 controls

SOC2-CC3.4 COSO principle 9: Identifies and assesses changes that could impact internal controls
SOC2-CC8.1 Change management processes are in place

APRA CPS 220 Risk Management · 1 control

CPS220-P48 Assessment Following Material Change Outside the Review Cycle

APRA CPS 230 Operational Risk Management · 1 control

CPS230-P26 Assessment of Business and Strategic Decisions on the Risk Profile

APRA CPS 234 · 1 control

CPS234-P31 Annual Review of Testing Program Sufficiency

C5 (Germany) · 1 control

C5-DEV-05 Risk assessment, categorisation and prioritisation of changes

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-02 Quality Testing

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

NIST SP 800-161 Rev 1 · 1 control

161R1-CM-4 Impact Analysis

NIST SP 800-171 Rev 3 · 1 control

03.04.04 Impact Analyses

NIST SP 800-218 · 1 control

SP800-218-PW.7.2 Perform Code Review and Analysis

NIST SP 800-53 Rev 5 · 1 control

NIST800-CM-4 Impact analyses

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 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