The 5 Critical controls
If you only check a few things this quarter, check these. Each one is a short path from the internet to your firewall or your network.

| ID | Control | Severity |
|---|---|---|
| PL-02 | No known-exploited vulnerability applies to the installed PAN-OS release | Critical |
| MA-02 | Administrative access is not offered on internet-facing interfaces | Critical |
| SP-01 | No rule allows any source to any destination for any application and service | Critical |
| SP-06 | Remote administration and database services are not reachable from the internet | Critical |
| NZ-07 | Port forwards (destination NAT) do not publish remote administration or database services | Critical |
All 141 controls by area
Default severity shown. In the audit, some checks raise or lower it to match what was found. The last area covers the review of the last 7 days of firewall logs.
01 · Management Access · 22 controls
| ID | Control | Default severity |
|---|---|---|
| MA-01 | Clear-text management protocols (HTTP, Telnet) are disabled on interfaces | High |
| MA-02 | Administrative access is not offered on internet-facing interfaces | Critical |
| MA-03 | Interface management profiles list the permitted administrator addresses | Medium |
| MA-04 | HTTP and Telnet are disabled on the dedicated management interface | High |
| MA-05 | Management interface restricts source addresses (permitted IP list) | Medium |
| MA-06 | Administrator sessions time out after 15 minutes or less | Medium |
| MA-07 | Administrator account lockout limits password guessing | Medium |
| MA-08 | Local administrator passwords must meet a complexity policy | Medium |
| MA-09 | API keys expire (key lifetime is set) | Medium |
| MA-10 | A legal login banner is displayed | Low |
| MA-11 | SNMP uses version 3 or is not enabled | High |
| MA-12 | Management web interface uses a TLS service profile and certificate you control | Medium |
| MA-13 | SSL/TLS service profiles require TLS 1.2 or later | Medium |
| MA-14 | Configuration commit lock is acquired automatically | Low |
| MA-15 | A log entry is written when the data plane is heavily loaded | Low |
| MA-16 | Two time servers (NTP) are configured | Medium |
| MA-17 | The firewall is synchronized to its time source | Medium |
| MA-18 | NTP uses authentication | Low |
| MA-19 | Two DNS servers are configured for the firewall | Low |
| MA-20 | The management web certificate is valid and trusted | Medium |
| MA-21 | Certificates stored on the firewall are valid and not close to expiry | High |
| MA-22 | Update server identity is verified | Low |
02 · Administrator Accounts · 7 controls
| ID | Control | Default severity |
|---|---|---|
| AA-01 | The default “admin” account is renamed or removed | Medium |
| AA-02 | Few accounts hold the Superuser role | Medium |
| AA-03 | Administrators sign in through central authentication | Medium |
| AA-04 | Administrator sign-in requires multifactor authentication | High |
| AA-05 | Service and shared accounts do not hold the Superuser role | Medium |
| AA-06 | Roles follow least privilege (not all administrators are Superuser) | Medium |
| AA-07 | Local accounts have a password profile (expiry) | Low |
03 · Platform & Lifecycle · 14 controls
| ID | Control | Default severity |
|---|---|---|
| PL-01 | PAN-OS release is still supported by the vendor | Low |
| PL-02 | No known-exploited vulnerability applies to the installed PAN-OS release | Critical |
| PL-03 | No unpatched Critical or High vendor advisory applies to the installed PAN-OS release | High |
| PL-04 | Application and threat content is current | Medium |
| PL-05 | Antivirus content is current | High |
| PL-06 | WildFire signatures are current | Medium |
| PL-07 | URL filtering database is current | Medium |
| PL-08 | Threat Prevention subscription is active | High |
| PL-09 | URL Filtering subscription is active | High |
| PL-10 | WildFire subscription is active | Medium |
| PL-11 | Hardware support entitlement is active | Medium |
| PL-13 | DNS Security subscription is active when DNS Security is configured | Medium |
| PL-12 | Device certificate is installed for cloud-delivered services | Low |
| PL-14 | Dynamic content updates are scheduled to install automatically | Medium |
04 · Security Policy · 22 controls
| ID | Control | Default severity |
|---|---|---|
| SP-01 | No rule allows any source to any destination for any application and service | Critical |
| SP-02 | Allow rules name the applications they permit (application is not “any”) | High |
| SP-03 | Allow rules use application-default ports instead of “any” service | Medium |
| SP-04 | Allow rules have security profiles attached | High |
| SP-05 | Inbound internet rules limit the permitted source addresses | Medium |
| SP-06 | Remote administration and database services are not reachable from the internet | Critical |
| SP-07 | Anonymizers and peer-to-peer applications are not allowed | High |
| SP-08 | Remote-access tools are restricted to approved users or systems | Medium |
| SP-09 | Rules do not rely on negated source or destination | Low |
| SP-10 | Disabled rules are removed | Low |
| SP-11 | No rule is shadowed (made unreachable) by an earlier rule | High |
| SP-12 | No rule duplicates another rule | Low |
| SP-13 | Rules are documented (description, owner, purpose) | Low |
| SP-14 | Temporary rules are removed on time | Medium |
| SP-15 | An explicit, logged “deny all” rule closes the rulebase | Low |
| SP-16 | The rulebase is of a manageable size | Low |
| SP-17 | Policy uses user identity (User-ID) for internal access | Low |
| SP-18 | Every enabled rule has been used | Medium |
| SP-19 | Rules unused for 180 days are reviewed | Low |
| SP-20 | Rule usage counters cover a long enough period | Low |
| SP-21 | Deny rules block known-malicious IP addresses (threat intelligence feeds) | Medium |
| SP-22 | Allow rules use application-default instead of custom port lists | Low |
05 · Object Hygiene · 5 controls
| ID | Control | Default severity |
|---|---|---|
| OH-01 | Unused address objects and groups are removed | Low |
| OH-02 | Unused service objects are removed | Low |
| OH-03 | No address group is empty | Low |
| OH-04 | Duplicate address objects are consolidated | Low |
| OH-05 | Unused security profiles and profile groups are removed | Low |
06 · Threat Prevention · 18 controls
| ID | Control | Default severity |
|---|---|---|
| TP-01 | Antivirus is applied to internet-facing allow rules | Medium |
| TP-02 | Anti-spyware is applied to internet-facing allow rules | Medium |
| TP-03 | Vulnerability protection is applied to internet-facing allow rules | Medium |
| TP-04 | URL filtering is applied to internet-facing allow rules | Medium |
| TP-05 | File blocking is applied to internet-facing allow rules | High |
| TP-06 | WildFire analysis is applied to internet-facing allow rules | High |
| TP-07 | Antivirus profiles block malware in all protocols | High |
| TP-08 | Vulnerability protection blocks critical and high severity threats | High |
| TP-09 | Vulnerability and anti-spyware profiles have no exceptions that allow threats | Medium |
| TP-10 | Anti-spyware blocks critical and high severity threats | High |
| TP-11 | DNS sinkholing and DNS Security block malicious domain lookups | High |
| TP-12 | Threat profiles in use are not detection-only | High |
| TP-13 | URL filtering blocks malware, phishing and command-and-control categories | High |
| TP-14 | Risky URL categories (new domains, dynamic DNS, anonymizers) are at least alerted | Medium |
| TP-15 | Credential phishing prevention is enabled in URL filtering | Medium |
| TP-16 | File blocking stops commonly abused file types | Medium |
| TP-17 | WildFire analysis covers all file types in both directions | High |
| TP-18 | Profile references on rules are valid | Medium |
07 · Encryption & Decryption · 6 controls
| ID | Control | Default severity |
|---|---|---|
| DC-01 | Outbound TLS traffic is decrypted for inspection | High |
| DC-02 | Decryption covers all internal zones that browse the internet | Medium |
| DC-03 | Decryption profiles block expired, untrusted and unsupported TLS sessions | Medium |
| DC-04 | Decryption profiles require TLS 1.2 and disable weak ciphers | Medium |
| DC-05 | A valid forward-trust certificate exists for SSL decryption | High |
| DC-06 | No-decrypt exceptions are narrow | Medium |
08 · VPN & GlobalProtect · 11 controls
| ID | Control | Default severity |
|---|---|---|
| VP-01 | IKEv1 aggressive mode is not used | High |
| VP-02 | IKEv2 is used for site-to-site VPN | Medium |
| VP-03 | IKE (phase 1) cryptography is strong | High |
| VP-04 | IPsec (phase 2) cryptography is strong | High |
| VP-05 | Perfect forward secrecy is enabled on IPsec tunnels | Medium |
| VP-06 | Site-to-site VPN uses certificate authentication or strong unique pre-shared keys | Low |
| VP-07 | IPsec anti-replay protection is enabled | Low |
| VP-08 | VPN tunnels are monitored for failure | Low |
| VP-09 | GlobalProtect sign-in requires multifactor authentication | High |
| VP-10 | GlobalProtect uses a TLS service profile requiring TLS 1.2 | Medium |
| VP-11 | GlobalProtect also validates client certificates (device authentication) | Low |
09 · Network & Zones · 10 controls
| ID | Control | Default severity |
|---|---|---|
| NZ-01 | Internet-facing zones have a Zone Protection profile | High |
| NZ-02 | Zone Protection profiles enable flood, reconnaissance and packet-based protection | Medium |
| NZ-03 | Packet buffer protection is enabled | Medium |
| NZ-04 | User-ID is enabled on internal zones | Low |
| NZ-05 | Every routed interface belongs to a zone | Medium |
| NZ-06 | No zone is left empty | Low |
| NZ-07 | Port forwards (destination NAT) do not publish remote administration or database services | Critical |
| NZ-08 | Every NAT rule has been used | Low |
| NZ-09 | Disabled NAT rules are removed | Low |
| NZ-10 | Guest and visitor networks are isolated from internal networks | High |
10 · 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 |
11 · 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 |
12 · Panorama & Fleet · 1 controls
| ID | Control | Default severity |
|---|---|---|
| PN-01 | The firewall reports to Panorama when it is managed centrally | Low |
13 · 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 |
Pass, Fail, Warning, Manual review
No false passes
Every control lists the data it needs. If that data could not be read, the control becomes Manual review with the reason, never a pass, and never a fail on an empty list.
Mapped to frameworks
Each control maps to NIST CSF 2.0 and ISO/IEC 27001:2022, so the same evidence serves your insurer, auditor and board. For a vendor-neutral starting point that covers any firewall, see our firewall security checklist.
Page 11 of 13: Palo Alto firewall security checklist
- 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
- 10. Sample report
- 11. Palo Alto firewall security checklist (this page)
- 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
Can we use this checklist ourselves?
Yes. It lists what we check and the default severity of each control. The audit adds the evidence, the business risk and the fix for each one.
Is this the CIS Palo Alto Firewall Benchmark?
No. It is our own control set, informed by Palo Alto Networks’ best-practice guidance and industry benchmarks such as the CIS Palo Alto Firewall Benchmark. Findings are mapped to NIST CSF 2.0 and ISO/IEC 27001:2022.
How often should we review our firewalls?
At least once a year, after major changes, and before a PAN-OS upgrade or a cyber insurance renewal.

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.


