Palo Alto Networks

Collect firewall logs from a Palo Alto Networks firewall and offer serious threats to the security signal inbox for a person to review.

The connector reads logs from the management interface of a Palo Alto Networks firewall through its XML API (the firewall's built-in programming interface). Aegis stores the logs it imports, counts them on the connector page, and offers new high and critical threat logs to the security signal inbox (the queue where a reviewer decides whether a signal from a connected tool becomes an incident). Nothing becomes an incident or evidence until a person accepts it.

At a glance

Direction Into Aegis.
What it brings in Threat, WildFire, URL filtering and traffic logs, as chosen for the connection, from a minimum severity and, on the first sync, over a chosen time range. Later syncs are incremental.
Where it lands Imported logs are counted in the Imported Log Statistics panel on the connector page. New high and critical threat logs from the last seven days are offered to the security signal inbox; accepting a signal creates the incident (see Incidents).
Credentials and permissions The firewall's management address (HTTPS, reachable from Aegis) and an API key of an account with read-only access to logs, with the XML API enabled on the management profile.
Owner of imported records Logs and signals have no owner; an incident belongs to the person who created or accepted it.
When it runs A background job pulls every enabled connection every five minutes, and you can sync on demand with Sync Now.
Set it up /connectors/paloalto, by people allowed to configure connectors, on a plan that includes the connector. One firewall connection per Aegis instance.

Who uses it

Manager and Admin can open the page, save the configuration, test the connection, run a sync and disconnect the connector. A Contributor or Viewer who opens /connectors/paloalto is redirected, because the page requires the Manager role. The connector must also be switched on for your organisation; if it is not, the page's actions are refused.

What's on this screen

No screenshot of this page was captured for this edition of the guide, so this section follows the page as the current build renders it. You reach it from the Palo Alto Networks tile on Connectors. From top to bottom:

Prepare the firewall

Do this on the firewall before you open Aegis. The page's Setup Instructions panel repeats it.

  1. Open the firewall's management interface and go to Device → Setup → Management. Enable XML API access on the management profile.
  2. Create an admin account with read-only access to logs, or generate an API key under Device → API Keys. Copy the key; you paste it into Aegis once.
  3. Check that the management interface answers over HTTPS from the network Aegis runs in.

Configure the connection

  1. Enter a Connection Name, for example the firewall's site. It is required and identifies the connection in sync results.
  2. Enter the Firewall Management URL, such as https://firewall.example.com. The form accepts only an https:// address. Enter the bare address: one with a path, a query string or a user name and password in it is refused when you save.
  3. Paste the API Key. The field is masked, and after saving it shows dots instead of the key. Leave it blank later to keep the stored key.
  4. Tick the Log Types to Sync. Threat and WildFire logs are ticked by default; URL filtering and traffic logs are not. At least one type must stay ticked.
  5. Choose the Minimum Severity (Informational to Critical, default Medium). Logs below it are not imported.
  6. Choose the Initial Sync Time Range (Last 1 hour to Last 7 days, default Last 1 hour): how far back the first sync looks. Choose a Sync Schedule (Every 5 minutes to Every 6 hours).
  7. Leave Connection Enabled on, then select Save Configuration. The button stays disabled until the name, a valid HTTPS address and one log type are present. While it saves it reads Saving...; a refused address or other problem appears in a red box at the top of the form.

Test the connection

  1. In Connection Status, select Test Connection. The label changes to Testing... while Aegis asks the firewall for its system information.
  2. On success the status reads Connected and a green box shows Connected to Palo Alto firewall with the firewall's hostname, model, serial and PAN-OS version where the firewall returns them. The Log Sync panel appears below.
  3. On failure the status reads Connection Failed with a short reason. The reason is deliberately general; fix the address, key or network path and test again.

Sync logs and read the statistics

  1. In Log Sync, select Sync Now. The button reads Syncing... and a blue bar shows that logs are being pulled from the firewall.
  2. When it finishes, a green Sync Complete box shows the time and how many logs were imported, or a red Sync Failed box shows why.
  3. Read Imported Log Statistics: Total logs, Linked to incidents, and counts By severity and By log type. Before the first sync it reads No logs imported yet. Run a sync to pull logs from the firewall.
  4. Open Security Signals under Security Incidents to review the high and critical threat logs the sync offered. Accept, merge or dismiss each one there (see Incidents).

Once the connector has synced, the page shows Last successful sync: with the date and time of the last completed sync, and it still does after a reload. The counts of a sync are shown only for the visit in which you ran it; the audit log records every sync.

Change or pause the connection

Disconnect the connector

  1. In Disconnect connector, select Disconnect. A confirmation asks you to confirm that the configuration and credentials are deleted and syncing stops.
  2. Confirm. Aegis deletes the connection and returns you to /connectors. Records already imported stay in Aegis, and you can configure the connector again later.

Tips and limits

Where this connects

Signals and incidents are handled in Incidents; rules that open incidents from connector events are described in Auto-incident rules. Accepted signals become evidence in Evidence. The full list of connectors is in Connectors.