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.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Firewall rules restricting remote entry to those points · Identity provider / directory
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
First move
Start with the 1 of 3 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
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