CMMC 2.0
Configuration Management

CMMC 2.0 CM.L2-3.4.6: Least Functionality

Configure systems to provide only the capabilities that are essential, applying the principle of least functionality.

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

What else in your programme already covers this

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

PCI DSS 4.0 · 5 controls

  • 1.2.5 1.2.5 Allowed services, protocols and ports justified
  • 2.2.4 2.2.4 Only necessary functionality enabled
  • 2.2.6 2.2.6 System security parameters configured against misuse
  • 7.2.1 7.2.1 Access control model defined
  • 7.3.1 7.3.1 Need-to-know access control system covers all components
  • ASD37-01 Application control (Essential)
  • ASD37-04 User application hardening (Essential)
  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)

ISO 27002:2022 · 4 controls

  • 8.19 Installation of software on operational systems
  • 8.2 Privileged access rights
  • 8.22 Segregation of networks
  • 8.9 Configuration management

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

CIS Controls v8 · 3 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-2.5 Allowlist Authorized Software
  • CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

ISO 27001:2022 · 3 controls

  • 8.19 Installation of software on operational systems
  • 8.27 Secure system architecture and engineering principles
  • 8.9 Configuration management
  • 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

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate

FedRAMP High · 1 control

  • CM-7 Least Functionality

FedRAMP Moderate · 1 control

  • CM-7 Least Functionality

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

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 Configuration Management

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 CM.L2-3.4.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 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. 1 were rejected on the FedRAMP Moderate pair alone.

Query this from an agent

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