Prisma Access service connection has no secondary tunnel or backup
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 service connection is a data center's path into Prisma Access. With one tunnel and no backup service connection, a single tunnel or device failure cuts mobile users and remote networks off from that data center.
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.
- Add a secondary IPsec tunnel on a second WAN link, or name a backup service connection, as Palo Alto Networks documents for redundancy.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services service-connection onboarding <site> secondary-ipsec-tunnel <tunnel>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 service-connection onboarding <site>Values to fill in2
- <site>
- The remote network or service connection
- <tunnel>
- The secondary IPsec tunnel
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 secondary tunnel needs a second tunnel on the data center device as well.
How to confirm the fix
- Confirm the service connection names a secondary tunnel or a backup service connection.
Limits
- Redundancy the data center provides some other way, outside Prisma Access, sits outside this check.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in IPSec VPN
- PAN-SEC-142Prisma Access infrastructure subnet is smaller than a /24
- 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-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
- PAN-SEC-150Prisma Access has service connections and no internal domains
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.