Ensure default VPC network is not used
Default VPC networks have permissive firewall rules and should not be used for production.
Security Impact
Default networks have overly permissive rules that may expose resources.
How to Remediate
Create custom VPC networks with restrictive firewall rules. Delete the default network.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your GCP environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Google Cloud VPC resources across your GCP projects 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 GCP v1.3.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
- gcp-networking-1
- Service
- Google Cloud VPC
- Category
- Network Security
- Severity
- MEDIUM
- CIS Benchmark
- 3.1
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free TrialRelated Google Cloud VPC Checks
View all checksEnsure legacy networks do not exist
Ensure firewall rules do not allow unrestricted SSH access
Ensure firewall rules do not allow unrestricted RDP access
Ensure VPC flow logs are enabled
Ensure Private Google Access is enabled for subnets