Rule covered by an earlier rule
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
The access or block the later rule was written for is not what the gateway enforces.
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.
- In SmartConsole, move the rule above the one that covers it, or delete it if the earlier rule's action is the intended one.
- Publish, then install the policy on the gateways that use it.
Command line
Check Point mgmt_cli and Gaia clish
mgmt_cli login > id.txtmgmt_cli set access-rule layer "<layer>" rule-number <rule-number> enabled false -s id.txtmgmt_cli publish -s id.txtmgmt_cli logout -s id.txt
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Nothing here installs a policy. Publish, review, then install the policy on your gateways yourself; Gaia changes need save config.
Read it back
mgmt_cli show access-rule layer "<layer>" rule-number <rule-number>Values to fill in2
- <layer>
- The access layer to change
- <rule-number>
- The rule number in that layer, as SmartConsole shows it today
Before you type it5
- Written from the Check Point Management API reference and Gaia clish syntax, not yet run on a device. Read each line before typing it.
- Run on the management server, or add -m with the server and -u with an administrator to each call; publish makes the change visible to other sessions.
- Install the policy on the affected gateways after reviewing the published change.
- If the covered rule states the intended access, move it directly above the rule that covers it instead of disabling it, and never above the stealth rule.
- A configuration shows definitions and references, not traffic, so review this before you run it.
How to confirm the fix
- Confirm which of the two rules states the intent before moving either.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Policies
- CKP-SEC-009Rule with no hits over the counting window
- CKP-SEC-010Accept rule allows a clear-text protocol
- CKP-SEC-011Inline layer accepts what its rules did not match
- CKP-SEC-012Accept rule to Any destination on a lateral movement service
- CKP-SEC-016Implied rules are not logged
- CKP-SEC-017Implied rule accepts ICMP requests
- CKP-SEC-031Implied rule accepts DNS queries over UDP
- CKP-SEC-032Implied rule accepts DNS zone transfers over TCP
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.