Prisma Access BGP session has no secret
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
A BGP session with no authentication accepts routes from anything that reaches the peer address over the tunnel, and those routes steer Prisma Access traffic.
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.
- Set the same BGP secret on the site and on its peer device.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services remote-networks onboarding <site> protocol bgp secret <secret>An 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 in2
- <site>
- The remote network or service connection
- <secret>
- The BGP secret
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.
- The same secret goes on the peer device, or the BGP session drops.
How to confirm the fix
- Confirm the BGP session is established again with the secret on both sides.
Limits
- Only whether a secret is written is read, never its value. Where the tenant's API answers without the field, the session is not judged.
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-147Prisma Access sends mobile user internet traffic to the data centers
- 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.