CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. Come to CPUG CON 2008 EUROPE in Switzerland on September 8th - 9th!
    Two days full of technical content for Check Point administrators in the beautiful Swiss Alps!
    We already have 52 attendees signed up from 14 countries!
2. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 8/25, 10/6, 11/3, 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3, 9/7.
3. Corrent S3500 SecureXL Turbocards For Sale - Last Six Remaining - Get Your Spares!
4. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > Topology Issues
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2007-10-31
infrared013 infrared013 is offline
Junior Member
 
Join Date: 2006-05-23
Posts: 9
Rep Power: 0
infrared013 has an average reputation (10+)
Default Spoofing?

Can anyone explain to me what a "spoofing group" is and why i need to add it in the topology configuration for an interface?
Reply With Quote
  #2 (permalink)  
Old 2007-10-31
melipla melipla is offline
Senior Member
 
Join Date: 2006-01-25
Posts: 781
Rep Power: 3
melipla has an average reputation (10+)
Default Re: Spoofing?

In short, anti-spoofing was designed to stop a computer from faking another computer's IP address. Spoofing is generally used by viruses or zombie PC's to hide their origin so that they can perform malicious activities like spread themselves or DDoS someone without being caught.

On a specific Interface properties for a gateway, you have two options sections: Topology and Anti-Spoofing. Identifying the topology of an interface is listing all the IPs that could originate from behind that interface. The Anti-spoofing defaults to blocking all IPs that you don't define as being in the topology.

An example would be, you have a DMZ of 10.1.1.1. A computer is infected and wants to serve malicious code out to unsuspecting victims, that computer sends out packets saying "I'm Google, here's your malicious webpage". What Anti-Spoofing will do is say, Google aka 192.168.1.1 doesn't exist on this interface so I won't allow this traffic to pass, thus saving the victim from being infected. Now you're the hero.

HTH
Reply With Quote
  #3 (permalink)  
Old 2007-11-05
plymouth plymouth is offline
Junior Member
 
Join Date: 2006-03-17
Posts: 8
Rep Power: 0
plymouth has an average reputation (10+)
Default Re: Spoofing?

What is happening in the case of every other packet being dropped for suspected spoofing?
My topology is similar to the many describe on the this topic. A segment one hop removed from my R55 cluster.
A host in that segment is pinging a host behind an R61 adjacent to my R55.

An icmp packet is accepted and passed through to the destination.
The next icmp paket, same source and destination, is dropped for suspected spoofing.

These spoofing errors only occur on the R55 cluster.

The requisite topology configurations appear to be in order.

How is this resolved?
Reply With Quote
  #4 (permalink)  
Old 2007-11-06
MarioL MarioL is offline
Senior Member
 
Join Date: 2007-01-18
Location: London
Posts: 375
Rep Power: 2
MarioL has an average reputation (10+)
Default Re: Spoofing?

By default "anti-spoofing" tends to be configured as the subnet behind the interface. If you have several subnets there, you should create all of them as network objects, then create a group and add them all in, and finally add that in the interface anti-spoofing (using "specific").

This way the firewall "knows" that all those subnets are connected there and stops blocking the traffic.

To add to what melipla already said, another very important reason why you WILL want anti-spoofing configured is so that I can't sent a packet with the source IP as one of your own internal networks and get it to be accepted by the policy because of your rules. Even if the replies would be routed in, this would allow blind attacks, DoS, etc...
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -7. The time now is 09:11.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
LinkBacks Enabled by vBSEO 3.0.0