Palo Alto Networks
The Palo Alto integration reads PAN-OS firewalls and Panorama through the PAN-OS XML API. It runs on an Integrator inside your network, because the management interface of a firewall is not something the CyberOptix CTEM Platform should reach over the internet.
It is read-only. The integration never commits, pushes or changes configuration.
What it collects
| Sync | Collects |
|---|---|
| Configuration backup | The running configuration, with secrets stripped on the Integrator before it leaves your network, versioned whenever it changes; security rules in evaluation order |
| Configuration review | Every configuration backup and NAT sync is reviewed against the configuration review checks, and what they find is raised as vulnerabilities on the device |
| Network discovery | Interfaces (zone, VLAN, virtual router, link state), the networks they are addressed into, and the routing table |
| Host discovery | ARP entries and DHCP leases: what the firewall has actually seen on the network |
| Exposure correlation | NAT and published-service rules, so an address reachable from outside is tied to what sits behind it |
Pointed at Panorama, every sync also lists the firewalls Panorama manages.
What the firewall reports is kept as its own record, alongside hosts and subnets rather than written into them. A host the firewall sees that no scan has found yet is shown as seen on the network, not added to your managed assets.
Create a read-only API key
- On the firewall or Panorama, create an Admin Role Profile that grants, under XML API, only Operational Requests and Configuration, and under Web UI and REST API, nothing. Leave Commit, User-ID and Export disabled.
- Create an administrator with that role and a strong password.
- Generate the key for that administrator:
curl -sk -X POST "https://<firewall>/api/?type=keygen" --data-urlencode "user=<admin>" --data-urlencode "password=<password>"
The <key> element in the response is the API key. The Integrator sends it in the
X-PAN-KEY header, never in a URL.
Connect it
- Under Integrations, add Palo Alto with the firewall's management hostname and the API key.
- In the integration's settings, assign the Integrator that can reach the firewall's management interface.
- Enable the syncs you want.
Certificates
Firewalls ship with a self-signed management certificate. The first connection accepts it and records its fingerprint on the integration; every later connection must present the same certificate. If you replace the certificate, clear the pinned fingerprint in the integration's settings so the new one is recorded. A certificate issued by a trusted CA is verified normally and never pinned.