Hi Netskopers,

For those of you which have published Active Directory via NPA, using the following guide...

Netskope Private Access for Microsoft Active Directory Domain Services - Netskope Knowledge Portal

The Windows client can then always connect to and authenticate with AD (since its always available via NPA).

Due to this, Windows is always applying the less restrictive Domain Firewall Profile even when the remote device is connected to an untrusted network (home wifi, public cafe etc). Normally the more restrictive Public Firewall Profile would be applied.

Is this a concern for others?

Have you solved this somehow?

Are there any other options other than make the Domain Profile more restrictive.