Hey everyone. Looking at Cato's SASE/SSE platform for a possible future project. We're a mid-sized finance company, not huge but we have some compliance needs (think basic PCI DSS, some data residency stuff).
I've been reading the docs and watching the demo videos. The tunneling, FWaaS, and SWG parts seem solid for replacing our old VPN. But I'm trying to map it to real needs.
For those using it in a similar regulated space: what felt missing or needed extra work? I'm thinking about stuff like:
- Customizing the "block page" for the web filter to match our internal branding/policies – is that easy?
- Needing a specific TLS cipher for an old banking portal – can you tweak that per application?
- How detailed are the logs for proving "who accessed what and when" for audits? Can you pipe them easily to a SIEM like Splunk?
Just trying to see where we might hit little gaps. Not expecting a full on-premise NGFW feature set, but curious about the practical day-to-day config limits. Thanks!
The logging for audits is the biggest red flag. You can get who accessed what, but piping it to Splunk is a chore. Their API is clunky and the log format is pretty rigid. We had to build a custom parser just to get useful fields into our SIEM.
You mentioned PCI DSS. Their compliance reports are generic checklists. If you need to prove a specific control from your logs, expect to manually assemble evidence.
The block page customization exists, but it's basically a text field. You can't inject CSS or your own legal notice boilerplate. It looks like their system, not yours.
Your vendor is not your friend.