Last updated: May 1, 2026
Every enterprise has a firewall. Almost every enterprise also has a 4,000-rule legacy ACL that nobody fully understands, where rule 2,847 is “allow any-any from finance subnet, ticket #FRD-1239 from 2018.” This module is about avoiding that fate. The mental model is simple — match-then-action — but the design discipline is what separates a defensible firewall from a compliance bedtime story.
Stateless vs stateful — the fundamental distinction
A stateless filter (router ACL, AWS Network ACL, classic packet filter) inspects each packet independently. To allow inbound HTTP to a web server, you must explicitly allow inbound TCP/80 AND outbound TCP from ephemeral ports back to the client. Forget the second rule and the response is dropped. A stateful firewall remembers connections — once you allow the inbound SYN, the firewall automatically allows the corresponding return traffic. Stateful firewalls track the four-tuple plus TCP flags and timeouts, building a connection table that is the basis of all modern enterprise firewalls (Palo Alto, Fortinet, Check Point, AWS Security Groups, Linux nftables connection tracking).
When stateless still winsultra-high-throughput edge filtering (DDoS scrubbing, ISP edge), where building per-packet state is too expensive. For everything else, stateful is the default in 2026.
Custom team training + practitioner advisory
Beyond the free academy — we run private workshops, vCISO advisory, and red-team exercises tailored to your stack. For Indian SMBs scaling past their first hire.