---
title: "NIST 800-171 3.1.6 (AC.L2-3.1.6): Non-Privileged Accounts"
description: "NIST SP 800-171 3.1.6 Non-Privileged Accounts: 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.6
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.6
records: 7
digest: sha3:3c7155d4907ef93c267eba90f004538fb9910fe7c02beba36ee84fb850d35d5a
---

# NIST 800-171 3.1.6 (AC.L2-3.1.6): Non-Privileged Accounts

NIST 800-171 / Access Control / 3.1.6

"Use non-privileged accounts or roles when accessing nonsecurity functions." ([NIST SP 800-171 Rev. 2, requirement 3.1.6](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.6.

## What 3.1.6 means in practice

Administrators should not read email, browse the web or do everyday work while signed in with administrator rights. The usual answer is two accounts for each administrator, one ordinary and one privileged, or an administrative role that is switched on only for the task at hand.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: AC.L2-3.1.6
- **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.6

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

- 3.1.6[a] nonsecurity functions are identified.
- 3.1.6[b] users are required to use non-privileged accounts or roles when accessing nonsecurity functions.

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

## Evidence that shows 3.1.6 is met

- A list of administrators showing each one's everyday account and separate privileged account.
- Policy text requiring non-privileged accounts or roles for nonsecurity work.
- Settings that keep mailboxes and web browsing away from privileged accounts, or that require activating an administrative role before use.

## How PolicyCortex gathers the evidence

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

- **Azure: Role assignments.** Checks that users holding privileged Azure roles also have separate non-privileged accounts for nonsecurity functions.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.6 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.5: Least Privilege](https://policycortex.com/nist-800-171/access-control/3.1.5)
- **Next**: [3.1.7: Privileged Functions](https://policycortex.com/nist-800-171/access-control/3.1.7)
- **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 | 44f943267485 | 3480f30a8795 |
| REC 0001 | MEANING | 34811c8daf9a | 44f943267485 |
| REC 0002 | POINTS AND POA&M | 55d629f688c9 | 34811c8daf9a |
| REC 0003 | ASSESSMENT OBJECTIVES | f7f8e2deee06 | 55d629f688c9 |
| REC 0004 | EVIDENCE | a4b545bdd80c | f7f8e2deee06 |
| REC 0005 | COLLECTORS | 0de13837b71f | a4b545bdd80c |
| REC 0006 | RELATED | 3c7155d4907e | 0de13837b71f |

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