Prisma Access infrastructure subnet is smaller than a /24
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
Palo Alto Networks states the infrastructure subnet must be a /24 or larger. The service takes its internal addresses from it, and a smaller subnet limits how far the deployment can grow.
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.
- Plan a /24 or larger infrastructure subnet with Palo Alto Networks support.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services service-connection service-subnet <prefix>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 service-subnetValues to fill in1
- <prefix>
- The address prefix
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 infrastructure subnet and AS are set when Prisma Access is set up. Changing them re-provisions the service; plan it with Palo Alto Networks support.
How to confirm the fix
- Confirm the infrastructure subnet is a /24 or larger.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
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-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-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.