NIST SP 800-171 Rev 3
03.04 CM (Configuration Management)

NIST SP 800-171 Rev 3 03.04.01: Baseline Configuration

Develop, document, and maintain current baseline configurations for the system; review and update baselines as required.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

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

PCI DSS 4.0 · 3 controls

  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs
  • 1.2.7 1.2.7 Six-monthly review of NSC configurations
  • 2.2.1 2.2.1 System configuration standards maintained
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies
  • ASD37-11 Operating system hardening (Very Good)
  • ASD37-36 System recovery capabilities (Very Good)
  • SEC01-BP06 Automate deployment of standard security controls
  • SEC06-BP02 Provision compute from hardened images

C5 (Germany) · 2 controls

  • C5-DEV-08 Version Control
  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CIS Controls v8 · 2 controls

  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure

FedRAMP High · 2 controls

  • CM-2 Baseline Configuration
  • CM-2(2) Automation Support for Accuracy and Currency

FedRAMP Moderate · 2 controls

  • CM-2 Baseline Configuration
  • CM-2(2) Automation Support for Accuracy and Currency

SOC 2 · 2 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • E8-UAH-ML2 User Application Hardening - Maturity Level 2
  • AUCDR-IS-2 Secure the network and systems within the data environment

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.9 Configuration management

ISO 27002:2022 · 1 control

  • 8.9 Configuration management

NIS2 Directive · 1 control

  • Art.21.2.g Basic cyber hygiene practices and cybersecurity training

NIST SP 800-172 · 1 control

  • 3.14.4e Refresh Systems and Components from a Trusted Baseline

NIST SP 800-218 · 1 control

UK Cyber Essentials · 1 control

  • CE-SC.1 Remove or Disable Unused Software

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.

Other controls in 03.04 CM (Configuration Management)

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

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.

Query this from an agent

The graph holds this control, the 37 it maps to, and the evidence behind each claim, over MCP and REST.