SC.L2-3.13.1 Boundary Protection
Monitor, control and protect communications at the external boundary of the system and at key internal boundaries.
3
artefacts
2
held by a system
0
at each review
easy
to go live
Endpoint management (MDM / EDR)
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Boundary device configuration such as firewall and gateway rulesets · Endpoint management (MDM / EDR)
- Monitoring evidence at those boundaries · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Network architecture identifying external and key internal boundaries · Policy repository / GRC workspace
First move
Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.
Common gaps auditors find
- External boundary protected while internal boundaries are flat
- Boundary devices configured but traffic not monitored
- Cloud and remote boundaries omitted from the architecture
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 sheetRA.L2-3.11.3 Vulnerability Remediation · SC.L2-3.13.2 Security Engineering