1.3.1 Inbound traffic to CDE restricted
Inbound traffic to the CDE is restricted to only that which is necessary; all other traffic is denied.
5
artefacts
1
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
- Firewall rule export with business justification per rule · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Rule review report · Document repository
governing documentDocuments that govern the control
- Default deny rule at end of ACL · Document repository
- Penetration test confirming filter effectiveness · Policy repository / GRC workspace
- Sample packet captures · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Any-any rules present
- Missing explicit deny
- No justification per rule
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 sheet1.2.8 Configuration files secured and synchronised · 1.3.2 Outbound traffic from CDE restricted