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

NIST SP 800-171 Rev 3 03.04.02: Configuration Settings

Establish, document, and implement configuration settings that reflect the most restrictive mode consistent with operational requirements; identify, document, and approve deviations.

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

What else in your programme already covers this

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

ASD Strategies to Mitigate Cyber Security Incidents · 5 controls

  • ASD37-03 Configure Microsoft Office macro settings (Essential)
  • ASD37-04 User application hardening (Essential)
  • ASD37-09 OS generic exploit mitigation (Excellent)
  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)

Azure Security Benchmark · 5 controls

  • ASBv3-GS-5 Define and implement security posture management strategy
  • 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
  • PV-2 Audit and enforce secure configurations

PCI DSS 4.0 · 4 controls

  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs
  • 2.2.1 2.2.1 System configuration standards maintained
  • 2.2.5 2.2.5 Insecure services, protocols or daemons secured
  • 2.2.6 2.2.6 System security parameters configured against misuse

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 3 controls

  • ANSSI-HYG-12 Change Default Authentication Elements on Equipment and Services
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

AWS Well-Architected Security Pillar · 3 controls

CIS Controls v8 · 3 controls

  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure

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

UK Cyber Essentials · 3 controls

  • CE-SC.1 Remove or Disable Unused Software
  • CE-SC.2 Change Default Passwords on Devices and Software
  • CE-SC.3 Disable Auto-Run Features

ACSC Essential Eight · 2 controls

  • E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
  • E8-UAH-ML2 User Application Hardening - Maturity Level 2

C5 (Germany) · 2 controls

  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening
  • C5-SP-03 Exceptions from Existing Policies and Instructions

FedRAMP High · 2 controls

  • CM-6 Configuration Settings
  • CM-6(1) Automated Management, Application, and Verification

FedRAMP Moderate · 2 controls

  • CM-6 Configuration Settings
  • CM-6(1) Automated Management, Application, and Verification

ISO 27001:2022 · 2 controls

  • 8.1 User end point devices
  • 8.9 Configuration 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-01 Configuration management practices are established and applied

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

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-2 Secure the network and systems within the data environment

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CMMC 2.0 · 1 control

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

NIST SP 800-172 · 1 control

  • 3.4.2e Automated Detection and Remediation of Unauthorized Software

NIST SP 800-53 Rev 5 · 1 control

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.02 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 gapsIf you hold C5 (Germany)68% covered · 31 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.164.9% covered · 34 gapsIf you hold ISO 27001:202262.9% covered · 36 gapsIf you hold CIS Controls v853.6% covered · 45 gapsIf 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 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST SP 800-171 Rev 3 controls