Skip to main content

I'm aware that the Egress IP option is generally applied per PoP, but I’d like to get more clarity regarding the Global Dedicated Egress IP option—specifically its configuration and potential risks. I would greatly appreciate guidance on the following points:

  • How many PoPs and Egress IPs are assigned when using the Global Dedicated Egress IP option?

  • Is it technically possible to apply the same Egress IP across all PoPs worldwide?

  • What potential risks should be considered when implementing such a global configuration?

Thanks in advance for your insights.

From our experience, after applying Global Dedicated Egress IP, a tenant will have two dedicated IPs for each Netskope data center — in our case, a total of 162 IPs. That’s why it is so expensive to purchase, whereas other competitors offer a more flexible pricing model for their egress IP services.

You can check your assigned IPs under Security Cloud Platform > Netskope Client > Enforcement > Proxy IP Addresses.

With Netskope’s current NewEdge infrastructure, it is not possible to assign the same egress IPs for a particular tenant across different data centers.

Hope it helps.


This is very helpful.
Are there any operational impacts from having IPs distributed worldwide?
I don’t think it is very practical to specify all IPs for sites that require IP restrictions (which is understandable if there are as many as 162).

As you know, at present it is not possible to allocate traffic destinations for each Dedicated Egress IP, but how are you operating in such cases? (I understand it is possible to choose whether to allocate to shared IPs.)

Also, if you happen to know, when a client initiates communication, the selection of each POP is determined by GSLB — does this remain the same even when Dedicated Egress IP is applied?

I would greatly appreciate your thoughts on this.


Reply