AC.L2-3.1.14 Remote Access Routing
Force remote access traffic through a limited set of managed access control points rather than allowing arbitrary entry paths into the network.
Source: CMMC 2.0, AC.L2-3.1.14. 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.
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
none for this control
periodic reviewEvidence produced at each review
- Evidence that alternative ingress paths are blocked · Identity provider / directory
governing documentDocuments that govern the control
- Network architecture identifying the managed remote access points · Policy repository / GRC workspace
- Firewall rules restricting remote entry to those points · Policy repository / GRC workspace
First move
Common gaps auditors find
- Multiple undocumented remote entry points
- Vendor appliances providing side channel access
- Split of remote traffic across unmanaged cloud services
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 sheetAC.L2-3.1.13 Remote Access Confidentiality · AC.L2-3.1.15 Privileged Remote Access