Zscaler Private Access (ZPA) Reviews

My primary use case for Zscaler Private Access (ZPA) is VPN replacement and zero trust access. I use Zscaler Private Access (ZPA) to give authorized users policy-based one-to-one connectivity to specific internal applications in our data center or cloud environments. I also use Zscaler Private Access (ZPA) to secure our hybrid cloud environment. For instance, when a developer needs to access a private staging server used in AWS, they connect directly through the closest Zscaler service edge. This makes the application invisible to the private internet, ensuring only the specialist can reach it.

Zscaler Private Access (ZPA) has significantly reduced our attack surface by making our internal apps invisible to the internet. It effectively eliminates lateral movement as users are only connected to the specific application they are authorized to use rather than the entire network segment.

Zscaler Private Access (ZPA) is highly stable. The architecture uses a global mesh of service edges with built-in fault tolerance and redundancy, providing an always-on experience that is far more reliable than our old hardware-based VPN concentrator.

Zscaler Private Access (ZPA) is elastically scalable because it is a software-defined perimeter and not an appliance-based solution. I can instantly scale to support thousands of additional users without needing to upgrade any physical hardware.

The best features are the AI-powered app segmentation that automatically discovers our applications. This saves a massive amount of manual configuration time and helps me build granular access policies much faster.

The app segmentation feature helps my team improve employee experience while giving our IT team peace of mind. It is truly a productivity tool that removes the clunkiness of a VPN. The initial discovery of legacy applications during setup can sometimes take more time to fine-tune, which is the only minor limitation.

Zscaler Private Access (ZPA) could be improved by making troubleshooting for specific mobile devices such as iPhones more intuitive, as identifying the root cause for mobile connectivity issues can sometimes be complex. The major improvement opportunity I would highlight is the troubleshooting functionality for mobile devices.

I have been using Zscaler Private Access (ZPA) for about three years to provide our distributed workforce with secure, seamless access to our internal applications.

Zscaler Private Access (ZPA) is highly stable. The architecture uses a global mesh of service edges with built-in fault tolerance and redundancy, providing an always-on experience that is far more reliable than our old hardware-based VPN concentrator.

Zscaler Private Access (ZPA) is elastically scalable because it is a software-defined perimeter and not an appliance-based solution. I can instantly scale to support thousands of additional users without needing to upgrade any physical hardware.

The customer support team is very knowledgeable about the ZTNA architecture and Zscaler Trust Portal provides excellent transparency into the health of the global cloud infrastructure.

I previously used a traditional legacy VPN. I switched because the VPN was too slow and hard to manage at scale, and it created a major security risk by putting users directly on the network.

Zscaler Private Access (ZPA) is an incredible enabler for modern hybrid work. The initial discovery of legacy applications during setup can sometimes take more time to fine-tune.

I have seen a significant return on investment since implementing Zscaler Private Access (ZPA). The ROI is often cited around 289% over the three years of typical enterprises. The key metrics include a 55% reduction in security breach risk and roughly 1.75 million in annual savings on infrastructure and legacy VPN licensing costs.

Zscaler Private Access (ZPA) is priced on a per-user, per-year basis. While it is a premium investment, the short payback period of about 11 months and consolidation of multiple point products make it very cost-effective in the long run.

I evaluated Cisco AnyConnect, Palo Alto, and Twingate. I finally chose Zscaler Private Access (ZPA) because it is the most deployed solution and offers the most mature AI-powered application segmentation.

Zscaler Private Access (ZPA) is a cloud-native service hosted on Zscaler's global cloud platform, which has over 150 points of presence. I use lightweight app connectors hosted in our own private data centers and public cloud like AWS or Azure to create secure inside-out connections to our applications. I use majorly the AWS one.

I purchased Zscaler Private Access (ZPA) through the AWS Marketplace, which allows me to simplify procurement, consolidate billing, and apply my Zscaler spend towards existing cloud commitments.

I would advise those looking into Zscaler Private Access (ZPA) to use the AI-powered app segmentation to automatically discover your applications. This feature saves a massive amount of manual configuration time and helps build granular access policies much faster.

