NIST SP 800-171 Rev 3 03.04.04: Impact Analyses

What else in your programme already covers this

This control maps to 30 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.

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

CCM-AIS-05 Automated Application Security Testing
CCM-CCC-02 Quality Testing
CCM-CCC-03 Change Management Technology

NIST SP 800-218 · 3 controls

SP800-218-PW.7.2 Perform Code Review and Analysis
SP800-218-PW.8.1 Executable Testing for Security
SP800-218-PW.8.2 Execute Security Testing

PCI DSS 4.0 · 3 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

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP07 Identify threats and prioritize mitigations using a threat model
SEC11-BP02 Automate testing throughout the development and release lifecycle

C5 (Germany) · 2 controls

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

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

CFTC-SS-32 Timely Advance Notice of Material Planned Changes
CFTC-SS-5 Systems Development and Quality Assurance Category

FedRAMP High · 2 controls

CM-3(2) Testing, Validation, and Documentation of Changes
CM-4 Impact Analyses

FedRAMP Moderate · 2 controls

CM-3(2) Testing, Validation, and Documentation of Changes
CM-4 Impact Analyses

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

SOC 2 · 2 controls

SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

Azure Security Benchmark · 1 control

DS-6 Enforce security of workload throughout DevOps lifecycle

CMMC 2.0 · 1 control

CM.L2-3.4.4 Security Impact Analysis

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-53 Rev 5 · 1 control

NIST800-CM-4 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 NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.04.04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

If you hold PCI DSS 4.071.1% covered · 28 gaps If you hold C5 (Germany)68% covered · 31 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.164.9% covered · 34 gaps If you hold ISO 27001:202262.9% covered · 36 gaps If you hold CIS Controls v853.6% covered · 45 gaps If you hold NIST SP 800-161 Rev 152.6% covered · 46 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. 0 were rejected on the PCI DSS 4.0 pair alone.

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