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

Subnet Security Best Practices

Implementing least privilege routing, minimizing public subnet usage, and monitoring NAT traffic flows.

Subnet Security Best Practices

What you'll learn: How to secure cloud subnets by minimizing attack surface, enforcing strict routing rules, and monitoring outbound traffic patterns.

The Three Pillars of Subnet Security

Now that you understand subnet types, NAT architectures, and multi-AZ design, it's time to harden your network layer with proven security practices.

1. Implement Least Privilege Routing

Your route tables should only allow traffic that's absolutely necessary. Think of route tables as the traffic laws of your VPC—don't create "shortcut" routes just because they're convenient.

Example principle: If a private subnet only needs internet egress through a NAT Gateway, don't add direct routes to other VPCs or peering connections unless required. Each route is a potential path for lateral movement in case of compromise.

2. Minimize Public Subnet Usage

Public subnets (those with direct internet gateway routes) expand your attack surface. Use them sparingly—typically only for:

  • Load balancers
  • Bastion hosts (and even these should be replaced with session management services when possible)
  • NAT Gateways themselves

Keep application servers, databases, and business logic in private subnets. Imagine public subnets as your building's lobby—it's exposed to the outside world, so you only put essential, hardened components there.

3. Monitor NAT Traffic Flows

Your NAT Gateway or NAT Instance is a critical security chokepoint. Enable VPC Flow Logs specifically for NAT resources to:

  • Detect unusual outbound connections (potential data exfiltration)
  • Identify compromised instances attempting command-and-control communication
  • Track which private resources generate the most egress traffic

Think of NAT monitoring as airport security cameras—they show you who's leaving, where they're going, and when suspicious patterns emerge.

Key Takeaway: Secure subnets by routing minimally, keeping resources private by default, and treating your NAT Gateway as a monitored security boundary—defense-in-depth starts with thoughtful network architecture.