SC.L2-3.13.5 Public-Access System Separation
Place publicly accessible system components on subnetworks that are physically or logically separated from internal networks.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Firewall or routing configuration enforcing the separation · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Network diagram showing the separated subnetwork for public components · Policy repository / GRC workspace
- Inventory of publicly accessible components · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Public facing servers residing on internal networks
- Separation exists but permissive rules allow broad internal access
- New public services deployed outside the segmented zone
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 sheetSC.L2-3.13.4 Shared Resource Control · SC.L2-3.13.6 Network Communication by Exception