SEC05-BP01 Create network layers
Design VPCs with separate public, private and restricted subnets per workload tier, isolating data tiers from internet-facing components.
4
artefacts
1
held by a system
0
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
- Route table configuration · 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
- NACL and security group baselines · Policy repository / GRC workspace
- Transit Gateway topology · 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
- 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