Running firewalls at scale: central management, logs and updates
▶ Start the interactive lesson
Burrow now has 52 firewalls. A new block rule took two days because someone logged into each one. Logs live on each box and roll over after a week. "One place to manage policy, one place for logs," Maya says. "And no firmware upgrades without a plan."
Key points
- A central manager holds shared objects and policies, splits device settings (interfaces, DNS, admin settings) from policy, and pushes changes in one go, with revision history and rollback.
- Most platforms use a commit / deploy model: you edit a candidate config, review the diff, then commit or push. Until then nothing changes on the box. "Did you commit?" is a classic support question.
- Logging: send traffic, threat and system logs to a log platform or SIEM (syslog, vendor log services). Keep enough retention for investigations and compliance. Build dashboards and reports for top apps, threats, users and blocked attempts.
- Updates come in two kinds: firmware/OS (planned, tested, follow the vendor's upgrade path, back up first) and security content (signatures, app and URL databases), which should update automatically.
- Automation: REST/XML APIs and tools like Ansible or Terraform create objects and rules from tickets, so there are fewer typos and changes are auditable.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →