Palo Alto PAN-OS policy examples
Rules for Palo Alto Networks firewalls running PAN-OS, one page per topic. Every rule has a passing config and a failing config, with the result rConfig gives for each. Run the rules against the output of show config running, in brace format.
| Topic | What the rules check | Rules |
|---|---|---|
| Management access | No Telnet or HTTP on the management interface or in any management profile, permitted IP addresses, a 1 to 10 minute idle timeout, a login banner, lockout after 1 to 5 failed attempts | 7 |
| AAA and local credentials | Password complexity with a minimum length of 12, admin login through an authentication profile | 2 |
| SNMP | No SNMPv2c community string | 1 |
| Logging | A syslog server profile with an address, system and configuration logs sent to syslog | 3 |
| Operational standards | Your NTP, syslog and DNS servers, a login banner, a comment on every ethernet interface, a hostname pattern, an SNMP location | 7 |
Where the examples come from
Every topic documents one file from the Palo Alto PAN-OS policy templates at release v1.5.0, which you can import into rConfig. The configs are sanitised excerpts of the sample configs that come with the templates. Where no sample fails a rule, the failing config is a sample excerpt with one line changed, and the page says which line. Every config shown was run through rConfig Pro’s evaluator with its rule, and gave the result shown.
The templates come with two hardened samples: one prints a statement per line, and the other prints some objects on one line, such as admin-lockout { failed-attempts 5; lockout-time 15; }. Every rule gives the same result on both, and some pages show both layouts.
The framework files (NIST, HIPAA and ISO/IEC 27001) collect these same rules, so they have no pages of their own here. See compliance frameworks.
If you are new to policy definitions, start with your first policy.