Netskope NewEdge BYOIP Integration Overview

Worth Knowing
Public admin docs describe Netskope-owned Dedicated Egress IPs (DEIP); a Netskope-hosted 2024 third-party scorecard references customer-IP egress, so current customer-prefix onboarding is not independently verified.

This page outlines Dedicated Egress IP (DEIP) and egress-addressing options on the Netskope NewEdge Security Service Edge (SSE) platform. Public Netskope product documentation primarily describes tenant-specific Dedicated Egress IP addresses allocated from Netskope-owned NewEdge ranges under AS55256, while a Netskope-hosted 2024 third-party network scorecard also mentions customer-IP egress; current customer-prefix BYOIP onboarding is therefore noted as not independently verified in public onboarding documentation.

Provider Details

FieldInformation
Provider NameNetskope (NewEdge SSE)
WebsiteDedicated Egress IP Data Sheet | Security Cloud Platform Configuration | NewEdge Network Scorecard (2024 PDF)
ASN(s)AS55256 (Netskope Inc, NewEdge cloud backbone)
BYOIP ScopePublic configuration guides document tenant-specific Dedicated Egress IPs (DEIP) drawn from Netskope-owned NewEdge pools. A vendor-hosted 2024 third-party scorecard references customer-IP egress, so current customer-prefix onboarding is not independently verified from public admin guides alone (confirm directly with Netskope).
Supported VersionsIPv4 documented for DEIP; IPv6 dedicated egress entitlements are not established in public documentation.
Supported ServicesNetskope Next Gen SWG and Cloud Firewall (FWaaS) traffic steered through NewEdge (Netskope Private Access uses Publisher-based source IP anchoring separately).

Technical Requirements

RequirementDetails
Prefix Size & Pool ModelStandard DEIP assigns at least two Netskope-owned IPv4 addresses per enabled NewEdge data plane/region. Public onboarding requirements for importing a customer-owned RIR prefix are not independently verified; confirm any custom enterprise prefix import options directly with Netskope.
ASN & RoutingDEIP addresses are originated by Netskope under AS55256.
ROA / LOANot required for Netskope-owned DEIP allocations; unverified for any custom customer-IP arrangement.

Step-by-Step BYOIP Process

Estimated Setup Time:Typically a few business days for standard Regional or Global DEIP enablement.Tested By Us:Not tested by BYOIP.info
Step 1

Engage your Netskope account team to license Regional or Global Dedicated Egress IP (DEIP) - and ask explicitly whether customer-owned prefix onboarding is available for your tenant if you require RIR-registered customer space rather than Netskope-owned DEIP addresses.

Step 2
For standard DEIP, enable Dedicated Egress IP Footprint in the Netskope admin console for the target NewEdge zones/regions.
Step 3
Export the assigned dedicated IPv4 addresses from the portal and update SaaS, IdP and partner firewall allowlists.

Worth Knowing

  • Evidence nuance: Public Netskope admin documentation describes Netskope-owned Dedicated Egress IPs (DEIP), whereas a Netskope-hosted 2024 third-party scorecard mentions customer-IP egress. Because current customer-prefix onboarding steps are not published in the public admin docs, treat customer-prefix BYOIP as unverified until confirmed with your Netskope account team.
  • NPA separation: Netskope Private Access (NPA) uses Publisher-based source IP anchoring rather than NewEdge DEIP pools.

Pricing and Plan Details

ItemDetails
FeesPaid add-on entitlement (Regional DEIP or Global DEIP) quoted on top of Netskope SSE/SASE subscriptions.
Bundled or StandaloneIntegrated add-on for Netskope NewEdge SWG and Cloud Firewall deployments.
Netskope: Dedicated Egress IP Addresses Data Sheet
Netskope Docs: Security Cloud Platform Configuration (DEIP)
Netskope-Hosted NewEdge SASE Network Scorecard (2024 PDF)

Published 21 November 2025 · Updated 12 November 2026

Related BYOIP supporters

All BYOIP supporters

FAQ