Objects and rule design: a policy set you can live with
▶ Start the interactive lesson
Burrow's old firewall has 900 rules. Half say things like "allow 10.4.7.0/24 to any". Nobody knows what they're for, and the auditor wants answers by Friday. Maya opens a fresh rule base. "This time we use objects, names, and comments. And we check what's never been hit."
Key points
- Objects are reusable names for things: addresses (host, subnet, range, FQDN), services (TCP 443), applications, schedules and groups of these. Change the object once and every rule using it updates.
- Dynamic objects update themselves: FQDN objects follow DNS, and external lists / threat feeds pull IPs or URLs from a URL on a schedule, so you can block a fresh list of bad IPs without editing rules.
- Rule order matters. Put specific rules (exceptions, blocks) above broad ones. A rule that can never match because something above it matches first is shadowed, which is a common audit finding.
- Hygiene: name every rule, add a comment or ticket number, enable logging, avoid "any/any", and review hit counts. Rules with zero hits for 90 days are candidates to disable, then delete.
- In big estates, central managers add layers: rules pushed before local rules (company-wide must-haves) and after them (catch-all clean-up), so a site admin can't override head office.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →