System for finding potential origins of spoofed internet protocol attack traffic

• US 8,806,634 B2
• Filed: 01/27/2012
• Issued: 08/12/2014
• Est. Priority Date: 04/05/2005
• Status: Active Grant

• Current Assignee: PacSec3, LLC (Pueblo Nuevo LLC)
• Original Assignee: Donald N. Cohen, Krishnamurthy Narayanaswamy
• Inventors: Cohen, Donald N., Narayanaswamy, Krishnamurthy
• Primary Examiner(s): Schwartz, Darren B
• Application Number:
  US13/360,153
• Publication Number:
  US 20130028259A1
• Time in Patent Office: 928 Days
• Field of Search: 726 11- 14, 726 22- 24
• US Class Current: 726/23
• CPC Class Codes: H04L 2463/146 Tracing the source of attacks
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002

Abstract

The invention computes approximate origins of data packets transmitted over the Internet. Law enforcement agencies and network operators can use it to assign responsibility for observed Internet activities. The invention uses a small number of cooperative locations (incoming links on routers or switches) to provide link identification data: whether a packet or did or did not traverse that location. The system uses these cooperative places to generate the link signature of a data packet—which cooperative locations observed and did not observe the packet. Potential origin locations are divided into pre-computed blocks that have the same link signatures to given destination locations. The blocks are used to generate reverse routing data, potential source addresses for different link signatures. Variations of the invention store relevant link identification and reverse routing data to find the origins of past packets or to compute the origins of packets from partial information about packets of interest.

Claims

1. A system for identifying a set of potential origins of Internet Protocol data packets on a network by a computer, said system comprising:

a plurality of cooperating locations on said network, said cooperating locations providing accurate and reliable information as to whether an identified data packet did or did not pass through said cooperating locations at an identified point in time;

a plurality of non-cooperating locations on said network, said non-cooperating locations receiving and transmitting data packets yet providing no or false information as to whether said identified data packet did or did not pass through said non-cooperating locations at said identified point in time;

a means for querying each of said cooperating locations as to whether said identified data packet did or did not pass through said cooperating locations at said identified point in time;

a response from each of said cooperating locations;

each response being a first predetermined value if said identified data packet did pass through said cooperating locations at said identified point in time;

each response being a second predetermined value if said identified data packet did not pass through said cooperating locations at said identified point in time;

said first predetermined value being different from said second predetermined value;

a link signature for each of said identified data packets;

said link signature comprising a string of digits including a plurality of said first predetermined values and a plurality of said second predetermined values;

a table of origins, said table of origins comprising identified destination locations, unions of all link signatures matching data packet information available for said identified data packet and origin locations consistent with said link signatures;

a sub-system for dividing said locations into blocks, where such blocks comprise said cooperating locations that have identical link signatures for routing the identified data packet to any location from another identified block at said identified point in time; and

a reverse routing table, said table reverse routing table comprising link signatures identifying at least one valid routing between selected locations in each destination/source pair of blocks in said network for said identified point in time; and

a means for said system to identify the set of possible origins for an identified data packet when a system user supplies a destination location and data packet information for said identified data packet.

2. The system as described in claim 1, wherein said table of origins comprises blocks having identified destination locations within them, unions of all link signatures matching data packet information available for said identified data packet and origin locations consistent with said link signatures in said reverse routing table.

3. The system as described in claim 1, wherein said cooperating locations comprise routers or switches on said network.

4. The system as described in claim 1, wherein said link signature for said identified data packet is gathered and maintained over a period of time, thereby permitting historical inquiries of said system.

5. The system as described in claim 1, wherein said link signatures identifying all possible valid routings between a selected cooperating location in each destination/source pair of blocks in said network for said reverse routing table are gathered further comprising:

an identified destination location in each block;

an identified responding source location in each block;

a probe packet;

said probe packet causing said source location to send an identifiable response packet to said destination location;

a means for deriving derived link signatures for each destination/source pair of locations from information returned by said identifiable response;

a means for assigning said derived link signatures as link signatures indicating valid routing to all destination locations within said block from all potential source locations within any other block; and

said link signature derived from said identifiable response to said probe packet being recognized as being one of those that could be observed for packets forwarded from said given source block to said given destination block at a given point in time.

