Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 216.73.216.191
Lock expires at: 2026/03/17 04:52 (1 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

Allows the same kind of segmentation we can get in an EC2 instance (security groups, ACL and so on) but in end user stations.
Zscaler has their own cloud. they offer there: authentication, firewall (inspection) and metrics

=== Agents ===
  * Requires Zscaler agent running on the computers ''client connector''
  * ''app connectors'' (for applications) [[https://help.zscaler.com/zpa/about-connectors|External_Link]]

=== Cloud ===
    * Zscaler Internet Access (ZIA) service. [[https://youtu.be/TVBbnxpo7V0?|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.
      * [[https://help.zscaler.com/zia/ranges-limitations|Limitations]]:
        * (1G/250Mb per GRE tunnel (outbound)). If more throughput, we need more tunnels (and more public IPs). [[https://help.zscaler.com/zia/understanding-generic-routing-encapsulation-gre|Link]]
        * 
    * Zscaler Private Access (ZPA) enabled. To access your organization's internal resources from any location. [[https://youtu.be/kvbKr7MVBlk|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?

dokucama

User Tools

Site Tools

Page locked

Page Tools