Cato makes it quite easy to implement SASE, thanks to a well-thought-out deployment process. For most installations, it takes little more than installing and connecting the Socket SD-WAN device to the internet. Configuration is done via the Cato’s central management console, which offers ample help, as well as recommended settings. The Cato Sockets are "internet aware,” meaning that as soon as the device is plugged into a viable internet connection, the device will automatically download the latest firmware, further easing the initial deployment. Once the socket is associated with a site, it will also automatically pull down the enterprise’s configuration and rule sets. Adding branch offices can be accomplished in a matter of minutes.

Those deploying the Socket SD-WAN Device do need to be aware of their connectivity options, and for most deployments, there are usually multiple connectivity paths used for failover and or load balancing. In many cases, those adopting the Cato SASE Platform are also looking to depreciate and retire MPLS connections or other legacy technologies. That means it is critical that the selected replacement is up and running before making that switch over.

However, Cato does not force deployers to immediately switch over to new connectivity providers. The platform supports hybrid WAN configurations where legacy connections (typically MPLS) run those in parallel with new connections to the internet. This allows network managers to transition away from MPLS circuits at their own pace or retain them for business continuity purposes.

Those supporting mobile or remote users will find adding users to the Cato Cloud simple as well. Remote users can choose to connect using the Cato client application or connect with a browser. Of course, support personnel can simply email the client file and guide remote staffers through the initial setup process or automate it completely if an ITSM/RMM solution is in place.

Hide Comments | Add Comment