SC-7 Boundary Protection
Monitor/control communications at external boundary and key internal boundaries; implement subnetworks for publicly accessible components.
5
artefacts
0
held by a system
1
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
- Denial of service protection configuration and capacity test results · Source control / CI pipeline
governing documentDocuments that govern the control
- Control implementation statement for SC-7 citing the system mission and inheritance from common controls · Document repository
- Network segmentation diagrams with VLAN and zone mapping · Policy repository / GRC workspace
- Boundary protection architecture with firewall and proxy rule documentation · Policy repository / GRC workspace
- Cryptographic standards specifying approved algorithms and key lengths · 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
- Firewall rule base contains stale allow any entries
- Internal traffic between services unencrypted within trusted zones
- Legacy TLS versions remain enabled on external 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 sheet