I like that Cato SASE Cloud is relatively straightforward to navigate, configure, and manage, despite having many moving parts. The platform's ease of use stands out, even with features like AI. I also really appreciate the technical support. I've worked with Cato support on complex issues, and I value how engineers are open to investigation and challenging assumptions, which makes resolving problems collaborative and effective. Although not all engineers operate the same way, the willingness to escalate issues and genuinely try to help is something I appreciate about their support team. Review collected by and hosted on G2.com.

One area I think could be improved is visibility around configuration changes. I regularly submit feature requests when I come across something operationally that I think could make the platform better. One live example that I haven't raised yet but it's on my list is being able to see directly on a rule who originally created it and who last modified it. That information is available through the auditing functionality, but when you are troubleshooting or reviewing a rule base, having to go into the audit trail and work backwards can be time-consuming, to say the least. Having that information available directly against the rule would make it much quicker to understand its history and give you useful context when investigating why something has been configured a particular way, especially when the rule counter is showing zero hits. Another area I would like to understand better is where Cato is heading with AI. I know Cato is already developing capabilities around AI security, including visibility and governance of AI usage, so for me, the interesting question is what that ultimately looks like operationally within the wider platform. As organizations move further into the AI era, I would like to see how these capabilities come together within the CMA and how naturally they fit into the day-to-day workflow of someone operating the environment. Review collected by and hosted on G2.com.