Temporary rule with no schedule or expiry
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
A rule whose name or description marks it as temporary but which has no schedule attached has nothing in the configuration that ends it, so it stays until someone removes or disables it.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- Attach a schedule object with an end date to the rule.
- Or set a calendar reminder and a tag with the removal date.
- Review whether the access is still needed at all.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 schedule <schedule-name> schedule-type non-recurring <start-date-time>-<end-date-time>An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Nothing here commits. Review the candidate configuration, then commit it yourself.
Read it back
show vsys vsys1 schedule <schedule-name>Values to fill in3
- <schedule-name>
- A name for the schedule
- <start-date-time>
- When this access should start
- <end-date-time>
- When this access should end
Before you type it2
- A non-recurring schedule takes the form YYYY/MM/DD@HH:MM.
- Attach the schedule to the rule once you have created it.
How to confirm the fix
- Confirm with the requester whether the access is still needed.
- If it is, attach a schedule with an explicit end date.
Limits
- Rules for a permanent service that happen to contain the word test in a hostname will match. Confidence is set below 1.0 for that reason.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Policies
- PAN-SEC-002Allow rule matches any application
- PAN-SEC-003Allow rule matches any service
- PAN-SEC-004Disabled rule left in the rulebase
- PAN-SEC-005Rule has no description and no tag
- PAN-SEC-007Allow rule with logging fully disabled
- PAN-SEC-008Rule does not log at session end
- PAN-SEC-009Rule has no log forwarding profile
- PAN-SEC-019Earlier rule covers this rule with different behavior
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.