Briefly describe your SASE architecture
Cato was architected from the ground up to address all key SASE requirements: convergence of networking and security into a single pass and identity-based engine, cloud-based and cloud-native service, global footprint, and support for all edges.
Cato has the following pillars:
- Global Private Backbone: SLA-backed network of 60+ PoPs, interconnected by multiple tier-1 carriers. It provides routing optimization, traffic acceleration, self-healing capabilities and full encryption to all traffic: WAN, cloud, and Internet.
- Security as a Service: A fully managed stack of enterprise-grade security capabilities converged into the backbone including NGFW, SWG, NG-Anti-Malware, IPS, and a Managed Threat Detection and Response (MDR) service. Scales up to 2gbps on a single connection with full decryption and deep packet security inspection.
- Edge SD-WAN (“Cato Socket”): a WAN edge appliance that connects locations to Cato, and between edge devices, over Internet, MPLS, and 4G/LTE. It provides application-based path selection and packet loss mitigation, driven by quality of service policies and real time link performance.
- Cloud Acceleration: Cato easily integrates multi-cloud DCs into the network via an agentless configuration or a virtual socket. Cloud application access is accelerated by egressing the traffic via the nearest PoP to the application regardless of source.
- Remote Access: Cato SDP/ZTNA connects users on any device to any application. All traffic is optimized and secured in the same way regardless if the user is in the office or at home.
- Unified Management: Cato provides customers with one management console for all policies and analytics. The policy is distributed and enforced across all PoPs and seamlessly extends to all enterprise traffic globally.