Implement Network Segmentation with VPC Design
Specification & Description
Establish network segmentation standards and tiered VPC design patterns to restrict traffic between public, application, and database subnets.
Technical Specifications
Unsegmented networks expose critical data tiers when front-facing application components face compromise. Standardized VPC designs enforce multi-tier isolation by separating workloads into public, private application, and isolated database subnets across distinct Availability Zones. Route tables restrict Internet Gateway access strictly to public subnets, application tiers reach external dependencies through NAT or transit inspection firewalls, and database subnets operate with no external routes. Security groups and Network ACLs enforce boundaries between tiers.
Security Rationale
Tiered network segmentation limits the blast radius of security incidents and prevents lateral movement across the workload environment. Standard VPC templates guarantee that default configurations disable public IP auto-assignment on internal subnets and deny direct inbound routes to sensitive data layers.
Business & Security Impact
Flat network architectures permit unauthorized lateral traversal. If an internet-facing workload is compromised, an attacker can directly target unsegmented database and internal application services without network friction.
Compliance Framework Mappings (5)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | SC-7AC-4 | 2 |
ISO 27001:2022ISO 27001 | A.8.22 | 1 |
PCI DSS v4.0PCI DSS | 1.2.11.3.1 | 2 |
CIS AWS Foundations Benchmark v3.0CIS AWS | 5.4 | 1 |
SOC 2SOC 2 | CC6.6 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Inspect VPC subnet attributes to detect unexpected public IP assignment on internal tiers, examine route tables to confirm data subnets have no internet gateway routes, and check default security groups for leftover allow rules.
Remediation Guide & Automation
Deploy VPCs using standard tiered subnet patterns (public, private application, and isolated database) with dedicated route tables. Explicitly disable public IP auto-assignment on internal subnets, remove default VPCs and default security group rules, and provision boundaries via Infrastructure as Code.
Step-by-Step Instructions
- Provision a VPC container with an approved non-overlapping CIDR block.
- Create distinct subnet tiers for public ingress, application logic, and isolated database services across at least two Availability Zones.
- Explicitly disable MapPublicIpOnLaunch on private application and database subnets.
- Associate dedicated route tables per tier, ensuring isolated subnets have no routes to Internet Gateways or NAT Gateways.
- Revoke all ingress and egress rules from default security groups in every VPC.