We performed a comparison between Okta Workforce Identity and Zscaler Zero Trust Exchange based on real PeerSpot user reviews.
Find out what your peers are saying about Zscaler, Palo Alto Networks, Cisco and others in ZTNA as a Service."We face no challenges in integrating the product with our legacy systems."
"It is a very stable solution."
"The product requires very little maintenance."
"A solution that's easy to use, stable, and reliable."
"The feature that is most valuable to me is the automated user provisioning that we set up using Okta as a major part of that process."
"The product’s most valuable feature is multifactor authentication."
"It is dependent on the evolution of your user base. It depends on usage per user, so the more sign-ins there are, the more expensive it becomes, so it works best for smaller companies from a financial perspective."
"This solution has a lot of capabilities and features."
"Sandboxing, DLP, and SSL inspection engine are the most valuable features of Zscaler SASE."
"I like its ease of use. It has a single pane of glass for the ZIA and ZPA pieces. It is very manageable. It is also very easy to deploy for secure access, and it gives half-decent coverage for visibility in terms of what the users use and what data is being proxied through the access gateway."
"The most valuable features of this solution are the CASB solutions, which is protecting their Office 365."
"The most valuable feature is its ability to establish connectivity for remote users and remote endpoints. It offers a high level of granularity compared to typical VPNs, which also encapsulate a lot of I/O."
"SASE's most valuable features are proxy and content filtering."
"What I find most valuable in Zscaler Private Access is that it's a VPN. Its connectivity as a VPN is its most valuable feature."
"The most valuable feature is the manageability of the micro tunnels."
"With SASE, we have a single platform that covers multiple task services with which we need to control access. All the features are equally valuable."
"On the admin side, we can create our own passwords instead of generating one, which is usually difficult to explain to a user."
"A room for improvement in Okta Workforce Identity is its price. It could be cheaper. The biggest benefit of the solution is that everything works securely without extra steps, so you're saving on your workforce's time and effort because your applications work smoothly and securely, but you'd need to pay some amount of money for that. Another area that could be improved, though not necessarily regarding Okta Workforce Identity, is the SSO applications because so many of the source applications charge extra money to put the SSO to work, which means you have to buy a more expensive license. Nowadays, SSO is a mainstream functionality and it should be out-of-the-box in those applications because it's so easy to set up."
"The initial setup can be complex at first."
"SSO and MFA for improved end-user experience, and protection against password spray attacks, account password self-service."
"RESTful Web Service calls and their response seem a bit slow."
"The pricing could be improved."
"Therefore, if you have 10 million users, that's almost 100 million, so it is costly."
"There should be automated aggregation and complete classification processes included in it."
"The pricing for Private Access seems to be on the expensive side, and I believe they should consider making it more competitive with other solutions."
"We faced certain migration and implementation challenges in executing the tasks, so I would suggest improvement related to the stability of the solution."
"There could be more DLP-related features. Additionally, there needs to be flexibility for integrating ISP features."
"It has a limitation, if you are creating a rule or something for a web application or something, you could only add five users, not more than that. Five or four users are only included in a rule. If you want to create a rule for more than five or four users, you have to go through other methods, not particularly with the application. Working within the application with this method would be quite easy as compared to listing a URL or a normal IP address."
"What could be improved in Zscaler Private Access is its notification. For example, if there's a speed issue, there should be a pop-up that alerts the user about it. If there is a network quality issue, for example, it isn't good enough to connect to, or the network quality is bad, there should be a notification from the solution. Zscaler Private Access also needs improvement in terms of its interface and security."
"Zscaler Private Access's reporting is poor. We should have more insight into the reports regarding what is blocked and allowed."
"The area that requires improvement is their support. The current support is lacking."
"The stability could be improved."
Okta Workforce Identity is ranked 7th in ZTNA as a Service with 56 reviews while Zscaler Zero Trust Exchange is ranked 1st in ZTNA as a Service with 34 reviews. Okta Workforce Identity is rated 8.6, while Zscaler Zero Trust Exchange is rated 8.4. The top reviewer of Okta Workforce Identity writes "Extremely easy to work with, simple to set up, and reasonably priced ". On the other hand, the top reviewer of Zscaler Zero Trust Exchange writes "Allows for strict access control, granting access to specific applications at a URL level rather than at the physical IP level". Okta Workforce Identity is most compared with Google Cloud Identity, Microsoft Entra ID, SailPoint IdentityIQ, Saviynt and Auth0, whereas Zscaler Zero Trust Exchange is most compared with Prisma Access by Palo Alto Networks, Cato SASE Cloud Platform, Axis Security, Cisco AnyConnect Secure Mobility Client and Cloudflare Access.
See our list of best ZTNA as a Service vendors.
We monitor all ZTNA as a Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
