Anti-spoofing off or detect only
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 arriving on the wrong interface with an internal source address passes the rules written for internal networks.
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 gateway or cluster object > Network Management, edit the interface, and under Topology select Perform Anti-Spoofing based on interface topology, Action Prevent, Spoof Tracking Log.
- 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 simple-gateway name "<gateway>" interfaces.<interface-index>.name "<interface>" interfaces.<interface-index>.anti-spoofing true interfaces.<interface-index>.anti-spoofing-settings.action "prevent" -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 simple-gateway name "<gateway>"Values to fill in3
- <gateway>
- The gateway or cluster object to change
- <interface-index>
- The interface's position in the object's interfaces list
- <interface>
- The interface 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.
- For a cluster, use set simple-cluster with the cluster object's name instead of set simple-gateway.
- The interfaces list is replaced as a whole: send every interface of the gateway, not only the one that changes.
How to confirm the fix
- Watch Logs & Monitor for anti-spoofing drops after the install, which show an interface topology that needs correcting.
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 Interfaces and Segmentation
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.