Zscaler is a cloud proxy that scans and provides security for traffic to cloud-based applications and resources.
Zscaler is location-independent. Even if you switch to another country, users will have the same security posture. For example, if you are in one country and travel to India tomorrow, you will still have the same security posture as the rest of your team. You will also be able to access all your resources over the Internet as a team, regardless of location. There is no dependency on local firewalls at the site. Everything is in the cloud, so you get security wherever you go.
Zscaler provides several security features, including encryption, URL filtering, application control, and credential theft protection. They are also updating their DLP capabilities.
The reports can be made easier. The solution takes time to fetch reports in the Database section. Otherwise, the reporting module itself is well-designed.
I have been using Zscaler SASE for two and a half years.
Zscaler is very stable. The customers use web services that cause issues over the internet.
Zscaler is highly scalable. Zscaler is a cloud-based service, so it takes care of all the data center and hardware infrastructure. Even if you only have one license, you will still have access to all of Zscaler's security features and performance capabilities. Around 2Lakh users are in Nestle, and all are using Zscaler.
We work with enterprise-level customers.
The customer support is good.
I have experience with Prisma Access. In terms of scalability and tech support, Zscaler is better. However, Prisma is better in other parameters because they have more experience in the firewall industry and are the leader in firewall technology. We at Nestle are forwarding most of our traffic to Zscaler for scalability. We are using Prisma for some essential functions.
The initial setup is easy. You have to plan very carefully how you are going to use Zscaler. Planning is critical, but implementation is achievable. You need to purchase cloud or host services and synchronize your user database to the rescheduler. Then, you just need to use the application to create a folder application on the system, and you are good to go.
Zscaler deployment time depends on the number of users and the policies to be deployed. A very simple setup can take around two to three weeks, while a very complex setup with multiple components can take months to implement.
We are the service providers of Nestle, which is a user of Zscaler.
New functionality is always being added to Zscaler's products, but there are some features that we cannot have in the cloud-based platform. For example, Pulse QoS and VPN are still available as standalone products. However, Zscaler offers a variety of products that can meet these needs, such as ZIA, ZPA, and ZDA.
Maintaining Zscaler is easy. It has a well-designed admin portal and policy control. At least 20-30 people are required to manage the Zscaler product with a worldwide presence, depending on the setup. For example, Nestle requires 1-2 people to manage their Zscaler deployment.
I recommend the Zscaler solution. If I get an opportunity to use it in an environment where the users are mostly roaming users and the entire network stack is in the cloud, I will recommend they use Zscaler products. It's a great product.
Overall, I rate the solution a ten out of ten.