You deployed the Netskope Client for Web steering in a large enterprise with dynamic steering.

When the Netskope Client is configured with dynamic steering and a bypass rule exists for an IP-restricted application, the traffic to that application is not forwarded to the Netskope data plane. Instead, it follows the default network path. For on-premises users, this means the traffic exits the corporate network through the enterprise’s egress point, using the enterprise’s public IP address. This is significant in the context of IP-restricted applications because such applications typically whitelist specific IP addresses. When traffic bypasses Netskope and egresses via the enterprise egress IP, it aligns with the IP restriction requirements. The DHCP-assigned RFC1918 address would not be used as the source IP in internet-bound communications; the public-facing enterprise egress IP is what is seen by the destination application.