---
title: "NIST 800-171 3.1.5 (AC.L2-3.1.5): Least Privilege"
description: "NIST SP 800-171 3.1.5 Least Privilege: 3 SPRS points, not 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.5
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.5
records: 7
digest: sha3:ab3a15f774aa8cd5d797706fa4b871dc1b97112e9213e026f7d8a6374176e9d0
---

# NIST 800-171 3.1.5 (AC.L2-3.1.5): Least Privilege

NIST 800-171 / Access Control / 3.1.5

"Employ the principle of least privilege, including for specific security functions and privileged accounts." ([NIST SP 800-171 Rev. 2, requirement 3.1.5](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.5.

## What 3.1.5 means in practice

Give each account only the access its work needs, and be strictest with administrator accounts and security functions such as managing accounts, logging and keys. Assessors look for a short, named list of privileged accounts, access granted by role, and reviews that take away privileges nobody uses.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: AC.L2-3.1.5
- **SPRS points**: 3 points. When it is not met, the DoD Assessment Methodology subtracts 3 from the score of 110.
- **CMMC POA&M**: Not allowed. It is worth 3 points, and 32 CFR 170.21(a)(2)(ii) admits only requirements worth 1 point, with one exception: 3.13.11 when encryption is used but not FIPS validated.

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.5

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

- 3.1.5[a] privileged accounts are identified.
- 3.1.5[b] access to privileged accounts is authorized in accordance with the principle of least privilege.
- 3.1.5[c] security functions are identified.
- 3.1.5[d] access to security functions is authorized in accordance with the principle of least privilege.

[NIST SP 800-171A (June 2018), assessment objectives for 3.1.5](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.1.5 is met

- An inventory of privileged accounts with the person and the reason for each.
- Role definitions for security functions such as account management, logging and key management.
- Access reviews showing excess privileges were found and removed.
- Settings for time-limited or just-in-time elevation, where it is used.

## How PolicyCortex gathers the evidence

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

- **Azure: Role assignments.** Checks Azure role assignments for broad privileged roles where narrower built-in or custom roles would do.
- **Okta: Directory.** Counts Okta super administrators and flags more than four.
- **AWS: IAM.** Checks that no customer managed IAM policy grants full administrative access, that IAM principals carry no inline policies, and that the root account has no access keys.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.5 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.4: Separation of Duties](https://policycortex.com/nist-800-171/access-control/3.1.4)
- **Next**: [3.1.6: Non-Privileged Accounts](https://policycortex.com/nist-800-171/access-control/3.1.6)
- **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 | e3de54c9249c | ba57e78d3224 |
| REC 0001 | MEANING | fae174fea275 | e3de54c9249c |
| REC 0002 | POINTS AND POA&M | aee61d4802e1 | fae174fea275 |
| REC 0003 | ASSESSMENT OBJECTIVES | ad7ade484161 | aee61d4802e1 |
| REC 0004 | EVIDENCE | d20dd8b295db | ad7ade484161 |
| REC 0005 | COLLECTORS | 837fe244fe2b | d20dd8b295db |
| REC 0006 | RELATED | ab3a15f774aa | 837fe244fe2b |

Head sha3:ab3a15f774aa8cd5d797706fa4b871dc1b97112e9213e026f7d8a6374176e9d0. 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.