SC.L2-3.13.6 Network Communication by Exception
Deny network communications traffic by default and permit only traffic explicitly allowed by exception.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Review records for permitted exceptions · Document repository
governing documentDocuments that govern the control
- Firewall and access control lists showing a default deny posture · Policy repository / GRC workspace
- Documented and approved exceptions with justification · Document repository
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
- Default deny at perimeter only while internal traffic is permit all
- Any to any rules present alongside the deny default
- Exceptions accumulated with no periodic review
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.5 Public-Access System Separation · SC.L2-3.13.7 Split Tunneling