Ensure VPC peering connections are documented and reviewed
VPC peering connections should be documented, reviewed regularly, and use proper route table configurations to limit access.
Security Impact
Undocumented or misconfigured peering connections can create unintended network paths between environments.
How to Remediate
Document all VPC peering connections. Review route tables to ensure only required CIDR ranges are routed through peering connections.
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, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-vpc-9
- 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