What the security policy rule review covers
Rule bases grow. A vendor needs access, a project needs a port, a test rule stays in place. After a few years most Palo Alto firewalls carry rules that are broader than anyone intended, rules that never match, and NAT rules that publish internal services to the internet.
We read every security and NAT rule on each firewall and in Panorama device groups, with its hit count, App-ID use, security profiles and logging, and score 27 controls. You also get the full rule base in Excel, with each rule flagged.

27 Security policy, NAT & object hygiene 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.
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 |
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 |
What we look for and why
Overly broad rules
Rules with any source, destination, application and service turn a next-generation firewall into a router. We find them, along with port-based rules that ignore App-ID.
What the internet can reach
Inbound NAT and security rules decide what is published. We list each published service, flag remote desktop, file sharing, SSH and database ports, and check what inspects the traffic.
Dead weight and blind spots
Rules with no hits in 90 days, rules shadowed by a broader rule above them and rules that do not log at session end. Each one is listed with its last hit.
A finding from the sample report
- Area
- Security policy
- Finding
- Two enabled rules allow all traffic
- Severity
- Critical
- Evidence
- Any-Out-Temp (trust to untrust) and Any-Any-Allow (any zone to any zone) allow every source, destination, application and service. Any-Any-Allow has no security profiles and more than 7 million hits.
- Fix
- Replace each rule with specific rules for the traffic that is actually needed, using the rule usage counters and traffic logs to identify it, then remove 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
Security profiles & threat prevention
Which allow rules inspect traffic, and which only let it through.
Zone protection & exposed services
Flood and scan protection, Authentication Portal and User-ID on internet-facing zones.
Page 4 of 13: Security policy & NAT rule review
- 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 (this page)
- 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
- 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 change or clean up rules for us?
No. The audit is read-only. The rule-base workbook marks each rule to remove, tighten or keep, and IT Perfection, a business also owned by Ali Hassani, can make the changes if you want hands-on help.
How do you know a rule is unused?
PAN-OS keeps a hit count and a last-hit time for each rule. We read those counters and note when they were last reset. A rule with no hits in 90 days is flagged for review, not deleted.
Do you review Panorama rules?
Yes. Pre-rules and post-rules from Panorama device groups are read together with local rules, in the order the firewall evaluates them.
What do you need to read hit counts?
Only the read-only audit account. Hit counts are read with an operational show command; no counter is reset.
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.


