NIST SP 800-172 3.14.4e: Refresh Systems and Components from a Trusted Baseline

What else in your programme already covers this

This control maps to 26 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 Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
NIST-CSF-PR.PS-01 Configuration management practices are established and applied
NIST-CSF-RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
NIST-CSF-RS.MI-02 Incidents are eradicated

NIST SP 800-53 Rev 5 · 4 controls

NIST800-CM-2 CM-2 Baseline Configuration
NIST800-SI-14 SI-14 Non-persistence
NIST800-SI-21 SI-21 Information Refresh
NIST800-SI-7 SI-7 Software, Firmware, and Information Integrity

Azure Security Benchmark · 2 controls

ASBv3-PV-3 Define and establish secure configurations for compute resources
ASBv3-PV-4 Audit and enforce secure configurations for compute resources

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

CCM-CCC-06 Change Management Baseline
CCM-CCC-09 Change Restoration

FedRAMP High · 2 controls

CM-2 Baseline Configuration
CM-2(3) Retention of Previous Configurations

FedRAMP Moderate · 2 controls

CM-2 Baseline Configuration
CM-2(3) Retention of Previous Configurations

C5 (Germany) · 1 control

C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CIS Controls v8 · 1 control

CIS-4.1 Establish and Maintain a Secure Configuration Process

CMMC 2.0 · 1 control

CM.L2-3.4.1 System Baselining

NIST SP 800-161 Rev 1 · 1 control

161R1-CM-2 Baseline Configuration

NIST SP 800-171 Rev 3 · 1 control

03.04.01 Baseline Configuration

PCI DSS 4.0 · 1 control

2.2.1 2.2.1 System configuration standards maintained

SOC 2 · 1 control

SOC2-CC7.5 CC7.5 Recovering from security incidents

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

NIST SP 800-172 3.14.4e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 controls already carry evidence.

If you hold NIST SP 800-53 Rev 568.6% covered · 11 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.165.7% covered · 12 gaps If you hold NIST SP 800-161 Rev 162.9% covered · 13 gaps If you hold FedRAMP Moderate60% covered · 14 gaps If you hold NIST Cybersecurity Framework 2.048.6% covered · 18 gaps If you hold C5 (Germany)45.7% covered · 19 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. 5 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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