Google Cloud Virtual Private Cloud has a network of 27 regions and 200+ countries and territories, boasting little to no downtime for its users. It is automatically configured or can be done by the user and allows you to bring your own IP addresses to reduce downtime caused by migration.
$0
based on services that process ingress traffic: Load Balancers, Cloud NAT, Protocol forwarding.
Zscaler Private Access
Score 7.9 out of 10
N/A
Zscaler Private Access™ (ZPA) gives users secure access to private apps and OT devices while enabling zero trust connectivity for workloads.
N/A
Pricing
Google Cloud Virtual Private Cloud (VPC)
Zscaler Private Access
Editions & Modules
egress traffic
$0 - 0.15
per GB
ingress traffic
$0
based on services that process ingress traffic: Load Balancers, Cloud NAT, Protocol forwarding.
Premium Tier (egress rates)
$0- $0.23
per month per GB of data delivered
Standard Tier (egress rates)
$0.045, $0.065, $0.085
per month per GB of data delivered: 150-500TB, 10-150TB, 0-10TB
Well-suited scenarios: 1. Large Organisations with more than at least a thousand employees. 2. Teams spanning across multiple countries or regions. 3. Research institutes require privacy and confidentiality. 4. Educational institutes to separate departments from various attacks. Less appropriate scenarios: 1. Startups have less than 100 employees. 2. Users are accessing resources from the same place.
The tool is, for the most part, very intuitive. Most of our issues so far (working through them with our Resident Engineer) are the one-off applications. We are working on some exemptions to make them functional. Besides that, the team loves the tool and how it can provide better security than our previous tool.
Application Segmentation and Listener Configuration - The way applications are defined and listened for is fundamental to ZPA, but can be a source of frustration, especially when dealing with legacy or non-HTTP protocols
The ZCC is the user's primary gateway, but its control over local system network behavior can sometimes clash with enterprise requirements.
VPC is a difficult concept to grasp and recommendations for configuring it would be helpful in educating the users to make the right choice while using the product in configuring networking for their cloud deployments. Also, the user interface can be intuitively designed so as to suggest templates to perform common configurations with regard to VPC.
Few things stand out. The ease of access: It very convenient - one click to open add details and done. Packet capture: Can't talk enough about this feature. Troubleshooting private access is always problematic,but this feature helped a lot. One thing that can be improved is early warning about expiring authentication
On Cloud storage, Google Cloud VPC has an edge over the rest of the service providers. Also, Google Cloud VPC is the ideal choice for AI/ML and data analytics because of Google's reputation in these fields. Google Cloud VPC, on the other hand, provides a secure private network, despite the fact that there is no trace of the public network on it. Google Cloud VPC services are also less expensive than those offered by other cloud service providers.
All of these tools are for different needs. Zscaler Private Access being for internal seems very simple as it really only allows filtering up to L4 whereas ZIA allows for filtering up to L7. ZDX often tries to give insight into the environment but since it only works with preconfigured items, that then means when a new problem shows up - ZDX isn't helpful troubleshooting postmortem. For the internal side of the house - Zscaler Private Access' strength is its simplicity to configure.
Positive: We have now charged users internally for the service
Negative: Dealing with users who also have the Zscaler Client Connector for their company, can cause confusions
Negative: Enabling the Zscaler Internet Access entitlement has been a major headache for us because Zscaler Private Access users can't autheniticate through ZIA on a non corporate device.
