Firewall policies: who gets in, who gets out
▶ Start the interactive lesson
Burrow is replacing its old router at head office with a next-gen firewall. Monday morning, nothing works. Staff can't reach the internet, and the helpdesk queue is filling up. Maya opens the firewall: interfaces up, routes fine. "Look at the policy list," she says. "It's empty. A firewall starts…
Key points
- A firewall checks every new connection against its policy list: incoming interface/zone, outgoing interface/zone, source, destination, service, then accept or deny.
- Policies are read top-down and the first match wins. Anything that matches nothing hits the implicit deny. Put specific rules above broad ones.
- Firewalls are stateful: an allowed connection creates a session. Replies match that session and come straight back, so you do not need a rule for return traffic. A WAN → LAN "allow all" rule is a hole, not a fix.
- Least privilege: allow only the sources, destinations and services that are needed, give each rule a clear name, log it, and review the list regularly (unused rules are risk and audit pain).
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →