SEC05-BP01 Create network layers
Design VPCs with separate public, private and restricted subnets per workload tier, isolating data tiers from internet-facing components.
Source: AWS Well-Architected Security Pillar, SEC05-BP01. 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
- Route table configuration · Cloud console / configuration management
- NACL and security group baselines · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- VPC and subnet design diagrams · Policy repository / GRC workspace
- Transit Gateway topology · Policy repository / GRC workspace
First move
Common gaps auditors find
- flat VPCs with single subnet tier
- databases in public subnets
- no NAT or egress controls
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 sheetSEC04-BP04 Initiate remediation for non-compliant resources · SEC05-BP02 Control traffic flow within your network layers