Skip to content
All CMMC practices
CMMC · Rev 2.13L2AC · Access Control

AC.L2-3.1.7

Privileged Functions

Requirement

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

Assessment objectives

An assessor checks each lettered objective separately. The letters in brackets elsewhere on this page, such as [a] or [b,c], refer to these.

Determine if:

  1. aprivileged functions are defined;
  2. bnon-privileged users are defined;
  3. cnon-privileged users are prevented from executing privileged functions; and
  4. dthe execution of privileged functions is captured in audit logs.

From the CMMC Level 2 Assessment Guide v2.13 · publisher approved 2026-10-31.

How to implement

Ordinary users must not be able to run privileged functions (install software, change security settings, create accounts, alter logs), and every privileged action must leave an audit trail. Define both lists, take local admin rights away from users, and make sure admin actions in the cloud consoles, directory, firewall and endpoints are logged and kept.

The minimum for a small organization · Expert CMMC's reading, not official text

Write down which actions count as privileged, make sure ordinary users cannot perform them, and make sure the systems record when they are performed. At minimum: a short list of privileged functions such as installing software, managing accounts and changing security settings [a]; who counts as a non-privileged user [b]; ordinary accounts without the rights to do those things [c]; and audit logging on in the identity system, servers, firewall and cloud services so each privileged action is recorded [d].

Expert CMMC's adviceseeCMMC Assessment Guide Level 2 v2.13p.37 AC.L2-3.1.7

Required outcome: what the requirement or its objectives call for. Recommended way: one common way to get there. Going further: worth doing, more than this practice asks.

  1. 1
    Required outcomePolicyDefine the privileged functions in your systems, for example creating or changing accounts and groups, installing software, changing security, firewall or logging settings, and restoring backups; and define the non-privileged users: everyone who does not hold an approved administrator role.[a][b]
    SourceCMMC Assessment Guide Level 2 v2.13objectives [a] and [b], p.37
    Quoted words
    • “privileged functions are defined”
    • “non-privileged users are defined”
  2. 2
    Required outcomeTechnicalPrevent non-privileged users from executing privileged functions.[c]

    You can tell it worked when a standard user's attempt to install software or change a security setting is refused.

    SourceCMMC Assessment Guide Level 2 v2.13objective [c], p.37
    Quoted words
    • “non-privileged users are prevented from executing privileged functions”
  3. 3
    Required outcomeTechnicalCapture the execution of privileged functions in audit logs.[d]

    You can tell it worked when a recent account change and a recent security setting change each appear in the logs with who made them and when.

    SourceCMMC Assessment Guide Level 2 v2.13objective [d], p.37
    Quoted words
    • “the execution of privileged functions is captured in audit logs”
  4. 4
    Recommended wayTechnicalRemove standard users from the local Administrators group, block software installers through device management or Group Policy, and restrict admin portals and firewall management to admin roles.[c]
    Expert CMMC's adviceseeCMMC Assessment Guide Level 2 v2.13p.37 AC.L2-3.1.7
  5. 5
    Recommended wayTechnicalTurn on and keep the audit logs for directory changes, the cloud service's audit log, firewall configuration changes and privilege elevation on endpoints, and send them to a central log store so they survive the loss of a device.[d]
    Expert CMMC's adviceseeCMMC Assessment Guide Level 2 v2.13p.37 AC.L2-3.1.7
  6. 6
    Recommended wayTechnicalOn Windows, turn on the audit subcategories Audit Special Logon and Audit Process Creation, so a sign-in with administrator rights (event 4672) and each program started (event 4688) are recorded, or use your endpoint detection tool's record of elevations. This gives [d] its evidence on the endpoints.[d]
    Expert CMMC's adviceseeCMMC Assessment Guide Level 2 v2.13p.37 AC.L2-3.1.7
  7. 7
    Recommended wayProcessReview privileged-function logs on a schedule you set (monthly is common), or alert on them, and keep the review record. AU.L2-3.3.1 and AU.L2-3.3.2 rely on the same logs.[d]
    Expert CMMC's adviceseeCMMC Assessment Guide Level 2 v2.13p.37 AC.L2-3.1.7

Evidence to collect

Artifacts that show the practice is implemented and operating. Tags show which assessment objectives each one supports.

A process you started recently is shown honestly by its dated procedure, the first record it produced and the date it began. No evidence row needs more history than the process has existed, and the review periods shown are suggestions unless a guide page or regulation is named beside them.

Prevention controls[c]

The detail for 4 evidence items: how to produce each, how fresh it must be, what it must include and what it does not show.

Free with an account. Create a free account or sign in.

How assessors check

What an assessor examines, asks and tests: 3 notes.

Free with an account. Create a free account or sign in.

Tools and products

Named options a contractor can adopt, with an honest cost tier. The industry standard is listed even when it is expensive, alongside what is free and acceptable for a very small shop.

Microsoft Intune Endpoint Privilege ManagementControlled elevationPaid
AutoElevate / ThreatLocker Elevation ControlControlled elevation (MSP tools)Paid
WazuhLog collection and alertingFree
Microsoft SentinelSIEMPaid
Windows Advanced Audit Policy + Group PolicyBuilt-in controlsFree

18 dated vendor facts and notes on 5 products for this practice: what each assumes, what it does not cover and what stays yours.

Free with an account. Create a free account or sign in.

Editorial mentions, not endorsements. Pricing and tiers change; confirm with the vendor and check FedRAMP or GCC High availability where CUI is involved.

Common pitfalls

