Course contentsShow
← Security
Lesson 1813 of 3,05237. Cloud Security - Network ArchitectureFree lesson

Default VPC Security Considerations

Understanding default VPC configurations, their security implications, and when to use custom VPCs instead.

Default VPC Security Considerations

What you'll learn: How default VPCs differ from custom VPCs and why understanding their implicit configurations is critical for cloud security.

When you create a cloud account (AWS, Azure, GCP), the provider often creates a default VPC for you automatically. While convenient for quick deployments, these defaults come with security trade-offs you must understand before deploying production workloads.

What Makes Default VPCs Different

A default VPC is preconfigured with:

  • Public subnets by default – All subnets have internet gateway routes, making resources potentially internet-facing
  • Permissive default network ACLs – Allow all inbound and outbound traffic
  • Automatic public IP assignment – Instances may receive public IPs without explicit configuration
  • Predictable IP ranges – Often use standard CIDR blocks (like 172.31.0.0/16 in AWS)

Think of a default VPC like moving into a furnished apartment: everything works immediately, but the locks might be generic and windows left open.

Security Implications

The convenience of default VPCs creates risks:

  • Unintended exposure: Resources become internet-accessible without realizing it
  • Lack of segmentation: All services share the same flat network space
  • Compliance issues: Default configurations rarely meet regulatory requirements for network isolation
  • Predictable targeting: Attackers know default ranges and configurations

When to Use Custom VPCs

For production environments, always create custom VPCs with:

  • Explicit private and public subnet separation
  • Custom CIDR blocks aligned to your segmentation strategy (from lesson 1812)
  • Restricted default deny network ACLs
  • No automatic public IP assignment

Use default VPCs only for temporary testing, sandboxes, or learning environments where internet exposure is acceptable.

Key Takeaway: Default VPCs prioritize convenience over security—production workloads require custom VPCs with explicit isolation, private subnets, and controlled internet access to prevent unintended exposure and meet security requirements.