Segmentation and virtual firewalls: VDOMs, vsys and the cloud
▶ Start the interactive lesson
Burrow's parent company wants Burrow and its sister company on the same pair of firewalls, but completely separated, with separate admins. Meanwhile the dev team is moving apps to the cloud and asks: "Can we have the same firewall there?"
Key points
- Virtual firewall contexts split one box into several logical firewalls, each with its own interfaces, zones, routing tables, policies and optionally admins. They're used by MSPs, multi-company groups and to separate management traffic.
- Traffic between contexts is blocked unless you deliberately link them (an internal virtual link or shared gateway) and allow it with policy in both.
- Segmentation inside one network (users, servers, OT/CCTV, guests, PCI card systems) limits how far an attacker can move. It's often a compliance requirement.
- Virtual and cloud firewalls run the same OS as VMs on hypervisors or in AWS/Azure/GCP (including cloud-native managed firewall services), and container firewalls protect Kubernetes. They're deployed with templates and automation (Terraform, Ansible).
- SASE / SSE moves firewalling into a cloud service that users and branches connect to, which is the direction many companies are heading.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →