Hit count is off
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
Without hit counts nobody can see which rules carry traffic, so rules that matter and rules nobody uses look the same.
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 Menu > Global properties > Hit Count and select Enable Hit Count, then on the gateway object select Hit Count under General Properties.
- 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 global-properties hit-count.enable-hit-count true -s id.txtmgmt_cli set simple-gateway name "<gateway>" hit-count true -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 global-propertiesmgmt_cli show simple-gateway name "<gateway>"
Values to fill in1
- <gateway>
- The gateway or cluster object 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.
- For a cluster, use set simple-cluster with the cluster object's name instead of set simple-gateway.
How to confirm the fix
- Confirm the Hits column shows values after the install.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
CIS Check Point Firewall Benchmark v1.1.0
Covers the whole recommendation
Where a control aligns with a recommendation of the CIS Check Point Firewall Benchmark v1.1.0, that recommendation is cited as a reference. Only that version was checked. A reference is not a certification.
More in Security Policies
- 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
- CKP-SEC-033Implied rule accepts RIP
- CKP-SEC-034Implied rule accepts DHCP and DNS to the gateway
- CKP-SEC-019Out of state TCP packets are not dropped
- CKP-SEC-035Out of state ICMP packets are not dropped
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.