Zscaler Private Access (ZPA)

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.

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.

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.

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.