AWS Builder Center
5 Step Plan - How TO think like the cloud using AWS Security Groups and NetworkACLs | What on-prem Firewall Engineers must know

5 Step Plan - How TO think like the cloud using AWS Security Groups and NetworkACLs | What on-prem Firewall Engineers must know

A hands-on walkthrough of how traditional on-premise firewall engineers can retrain their way of thinking to cloud-native security with AWS Security Groups and Network ACLs

Moving from Config of on-prem hardware firewalls like Sophos XG, the concept of network security has always been perimeter based. You're defining zone-to-zone policies, you're working with static CIDRs for ranges, you are filtering packets that come into or go out of your company perimeter.
When you start learning AWS, for Cloud Practitioner and Solutions Architect certs you soon realize that cloud security is completely different, not perimeter based, but finely tuned micro-segmentation.
Here is how I mapped my on-prem network security skill set to core AWS Networking principles.
  1. Statefulness - Security Groups vs Traditional Firewall Rules
In a traditional firewall, you usually have a double entry rule - inbound port/protocol is defined, followed by an outbound Port/protocol on that interface (sometimes this relies heavily on statefull connection tracking at the border).
AWS Security Groups act as a stateful virtual firewall at the instance level (ENI), not at the subnet level. If you open port 443 to your instances, your instances can automatically communicate out to the internet without a specific egress rule defined in the Security Groups.
This works at the instance level, this means even if two instances live in the same subnet (and can 'see' each other at layer 3), they cannot communicate unless specific ALLOW rules are defined in their respective Security Groups.
2. The Two Tier Defense - Security Groups and NACLs Combined
The most common confusion for traditional network engineers is the role of the NACL and Security Group and it’s easier to explain with this summary.
Network ACLs - Stateless, applied at the SUBNET level. Evaluate rules in order, and are the primary place that you can create specific DENY rules to block IPs before traffic ever gets to your workload.
Security Groups - Stateful, applied at the INSTANCE level. Will only evaluate ALLOW rules. Anything that is not explicitly allowed is denied by default (Zero Trust).
3. Identify aware Security Rules
Traditional on-premise networking has always relied on IP addresses or CIDR blocks for rules. AWS has this elegant option where Security Groups can reference other Security Groups. Rather than allowing traffic to database port 3306 through to the CIDR block for a subnet, your database Security Group will allow traffic only from the Security Group ID of your web tier security groups. This means there will be no need to re-engineer firewall rules when instances auto-scale!
Key Takeaway for Aspiring Cloud Architects:
Your traditional networking knowledge won't be obsolete in AWS, instead it will be fine-tuned for the cloud. Understanding the concept of how your subnets and your workload boundaries operate differently via NACLs and Security Groups respectively will pave the way to well-architected solutions.
What are the differences between your traditional firewall rules and the approach you're taking with Security Groups and NACLs? Let me know in the comments below!
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article