Prisma Access site receives a default route from Prisma Access
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
Prisma Access advertises 0.0.0.0/0 into the site over BGP. Palo Alto Networks asks that no other default route be advertised in that network by BGP; with two, the site's internet traffic follows whichever wins, which the configuration cannot show.
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 the site is meant to reach the internet through Prisma Access, and confirm nothing else advertises a default route by BGP there.
- Otherwise turn Advertise Default Route off for this site.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services remote-networks onboarding <site> protocol bgp originate-default-route 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 remote-networks onboarding <site> protocol bgpValues to fill in1
- <site>
- The remote network or service connection
Before 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.
- Keep it only where the site takes its internet route from Prisma Access and no other default route is advertised there by BGP.
How to confirm the fix
- On the site's device, confirm which default route it installs.
Limits
- Other default routes in the customer network sit outside Prisma Access.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in IPSec VPN
- PAN-SEC-141Prisma Access infrastructure subnet overlaps a reserved range
- PAN-SEC-142Prisma Access infrastructure subnet is smaller than a /24
- PAN-SEC-143Prisma Access remote network subnet overlaps another network
- 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-147Prisma Access sends mobile user internet traffic to the data centers
- PAN-SEC-148Prisma Access BGP session has no secret
- PAN-SEC-149Prisma Access internal DNS server is 127.0.0.1
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.