Troubleshooting Edge DX and Netskope CASB

A user asked about Netskope CASB causing Edge DX to show their IP address as a Netskope owned one instead of their actual ISP IP. They found an article about ZScaler needing to be set up to bypass some ControlUp URLs for the real IP to show, and asked if this would likely be the same fix for Netskope. Another user responded saying they had a similar issue with ZScaler and needed to set up a bypass in order to correctly report ISPs. It is likely that EdgeDX is looking at the IP the client is coming in from and showing the Netskope IP. The ZScaler bypass information can be found here: https://support.controlup.com/docs/show-the-real-ip-address-for-devices-using-zscaler-vpn

Read the entire ‘Troubleshooting Edge DX and Netskope CASB’ thread below:

Hello, we use Netskope CASB in our environment, and for all the workstations that have this installed, Edge DX sees their IP addresses as a Netskope owned IP address instead of the actual external IP address of whatever ISP the client is connected to. This makes Edge DX think all of our clients are connected in Dallas, which is where our block of Netskope IPs originate from. I found this article discussing a similar issue for devices using ZScaler, where ZScaler had to be set up to bypass some ControlUp URLs so that the real IP address would show up. Would this likely be the same fix for our issue with using Netskope? https://support.controlup.com/docs/show-the-real-ip-address-for-devices-using-zscaler-vpn

Hey Alex, I can’t speak for Netskope but we had Zscaler in our environment and it required a bypass in zscaler to get our devices ISPs correctly reporting. I think EdgeDX just looks at the IP the client is coming in from so if you see the Netskope IP that likely means all your client traffic to EdgeDX is likely being proxied though Netskope.

Continue reading and comment on the thread ‘Troubleshooting Edge DX and Netskope CASB’.  Not a member? Join Here!