My company relies on Zscaler Private Access (ZPA)'s cloud-native architecture to protect our private applications and sensitive data.

I give Zscaler Private Access (ZPA) a rating of 9 out of 10.

My primary use case for Zscaler Private Access (ZPA) is securing application-level access to internal applications without exposing the network to the public network. Previously, VPN gave users broad network access, which increased the risk capacity. With ZPA, we follow the Zero Trust principle, allowing users access only to the specific applications they are authorized for, and this dramatically improves security and compliance.

A strong example of how I use Zscaler Private Access (ZPA) for securing application-level access occurred during a company-wide shift to remote work, as VPN concentrators were overloaded, causing slow connections and outages. After moving critical apps to ZPA, users connected directly through the Zscaler cloud, and consistent performance significantly helped desk VPN ticket drops. Our remote employees can access applications more smoothly, even from different geographies and networks, especially considering the multiple issues faced during COVID-19. This example correlates all those issues where no one could access all those applications and the exposure over the internet was critical. At the time, there were many gaps, and through ZPA, it is easy to configure and provides easy access to all those internal applications with least privilege access.

Zscaler Private Access (ZPA) offers many features, including Zero Trust Network Access, which adheres to the principle of "never trust, always verify." Additionally, it provides application-level access, allowing specification of applications that significantly reduce the risk of lateral movement and eliminate network exposure. There is also the option to create identity-based policies, and since it is a cloud-native architecture, there is no dependency on on-premise or hybrid solutions. In terms of scalability, ZPA supports multi-cloud and hybrid environments while providing a seamless user experience as users connect transparently without the need to launch or manage VPN tunnels, which is a great feature.

Instead of creating VPN accounts with broad permissions, we now grant vendors access to only one application via Zscaler Private Access (ZPA). This approach makes audits easier, improves security, and gives management confidence that external access is tightly controlled and logged without additional network complexity. This is also the best solution for our audit needs since there is no firewall needed; we use remote access solutions that require and provide least privilege access to users, which helps with risk, compliance, governance, and adheres to the Zero Trust principle.

Zscaler Private Access (ZPA) positively impacts my organization through application segmentation and access policy management. On a daily basis, I review access policies, onboard new applications, and validate users based on identity and posture solutions. This method is far safer than traditional subnet-based access, aligning with the Zero Trust architecture principle.

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.

I have been working with Zscaler Private Access (ZPA) for around two years, having initially deployed it during a phase when remote work demand rapidly increased. Over time, ZPA became a core part of our access strategy, replacing a large part of the VPN community footprint and supporting both permanent employee and external partners' access solutions to internal applications securely.

Zscaler Private Access (ZPA) is very stable in production, with extremely rare outages and minimal user complaints. Even during peak usage or mass remote access events, performance remains consistent, which is critical for an enterprise environment handling business-critical applications.

Scalability is one of Zscaler Private Access (ZPA)'s strongest points, allowing us to onboard hundreds of users quickly without altering infrastructure since it is cloud-based. Scaling users or applications does not require any additional hardware or complex restructuring, presenting a significant operational advantage based on subscription counts.

The customer support for Zscaler Private Access (ZPA) is good, responding quickly to tickets and engaging via Zoom sessions.

Positive

Previously, we used traditional VPN solutions such as IPsec and SSL VPN, which provided network-level access and posed significant security risks. We switched to ZPA to embrace the Zero Trust approach, reduce the attack surface, and enhance the remote user experience without creating traffic bottlenecks through a centralized VPN gateway.

The biggest impact on my team from Zscaler Private Access (ZPA) is the overhead reduction in timing and monitoring all applications through one GUI base. It is easy to integrate, with no complex configurations required, unlike traditional VPNs, which depend on firewalls and a host of policies. In the current SaaS environment, ZPA offers a good comparison and overview, paired with excellent security and monitoring tools.

The cost associated with Zscaler Private Access (ZPA) depends entirely on the number of users and licenses purchased, and while I have not put an extensive focus on return on investment metrics, it is a good cost model.

