Ensure default VPC is not used
The default VPC in each region should not be used for workloads. Default VPCs have overly permissive default security group and subnet configurations.
Security Impact
Default VPCs have public subnets with auto-assigned public IPs, increasing exposure of resources.
How to Remediate
Create custom VPCs with appropriate CIDR ranges and security configurations. Delete or restrict access to default VPCs.
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 CIS AWS v1.5.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-vpc-3
- Service
- Virtual Private Cloud (VPC)
- Category
- Network Design
- Severity
- MEDIUM
- CIS Benchmark
- 5.4
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial