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.
Source: AWS Well-Architected Security Pillar, SEC05-BP03. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open AWS Well-Architected Security Pillar in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Network Firewall stateful rules · Cloud console / configuration management
- GWLB appliance configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Inspection VPC design · Document repository
- TLS inspection policy · Policy repository / GRC workspace
First move
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