Apply the same rules everywhere — public cloud, on-prem, and Kubernetes alike
The problem
- Keeping departments, customers, or environments cleanly separated usually means separate tools per environment — one for a public cloud region, another for the datacenter, another for Kubernetes.
The solution
- Headends register as clusters labeled by region and datacenter, so a public cloud region and an on-prem datacenter both plug into the same central policy — no separate setup per location.
- Tobogganing applies the same routing and segmentation controls to conventional infrastructure and to Kubernetes pods, from the same platform.
Outcomes
- One security model to maintain, not one per environment.
- New sites — a cloud region, a datacenter, or a Kubernetes cluster — plug into rules that already exist instead of starting from scratch.