Prisma Access agent profile does not collect HIP data
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
Without host information no security rule can ask about the endpoint's posture, so an unpatched or unmanaged device connects on the same terms as a compliant one.
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.
- Turn on Collect HIP Data in the agent profile, then reference HIP profiles in the Mobile Users security rules.
Command line
Panorama CLI, Prisma Access template, vsys1
set template <template> config vsys vsys1 global-protect global-protect-portal <portal> client-config configs <agent-config> hip-collection collect-hip-data yesAn 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 template <template> config vsys vsys1 global-protect global-protect-portal <portal> client-config configs <agent-config>Values to fill in3
- <template>
- The template that holds this setting
- <portal>
- The Prisma Access GlobalProtect portal
- <agent-config>
- The agent configuration to change
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.
- This setting lives on a device or in a template. On a Panorama, name the template it belongs to.
How to confirm the fix
- Confirm the agent profile collects HIP data and a connected endpoint reports it.
Limits
- A profile that does not state the setting is not judged.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Remote access VPN
- PAN-SEC-139Prisma Access mobile user IP pool overlaps another network
- PAN-SEC-140Prisma Access mobile user IP pool is smaller than a /23
- 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.