Platform notes

  • Microsoft 365 (GCC / GCC High)
  • Google Workspace
  • On-premises or MSP-managed

Notes for 3 platforms.

Free with an account. Create a free account or sign in.

Related practices: AC.L2-3.1.5, AC.L2-3.1.6, AU.L2-3.3.1, AU.L2-3.3.2, CM.L2-3.4.5

Editorial implementation guidance published November 19, 2026. It is not part of the official requirement and does not replace the assessment guide.

The NIST requirements this practice is built on, what NIST made of each in the newer edition, and the SP 800-53 controls behind them, each from an official NIST or DoD table. Open any one to read it and see every CMMC practice it supports.

NIST SP 800-171 Rev 2

3.1.7

SP 800-171 Rev 3

03.01.07

SP 800-53 Rev 4

AC-6 (9)AC-6 (10)

SP 800-53 Rev 5

AC-6(9)DSAC-6(10)DS
How these were reached
  • AC-6(9) · Least Privilege | Log Use of Privileged Functions
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 AC-6 (9) → 800-53 Rev 5 AC-6(9)
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.01.07 → 800-53 Rev 5 AC-6(9)NIST: 03.01.07 also: 3.4.9, 3.13.3 addressed by
  • AC-6(10) · Least Privilege | Prohibit Non-privileged Users from Executing Privileged Functions
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 AC-6 (10) → 800-53 Rev 5 AC-6(10)
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.01.07 → 800-53 Rev 5 AC-6(10)NIST: 03.01.07 also: 3.4.9, 3.13.3 addressed by

Rev 5 paths: D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison; S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL); C SP 800-172 (Feb 2021) Appendix C. NIST also names this Rev 3 requirement as the successor of other withdrawn requirements: open “How these were reached” under the Rev 5 controls for which, in NIST's words.

Where each link comes from (8 links from 5 official documents)

32 CFR Part 170 Office of the Federal Register / GPO

  • AC.L2-3.1.7 → 3.1.7“Level 2 security requirement”32 CFR 170.14(c)(1) numbering (REQ is the NIST SP 800-171 R2 requirement number) and 170.14(c)(3)

NIST SP 800-171 Rev 2 → Rev 3 change analysis NIST

  • 3.1.7 → 03.01.07“No Significant Change”sheet "Change Analysis 800-171 R2-R3" row 8

NIST SP 800-171 Rev 2 NIST

NIST SP 800-53 Rev 4 → Rev 5 comparison NIST

NIST SP 800-171 Rev 3 (OSCAL) NIST

  • 03.01.07 → AC-6(9)“Source control”control 03.01.07 link rel=reference (AC-06(09))
  • 03.01.07 → AC-6(10)“Source control”control 03.01.07 link rel=reference (AC-06(10))

Further discussion

Non-privileged users should receive only those permissions required to perform their basic job functions. Privileged users are granted additional permissions because their jobs require them. Privileged functions typically involve the control, monitoring, or administration of the system and its security measures. When these special privileged functions are performed, the activity must be captured in an audit log, which can be used to identify abuse. Non-privileged employees must not be granted permission to perform any of the functions of a privileged user. This requirement, AC.L2-3.1.7, manages non-privileged users by logging any attempts to execute privileged functions. AC.L2-3.1.7 leverages AU.L2-3.3.2, which ensures logging and traceability of user actions. AC.L2-3.1.7 also extends AC.L2-3.1.2, which defines a requirement to limit types of transactions and functions to those that authorized users are permitted to execute. Example Your organization handles CUI and has put security controls in place that prevent non-privileged users from performing privileged activities [a,b,c]. However, a standard user was accidentally given elevated system administrator privileges. The organization has implemented an endpoint detection and response solution that provides visibility into the use of privileged activities. The monitoring system logs a security misconfiguration because the use of administrative privileges was performed by a user who was not known to have that ability. This allows you to correct the error [d]. Potential Assessment Considerations • Is it possible to identify who enabled privileges at any particular time [d]? • Are the privileged system functions documented (e.g., functions that involve the control, monitoring or administration of the system, including security functions and log management) [a]? • Do documented procedures describe the configuration of the system to ensure system roles do not grant non-privileged users the ability to execute privileged functions [c]? • Do procedures describe the configuration of system settings to capture the execution of all privileged functions in audit logs [d]?

Practice guide notes

Implementation guidance

Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.

In plain language

Prevent ordinary users from performing privileged functions and record privileged activity.

Implementation example

Example from the source assessment guide (not a mandatory implementation): Your organization handles CUI and ha s put security controls in place that prevent non- privileged users from performing privileged activities [a,b,c]. However, a standard user was accidentally given elevated system administrator privil eges. The organization has implemented an endpoint detection and response solution that provides visibility into the use of privileged activities. The monitoring system logs a security misconfiguration because the use of administrative privileges was performed by a user who was not known to have that ability. This allows you to correct the error [d].

Evidence examples

Examples suggested by the source guide (not an exhaustive or mandatory checklist): Privacy and security policies, procedures addressing system use notification; documented approval of system use notification messages or banners; system audit logs and records; system design documentation; user acknowledgements of notification message or banner; system security plan; system use notification messages; system configuration settings and associated documentation; other relevant documents or records

Common mistakes

Restricting an administrator menu while leaving another path to the same privileged function.

Track this in a workspace

The compliance workspace tracks each objective, its evidence and the tasks to close gaps. It is open to invited contractors while in pilot: request access below.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Source: DoD CIO · https://dodcio.defense.gov/CMMC/