Privileged Functions
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
What an assessor scores, the objectives
AC.L2-3.1.7 is met only when every one of these 4 objectives, from NIST SP 800-171A, is satisfied. A single missed objective makes the whole requirement not met.
- a.privileged functions are defined
- b.non-privileged users are defined
- c.non-privileged users are prevented from executing privileged functions
- d.the execution of privileged functions is captured in audit logs
How a C3PAO checks it
NIST SP 800-171A defines three assessment methods. For AC.L2-3.1.7, an assessor uses these:
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
Personnel with responsibilities for defining least privileges necessary to accomplish specified tasks; personnel with information security responsibilities; system developers
Mechanisms implementing least privilege functions for non- privileged users; mechanisms auditing the execution of privileged functions
What it means, in context
Privileged functions include establishing system accounts, performing system integrity checks, conducting patching operations, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. Note that this requirement represents a condition to be achieved by the definition of authorized privileges in 3.1.2 (AC.L2-3.1.2). Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat.
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 lo g, which can be use d 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 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]. 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]?
What passing evidence looks like
A list of privileged functions, proof standard users cannot run them (a permissions screenshot or a denied attempt), and an audit log line showing a privileged action was captured.
Common ways contractors fail AC.L2-3.1.7
- !Objective [d] wants privileged actions IN the logs. Turn on audit logging before you capture, then perform one admin action and show the log entry.
The step by step walkthrough for Microsoft 365 GCC High, Google Workspace, and on premises setups, plus the exact evidence to capture, lives inside the Level 2 Accelerator.
Prove AC.L2-3.1.7, and the other 109
The Level 2 Accelerator walks all 110 requirements with you, generates your SSP, POA&M, and Audit Room from real evidence, includes the full Level 1 platform, and puts a credentialed officer alongside you for 180 days. Filed in 180 days, or we work free until you are.
No credit card. Phase 2 begins Nov 10, 2026, when applicable DoD solicitations start requiring a current Level 2 status to win the award.
AC.L2-3.1.7 questions, answered
How many points is CMMC requirement AC.L2-3.1.7 worth?+
AC.L2-3.1.7 is worth 1 point in the CMMC Level 2 score under 32 CFR 170.24. If it is not met, you lose 1 from your total of 110.
Can AC.L2-3.1.7 be placed on a POA&M?+
Yes. A gap on AC.L2-3.1.7 can be deferred to a Plan of Action and Milestones, provided your overall score is 88 or better and the item closes within 180 days.
What family does AC.L2-3.1.7 belong to?+
AC.L2-3.1.7 is in the Access Control (AC) family, one of the 14 families of NIST SP 800-171 that make up CMMC Level 2.
- NIST SP 800-171 Rev. 2 3.1.7