Prisma Access sends mobile user internet traffic to the data centers
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
Mobile users' internet traffic goes through the data centers instead of out of Prisma Access. It works only while a data center advertises a default route; Palo Alto Networks warns that otherwise routing through service connections fails.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- Keep it only where internet traffic is meant to leave through the data centers, and confirm each data center advertises a default route.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services traffic-steering All-Traffic-To-DC noAn example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Nothing here commits or pushes. Review, commit, then push to Prisma Access yourself.
Read it back
show plugins cloud_services traffic-steeringBefore you type it3
- Prisma Access is set in the Cloud Services plugin on Panorama: commit to Panorama, then push the change to Prisma Access from the plugin.
- A tenant managed by Strata Cloud Manager has no command line: make the same change in Prisma Access Setup and push it.
- Leave it on only where mobile users' internet traffic is meant to go through the data center, and the data center advertises a default route.
How to confirm the fix
- Confirm the data centers advertise a default route to Prisma Access.
Limits
- What the data centers advertise sits outside this check.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in IPSec VPN
- PAN-SEC-143Prisma Access remote network subnet overlaps another network
- PAN-SEC-144Prisma Access site receives a default route from Prisma Access
- PAN-SEC-145Prisma Access service connection summarizes mobile user routes while remote networks exist
- PAN-SEC-146Prisma Access service connection has no secondary tunnel or backup
- PAN-SEC-148Prisma Access BGP session has no secret
- PAN-SEC-149Prisma Access internal DNS server is 127.0.0.1
- PAN-SEC-150Prisma Access has service connections and no internal domains
- PAN-SEC-155Prisma Access infrastructure BGP AS is not a private AS
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.