Security and data handling

Firewall Fleet Health reads your Palo Alto Networks fleet through a read-only API account, and the dashboard makes no changes to your firewalls. Secrets are masked in the config history before anything is saved, the API key stays on the dashboard server and is never shown back, and signed-in users see only what their role allows. You choose where it runs: hosted by ROC, or on your own server so all data stays on-site.

What access does it need to our firewalls?

A read-only API account on Panorama, or on each firewall in direct mode. The dashboard only reads: you can mute a firewall or mark it out of service, and those settings live in the dashboard, not on the firewall.

Every connection that carries the API key is certificate-verified, with no option to skip the check. You upload a CA certificate or accept the device's certificate by its fingerprint, and if that certificate changes the collector stops and every user sees a warning.

How are secrets handled?

  • The API key is stored on the dashboard server, readable only by the service, and never shown or logged. Change the address or account and the old key is deleted.
  • If you generate the key from the account's password, the password is used once and not stored.
  • Config change history masks secrets before saving: passwords, keys, SNMP communities, encrypted values and anything that looks like a key read as •••••. A change where only a secret changed is still listed, labelled "secret changed".
  • Dashboard passwords are stored as salted hashes, never in plain text.

Who can see and do what?

Every page needs a signed-in user. Four roles decide the rest, and an activity log records sign-ins and every change to users and settings.

exec
The Overview status board only.
tech
The dashboard, without the Events tab and without muting.
engineer
Every tab, plus muting firewalls and marking them in or out of service.
admin
Everything, plus users, the activity log and settings.

What do we open on our network?

For the IPsec tunnel, one rule allowing a single ROC address to reach Panorama on TCP 443 only. For the WireGuard tunnel box, outbound UDP from one host and nothing inbound. For direct access, only ROC's public address is allowed to reach the API. The details are on the How it connects page.

Hosted dashboards are reached through an encrypted Cloudflare Tunnel, so the server opens no inbound web ports. IPsec tunnels end on ROC's firewall, and a WireGuard tunnel box connects out to one UDP port at ROC.

Where is our data kept, and for how long?

Hosted by ROC, each customer's dashboard and data sit on ROC's server. Self-hosted, the Docker image runs on your own server and all data stays on-site.

Data is kept for fixed periods:

  • 18 months of firewall events and config changes
  • 13 months of daily trends
  • 30 days of tunnel status
  • 7 days of 5-minute detail
Bars drawn to scale: 18 months is the full width.

Bring us your security questions

Have a security review to get through? Book a demo and bring your questions.