Bittersweet Zscaler
December 04, 2019

Bittersweet Zscaler

Samuel Hadid | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Zscaler Web Security

Zscaler is being used as a transparent proxy to prevent users from exhausting the bandwidth resources. There are some implementations customized for mobile networks and wired networks, where we have certain needs for a variety of devices and require coverage of others. Not implemented for networks where behavior/anomaly-based analysis is required.
  • Reverse Proxy
  • Forward Proxy
  • Protection
  • Poor mgmt. capabilities
  • Not so flexible
  • Hard to segment
  • Hard to implement as fault tolerant
  • Outages
  • Too much effort time
  • Not flexible
The Zscaler solution was selected in order to fulfill the needs of the variety of networks that we manage since the device requirements are so varied. Also, it was required to be as transparent and non-intrusive as possible to improve efficiency. Also, the basic implementation was simple and fast enough.
While overall support was always nice and polite, most of the time it was hard to reach them and it took awhile for them to respond back in urgent cases. It was probably an isolated case but, still, it's hard to manage a tool without proper support from the vendor when in need.

Do you think Zscaler Internet Access delivers good value for the price?

Not sure

Are you happy with Zscaler Internet Access's feature set?

Yes

Did Zscaler Internet Access live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Zscaler Internet Access go as expected?

Yes

Would you buy Zscaler Internet Access again?

No

Citrix Virtual Apps and Desktops (formerly XenDesktop), Metasploit, Nmap
I think the Zscaler platform is pretty well suited for short-scale networks/architectures since is hard to segment and a single error could bring down operations in your company - we've had a couple of those. At some point, the lack of flexibility has forced the implementation to take a whitelisting approach rather than a blacklisting/behavior/anomaly approach.