Prisma Access remote network subnet 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
Remote network subnets must not overlap each other or the infrastructure subnet unless overlapping subnets are allowed. With overlaps not allowed, Prisma Access cannot tell which site an address belongs to, and traffic for one site can be delivered to the other.
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.
- Renumber the overlapping subnet, or, where the overlap is intended (guest networks that reach only the internet), allow overlapping subnets and accept the features that then do not apply.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services remote-networks onboarding <site> subnets <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 remote-networks onboarding <site> subnetsValues to fill in2
- <site>
- The remote network or service connection
- <prefix>
- The address prefix
Before you type it2
- 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.
How to confirm the fix
- Confirm no two remote networks list overlapping subnets, and none overlaps the infrastructure subnet.
Limits
- Where the reading does not say whether overlapping subnets are allowed, remote networks are not compared with each other.
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-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.