Firewall Support Center

Check Point Anti-Spoofing Drops Legitimate Traffic: Troubleshoot Interface Topology

Investigate legitimate traffic flagged as spoofed by checking the observed ingress interface, source network, routing design, and gateway topology.

Observe
Source address and ingress interface
Compare
Expected networks behind interface
Validate
Topology, policy installation, retest
Conceptual troubleshooting map. Example addresses and scenarios are illustrative.

Why an allow rule may not resolve the drop

A new branch network can fail immediately after a routing change even though an access rule allows it. If the gateway reports an anti-spoofing drop, investigate the source network’s relationship to the ingress interface. Anti-spoofing evaluates whether that source is expected behind the interface according to the gateway topology.

This is not evidence that every packet labeled spoofed is malicious. An outdated topology definition can also conflict with legitimate traffic. At the same time, do not assume the topology is wrong just because the user recognizes the source address. Prove the intended routing design and packet arrival first.

Capture a precise incident record

Record the affected source and destination, service, timestamp, gateway or cluster member, and ingress interface. Find the matching security log and confirm that anti-spoofing is the actual reason. A generic timeout or a normal cleanup-rule drop calls for a different investigation.

For an illustrative case, a new 10.30.40.0/24 branch arrives through an internal transit interface. Existing office subnets work. Compare the failing branch with one working subnet using the same destination and service. This controlled comparison helps separate a source-topology issue from a server or application problem.

Compare actual and configured topology

In SmartConsole, open the gateway object’s Network Management settings and inspect the relevant interface topology. Depending on release and design, the internal network definition may describe a directly connected network, a specific object or group, or route-based topology. Verify the configured method rather than assuming routes automatically update every topology definition.

Check the actual source address arriving at the gateway, including any upstream NAT. Then compare the approved network map, interface roles, routing information, and object membership. A branch behind a transit router will not necessarily fit a definition containing only the transit subnet. Conversely, a wrong physical or routed path may explain the unexpected ingress interface.

Correct the model through change control

If the documented design requires that branch behind the interface, correct the narrowly relevant topology or object definition. Review interface retrieval changes before accepting them because they may affect more than the incident subnet. Save the intended settings and install the relevant Access Control policy on the correct target, following the procedure for your release.

Keep anti-spoofing enforcement effective. Detect mode allows packets while logging them, so changing from Prevent to Detect is a security behavior change. Broad exceptions can also mask the actual routing problem. Neither should be the default fix for an unexplained drop. Review cluster consistency and dynamic-topology behavior when those features are part of the deployment.

Validate from both directions

Repeat the exact failed connection after the approved change. Verify the expected ingress interface, absence of the matching anti-spoofing drop, correct access-rule match, and a successful application response. Test a representative existing subnet as well, since repairing one branch should not break another.

Where an authorized lab or test plan exists, also confirm that an invalid source/interface combination remains blocked. Attach the before-and-after topology evidence and test results to the change record. If traffic still fails without the original anti-spoofing event, continue with routing, NAT, access policy, and packet-capture analysis instead of repeatedly expanding topology scope.

References and further reading

Check Point preventing IP spoofing, R82.10

Choose fw monitor or tcpdump