Skip to content
Guides & References

Palo Alto PAN-OS policy templates

The Palo Alto PAN-OS policy templates in rconfig/pro-policy-definitions v1.5.0: what each rule checks, minimum versions, references and framework files.

Policy LibraryUpdated
On this page

Palo Alto PAN-OS policy templates

Policy templates for Palo Alto Networks firewalls running PAN-OS, from the palo-alto/ folder. They check the brace format returned by show config running: nested { } containers with one statement per line ending in ;. This page documents release v1.5.0. See importing a policy template to load one into rConfig.

For worked examples of these rules, with a passing and a failing config for each, see the Palo Alto PAN-OS platform pages.

Hardening definitions

PAN-OS management access

pro-policy-definitions / palo-alto /panos-management-access.policyView on GitHub
Kind
Hardening
Rules
7
Minimum rConfig
8.3.0
Release
v1.5.0

No Telnet or HTTP on the management interface or in any interface management profile, management access limited to permitted IP addresses, an administrator idle timeout of 1 to 10 minutes, a login banner, and administrator lockout after 1 to 5 failed attempts.

Rule Method What it checks
Telnet is not enabled on the management interface (fails on disable-telnet no) must_not_match_regex No disable-telnet no; statement. Passes whether or not disable-telnet yes; is printed.
HTTP is not enabled on the management interface (fails on disable-http no) must_not_match_regex No disable-http no; statement.
No interface management profile enables Telnet or HTTP (fails on telnet yes or http yes) must_not_match_regex No telnet yes; or http yes; statement anywhere. https yes; does not match.
Management access is limited to permitted IP addresses (deviceconfig system permitted-ip) evaluate_block The deviceconfig block has a permitted-ip list with at least one entry.
The administrator idle timeout is 1 to 10 minutes (deviceconfig setting management idle-timeout) evaluate_block The deviceconfig block has idle-timeout with a value from 1 to 10.
A login banner is configured (deviceconfig system login-banner) must_match_regex A login-banner statement with text after it.
Administrator accounts lock after 1 to 5 failed attempts (admin-lockout failed-attempts) evaluate_block The deviceconfig block has failed-attempts with a value from 1 to 5.

References

Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.

Rule NIST SP 800-53 HIPAA (45 CFR) ISO/IEC 27001:2022
Telnet is not enabled on the management interface (fails on disable-telnet no) AC-17 164.312(a)(1) A.8.5
HTTP is not enabled on the management interface (fails on disable-http no) CM-7 164.312(c)(1) A.8.5
No interface management profile enables Telnet or HTTP (fails on telnet yes or http yes) CM-7 164.312(c)(1) A.8.5
Management access is limited to permitted IP addresses (deviceconfig system permitted-ip) AC-17 None A.8.20
The administrator idle timeout is 1 to 10 minutes (deviceconfig setting management idle-timeout) AC-3 None A.8.5
A login banner is configured (deviceconfig system login-banner) None None A.8.5
Administrator accounts lock after 1 to 5 failed attempts (admin-lockout failed-attempts) AC-7 None A.8.5