Regarding pricing, setup costs, and licensing for Zscaler Private Access (ZPA), while it is not the cheapest solution, when you factor in the reduced VPN infrastructure, hardware maintenance, and operational overhead, the cost becomes easier to justify. The simplicity of licensing also aids in scaling the users, allowing it to be viewed more favorably as a viable solution.

We evaluated other options from Palo Alto and Fortinet, but Zscaler Private Access (ZPA) stood out due to its cloud-native design, global scalability, and true application-level access model, which aligns better with our long-term Zero Trust strategy.

My advice to others considering Zscaler Private Access (ZPA) is to invest time in application segmentation and identity integrations. ZPA yields the best results when applications are well-classified, and access policies are clearly defined. Additionally, training your operational team early will help them fully leverage the troubleshooting and monitoring capabilities available. The company also provides premium solutions on the TAC side, capable of responding within two to five minutes based on ticket severity levels.

Zscaler Private Access (ZPA) is a mature, enterprise-grade Zero Trust solution that delivers security and operational benefits. It is a great solution and ranks highly in Gartner reports. Recently, I have noticed some shifts in its standing on these reports and some downsides, possibly due to cost issues, so it is vital to ensure all aspects align with licensing costs. I gave this solution a rating of nine out of ten.

Positive

Zscaler Private Access (ZPA) is a Zero Trust Network Access solution. When replacing traditional remote access VPN technology, which is not aligned with NIST 800-207 Zero Trust principles, Zscaler Private Access (ZPA) is the solution. It serves enterprises that prefer not to manage the underlay by installing a client connector agent on end-user machines. It provides access to private applications and SaaS applications remotely when users are traveling while building secure connectivity and ensuring least privilege access to these applications rather than everything within the perimeter.

The base bundle of Zscaler Private Access (ZPA) comes with essential features that depend on client requirements. For secure private access, configuration of client connectors and app connectors on-premises or in the cloud is necessary. Additional features include remote browser isolation capability and secure browser access, which can replace existing Privileged Access Management solutions. DLP capabilities and double encryption ensure the underlying provider cannot strip packets and examine contents.

I would assess the security level achieved with Zscaler Private Access (ZPA)'s Zero Trust architecture as inherent to the system. The security policies focus on users and applications rather than network-based constructs. It offers configuration levers for ingesting risk from identity and application standpoints, generating a cumulative score that can trigger connection drops when breaching thresholds. These features align with NIST 800-207 principles. The Risk360 view helps assess security policies and rule sets, providing recommendations for policy tightening.

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.

I have worked with Akamai since 2019, when I first gained exposure to it.

I have worked with Zscaler Private Access (ZPA) and Palo Alto as an enterprise security architect across multiple client engagements as part of network security implementations. I have also worked with competitors including Cloudflare. As we were partners, we received preferential access to support. I rate this solution 9 out of 10.

Our use case for Zscaler Private Access (ZPA) is that it provides Private Access.

Zscaler Private Access (ZPA) means allowing users access to the internal network in AWS in a secure way.

I use Zscaler Private Access (ZPA) to secure remote access to internal applications.

The most valuable feature of Zscaler Private Access (ZPA) is the ability to manage access with policies, all in one, which provides our security team the ability to provide the required permission for each team, and also visibility. If something goes wrong, I have a very friendly UI to see what's going wrong, why the user is blocked, or what the issue might be.

Zscaler has allowed an easy, secure way for us to access our internal resources from outside.

Its effectiveness for my organization is mainly security, as users can access those applications only if they have the permission to go through Zscaler.

Zscaler has helped with operational flexibility because when a new employee starts, it's very easy to give them the required permissions. Everything is managed in an Active Directory or Okta in our case, and it's very easy to have the user ready to start working with just a few clicks.

Zscaler Private Access (ZPA) is a very good product, though there are some areas for improvement.

The solution is not scalable; we deploy it in a high-availability environment, but it's not automated. We need to deploy it and ensure it will be available in two different Availability Zones, but it's not something that can be done with automation, such as auto-scaling.

