Level 2 · Configuration Management

CM.L2-3.4.6

Least Functionality

Least functionality starts with a defensible definition of essential capabilities.

Score: 5 POA&M: Not eligible
GAVII Cybersecurity assessment reference

Official reference

The requirement

Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.

DoD CMMC Assessment Guide, Level 2, version 2.13. CM.L2-3.4.6; requirement and objectives, printed page 103 ↗

Assessment objectives

What must be established

Determine if each applicable objective is satisfied. The labels below follow the cited DoD assessment guide.

  1. [a]

    essential system capabilities are defined based on the principle of least functionality; and

  2. [b]

    the system is configured to provide only the defined essential capabilities.

MET requires evidence that all applicable objectives are satisfied. Final, approved evidence is needed. A NOT APPLICABLE determination needs a scope-based basis and is equivalent to MET for scoring. Enduring exceptions and temporary deficiencies have specific conditions under 32 CFR 170.24; they are not a general permission to defer implementation.

GAVII Cybersecurity assessment approach

Connect the objective to the evidence

Review whether the system supplies only the capabilities needed for its purpose. Distinguish an essential capability from a convenience feature left enabled by default.

Assessment focus: objectives [a], [b]. Use the methods together; a single example does not establish every objective.

Examine

Inspect approved system roles, essential-capability definitions, baseline settings, and configuration review records.

Interview

Why is each major capability needed for the system's business or security purpose?

Demonstrate or test

Compare a representative system's enabled capabilities with its approved role and investigate a nonessential example.

Evidence gaps to look for

  • A generic operating-system image enables unnecessary features.
  • Administrators cannot explain why a capability remains active.

GAVII Cybersecurity’s examples illustrate ways to examine, interview, and test. They are not a mandatory artifact list or a guarantee of an assessment result. Combine methods and address every applicable objective in the actual scope.

Assessment constraints

Scoring and POA&M eligibility

Score: 5

If this requirement is NOT MET, deduct 5 points from the Level 2 maximum of 110. The deduction applies to the requirement, not separately to each objective.

Scoring rule ↗

POA&M: Not eligible

This requirement has a deduction greater than 1 point and does not qualify for the limited encryption exception. It cannot be deferred on the POA&M used for Conditional Level 2 status.

POA&M rule ↗

Conditional Level 2 requires a score of at least 88 out of 110 and satisfaction of every eligibility condition. A 1-point requirement is not automatically eligible. The permitted POA&M must be closed through the appropriate closeout assessment within 180 days of the Conditional CMMC Status Date. An operational remediation plan does not confer Conditional Status.

Assessment planning

Location and observation

Not specifically listed in CAP P.11

This requirement is not specifically listed in CAP P.11. That does not establish that remote assessment is sufficient: the Lead CCA and C3PAO determine an adequate approach for the actual scope and evidence.

CAP §P.11, pages 10–11 ↗

Check the source

References and related requirements

Program timing and contract applicability can change independently of these requirements. Check current DoD program notices and your solicitation or contract before making a compliance decision. Open the official DoD resource hub.

Get your free consultation.