When the gateway stops, enforcement should not.
Routing browsing through a secure gateway works until the gateway stops responding. Then either the workforce stops, or someone opens a bypass and protection goes dark. The Enforce agent removes that choice.
Talk to salesThe scenario
Your primary gateway has a regional outage at 11 in the morning. Browsing fails across the company. The service desk queue fills, and someone proposes a temporary bypass that nobody will remember to remove.
How Enforce handles it
- 01
The agent has been probing the primary path all along and notices it degrade.
- 02
It moves traffic to a backup gateway you already own, using a per route allow list. Users see no prompt.
- 03
While on the backup, the agent keeps blocking malicious and disallowed sites from its local copy of policy.
- 04
When the primary recovers, traffic returns to it. The failover and its duration are logged, and an alert reaches your Slack channel.
Context
Enforce runs alongside your gateway at all times. It does not replace it, and it is not idle while the gateway is healthy.
See Enforce on your own traffic.
We start in watch mode on a group you choose and show you what Enforce would have blocked before anything is switched on.
Talk to sales