Established traffic rules allow ACLs to permit inbound packets only when they are replies to outbound requests originating from inside the network, blocking unsolicited traffic from external threat actors. This mechanism forms the foundation of stateful packet inspection and modern firewall behavior.
Established Traffic Rule
There's another type of rule that we need to be familiar with: the established traffic rule.
Let's develop a little scenario here. What we have is LAN 1 here, which is a bunch of machines that need to communicate, and so on and so forth. And we have LAN 2 here, a bunch of machines that need to communicate as well. And then we have our WAN interface. This goes to the outside world, the cloud, the internet.
But we have an issue out there. There are hackers, there are threat actors, there are adversaries that are going to try to get into your network. And if you allow them, what they will do is come in through their WAN connectivity and go into your other networks. We want to avoid this. We want to stop them from being able to get into our networks. As a result, what we're going to do is post the ACL at the front door. We're going to guard it against these adversaries so they can't get in. So we're not going to allow traffic to come in through this WAN interface.
But this causes a problem, because now a machine is going to want to access the internet. So what they're going to do is go out and access the internet. There's a packet that goes out and says, "Hey, I'd like this website." And what will happen is this website will then return back, and it will make a reply back and send it back to this machine over here. But the security guard, this access control list, is going to say, "Uh-uh, no, you're not getting into my network. I'm protecting my network."
This is where established traffic comes into place. This is a special rule that can be put on certain interfaces. So what will happen is that this machine will reach out to something on the internet, and when it does that, this router right here will establish what is the source IP address and what is the destination IP address. So now when the traffic comes back through, this ACL right here will allow traffic to come back and reach the machine. So now we can get the traffic that we asked for.
So let's say this machine is 192.168.54.16, and it's going into this router, coming out to get to 216.15.24.20. When it makes this journey, this interface is going to record that 192.168.54.16 is communicating with 216.15.24.20. So now when the reply packet comes through, it's going to say, well, is this the source, and is it going to this destination? And it'll look at the ports as well. If that's the case, then it will say, okay, then I will allow it back in to get to this machine right here.
Now when the adversary reaches out and tries to get in, it doesn't see that in this table and says, nope, you're not allowed. So I'm not going to allow you to get into this network.
This is the premise of how firewalls work. What we want is we want traffic to be able to go out to the rest of the world. But if it was coming back in and was not requested, then this firewall is going to stop that traffic from coming in to the rest of the network.
One thing we could associate this with is a stateful firewall, or stateful packet inspection. When we're doing something like this, it's really stateful packet inspection. Know that there's an association between this established traffic and allowing it, and this stateful packet inspection.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →