About this interactive
What you're doing: one firewall, FW1, standing between three security zones — Trust (the staff LAN on 10.10.0.0/24), DMZ (the public web server web01 at 172.16.5.10) and Untrust (the internet). Five rules have to carry the entire policy, and you place them in order along with the zone-to-interface map and FW1's inspection mode. Then six test packets are traced against what you built. Why it matters: a zone-based firewall writes policy between zone pairs rather than per interface, reads it top down, stops at the first match, and ends in an implicit deny nobody types — and on top of all that it either remembers connections or it does not, which is the single biggest thing separating a modern firewall from a packet filter. How to use it: work each rule out from the business requirements before you read the cards, then trace the packets one at a time down the policy you wrote rather than guessing from intent. Watch two of the six in particular. The reply to a staff web request is permitted by a stateful FW1 without any rule being read at all, and dropped by a stateless FW1 on the implicit deny — same policy, opposite verdicts. And the workstation sending mail straight out to the internet is denied only because a narrow deny sits above the broad permit; move it one line down and it never fires again.
About TechKnowSurge
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 →