---
title: "NIST 800-171 3.1.13 (AC.L2-3.1.13): Remote Access Encryption"
description: "NIST SP 800-171 3.1.13 Remote Access Encryption: 5 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.13
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.13
records: 7
digest: sha3:6f9bb62827a301836480f70ae229b0eb44f1b0a13eb7f8d94a016758b9bdadd7
---

# NIST 800-171 3.1.13 (AC.L2-3.1.13): Remote Access Encryption

NIST 800-171 / Access Control / 3.1.13

"Employ cryptographic mechanisms to protect the confidentiality of remote access sessions." ([NIST SP 800-171 Rev. 2, requirement 3.1.13](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.13.

## What 3.1.13 means in practice

Remote sessions are encrypted so CUI cannot be read on its way across the internet. That covers VPNs, remote desktop gateways and management connections, and because the encryption protects CUI it should come from FIPS-validated cryptographic modules, as 3.13.11 requires.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: AC.L2-3.1.13
- **SPRS points**: 5 points. When it is not met, the DoD Assessment Methodology subtracts 5 from the score of 110.
- **CMMC POA&M**: Not allowed. It is worth 5 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.
- **Scoring note**: If the system permits no remote access, mark Met: Annex A subtracts nothing.

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

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

- 3.1.13[a] cryptographic mechanisms to protect the confidentiality of remote access sessions are identified.
- 3.1.13[b] cryptographic mechanisms to protect the confidentiality of remote access sessions are implemented.

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

## Evidence that shows 3.1.13 is met

- VPN and remote gateway configuration showing the protocols and ciphers in use.
- FIPS 140 validation certificates for the cryptographic modules that protect remote sessions.
- A list of every remote access path with the encryption each one uses.

## How PolicyCortex gathers the evidence

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

- **Azure: VPN gateways.** Reads each Azure VPN gateway's IPsec policies and checks that remote access connections use FIPS-validated cryptographic mechanisms.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.13 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.12: Remote Access Control](https://policycortex.com/nist-800-171/access-control/3.1.12)
- **Next**: [3.1.14: Remote Access Routing](https://policycortex.com/nist-800-171/access-control/3.1.14)
- **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 | 3e2a45035389 | 2aeb8f039f72 |
| REC 0001 | MEANING | 50a07c711e91 | 3e2a45035389 |
| REC 0002 | POINTS AND POA&M | 94f5ae004446 | 50a07c711e91 |
| REC 0003 | ASSESSMENT OBJECTIVES | 4450ccd70098 | 94f5ae004446 |
| REC 0004 | EVIDENCE | a858b7244938 | 4450ccd70098 |
| REC 0005 | COLLECTORS | b8e904f415ab | a858b7244938 |
| REC 0006 | RELATED | 6f9bb62827a3 | b8e904f415ab |

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