I would appreciate seeing dynamic scaling implemented because it would be beneficial if an instance goes down to automatically start another one.

I have used Zscaler Private Access (ZPA) for a minimum of two to three years.

When we tried to deploy it, the first thing it indicated was that we were not subscribed, so we subscribed, and then the product was available for us.

The solution is not scalable; we deploy it in a high-availability environment, but it's not automated. We need to deploy it and ensure it will be available in two different Availability Zones, but it's not something that can be done with automation, such as auto-scaling.

Regarding auto-scaling or dynamically scaling, I am not familiar with this capability if it exists as a new feature.

I have not worked with customer support, as our IT department takes care of anything that isn't working and requires support.

Positive

The deployment process is actually very easy; we manage it with Terraform, so we are deploying the instance, activating it, and it's ready to go.

After we have the Terraform set up, it takes just minutes to deploy.

I do not use the micro-segmentation feature.

I'm not exposed to the pricing, so I cannot give feedback on that as I'm just a technical DevOps person deploying it.

Zscaler has helped to manage complexity and cost compared to traditional network architecture.

On a scale of 1-10, I rate Zscaler Private Access (ZPA) a 9.

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.

Positive

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.

We are using secure remote access for internal applications, and that's why we are using Zscaler Private Access (ZPA) now. I work with Zscaler Private Access (ZPA). I use it just for the VPN functionality.

The best advantage of the product is that it is always on as a VPN, which gives us much more functionality. It is basically easy to use and easy to configure. The solution for Zscaler Private Access (ZPA) is seamless for this.

From a visibility perspective, they have added more content features where we can see security and other aspects through available dashboards. That's the only notable addition, plus they are implementing the overall security architecture of tenants, which gives much more information to work with.

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 been using it for around four or five years.

The installation and deployments are straightforward; it is just a two-liner process. There is something in the documentation that might need changes, but it's pretty straightforward.

The documentation has to be perfect as it has not been updated for a long time. They need to update it based on the latest version and the commands we use.

The solution is stable enough.

We are using cloud services, but I am not sure about the scalability specifically.

Based on the limited users, this is perfectly fine since we are using only one box, and we haven't faced many issues with that.

I am not happy with the technical support from Zscaler Private Access (ZPA), particularly in India, where reachability is an issue with salespersons. Sometimes we need to reach a salesperson to get issues resolved, especially for mobile problems we're still facing. We lack specific root causes, and it's tough to relay information to users, considering multiple contributors such as phone numbers and internet service providers. We need more visibility on what problems users are facing with reachability.

I would rate technical support six points out of ten.

Neutral

I have not used any other VPNs apart from Zscaler Private Access (ZPA).

I see some ROI in the product. Since we have a very small team, the ROI is around 20% to 30%. I would say 30%.

I am not using AWS Backup anymore since we spoke almost two years ago. I have a backup solution managed by another team, and there's a discussion about AWS for backup. I am responsible for the IT security part only.

I do not work with popular vendors such as Palo Alto or Fortinet, as my primary domain is Check Point, and it's all about security. I use Check Point for this purpose. I do not work with the product ZoneAlarm. We use only a specific firewall from Check Point and utilize only the firewall. We are not using Check Point CloudGuard Web Application Firewall; we are using a normal firewall, the Firewall as a gateway. The name of the product is Check Point Firewall Gateway.

I am not using a web gateway. We do not use products such as Harmony or Harmony Browse. I am using a VPN from Cisco for endpoint protection. I am not using the cloud firewall from Zscaler Private Access (ZPA). I am not working with Zscaler B2B or ZTNA as a service.

From a troubleshooting perspective, we face an issue with iPhones affecting about 10% of users. Even when we provide logs, they are not able to figure out what exactly is happening. It's not possible for users to collect logs each time, and this is a peculiar problem happening with 10 to 15 users.

The operational flexibility is very effective; there are no problems, and I did not have any issues with that. The solution is affordable, but there are other parts that could add much more information, which may not be useful for us at the moment, making it a bit expensive. There is also a China-specific solution, which is really expensive.

