What evidence do auditors commonly ask for on AC.L2-3.1.13 Remote Access Confidentiality?

Remote access encryption configuration showing protocol and cipher settings; Evidence that weak or plaintext remote protocols are disabled; Certificate or key management records for the remote access service.

What is the most common gap auditors find on AC.L2-3.1.13?

Legacy plaintext protocols still enabled as fallback

CMMC 2.0 · Access Control

`AC.L2-3.1.13` Remote Access Confidentiality

Apply cryptographic protection to remote access sessions so session confidentiality is preserved in transit.

Source: CMMC 2.0, AC.L2-3.1.13. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.

artefacts

held by a system

at each review

moderate

to go live

Key management / PKI

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Remote access encryption configuration showing protocol and cipher settings · Key management / PKI

periodic reviewEvidence produced at each review

Evidence that weak or plaintext remote protocols are disabled · Identity provider / directory
Certificate or key management records for the remote access service · Key management / PKI

governing documentDocuments that govern the control

none for this control

First move

Start with the 1 of 3 artefacts that already live in a system (Key management / PKI); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Legacy plaintext protocols still enabled as fallback
Encryption terminated at an intermediary leaving segments in clear
Cipher suites unreviewed and outdated

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

AC.L2-3.1.12 Control Remote Access · AC.L2-3.1.14 Remote Access Routing