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.

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
| ID | Control | Default severity |
|---|---|---|
| LM-01 | Logs are forwarded to a central collector (syslog, HTTP or Panorama) | High |
| LM-02 | Syslog forwarding is encrypted (TLS) | Medium |
| LM-03 | System logs are forwarded | Medium |
| LM-04 | Configuration change logs are forwarded | Medium |
| LM-05 | Critical system events raise an alert (email, SNMP trap or HTTP) | Medium |
| LM-06 | A log forwarding profile covers traffic, threat, URL and WildFire logs | Medium |
| LM-07 | Every allow rule forwards its logs through a log forwarding profile | Medium |
| LM-08 | Rules log at session end | Medium |
| LM-09 | Traffic blocked by the default (implicit) deny is logged | Medium |
| LM-10 | Traffic allowed within a zone (intrazone-default) is logged | Low |
| LM-11 | Repeated log entries are not suppressed | Low |
High Availability & Resilience · 6 controls
| ID | Control | Default severity |
|---|---|---|
| HA-01 | The firewall is deployed as a high-availability pair | Medium |
| HA-02 | Both HA members are healthy | High |
| HA-03 | HA configuration is synchronized | Medium |
| HA-04 | HA control link has a backup | Low |
| HA-05 | HA link or path monitoring is enabled | Low |
| HA-07 | Session table capacity is adequate | Medium |
Panorama & Fleet · 1 controls
| ID | Control | Default severity |
|---|---|---|
| PN-01 | The firewall reports to Panorama when it is managed centrally | Low |
Threat Activity (log review) · 8 controls
| ID | Control | Default severity |
|---|---|---|
| TA-01 | Failed administrator sign-ins are low and come from management networks | High |
| TA-02 | Administrators sign in from trusted management addresses only | High |
| TA-04 | No critical or high-severity system events were logged | High |
| TA-03 | Configuration changes are made by named administrators | Medium |
| TA-08 | Configuration changes happen during normal working hours | Low |
| TA-05 | Critical and high-severity threats were blocked, not just alerted | High |
| TA-06 | External sources are not repeatedly attacking published services | Medium |
| TA-07 | No internal host is contacting command-and-control or malicious domains | High |
What we look for and why
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.
Accurate time
Without NTP, log times drift and incidents cannot be lined up across systems. We check the time sources and the time zone.
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.
A finding from the sample report
- 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
A read-only audit in five steps
Scoping call
We confirm the firewalls, Panorama, sites, GlobalProtect and who on your side should be told before the run. 30 minutes.
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.
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.
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.
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.
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.
Page 9 of 13: Logging, HA, backup & Panorama
- 1. Palo Alto Firewall Security Audit (hub)
- 2. PAN-OS management interface security
- 3. PAN-OS end of life & vulnerabilities
- 4. Security policy & NAT rule review
- 5. Security profiles & threat prevention
- 6. SSL/TLS decryption review
- 7. GlobalProtect & IPsec VPN security
- 8. Zone protection & exposed services
- 9. Logging, HA, backup & Panorama (this page)
- 10. Sample report
- 11. Palo Alto firewall security checklist
- 12. Pricing
- 13. How to audit a Palo Alto firewall
Palo Alto Networks, PAN-OS, Panorama, GlobalProtect, Prisma, Strata, WildFire, App-ID and User-ID are trademarks or registered trademarks of Palo Alto Networks, Inc. OC Security Audit is an independent assessment firm and is not affiliated with, sponsored by or endorsed by Palo Alto Networks. All sample companies, firewalls and findings shown on this page are fictional and used for illustration only. The assessment is read-only: no configuration changes, commits or active tests are performed.

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.
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.

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.