I agree to share my details with the Zscaler vendor. I do not want to be a reference for Zscaler Private Access (ZPA).

On a scale of 1-10, I rate this solution a 9.

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.

The main use case is to access the local network or the customer network, the servers, and applications. This is the primary use case for Zscaler Private Access (ZPA) as we use it. Additionally, we use it to access cloud resources such as Microsoft Azure, as it's the easiest and most secure way to access these servers.

Zscaler Private Access (ZPA) is much more secure than VPN because users are only allowed to access specific applications rather than the whole network. The seamless operation ensures users don't experience any issues or the need to sign in separately. It's very comfortable to use, especially with remote work, as there is no difference whether users are in the office or working from home.

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.

We have been working with ZPA for about four to five years.

Zscaler Private Access (ZPA) is highly stable, and I rate it ten out of ten.

I rate the scalability of ZPA as ten out of ten because it's a cloud service and can scale as needed.

The technical support for ZPA is excellent, rated ten out of ten. We have a perfect support system, and they are always helpful.

Positive

We started using ZPA because it was the leading solution on the market, although we reviewed other options.

The initial setup is rated as three out of ten because it involves Linux and command lines, making it relatively difficult.

One person is usually enough for deployment, depending on the time slot available. We conduct onboarding workshops to define use cases and server access needs.

The pricing of ZPA is rated five out of ten, which I consider to be in the middle. I believe it is justified for the capabilities provided.

We reviewed other solutions, but Zscaler offered much more features and configuration options tailored to customer needs.

ZPA is rated eight out of ten due to deployment complexity, but it's a very good solution overall.

I worked with these organizations for implementing Secure Service Edge and SASE solutions, including Cloud Access Security Brokers, such as Netskope and Zscaler.

Zscaler and Netskope are the main solutions I work with for various use cases.

Based on my experience, I have worked at the enterprise level only, for large companies such as banks and financial institutions that are transitioning from traditional solutions to new secure service edge solutions.

Zscaler has three components. Specifically, Zscaler Internet Access for secure web access, Zscaler Private Access (ZPA) that is a replacement of traditional VPN solution for securely accessing internal private applications without giving access to the whole network. It works by giving access to the particular application the user wants to access, and it checks numerous factors before granting access to the particular application, including posture checks, authentication, and authorization. Zscaler Digital Experience is a monitoring tool that monitors all application performance, network performance, and more. It helps us troubleshoot issues in a very short time.

When discussing Zscaler Private Access (ZPA) mainly, it is very helpful as a replacement for traditional VPN. In traditional VPN, we used to give access to the whole network, which increased attack vectors. Zscaler Private Access (ZPA) is more secure than these particular VPN solutions. We have implemented this solution for enhanced security. As a cybersecurity professional, I approach these answers from a security perspective.

Micro-segmentation, authentication, and authorization are key features in Zscaler Private Access (ZPA). We can implement role-based access and limit user access by creating different groups. For example, if the HR department needs access to only HR applications, we can create specific groups with appropriate access levels. This segregates access and makes it more secure. They also provide features such as browser isolation, which creates a separate browser when users are accessing content, thus creating an isolated environment to prevent attacks.

They provide integrations with various other security tools. The solution utilizes AI capabilities for various detections and responses. The solution has inbuilt AI for all detection capabilities.

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.

Overall, with Zscaler, I have worked for around five years, and particularly with Zscaler Private Access (ZPA), I have three years of experience.

The deployment took approximately six months.

Sometimes connection errors occur when users are unable to connect to the particular cloud.

These connection errors started occurring post rollout, not just during the implementation.

For small and medium enterprises, it will be too expensive.

I have worked with the Zscaler technical team.

I would rate them around eight as they were pretty good.

Positive

The traditional solutions were still in use when we migrated to the current solutions. The migration process required extensive documentation and multiple testing phases.

Prices for Zscaler Private Access (ZPA) are higher than traditional solutions, but it provides enhanced security.

Product-wise, I would give Zscaler Private Access (ZPA) a seven. The overall rating for the solution is eight out of ten.