Prisma Access mobile user IP pool overlaps another network
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 routes a mobile user's address back to the user. Where the same addresses also belong to the infrastructure subnet, a site or another pool, return traffic for one of them is sent to the other, and connections from the users in the overlap fail in ways that look like application faults.
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.
- Give the pool a prefix that overlaps nothing else Prisma Access routes: the infrastructure subnet, every remote network and service connection subnet, and every other pool.
- Size the new pool at twice the number of devices in that region, a /23 or larger.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services mobile-users onboarding <onboarding> ip-pools <region> ip-pool <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 mobile-users onboarding <onboarding> ip-poolsValues to fill in3
- <onboarding>
- The mobile users onboarding entry (the portal name)
- <region>
- The region, or worldwide
- <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.
- A new pool applies to new connections. Plan it with the users of that region.
How to confirm the fix
- Confirm the pool no longer overlaps any of the prefixes this finding names.
- From a mobile user in that region, reach a data center resource and a branch resource.
Limits
- Only prefixes are compared. A value that is not an address prefix is recorded as not read.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Remote access VPN
- PAN-SEC-140Prisma Access mobile user IP pool is smaller than a /23
- PAN-SEC-151Prisma Access agent profile does not collect HIP data
- PAN-SEC-152Prisma Access tunnel profile allows direct access to the local network
- PAN-SEC-153Prisma Access agent connects only on demand
- PAN-SEC-154Prisma Access tunnel profile excludes a route broader than an included one
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.