---
title: "NIST 800-171 3.1.15 (AC.L2-3.1.15): Privileged Remote Access"
description: "NIST SP 800-171 3.1.15 Privileged Remote Access: 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.15
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.15
records: 7
digest: sha3:b1e492c93f629ac8db5d8ad828d66a0c7d90bed6720f8c5071d3072cc23319c6
---

# NIST 800-171 3.1.15 (AC.L2-3.1.15): Privileged Remote Access

NIST 800-171 / Access Control / 3.1.15

"Authorize remote execution of privileged commands and remote access to security-relevant information." ([NIST SP 800-171 Rev. 2, requirement 3.1.15](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.15.

## What 3.1.15 means in practice

Administrative commands and security settings may be used from outside the network only where that use has been specifically authorized. List which privileged commands and which security-relevant information may be reached remotely and by whom, and grant that access deliberately, often through a privileged access workstation or a jump host.

## SPRS points and the CMMC POA&M

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

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

- 3.1.15[a] privileged commands authorized for remote execution are identified.
- 3.1.15[b] security-relevant information authorized to be accessed remotely is identified.
- 3.1.15[c] the execution of the identified privileged commands via remote access is authorized.
- 3.1.15[d] access to the identified security-relevant information via remote access is authorized.

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

## Evidence that shows 3.1.15 is met

- A list of the privileged commands and security-relevant information approved for remote use.
- Authorization records for the administrators allowed to use them remotely.
- Configuration of the privileged access path, such as a jump host or a privileged access management tool, with its session logs.

## How PolicyCortex gathers the evidence

No PolicyCortex collector reads the evidence for 3.1.15. Your team provides the evidence listed above.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.15 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.14: Remote Access Routing](https://policycortex.com/nist-800-171/access-control/3.1.14)
- **Next**: [3.1.16: Wireless Authorization](https://policycortex.com/nist-800-171/access-control/3.1.16)
- **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 | 0e96d61a4cf4 | 02053ec2b601 |
| REC 0001 | MEANING | a1fff2243f03 | 0e96d61a4cf4 |
| REC 0002 | POINTS AND POA&M | 104ece79589a | a1fff2243f03 |
| REC 0003 | ASSESSMENT OBJECTIVES | 107e9ca9adf4 | 104ece79589a |
| REC 0004 | EVIDENCE | c288a875a5e2 | 107e9ca9adf4 |
| REC 0005 | COLLECTORS | a9183bc6ff3e | c288a875a5e2 |
| REC 0006 | RELATED | b1e492c93f62 | a9183bc6ff3e |

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