6. The system as described in claim 1, wherein said link signature in said reverse routing table are gathered and maintained over a period of time, thereby permitting historical inquiries of said reverse routing table.

7. The system as described in claim 1, wherein definitions of said blocks are updated as new link signature information related to locations within said blocks is received, thereby maintaining said blocks as groups of locations having identical link signatures for routing a packet to an identified location at said identified point in time.

8. The system as described in claim 1, further comprising tools for collecting and storing information at cooperating locations related to data packets passing through said cooperating locations over identified periods of time, said information comprising at least link signature and routing information related to said packets, thereby providing further means for identifying potential origins for data packets based upon partial packet information.

9. A method for identifying a set of potential origins of Internet Protocol data packets on a network having cooperating locations and non-cooperating locations, by a computer said method comprising the steps of:

identifying a plurality of cooperating locations and non-cooperating locations in said network, said cooperating locations providing accurate and reliable information as to whether an identified data packet did or did not pass through each cooperating location at an identified point in time;

said non-cooperating locations receiving and transmitting data packets yet providing no or false information as to whether said identified data packet did or did not pass through each non-cooperating location at said identified point in time;

querying each of said cooperating locations as to whether said identified data packet did or did not pass through said cooperating locations at an identified point in time;

receiving a response from each of said cooperating locations;

each response being a first predetermined value if said identified data packet did pass through said cooperating locations at said identified point in time;

each said response being a second predetermined value if said identified data packet did not pass through said cooperating locations at said identified point in time;

said first predetermined value being different from said second predetermined value;

creating a link signature for each of said identified data packets, said link signature comprising a string of digits including a plurality of said first predetermined values and a plurality of said second predetermined values;

developing a table of origins from said link signatures, said table of origins comprising identified destination locations, unions of all link signatures matching data packet information available for said identified data packets and origin locations consistent with said link signatures;

dividing said locations into blocks, where such blocks comprise locations that have identical link signatures for routing a packet to any location from another identified block at said identified point in time;

creating a reverse routing table, said reverse routing table comprising link signatures identifying at least one valid routing between selected locations in each destination/source pair of blocks in said network for said identified point in time;

allowing a system user to supply a destination location and data packet information regarding an identified data packet; and

performing computations to identify said set of possible origins for said identified data packet.

10. The method as described in claim 9, comprising the further step of:

developing a table of origins wherein said table of origins comprises blocks having identified destination locations within them, unions of all link signatures matching data packet information available for said identified data packet and origin locations consistent with said link signatures in said reverse routing table.

11. The method as described in claim 9, wherein said cooperating locations comprise routers or switches on said network.

12. The method as described in claim 9, further comprising the step of gathering and maintaining said link signature for said identified data packet over a period of time on said computer, thereby permitting historical inquiries of said system.

13. The method as described in claim 9, wherein said method of developing link signatures identifying all possible valid routings between a selected cooperating location in each destination/source pair of blocks in said network for said reverse routing table further comprising the steps of:

identifying a destination location in each block;

identifying a responding source location in each block;

sending a probe packet to said source location;

said probe packet causing said source location to send an identifiable response packet to said destination location;

deriving derived link signatures for each destination/source pair of locations from information returned by said identifiable response;

making an assignment of said derived link signatures as link signatures indicating valid routing for all destination locations within said block to all potential source locations within any other block; and

recognizing said link signature derived from said identifiable response to said probe packet as being one of those that could be observed for packets forwarded from said given source block to said given destination block at a given point in time.

14. The method as described in claim 9, further comprising the steps of:

gathering and maintaining said link signatures in said reverse routing table over a period of time; and

thereby permitting historical inquiries of said reverse routing table.

15. The method as described in claim 9, further comprising the step of updating definitions of said blocks as new link signature information related to cooperating locations within said blocks is received, thereby maintaining said blocks as groups of locations having identical link signatures for routing a packet to an identified location at said identified point in time.

16. The method as described in claim 9, further comprising the step of collecting and storing information at cooperating locations related to data packets passing through said cooperating locations over identified periods of time, said information comprising at least link signature and routing information related to said packets, thereby providing further means for identifying potential origins for data packets based upon partial packet information.