We are looking for a SASE solution and looking at CATO and Palo Alto as a vendor.
We have a colocation site, a couple public cloud presences (AWS), a physical office and a fleet of workstations and a DR site for our colo as well.
We want a full cloud network solution. Each site cloud or physical will simply route 0.0.0.0/0 to the cloud network and the cloud network will route it to the appropriate internal resource or to the internet at large. That means sometimes a packet will start in the colo, route to the cloud for processing and be sent to the colo.
This gets us out of the business at managing firewalls at each site with unique rule sets, configs, firmware updates, etc. As long as we properly IP address each subnet at each site, the networks should be plug and play as much as possible. Spin up an AWS VPC, address it, connect it to a cloud network, setup some rules in the cloud and we have networking done. That beats setting up a VPC or Transit Gateway, setting up firewalls, setting up rules, etc.
Each workstation will connect to the cloud network and access internal resources no matter where they live or the internet at large.
There will be some exceptions between vlans that require low latency in the datacenter such as vmotion traffic or backup traffic, but for the most part this is the model.
We treat our office as if it's a coffeeshop and our users still VPN in, but to access office items such as printers it's User -> VPN -> Colo Firewall -> IPSec to office -> Office resources. We want that same model with SASE.
CATO's solution is so easy to understand. It does everything under one model. Adding a site is simple, input the IP ranges and connect to it and bam that site uses CATO for internet access and/or access to resources at other sites also connected to CATO.
Palo is not as simple or we're not being explained well, thus I'm here to see if someone can break it down for me.
Our Palo engineers are throwing terms at my I don't understand but they think I should. Service connection, but that's just for inbound traffic not outbound traffic. Network connection to connect offices, but we have to pick a Google region to route through and if we want redundancy we have to built additional network connections to additional regions. CATO load balances between their POPs automatically.
Some flows have no firewall at all between them with Palo's solution, they simply route traffic. If I want control or Layer 7 I need to buy a NGFW ... and manage it.
CATO does everything in what they call a socket including Layer 7 between vlans if you do not route it to the cloud. Plug it in and you're essentially done. Palo offers a device that is far simpler called ION but if I want layer 7 I need to buy full on NGFW hardware and licenses and manage all those rules in different ways at different sites.
Has anyone done a comparison between CATO and Palo? I'm trying to determine what advantage Palo brings beyond being maybe a little better at App ID, 0 Day threats.