How Firewall Fleet Health connects to your firewalls

Firewall Fleet Health connects to your Palo Alto Networks fleet in one of three ways when ROC hosts it: an IPsec tunnel from your firewall to ROC, a small WireGuard tunnel box on your network, or direct access over the internet limited to ROC's address. You can also run it yourself as a Docker container. In every case it reads through a read-only API account and makes no changes to your firewalls.

Which connection option should we pick?

Pick whichever your security policy allows. Each is an ordinary change for a firewall team.

Ways to connect Firewall Fleet Health to your firewalls
OptionWhat it takesBest for
IPsec tunnel to ROC One site-to-site IKEv2 tunnel from their firewall to ROC, a route for one ROC address, one security rule allowing it to Panorama on TCP 443. Nothing installed. Most Palo Alto shops
WireGuard tunnel box Run ROC's small container on a host that can reach Panorama; it connects out to ROC over UDP. Policy forbids vendor tunnels, or the firewall can't be changed
Direct over the internet Allow only ROC's public address to reach Panorama's (or the firewalls') API, with a security policy and allowlist. Fastest proof of concept
Self-hosted (Docker) Run the dashboard image on their own server with a ROC license; data never leaves their network. Data must stay in-house

What changes for an IPsec tunnel to ROC?

  • One site-to-site IKEv2 tunnel from your firewall's public address to ROC's firewall, with a pre-shared key that ROC sends separately.
  • One route for a single ROC address into that tunnel.
  • One security rule allowing that ROC address to reach Panorama on TCP 443, and nothing else.

Nothing is installed on your network and Panorama is not exposed to the internet. ROC sends your firewall team a setup sheet with the exact settings.

What changes for the WireGuard tunnel box?

  • A small Linux host or VM with Docker that can reach Panorama on TCP 443.
  • Outbound UDP from that host to ROC.

ROC's small container runs on that host and connects out to ROC. Nothing inbound is opened, and through the tunnel ROC can open HTTPS connections to the Panorama addresses you list and nothing else. Stopping the container ends the tunnel.

What changes to connect directly over the internet?

  • A security policy that allows only ROC's public address to reach the API on Panorama, or on each firewall if you run without Panorama.

This is the quickest way to start a proof of concept. For a setup that runs long term, either tunnel keeps the API off the internet.

What does self-hosting involve?

  • A Linux server with Docker that can reach Panorama, or each firewall, on TCP 443.
  • The dashboard image and a ROC license, both supplied by ROC.

The dashboard and all of its data stay on your network, and your staff reach it over HTTPS on that server. A ROC engineer does the first sign-in, connects it to Panorama and loads the license.

What does it read once connected?

With Panorama, it reads Panorama's inventory and logs and asks each managed firewall for its counters through Panorama, all over HTTPS on TCP 443 with a read-only account. Without Panorama, direct mode asks each firewall's API itself. Every connection that carries the API key is certificate-checked, and the key is stored on the dashboard server and never shown again.

Pick an option with us

Not sure which option fits your policy? Book a demo and we will go through it with your firewall team.