SC-7 Boundary protection
Requires communications to be monitored and controlled at external managed interfaces and at key internal interfaces, publicly accessible components to sit in subnetworks physically or logically separated from internal n
4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Firewall and gateway rule sets with review records · Cloud console / configuration management
- Evidence publicly accessible components are separated from internal networks · Document repository
governing documentDocuments that govern the control
- Network architecture diagram identifying external and key internal managed interfaces · Policy repository / GRC workspace
- Inventory of external connections showing each passes through a managed interface · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Undocumented external connections such as vendor tunnels bypass the managed interfaces
- Internal interfaces unmonitored, so lateral movement is invisible
- Publicly accessible components share a network segment with internal 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 sheetSC-6 Resource Availability. Protect the availability of resources by allocating [organization-defined] by [organization-defined] · SC-8 Transmission confidentiality and integrity