Inline layer accepts what its rules did not match
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 parent rule's narrow match is undone inside the layer: every packet that reaches it is allowed unless a rule in the layer drops 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.
- In SmartConsole, open the inline layer and set its last rule to Drop with Track Log, or set the layer's Implicit Cleanup Action to Drop under Edit Layer > Advanced.
- 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-layer name "<layer>" implicit-cleanup-action "drop" -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-layer name "<layer>"Values to fill in1
- <layer>
- The access layer to change
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.
- Use the inline layer's name.
- If the layer's last rule accepts Any to Any on Any service, change that rule too, or the implicit action never applies.
How to confirm the fix
- Confirm from the inline layer's logs which traffic its last rule carried before the change.
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-007Disabled rule kept in the policy
- CKP-SEC-008Gateway reachable from Any
- CKP-SEC-009Rule with no hits over the counting window
- CKP-SEC-010Accept rule allows a clear-text protocol
- CKP-SEC-012Accept rule to Any destination on a lateral movement service
- CKP-SEC-015Rule covered by an earlier rule
- CKP-SEC-016Implied rules are not logged
- CKP-SEC-017Implied rule accepts ICMP requests
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.