CMMC readiness · NIST 800-171 alignment · DFARS support Mon–Fri · 0800–1800 ET
Controls / Access Control / 3.1.13
3.1.13
AC.L2-3.1.13 · Level 2

Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

NIST SP 800-171 Rev 2 · §3.1.13

Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

Assessment objectives

From NIST SP 800-171A · 2 objectives must be met to satisfy this control
3.1.13[a] cryptographic mechanisms to protect the confidentiality of remote access sessions are identified.
Examine
[SELECT FROM: Access control policy; procedures addressing remote access to the system; security plan; system design documentation; system configuration settings and associated documentation; cryptographic mechanisms and associated configuration documentation; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: System or network administrators; personnel with information security responsibilities; system developers].
Test
[SELECT FROM: Cryptographic mechanisms protecting remote access sessions].
3.1.13[b] cryptographic mechanisms to protect the confidentiality of remote access sessions are implemented.
Examine
[SELECT FROM: Access control policy; procedures addressing remote access to the system; security plan; system design documentation; system configuration settings and associated documentation; cryptographic mechanisms and associated configuration documentation; system audit logs and records; other relevant documents or records].
Interview
[SELECT FROM: System or network administrators; personnel with information security responsibilities; system developers].
Test
[SELECT FROM: Cryptographic mechanisms protecting remote access sessions].

What we look for in practice

The following are placeholder notes that should be refined based on practice experience.

What assessors look for in practice. Documented evidence that this control is implemented across all CUI-handling systems within scope. Specific artifacts vary, but expect requests for written procedures, system configurations, and operational records demonstrating the control is active.

Common failure patterns. Typical issues include incomplete documentation, inconsistent implementation across systems, and missing periodic review records. Refine this section as your practice accumulates direct assessment experience.

Strong evidence looks like. Formal policy referencing this control, technical configurations demonstrating enforcement, periodic review logs with sign-off, and procedures for handling exceptions.

Scoring and POA&M context. 5-point control under the DoD Assessment Methodology. Highest scoring impact — treat as a foundational requirement. Not POA&M-eligible — must be implemented at assessment time.