Professionals discussing network security in a server aisle
Visibility & resilience

Palo Alto Logging, High Availability and Panorama Review

Are firewall logs leaving the firewall, is the HA pair healthy, and could you rebuild a firewall from last night’s backup?

Security consultant reviewing firewall findings with a client
Evidence

Logs that never leave the firewall are lost with it

We check log forwarding for traffic, threat, system and configuration logs, and how long each is kept.

IT engineer reviewing firewall logs at a data center workstation
Recovery

A configuration backup you can actually restore

Scheduled exports, Panorama sync and high availability state, checked.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote audits & advisory
Visibility & resilience

What the logging, HA and Panorama review covers

When something goes wrong, the firewall’s logs are the evidence and its configuration backup is the way back. Both are easy to get wrong: logs kept only on the appliance, time that drifts, a high availability pair that is out of sync, or a backup nobody has tested.

We read log forwarding, time and alert settings, high availability state, backup schedules and, where you use Panorama, the connection and sync status of every managed firewall: 26 controls, each with evidence.

Employee at a workstation showing a protected session
The controls

26 Logging, HA, Panorama & log review controls we evaluate

Each control ends as Pass, Fail, Warning or Manual review, with the evidence behind it. Some checks raise or lower the default severity to match what was found.

Logging & Monitoring · 11 controls

IDControlDefault severity
LM-01Logs are forwarded to a central collector (syslog, HTTP or Panorama)High
LM-02Syslog forwarding is encrypted (TLS)Medium
LM-03System logs are forwardedMedium
LM-04Configuration change logs are forwardedMedium
LM-05Critical system events raise an alert (email, SNMP trap or HTTP)Medium
LM-06A log forwarding profile covers traffic, threat, URL and WildFire logsMedium
LM-07Every allow rule forwards its logs through a log forwarding profileMedium
LM-08Rules log at session endMedium
LM-09Traffic blocked by the default (implicit) deny is loggedMedium
LM-10Traffic allowed within a zone (intrazone-default) is loggedLow
LM-11Repeated log entries are not suppressedLow

High Availability & Resilience · 6 controls

IDControlDefault severity
HA-01The firewall is deployed as a high-availability pairMedium
HA-02Both HA members are healthyHigh
HA-03HA configuration is synchronizedMedium
HA-04HA control link has a backupLow
HA-05HA link or path monitoring is enabledLow
HA-07Session table capacity is adequateMedium

Panorama & Fleet · 1 controls

IDControlDefault severity
PN-01The firewall reports to Panorama when it is managed centrallyLow

Threat Activity (log review) · 8 controls

IDControlDefault severity
TA-01Failed administrator sign-ins are low and come from management networksHigh
TA-02Administrators sign in from trusted management addresses onlyHigh
TA-04No critical or high-severity system events were loggedHigh
TA-03Configuration changes are made by named administratorsMedium
TA-08Configuration changes happen during normal working hoursLow
TA-05Critical and high-severity threats were blocked, not just alertedHigh
TA-06External sources are not repeatedly attacking published servicesMedium
TA-07No internal host is contacting command-and-control or malicious domainsHigh
Why it matters

What we look for and why

01

Logs your SIEM can use

Traffic, threat, system and configuration logs should reach a SIEM, a syslog server or Panorama. We check each log type and list the rules that do not forward.

02

Accurate time

Without NTP, log times drift and incidents cannot be lined up across systems. We check the time sources and the time zone.

03

Recovery readiness

An HA pair out of sync can fail over to the wrong configuration. We check HA state, link and path monitoring, and whether configuration backups are scheduled off the firewall.

Sample

A finding from the sample report

SAMPLE · Veltrana Logistics (fictional company) · illustrative data
Area
Logging
Finding
System logs are not forwarded to a collector
Severity
Medium
Evidence
High availability changes, administrator sign-ins, content update failures and hardware events stay on the firewall. Syslog server siem01 also receives logs over unencrypted UDP.
Fix
Add a system log forwarding match list (Device > Log Settings > System) to the syslog or Panorama destination, and switch syslog to TLS where the collector supports it.

Every finding in the real report has this shape. See the full sample report

How it works

A read-only audit in five steps

STEP 1

Scoping call

We confirm the firewalls, Panorama, sites, GlobalProtect and who on your side should be told before the run. 30 minutes.

STEP 2

Read-only access

Your administrator creates one Superuser (read-only) account on each firewall, or on Panorama if it manages them. That account is the only change, and your team makes it.

STEP 3

Read-only collection

The collector reads the configuration, rule hit counts and system status over HTTPS through the PAN-OS XML API, from a computer inside your network.

STEP 4

Review and scoring

141 controls in 13 areas are scored with evidence, including a review of the last 7 days of firewall logs. Ali reviews every finding, groups them into business risks and maps them to NIST CSF 2.0 and ISO/IEC 27001:2022.

STEP 5

Report and roadmap

Executive and technical reports, a rulebase review, a log review, a risk register, a roadmap and an Excel workbook, walked through on a call with your owner and your firewall administrator.

Read-only means read-only. The audit never commits, changes or deletes a setting, never installs software or content updates and never restarts a firewall. It is designed so your end users notice nothing.
Related

Where to go next

Sample report

How every area comes together in the executive and technical reports.

Palo Alto firewall security checklist

All 141 controls in one list.

This series

Page 9 of 13: Logging, HA, backup & Panorama

Ali Hassani, CISO, OC Security Audit
CISO-led audit

Guided by Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Every Palo Alto audit is read-only, evidence-based and written so an owner and a firewall administrator can both act on it.

FAQ

Questions IT leaders ask

Do you read our traffic logs?

We read log settings and forwarding, not the content of your traffic logs. Where a check needs counts, such as rule hits, we read the counters, not the sessions.

We have no SIEM. Is that a failure?

Forwarding to Panorama or a syslog server also counts. The report recommends the simplest option that fits your size and compliance needs.

Do you check Panorama itself?

Yes, if you use it: its administrators, management access, PAN-OS release, the connection and sync status of each managed firewall, and its backup schedule.

Will anyone notice the audit?

End users should not notice anything. Your firewall administrators and your SIEM will see logins by the audit account in the System log. We tell your IT or security contact the date, time, account and computer in advance.

Optional implementation help

OC Security Audit only audits, read-only. If you want hands-on help, IT Perfection, a managed IT business also owned by Ali Hassani, can implement the fixes and support ongoing firewall and VPN management. Using it is optional.

IT Perfection managed firewall & VPN
Team investigating a security incident together

Know what your firewall really allows, before an attacker tests it

Schedule a consultation. We scope the Palo Alto firewall audit in 30 minutes and quote one fixed price.

Read-only audit. No changes to your firewalls. Irvine, Orange County and Southern California on-site; remote nationwide.