Ensure VPC has separate public and private subnets
VPCs should have separate public and private subnets to enable proper network segmentation and minimize exposure of internal resources.
Security Impact
Without network segmentation, internal resources may be exposed to the internet unnecessarily.
How to Remediate
Create private subnets for databases, application servers, and other internal resources. Use public subnets only for load balancers and NAT gateways.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Virtual Private Cloud (VPC) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-vpc-5
- Service
- Virtual Private Cloud (VPC)
- Category
- Network Design
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial