Zscaler Private Access (ZPA) Reviews

The main use cases for Zscaler Private Access (ZPA) include allowing network access. We use it mostly for private laptops and Macs, and we are also using it for communication between EC2s.

I can provide examples of how it has been effective in the organization. We use Zscaler Private Access (ZPA) to control the communication, mostly for the bands and working groups within the organization itself, so we can have complete control of who can access which resources on Amazon.

The features I appreciate the most about Zscaler Private Access (ZPA) are that it is very easy to use, and we have Terraform for it, which makes it even easier and very straightforward.

I have utilized the segment feature, and we call it segmentation, though I am not certain if there is a difference between micro-segmentation and segmentation itself.

It has helped my organization in terms of minimizing lateral movement within the network, and I can confirm that.

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.

I have used Zscaler Private Access (ZPA) for two years now, as I have been with the company for two years.

I have not used Zscaler Private Access (ZPA)'s cloud-native architecture for scaling.

I have not had to use their customer service or technical support.

Perhaps our IT department did, but I have not had any issues since then.

In terms of the setup, I am using Terraform for it, so it is very straightforward. We are using Infrastructure as Code, so I am not certain if there is an interface that can be improved.

I was not involved in the setup as it was implemented before I joined the company.

I have found Zscaler Private Access (ZPA) to be very effective at providing operational flexibility during my organization's transition to cloud environments.

I do not remember the name of any other solutions that were considered before implementing Zscaler Private Access (ZPA), but there were several POCs conducted before the company decided on Zscaler Private Access (ZPA).

It is pretty straightforward and easy to use. On a scale of one to ten, I would rate Zscaler Private Access (ZPA) a ten.

On-premises

For our main use cases for Zscaler Private Access (ZPA), it’s providing us a VPN solution for our clients, connecting to data build resources, and providing them security.

It's challenging to explain which features of Zscaler Private Access (ZPA) are most valuable because the main client is the IT department in our company, and we, as DevOps, are deploying this solution as infrastructure for them. From our case, and as I'm familiar with this tool, the most value is the VPN connection because it provides access for all company members to data builds in a secure way.

Zscaler Private Access (ZPA) does an excellent job offering secure remote access to internal applications for our distributed workforce because it provides a granular way to grant access for specific people with specific applications.

Zscaler Private Access (ZPA) has been very effective in providing operational flexibility during our company's transition to cloud environments, as it helped us significantly, and it was deployed even before we migrated to the cloud itself.

Concerning improvements for Zscaler Private Access (ZPA), we have occasional issues, but I don't think they are related to the product itself; they may be related more to infrastructure problems or something else related to the network because it's a network application.

The current pain points we sometimes experience relate to the additional security applications we have on the laptops, and sometimes I don't know if I didn't get any notification from the application because it's an agent problem or something security-wise blocking this.

I have been using Zscaler Private Access (ZPA) for more than three years.

I would describe my experience deploying Zscaler Private Access (ZPA) as very straightforward, but I think it could allow more automatic ways to deploy and configure instead of having to connect to each new instance manually and configure it.

We didn’t have any issues with Zscaler Private Access (ZPA)’s stability, availability, or reliability.

I don’t know how Zscaler Private Access (ZPA)’s cloud-native architecture is used for scaling within my company, but we do use something deployed in the cloud, and from my perspective, we only deploy the agent, exactly what we took from the marketplace.

As for support from Zscaler Private Access (ZPA), I might have used it, but it’s primarily handled by the IT team.

I know we had something before Zscaler Private Access (ZPA) to address similar needs, but I don’t remember the application name. The decision to move to Zscaler Private Access (ZPA) was possibly because it’s more native in the cloud environment and provides us an easier way to get or configure this.

In regard to other solutions I considered before implementing Zscaler Private Access (ZPA), I don’t know because the decision on what to use and what to install came from management.

Regarding the micro-segmentation feature of Zscaler Private Access (ZPA), I can explain less, and I think the IT team who are managing it can explain better.

I don't know how Zscaler Private Access (ZPA) has helped minimize lateral movement within our network because I don't know how to measure this reduction.

Since implementing Zscaler Private Access (ZPA), I've not noticed any changes in the visibility or monitoring of user access patterns because it's not part of our responsibility. We deploy it, and the IT team is configuring and monitoring it, fixing issues if it's working or not.

I'm not familiar with all benefits from using Zscaler Private Access (ZPA) that I haven't discussed, as I am only familiar with the VPN-related functionality and the segmentation which provides granular security access for the clients.

I rate Zscaler Private Access (ZPA) eight out of ten.

Public Cloud

Other

I am helping a customer to evaluate Palo Alto IoT Security and Cloudflare solutions. Additionally, I am a partner with Zscaler and work with Zscaler Private Access (ZPA) for secure access to private networks and VPN replacement.

Zscaler Private Access (ZPA) is the most mature compared to other vendors in terms of features and stability. It has been in the market for a while, resulting in more features compared to other vendors. It effectively provides security and zero trust network access.

The price is a concern as it increases every year and becomes more expensive, driving customers and other vendors to look for alternatives.

I have been dealing with Zscaler Private Access (ZPA) for more than five years.

The initial setup is easy, but the production implementation can be complex.

Zscaler Private Access (ZPA) is stable and one of its advantages.

Scalability is good with Zscaler Private Access (ZPA).

The level of support used to be good but is now decreasing. It is not improving. I would rate support around four out of ten points.

Neutral

The initial setup is easy.

Pricing is a concern as it increases every year, making the solution more expensive for customers.

The comparison involves Palo Alto IoT Security, Cloudflare, and Zscaler Private Access (ZPA). Network security solutions like zero trust options such as Zscaler and Cloudflare are considered.

In terms of product, I rate Zscaler Private Access (ZPA) eight to nine out of ten.

Hybrid Cloud

Other

We do not manage the vendor machines. We provide them with a passwordless solution. Multiple tenants are enabled on the vendor's machines from their organizations. Accordingly, they connect to both Zscaler and their own environment. We provide limited access to servers and use privileged remote access or browser access when needed.

Zscaler Private Access helps by resolving network choke issues, allowing application access from public networks without needing to integrate with internal networks. We provide browser and privileged remote access for vendors without managing their machines. The deployment of app connectors through MLA eliminates duplicate rules and policies.

One area for improvement is setting posture profiles for vendor machines. It's not yet enabled by Zscaler, however, it is in the pipeline.

I have been working with Zscaler Private Access for more than six or seven years.

Due to posture setting issues, I rate the stability as eight out of ten.

Scalability is ten out of ten as it's effective and expansive.

Customer service and support are rated seven or eight out of ten, needing improvement in quality and response time.

Positive

The setup process is simple if approached appropriately. It involves understanding use cases, reviewing customer feedback, and planning project execution geolocation-wise.

Although the solution is costly, its features justify the price for securing the organization from various access types. Competitors with lower pricing exist.

Netskope is a competitor product to Zscaler.

Overall, I rate Zscaler Private Access as nine out of ten. 

The solution is more suitable for enterprise-level companies because of its cost.

Hybrid Cloud

Other

Most of the users are using this because of the migrations from the traditional VPN to this next generation of GP services.

It provides national security and a great user experience. It's very beneficial.

It provides security and has a great service user experience. The scalability is amazing. Whenever we need to upgrade the users, it increases immediately.

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.

We have been using it for the last two years.

The stability is good. It's average, you can say. There are some bugs which need to be resolved.

The solution is highly scalable.

The customer service is really good. It's about nine out of ten, you could say.

Positive

The initial setup is very easy.

The cost has increased now. Before, it was less expensive. Now it's higher. I would rate it a seven out of ten. It is expensive.

Since it is an estimation solution, we have to use it. 

I'd rate the solution eight out of ten.