---
title: "NIST 800-171 3.1.7 (AC.L2-3.1.7): Privileged Functions"
description: "NIST SP 800-171 3.1.7 Privileged Functions: 1 SPRS point, allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/access-control/3.1.7
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.7
records: 7
digest: sha3:90abfc6afcfe020b326b74b5473e2f5da56e2f3850bad2b53d5cfdb6f642815f
---

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

NIST 800-171 / Access Control / 3.1.7

"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](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.7.

## 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](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## 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](https://doi.org/10.6028/NIST.SP.800-171A)

## 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.](https://policycortex.com/sprs-score-calculator#family-AC)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 22 Access Control requirements (3.1).](https://policycortex.com/nist-800-171/access-control)
- **Previous**: [3.1.6: Non-Privileged Accounts](https://policycortex.com/nist-800-171/access-control/3.1.6)
- **Next**: [3.1.8: Unsuccessful Logons](https://policycortex.com/nist-800-171/access-control/3.1.8)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | 8dc58eec86b4 | 441987f3a689 |
| REC 0001 | MEANING | 6a3ba0c38051 | 8dc58eec86b4 |
| REC 0002 | POINTS AND POA&M | 74d12f092f6d | 6a3ba0c38051 |
| REC 0003 | ASSESSMENT OBJECTIVES | 600f2d8f3097 | 74d12f092f6d |
| REC 0004 | EVIDENCE | ca07d2641594 | 600f2d8f3097 |
| REC 0005 | COLLECTORS | 3f35f0eb9ada | ca07d2641594 |
| REC 0006 | RELATED | 90abfc6afcfe | 3f35f0eb9ada |

Head sha3:90abfc6afcfe020b326b74b5473e2f5da56e2f3850bad2b53d5cfdb6f642815f. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.