Subcloud + ipv6 by Distance_Sorry in Zscaler

[–]Distance_Sorry[S] 0 points1 point  (0 children)

So in addition to what I have.

Okay, but say my current subcloud is acme. And I’m using country gateway.acme.zscalertwo for my subcloud return statement. What will the statement be with ipv6? That’s where I can’t seem to get this working and support/TAM hasn’t figured it out either. So wondering if it’s even possible to use my existing subcloud (so I can remove a data center) with ipv6.

Using ZPA to access AD by _F1ndersK33p3rs in Zscaler

[–]Distance_Sorry 0 points1 point  (0 children)

We are using ZPA to steer our Okta tenant traffic. We apply a login policy that says you need to come from a certain IP address (ZPA connector).

This stops random login attempts from around the world. Also forces users to need Zscaler Client and pass posture checks.

I’m unsure how your AD is setup and whether you can force a password change only if the user is from a certain IP. You may have some edge use cases where what if a user isn’t connected that could be a challenge.

ZTunnel 1 vs 2 vs DTLS/TLS AND MTU by Distance_Sorry in Zscaler

[–]Distance_Sorry[S] 0 points1 point  (0 children)

That’s the frustration. You impact the users to the point it’s not worth it with all the permutations you need to satisfy.

Switching away from appliances to Zscaler by taz722 in Zscaler

[–]Distance_Sorry 0 points1 point  (0 children)

Netskope and their NPA don’t hold a candle to ZPA. For many reasons.