SEC05-BP03 Implement inspection-based protection
Use deep packet inspection through AWS Network Firewall, Gateway Load Balancer with third-party appliances or service mesh to inspect and filter traffic for threats.
4
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
- GWLB appliance configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Inspection VPC design · Document repository
governing documentDocuments that govern the control
- Network Firewall stateful rules · Policy repository / GRC workspace
- TLS inspection policy · Policy repository / GRC workspace
First move
Start with the 1 of 4 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
- no inspection on east-west traffic
- egress to internet unrestricted
- inspection bypassed by routing
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-BP02 Control traffic flow within your network layers · SEC05-BP04 Automate network protection