NIST 800-171 3.1.7 (AC.L2-3.1.7): Privileged Functions

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

NIST SP 800-171 Rev. 2, requirement 3.1.7

CMMC Level 2 practice AC.L2-3.1.7Published 2026-11-11

What 3.1.7 means in practice

Two things are asked. Ordinary users must be technically unable to run administrative functions, such as creating accounts, changing security settings or switching off protection. And every use of those functions must leave an audit log entry that an assessor can find.

SPRS points and the CMMC POA&M

CMMC Level 2 practice: AC.L2-3.1.7
SPRS points: 1 point. When it is not met, the DoD Assessment Methodology subtracts 1 from the score of 110.
CMMC POA&M: Allowed. It is worth 1 point, and 32 CFR 170.21(a)(2)(ii) admits requirements worth 1 point. Conditional status also needs a score of at least 88, and the item must be closed within 180 days.

Sources: NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A; 32 CFR 170.21, Plan of Action and Milestones requirements.

What an assessor checks for 3.1.7

NIST SP 800-171A gives 4 determination statements for 3.1.7, each found satisfied or other than satisfied. Determine if:

3.1.7[a] privileged functions are defined.
3.1.7[b] non-privileged users are defined.
3.1.7[c] non-privileged users are prevented from executing privileged functions.
3.1.7[d] the execution of privileged functions is captured in audit logs.

NIST SP 800-171A (June 2018), assessment objectives for 3.1.7

Evidence that shows 3.1.7 is met

A defined list of the privileged functions in the system.
Configuration that denies those functions to non-privileged users, such as role definitions or the removal of local administrator rights.
Audit log entries recording privileged functions, for example role changes or changes to security settings.

How PolicyCortex gathers the evidence

PolicyCortex reads this evidence with the collectors below, read only, and grades 3.1.7 from it. Each line says what the product checks.

Azure: Role assignments. Checks Azure role assignments so that non-privileged users cannot execute privileged functions.

Related pages

Calculator: SPRS score calculator: mark 3.1.7 and the other 109 requirements and see the score.
Sample package: Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.
Family: All 22 Access Control requirements (3.1).
Previous: 3.1.6: Non-Privileged Accounts
Next: 3.1.8: Unsuccessful Logons
All requirements: All 110 NIST SP 800-171 requirements, by family.

Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages, the architecture page, and the two pages on authorization.

proof.state: Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
proof.change: Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
proof.agency: Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
architecture: Architecture. How the chain is built and where the evidence is stored in each delivery mode.
authorization: Continuous ATO. How an authorizing official's decision is recorded with its package, and how the authorized system is checked against it every hour.
baseline: NIST SP 800-53. The Low, Moderate and High baselines as evidence, with the SSP, SAR and POA&M generated from one record.