After deploying Zscaler Private Access (ZPA), I notice a reduction in VPN-related support tickets, particularly during peak hours, and audits become smoother because access is clearly defined per application. Our incident response team reports improved visibility into user access events, making investigations faster and more accurate. While ZPA greatly improves the management process, the administrative interface could be more intuitive, particularly for troubleshooting scenarios requiring navigation across multiple dashboards and logs during real operational settings, especially in incidents. Simpler visibility into traffic flow and access decisions would significantly speed up root cause analysis. To improve Zscaler Private Access (ZPA), we need more real-world deployment examples and technical documentation, including step-by-step guides for complex scenarios such as multi-cloud legacy app integration. These resources would help engineers implement and troubleshoot faster, especially during initial rollouts and major environmental changes. The training costs associated with Zscaler Private Access (ZPA) are very high, and there are few resources available online. This makes understanding customer and employee needs challenging. There are many dependencies on the internet, and it is not straightforward to comprehend the entire infrastructure architecture and how ZPA operates. I do not give a perfect ten because I notice a lot of dependencies on the TAC, along with complexity in the UI. Sometimes, fully understanding the policy workflow and troubleshooting tools require improvement, especially concerning dashboard usability and diagnostics. There are many restrictions that hinder troubleshooting without a TAC engineer.
Zscaler Private Access (ZPA) can be improved by expanding integrations. While they integrate with standard vendors such as CrowdStrike, deeper integrations with other vendors are needed. They should harmonize risk scores between different vendors, as each might score things differently, requiring a robust handshake for meaningful integration. There is room for having a complete on-premises option. While Zscaler Private Access (ZPA) wants users to utilize their infrastructure for scale benefits, regulated environments such as government and investment banks need on-premises processing for regulations and low latency requirements. High-frequency trading firms require processing traffic internally rather than through internet channels. In the future, I expect expansion of integrations because architects need flexibility in vendor selection based on use cases. The solution needs better handshake capabilities between vendors for risk scores and other metrics. Support-wise, they have a strong presence globally, including challenging markets such as China, though very remote offshore areas remain uncovered.
Senior IT Specialist Network and Security at a marketing services firm with 201-500 employees
Real User
Top 5
Jun 18, 2025
The only room for improvement is the troubleshooting problem with iPhones as of now. The review should be anonymous; there should not be any personal or business details given. Both should be anonymous.
I have not thought about how Zscaler Private Access (ZPA) can be improved, so I do not have any specific suggestions. For the next release, I hope to see features that would make Zscaler Private Access (ZPA) even better, but I am quite satisfied with the product, so I am unsure if there is anything better they can implement.
Learn what your peers think about Zscaler Private Access (ZPA). Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
Technical management of Network Security - Network Hub at a comms service provider with 5,001-10,000 employees
Real User
Top 10
Mar 19, 2025
The rollout process could be much easier, and the configuration of identity providers like Azure is more complicated than with other zero trust network providers. This can be a pain point. Additionally, the software rollout process needs improvement as it requires knowledge of Linux command lines.
Zscaler Private Access enhances security by enabling access to specific applications without exposing entire networks. It is designed for scalability and flexibility, making it particularly suitable for cloud transitions and remote work environments.Zscaler Private Access offers a comprehensive solution for modern security needs by ensuring secure remote application access. This is achieved through its advanced features such as micro-segmentation and AI capabilities. Organizations can...
After deploying Zscaler Private Access (ZPA), I notice a reduction in VPN-related support tickets, particularly during peak hours, and audits become smoother because access is clearly defined per application. Our incident response team reports improved visibility into user access events, making investigations faster and more accurate. While ZPA greatly improves the management process, the administrative interface could be more intuitive, particularly for troubleshooting scenarios requiring navigation across multiple dashboards and logs during real operational settings, especially in incidents. Simpler visibility into traffic flow and access decisions would significantly speed up root cause analysis. To improve Zscaler Private Access (ZPA), we need more real-world deployment examples and technical documentation, including step-by-step guides for complex scenarios such as multi-cloud legacy app integration. These resources would help engineers implement and troubleshoot faster, especially during initial rollouts and major environmental changes. The training costs associated with Zscaler Private Access (ZPA) are very high, and there are few resources available online. This makes understanding customer and employee needs challenging. There are many dependencies on the internet, and it is not straightforward to comprehend the entire infrastructure architecture and how ZPA operates. I do not give a perfect ten because I notice a lot of dependencies on the TAC, along with complexity in the UI. Sometimes, fully understanding the policy workflow and troubleshooting tools require improvement, especially concerning dashboard usability and diagnostics. There are many restrictions that hinder troubleshooting without a TAC engineer.
Zscaler Private Access (ZPA) can be improved by expanding integrations. While they integrate with standard vendors such as CrowdStrike, deeper integrations with other vendors are needed. They should harmonize risk scores between different vendors, as each might score things differently, requiring a robust handshake for meaningful integration. There is room for having a complete on-premises option. While Zscaler Private Access (ZPA) wants users to utilize their infrastructure for scale benefits, regulated environments such as government and investment banks need on-premises processing for regulations and low latency requirements. High-frequency trading firms require processing traffic internally rather than through internet channels. In the future, I expect expansion of integrations because architects need flexibility in vendor selection based on use cases. The solution needs better handshake capabilities between vendors for risk scores and other metrics. Support-wise, they have a strong presence globally, including challenging markets such as China, though very remote offshore areas remain uncovered.
The only room for improvement is the troubleshooting problem with iPhones as of now. The review should be anonymous; there should not be any personal or business details given. Both should be anonymous.
I have not thought about how Zscaler Private Access (ZPA) can be improved, so I do not have any specific suggestions. For the next release, I hope to see features that would make Zscaler Private Access (ZPA) even better, but I am quite satisfied with the product, so I am unsure if there is anything better they can implement.
Sometimes the team takes more time to provide responses on certain issues, which is why I do not rate it a perfect 10 out of 10.
The price is a concern as it increases every year and becomes more expensive, driving customers and other vendors to look for alternatives.
The rollout process could be much easier, and the configuration of identity providers like Azure is more complicated than with other zero trust network providers. This can be a pain point. Additionally, the software rollout process needs improvement as it requires knowledge of Linux command lines.
One area for improvement is setting posture profiles for vendor machines. It's not yet enabled by Zscaler, however, it is in the pipeline.
There are some bugs in the solution, which they are clearly working on, and they are still not resolving them. So it's taking some time.