Two bad options
Historically, enterprises either backhauled branch internet traffic to headquarters for inspection — adding latency — or let branches go to the internet directly with minimal security.
A third way
Branches connect to the nearest Peer1IX hub. Internet-bound traffic passes through Peer1ix FWaaS at that hub and exits locally.
What users notice
Faster access to SaaS and websites, because traffic does not travel to a distant headquarters first.
What security teams get
One policy, enforced the same way for every branch, with central logs.
Combine with SD-WAN
SD-WAN tunnels from branches can terminate at the hub, where FWaaS inspects traffic before it goes to the internet or into private networks.
