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

NIST SP 800-171 Rev 3 03.04.06: Least Functionality

Configure system to provide only essential capabilities; prohibit or restrict use of specified functions, ports, protocols, software, and services.

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

What else in your programme already covers this

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

  • ASD37-04 User application hardening (Essential)
  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)
  • ASD37-24 Non-persistent virtualised sandboxed environment (Very Good)

PCI DSS 4.0 · 4 controls

  • 1.2.5 1.2.5 Allowed services, protocols and ports justified
  • 1.2.6 1.2.6 Security features for insecure services in use
  • 2.2.3 2.2.3 Primary functions with different security levels managed
  • 2.2.4 2.2.4 Only necessary functionality enabled

ACSC Essential Eight · 3 controls

  • E8-APP-ML1 Application Control (ML1)
  • E8-UAH-ML1 User Application Hardening - Maturity Level 1
  • E8-UAH-ML3 User Application Hardening - Maturity Level 3
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
  • ANSSI-HYG-21 Use Secure Protocols Wherever They Exist
  • ANSSI-HYG-27 Prohibit Internet Access from Administration Workstations and Servers

CIS Controls v8 · 3 controls

  • CIS-2.5 Allowlist Authorized Software
  • CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software
  • CIS-9.4 Restrict Unnecessary or Unauthorized Browser and Email Client Extensions

FedRAMP High · 3 controls

  • AC-18(3) Wireless Access | Disable Wireless Networking (AC-18(3))
  • CM-7 Least Functionality
  • CM-7(1) Periodic Review

FedRAMP Moderate · 3 controls

  • AC-18(3) Wireless Access | Disable Wireless Networking (AC-18(3))
  • CM-7 Least Functionality
  • CM-7(1) Periodic Review
  • SEC05-BP02 Control traffic flow within your network layers
  • SEC06-BP02 Provision compute from hardened images
  • AM-2 Use only approved services
  • ASBv3-NS-8 Detect and disable insecure services and protocols

C5 (Germany) · 2 controls

  • C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CMMC 2.0 · 2 controls

ISO 27001:2022 · 2 controls

  • 8.18 Use of privileged utility programs
  • 8.9 Configuration management

UK Cyber Essentials · 2 controls

  • CE-FW.5 Remove or Disable Unused Rules
  • CE-SC.1 Remove or Disable Unused Software

ISO 27002:2022 · 1 control

  • 8.18 Use of privileged utility programs

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

SOC 2 · 1 control

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious 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.06 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 45 it maps to, and the evidence behind each claim, over MCP and REST.