network_stuff:zscaler
This is an old revision of the document!
Allows the same kind of segmentation we can get in an EC2 instance (security groups, acl and so on) but in end user stations
Agents
- Requires zscaler agent running on the computers
client connector app connectors(for applications) External_Link
Cloud
- zscaler has their own cloud. they offer there: authentication, firewall (inspection) and metrics
- Zscaler Internet Access (ZIA) service. External Link
- ZIA uses GRE tunnel/s to the zscaler location to 'bundle' all users inside the same tunnel. That optimizes the routing to the zscaler cloud.
- That tunnel is limited to 1G and to 1k users. More users require more locations with more tunnels.
-
- (1G/250Mb per GRE tunnel (outbound)). If more throughput, we need more tunnels (and more public IPs). Link
-
- Zscaler Private Access (ZPA) enabled. To access your organization's internal resources from any location. External Link
Topics
PAC files
https://help.zscaler.com/zia/understanding-pac-file
Example of use: “create a wildcard that redirects all traffic of *.data.cloud.mycompany.mygroup.com (an example) towards the internal DNS from the perspective of PAC file?
network_stuff/zscaler.1725215018.txt.gz · Last modified: by jotasandoku
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