Known limitations

  • PAN-OS prints only settings that are in the configuration. Telnet and HTTP are off by default, so those rules fail on the insecure value rather than requiring the secure one. A permitted IP list, an idle timeout (default 60 minutes) and a lockout (default unlimited) are not set by default, so those rules need the setting.
  • The permitted IP, idle timeout and lockout rules are scoped to deviceconfig. A permitted-ip list in an interface management profile, or an idle timeout elsewhere (for example GlobalProtect), does not count.
  • The scope anchors rely on rConfig matching scope: against the line with its indentation removed. Every PAN-OS container is indented under config {, so ^deviceconfig \{$ matches only because the indentation is removed first.

PAN-OS AAA

pro-policy-definitions / palo-alto /panos-aaa.policyView on GitHub
Kind
Hardening
Rules
2
Minimum rConfig
8.3.0
Release
v1.5.0

Password complexity enabled with a minimum length of 12 or more, and administrator authentication through an authentication profile.

Rule Method What it checks
Password complexity is enabled with a minimum length of 12 or more (mgt-config password-complexity) evaluate_block The password-complexity block has enabled yes; and minimum-length from 12 to 16.
Administrators authenticate through an authentication profile (deviceconfig system authentication-profile) evaluate_block The deviceconfig block has an authentication-profile statement with a profile name.

References

Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.

Rule NIST SP 800-53 HIPAA (45 CFR) NIST CSF 1.1 ISO/IEC 27001:2022
Password complexity is enabled with a minimum length of 12 or more (mgt-config password-complexity) IA-5 None None A.5.17
Administrators authenticate through an authentication profile (deviceconfig system authentication-profile) AC-2 164.312(a)(1) PR.AC-1 A.8.5

Known limitations

  • No rule checks the administrator password hash: which hash each PAN-OS release writes could not be confirmed.
  • The authentication profile rule checks that a profile is named, not what the profile contains.

PAN-OS SNMP

pro-policy-definitions / palo-alto /panos-snmp.policyView on GitHub
Kind
Hardening
Rules
1
Minimum rConfig
8.0.2
Release
v1.5.0

No SNMPv2c community.

Rule Method What it checks
No SNMPv2c community is configured (fails on snmp-community-string) must_not_match_regex No snmp-community-string statement anywhere in the config.

References

Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.

Rule NIST SP 800-53 HIPAA (45 CFR) ISO/IEC 27001:2022
No SNMPv2c community is configured (fails on snmp-community-string) SC-12 164.312(e)(1) A.8.5

Known limitations

  • No rule checks the SNMPv3 user algorithms: whether PAN-OS prints default SNMPv3 algorithms could not be confirmed.

PAN-OS logging

pro-policy-definitions / palo-alto /panos-logging.policyView on GitHub
Kind
Hardening
Rules
3
Minimum rConfig
8.3.0
Release
v1.5.0

A syslog server profile with a server address, and system and configuration logs forwarded to syslog.

Rule Method What it checks
A syslog server profile has a server address (shared log-settings syslog … server) evaluate_block Each syslog block has a server statement with an address.
System logs are forwarded to syslog (log-settings system match-list send-syslog) evaluate_block In log-settings, the system match list has a send-syslog entry, printed over several lines or on one.
Configuration logs are forwarded to syslog (log-settings config match-list send-syslog) evaluate_block In log-settings, the config match list has a send-syslog entry, printed over several lines or on one.

References

Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.

Rule NIST SP 800-53 HIPAA (45 CFR) NIST CSF 1.1 ISO/IEC 27001:2022
A syslog server profile has a server address (shared log-settings syslog … server) AU-2, AU-12 164.312(b) DE.CM-1 A.8.15
System logs are forwarded to syslog (log-settings system match-list send-syslog) AU-2, AU-12 164.312(b) None A.8.15
Configuration logs are forwarded to syslog (log-settings config match-list send-syslog) AU-2, AU-12 164.312(b) None A.8.15

Known limitations

  • A scoped rule fails when no block matches its scope, so a firewall with no syslog server profile fails the syslog server rule.
  • A log forwarding profile that sends traffic and threat logs to syslog does not count for the system and configuration log rules.
  • Multi-vsys layouts are not covered. On a multi-vsys firewall, log settings can sit under each vsys, and the scoped rules may see several blocks or none.

Framework files

Framework files are generated from the hardening files above. Each one collects every hardening rule that lists a reference for one framework, copied unchanged, with the control reference added to the start of its description (for example NIST AC-17: ...). The rule tables, references and known limitations are in the topic sections linked below.

Framework File Rules Minimum rConfig Collects rules from
NIST SP 800-53 panos-nist-800-53.policy 12 8.3.0 PAN-OS AAA, PAN-OS logging, PAN-OS management access, PAN-OS SNMP
NIST CSF 1.1 panos-nist-csf.policy 2 8.3.0 PAN-OS AAA, PAN-OS logging
HIPAA Security Rule (45 CFR 164.312) panos-hipaa.policy 8 8.3.0 PAN-OS AAA, PAN-OS logging, PAN-OS management access, PAN-OS SNMP
ISO/IEC 27001:2022 Annex A panos-iso27001.policy 13 8.3.0 PAN-OS AAA, PAN-OS logging, PAN-OS management access, PAN-OS SNMP

A framework file lists checks relevant to that framework. It is not a certification or a full assessment, and a device that passes it is not certified against the framework.

Operational standards

PAN-OS operational standards

pro-policy-definitions / palo-alto /panos-operational-standards.policyView on GitHub
Kind
Operational standards
Rules
7
Minimum rConfig
8.3.0
Release
v1.5.0

Checks drift from your own operational standard, not a hardening baseline: standard NTP, syslog and DNS servers, a login banner, a comment or link-state down on every ethernet interface, a hostname naming pattern and an SNMP location. Replace the example values (RFC 5737 addresses such as 192.0.2.10, and the hostname pattern) with your own before use.

Rule Method What it checks
NTP servers are set to your standard (replace 192.0.2.10 and 192.0.2.11) evaluate_block The config has ntp-server-address 192.0.2.10; and ntp-server-address 192.0.2.11;.
Syslog servers are set to your standard (replace 192.0.2.20 and 192.0.2.21) evaluate_block Each syslog block has server 192.0.2.20; and server 192.0.2.21;.
DNS servers are set to your standard (replace 192.0.2.30 and 192.0.2.31) evaluate_block The dns-setting block has primary 192.0.2.30; and secondary 192.0.2.31;.
A login banner is set (login-banner, any text; nothing to replace) must_match_regex A login-banner statement with text after it.
Every ethernet interface has a comment or is set to link-state down (nothing to replace) evaluate_block Every ethernetN/N block has a non-empty comment or link-state down;.
The hostname follows your naming pattern (replace the example pattern [a-z]{3}-fw[0-9]{2}, for example dub-fw01) evaluate_block The deviceconfig block has a hostname statement that matches the pattern exactly.
An SNMP location is set (snmp-setting snmp-system location, any text; nothing to replace) evaluate_block The snmp-system block has a location statement with text after it.

Known limitations

  • PAN-OS has two NTP server slots, primary-ntp-server and secondary-ntp-server, so the NTP rule checks both addresses. The NTP, syslog and DNS rules check that each standard server is configured, not that no other server is.
  • The rules are regular expressions: escape the dots when you replace an address, for example 192\.0\.2\.20.
  • Subinterfaces sit inside their parent’s block, under units, so a parent passes the interface rule if any line in its block, including a subinterface, has a comment. Aggregate (ae) and VLAN interfaces are not checked. Unused ports are usually not in the configuration at all.
  • A scoped rule fails when no block matches, so a firewall with no syslog server profile or no snmp-system block fails those rules.

Type to search.