What's New in the NetSec Platform
Service Provider Backbone Integration
Table of Contents
Service Provider Backbone Integration
Learn about how services providers can use their backbone in Prisma Access.
Integrate Prisma Access with a service provider (SP) backbone, which
allows you (the SP) to assign specific region and egress internet capabilities to
your tenants, providing more granular control over the Prisma Access egress traffic.
Without the SP Backbone feature, Prisma Access egress traffic uses public cloud
providers for network backbone instead.
The following diagram represents Prisma Access egress traffic without SP Backbone
integration.
![]()
The following diagram represents Prisma Access egress traffic with SP Backbone
integration.
![]()
Service Provider Backbone Integration was introduced with Prisma Access 4.1.
From Prisma Access version 5.0, you can allow inbound flows to other remote networks
over the Service Provider (SP) backbone when you configure the non-inbound access
remote network.
SP interconnect supports only the following:
- Mobile users, service connections, and remote networks
- GCP Regions
- New Prisma Access deployments
- Explicit proxy egress traffic
From March 2024, you can configure, view, and monitor Service Provider IP address pools
to leverage your own IP addresses for Prisma Access egress traffic instead of the
egress through public cloud providers.
From Prisma Access version 5.2, you (the Service Provider) now have the flexibility
to select AWS as well as GCP for your customers' public cloud egress traffic. You'll
see the additional regions in your license activation, you'll see different tabs for
GCP and AWS in your connections and IP address pools, and you'll also be able to
monitor the public clouds separately.