Ordered layer accepts what no rule matched
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 packet must be accepted by every ordered layer. A layer that ends by accepting everything filters nothing beyond its own drop rules, which is often believed to be stricter than it is.
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 Security Policies > Access Control > Policy, right-click the layer and choose Edit Layer > Advanced, and set Implicit Cleanup Action to Drop.
- If the layer's last rule accepts Any to Any on Any service, change its action to Drop with Track Log, or narrow it.
- 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 it4
- 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 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 layer's logs which traffic its last rule or implicit cleanup carried before the change, and that the applications still work after it.
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-002Accept rule from Any to Any on Any service
- CKP-SEC-003Accept rule from Any source to internal or DMZ hosts
- CKP-SEC-004Accept rule does not log
- CKP-SEC-005Layer has no logged cleanup rule
- 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
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.