SEC05-BP02 Control traffic flow within your network layers
Restrict traffic within each network layer to only the flows each workload component needs, controlling both traffic entering from external systems and traffic between internal components.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Security group and network ACL rule sets with justification per rule · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence of review or automated analysis of overly permissive rules · Cloud console / configuration management
governing documentDocuments that govern the control
- Documented allowed flow matrix for the workload · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- wide open internal traffic once inside the perimeter
- 0.0.0.0/0 ingress rules left from testing
- no flow inventory so unused rules are never removed
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 sheetSEC05-BP01 Create network layers · SEC05-BP03 Implement inspection-based protection