Accept rule from Any source to internal or DMZ hosts
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
Any source includes the internet. Hosts behind internal or DMZ interfaces are reachable by everyone on the services the rule names, which is acceptable only for a published service and then only on that service.
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 rule and replace Any in Source with the networks that need the access, or with the Internet object for a service published on purpose.
- Keep published services in a section of their own, on the narrowest service they need.
- 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> source "<source>" -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 in3
- <layer>
- The access layer to change
- <rule-number>
- The rule number in that layer, as SmartConsole shows it today
- <source>
- The networks that need the access
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.
- Narrowing this changes who reaches what. Confirm the new set covers the traffic the application needs.
How to confirm the fix
- Confirm from the rule's logs which sources use it before narrowing, and that the published service still answers 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 part of the 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-001Accept rule on Any service
- CKP-SEC-002Accept rule from Any to Any on Any service
- CKP-SEC-004Accept rule does not log
- CKP-SEC-005Layer has no logged cleanup rule
- CKP-SEC-006Ordered layer accepts what no rule matched
- CKP-SEC-007Disabled rule kept in the policy
- CKP-SEC-008Gateway reachable from Any
- CKP-SEC-009Rule with no hits over the counting window
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.