PAN-OS management access
Rules for how admins reach the firewall: no clear-text protocols, management limited to known addresses, idle sessions closed, a warning before login, and lockout after failed logins. They come from the panos-management-access policy template.
Every example on this page was checked with rConfig Pro's policy engine on Each of the 16 configs below was run through rConfig Pro’s evaluator with the rule above it, and gave the result shown. The configs are sanitised excerpts of the sample configs that come with the template.
All the rules come from panos-management-access.policy in the policy templates (v1.5.0). Import the whole file with Import Templates (see importing a policy template), or copy one rule into your own definition. The Palo Alto PAN-OS templates page lists the file’s known limitations. Run the rules against show config running (brace format).
| Rule | Method | Since |
|---|---|---|
| No Telnet on the management interface | must_not_match_regex |
8.0.2 |
| No HTTP on the management interface | must_not_match_regex |
8.0.2 |
| No Telnet or HTTP in interface management profiles | must_not_match_regex |
8.0.2 |
| Management limited to permitted IP addresses | evaluate_block |
8.3.0 |
| Admin idle timeout of 1 to 10 minutes | evaluate_block |
8.3.0 |
| Login banner | must_match_regex |
8.0.0 |
| Admin lockout after 1 to 5 failed attempts | evaluate_block |
8.3.0 |
No Telnet on the management interface
Telnet sends logins in clear text. Telnet on the management interface is off by default, so this rule only fails when the config turns it on with disable-telnet no;. It passes whether or not disable-telnet yes; is printed.
// Telnet is not enabled on the management interface (fails on disable-telnet no)#[must_not_match_regex]/(^|[{;])\s*disable-telnet no;/mdeviceconfig { system { service { disable-telnet yes; disable-http yes; } }}Why: Telnet is disabled.
deviceconfig { system { service { disable-telnet no; disable-http no; } }}Why: disable-telnet no turns Telnet on.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | AC-17 |
| HIPAA (45 CFR) | 164.312(a)(1) |
| ISO/IEC 27001:2022 Annex A | A.8.5 |
Tested with: sample excerpts from PAN-OS 11.1.4 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
No HTTP on the management interface
HTTP sends the web UI login in clear text. Like Telnet, it is off by default, so the rule fails only on disable-http no;.
// HTTP is not enabled on the management interface (fails on disable-http no)#[must_not_match_regex]/(^|[{;])\s*disable-http no;/mdeviceconfig { system { service { disable-telnet yes; disable-http yes; } }}Why: HTTP is disabled.
deviceconfig { system { service { disable-telnet no; disable-http no; } }}Why: disable-http no turns HTTP on.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | CM-7 |
| HIPAA (45 CFR) | 164.312(c)(1) |
| ISO/IEC 27001:2022 Annex A | A.8.5 |
Tested with: sample excerpts from PAN-OS 11.1.4 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
No Telnet or HTTP in interface management profiles
An interface management profile lets admins reach the firewall on a data interface. This rule fails if any profile has telnet yes; or http yes;. https yes; does not match, so HTTPS is allowed.
// No interface management profile enables Telnet or HTTP (fails on telnet yes or http yes)#[must_not_match_regex]/(^|[{;])\s*(telnet|http) yes;/minterface-management-profile { MGMT-HTTPS-SSH { https yes; ssh yes; ping yes; permitted-ip { 192.0.2.0/24; 198.51.100.0/24; } } ALLOW-PING { ping yes; }}Why: The profiles allow HTTPS, SSH and ping only.
interface-management-profile { MGMT-HTTPS-SSH { https yes; ssh yes; ping yes; permitted-ip { 192.0.2.0/24; 198.51.100.0/24; } } ALLOW-PING { ping yes; }}Why: The same profiles printed on one line give the same result.
interface-management-profile { MGMT-HTTPS-SSH { https yes; http yes; ssh yes; ping yes; permitted-ip { 192.0.2.0/24; 198.51.100.0/24; } }}Why: The MGMT-HTTPS-SSH profile allows HTTP.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config 1 | pass | PASS |
| Passing config 2 | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | CM-7 |
| HIPAA (45 CFR) | 164.312(c)(1) |
| ISO/IEC 27001:2022 Annex A | A.8.5 |
Tested with: sample excerpts from PAN-OS 11.1.4 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
Management limited to permitted IP addresses
Without a permitted IP list, any address that can route to the management interface can try to log in. This rule checks the deviceconfig block for a permitted-ip list with at least one entry. A list in an interface management profile does not count.
// Management access is limited to permitted IP addresses (deviceconfig system permitted-ip)#[evaluate_block]scope: ^deviceconfig \{$all: - regex: '/(^|[{;])\s*permitted-ip \{\s*[^\s}]/m'deviceconfig { system { login-banner "Authorised use only. All activity is monitored and recorded."; service { disable-telnet yes; disable-http yes; } permitted-ip { 192.0.2.0/24; 198.51.100.0/24; } authentication-profile AUTH-TACACS; }}Why: Management is limited to two networks.
deviceconfig { system { service { disable-telnet no; disable-http no; } }}Why: There is no permitted-ip list under deviceconfig.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | AC-17 |
| ISO/IEC 27001:2022 Annex A | A.8.20 |
Tested with: sample excerpts from PAN-OS 11.1.4 (synthetic). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
Admin idle timeout of 1 to 10 minutes
The default idle timeout is 60 minutes and is not printed. This rule needs idle-timeout with a value from 1 to 10 in the deviceconfig block. A timeout set elsewhere, for example for GlobalProtect, does not count.
// The administrator idle timeout is 1 to 10 minutes (deviceconfig setting management idle-timeout)#[evaluate_block]scope: ^deviceconfig \{$all: - regex: '/(^|[{;])\s*idle-timeout ([1-9]|10);/m'deviceconfig { setting { management { idle-timeout 10; admin-lockout { failed-attempts 5; lockout-time 15; } } }}Why: Idle admin sessions close after 10 minutes.
deviceconfig { setting { management { } config { rematch yes; } }}Why: No idle-timeout is set, so the 60 minute default applies.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | AC-3 |
| ISO/IEC 27001:2022 Annex A | A.8.5 |
Tested with: sample excerpts from PAN-OS 11.1.4 (synthetic). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
Login banner
A login banner warns users before they log in. This rule passes if any login-banner line has text after it.
// A login banner is configured (deviceconfig system login-banner)#[must_match_regex]/(^|[{;])\s*login-banner \S/mdeviceconfig { system { hostname dub-fw01; domain example.com; login-banner "Authorised use only. All activity is monitored and recorded."; }}Why: A login banner is set.
deviceconfig { system { hostname dub-hq-fw02; domain example.com; service { disable-telnet no; disable-http no; } }}Why: There is no login-banner line.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| ISO/IEC 27001:2022 Annex A | A.8.5 |
Tested with: sample excerpts from PAN-OS 11.1.4 (synthetic). Minimum rConfig 8.0.0 (must_match_regex). Editions: Pro, Vector, Enterprise.
Admin lockout after 1 to 5 failed attempts
By default PAN-OS does not lock an admin account after failed logins. This rule needs failed-attempts with a value from 1 to 5 in the deviceconfig block.
// Administrator accounts lock after 1 to 5 failed attempts (admin-lockout failed-attempts)#[evaluate_block]scope: ^deviceconfig \{$all: - regex: '/\bfailed-attempts [1-5];/m'deviceconfig { setting { management { idle-timeout 10; admin-lockout { failed-attempts 5; lockout-time 15; } } }}Why: Accounts lock after 5 failed attempts.
deviceconfig { setting { management { idle-timeout 10; admin-lockout { failed-attempts 5; lockout-time 15; } } }}Why: The same setting printed on one line gives the same result.
deviceconfig { setting { management { } config { rematch yes; } }}Why: There is no admin-lockout, so failed attempts are unlimited.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config 1 | pass | PASS |
| Passing config 2 | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | AC-7 |
| ISO/IEC 27001:2022 Annex A | A.8.5 |
Tested with: sample excerpts from PAN-OS 11.1.4 (synthetic). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
Related reference
- Palo Alto PAN-OS policy templates: every rule in
panos-management-access.policy, its references and known limitations. - Policy Definitions: the definition file format and every method.
- Policy Assignments: run a definition against your devices.
- Policy Compliance Results: read the pass and fail results.