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:
-
Breadcrumb and header.
Connectors / Palo Alto Networks, the titlePalo Alto Networks Firewall Connectorand a one-line description. -
Configuration. A blue box,
Required Firewall Configuration, lists what the API key needs. Below it:Connection Name,Firewall Management URL,API Key, fourLog Types to Synccheckboxes, theMinimum Severity,Initial Sync Time RangeandSync Schedulelists, aConnection Enabledswitch andSave Configuration. -
Connection Status. A status dot and label (
Not Tested,Testing...,ConnectedorConnection Failed), the last recorded error if a sync failed, andTest Connectiononce a firewall is saved. Before that it readsConfigure and save a firewall connection above to enable testing. -
Log Sync. Shown only while the status is
Connected: theSync Nowbutton, the result of the last manual sync and theImported Log Statisticspanel. - Disconnect connector. Shown once a connection is saved, to people allowed to delete connectors.
-
Reference panels.
Setup Instructions(seven steps on the firewall side),Log Types(what each type contains) andSeverity Mapping(how firewall severities map to Aegis incident impact).
Prepare the firewall
Do this on the firewall before you open Aegis. The page's
Setup Instructions panel repeats it.
-
Open the firewall's management interface and go to
Device → Setup → Management. Enable XML API access on the management profile. -
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. - Check that the management interface answers over HTTPS from the network Aegis runs in.
Configure the connection
-
Enter a
Connection Name, for example the firewall's site. It is required and identifies the connection in sync results. -
Enter the
Firewall Management URL, such ashttps://firewall.example.com. The form accepts only anhttps://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. -
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. -
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. -
Choose the
Minimum Severity(InformationaltoCritical, defaultMedium). Logs below it are not imported. -
Choose the
Initial Sync Time Range(Last 1 hourtoLast 7 days, defaultLast 1 hour): how far back the first sync looks. Choose aSync Schedule(Every 5 minutestoEvery 6 hours). -
Leave
Connection Enabledon, then selectSave Configuration. The button stays disabled until the name, a valid HTTPS address and one log type are present. While it saves it readsSaving...; a refused address or other problem appears in a red box at the top of the form.
Test the connection
-
In
Connection Status, selectTest Connection. The label changes toTesting...while Aegis asks the firewall for its system information. -
On success the status reads
Connectedand a green box showsConnected to Palo Alto firewallwith the firewall's hostname, model, serial and PAN-OS version where the firewall returns them. TheLog Syncpanel appears below. -
On failure the status reads
Connection Failedwith a short reason. The reason is deliberately general; fix the address, key or network path and test again.
Sync logs and read the statistics
-
In
Log Sync, selectSync Now. The button readsSyncing...and a blue bar shows that logs are being pulled from the firewall. -
When it finishes, a green
Sync Completebox shows the time and how many logs were imported, or a redSync Failedbox shows why. -
Read
Imported Log Statistics:Total logs,Linked to incidents, and countsBy severityandBy log type. Before the first sync it readsNo logs imported yet. Run a sync to pull logs from the firewall. -
Open
Security Signalsunder 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
-
Edit any field and select
Save Configuration; the existing connection is updated in place. -
If you change the
Firewall Management URLto a different address, re-enter the API key in the same save. Aegis refuses to send the stored key to a firewall other than the one it was entered for. -
Turn
Connection Enabledoff and save to pause syncing without losing the configuration.
Disconnect the connector
-
In
Disconnect connector, selectDisconnect. A confirmation asks you to confirm that the configuration and credentials are deleted and syncing stops. -
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
- Traffic logs are high in volume; switch them on only when you need them.
-
Management addresses on private networks (such as
10.x,172.16–31.xand192.168.x) are accepted. Loopback, link-local and cloud-metadata addresses, and names such aslocalhost, are refused when you save. A hostname is checked when the connection is tested or synced, not when you save. -
In the current build the background job pulls every enabled connection every
five minutes. The
Sync Schedulechoice is saved with the connection, but the job does not read it yet. -
The sync panel appears only while the status is
Connected. After saving a new configuration, runTest Connectionagain to bring it back. -
If some log types fail during a sync,
Connection Statusshows that the last sync was partial; the failed types are retried on the next sync. - Only high and critical threat logs go to the signal inbox, at most 100 per sync, oldest first. A log that is already a signal, evidence or linked to an incident is not offered again. Raw logs never go straight into the Evidence Locker; only an accepted or merged signal becomes evidence.
- The page shows counts, not a list of individual logs. Review individual threats as signals. An incident can also be created from a single imported log through the Aegis API, which needs permission to create incidents; this page has no button for it, and a log already linked to an incident is not linked again.
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.