|Publication number||US6725378 B1|
|Application number||US 09/293,479|
|Publication date||Apr 20, 2004|
|Filing date||Apr 15, 1999|
|Priority date||Apr 15, 1998|
|Publication number||09293479, 293479, US 6725378 B1, US 6725378B1, US-B1-6725378, US6725378 B1, US6725378B1|
|Inventors||Christoph L. Schuba, Ivan V. Krsul, Diego Zamboni, Eugene H. Spafford, Aurobindo M. Sundaram, Markus G. Kuhn|
|Original Assignee||Purdue Research Foundation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (20), Non-Patent Citations (6), Referenced by (209), Classifications (10), Legal Events (8)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application claims the benefit of U.S. Provisional Patent Application Ser. No. 60/081,829 filed Apr. 15, 1998 that is hereby incorporated by reference in its entirety herein.
The present invention relates to computer network security, and more particularly, but not exclusively, relates to protection from denial of service attacks caused by initiating, but not completing a number of spurious connections through the Internet.
Concomitant with the development of computer networks, schemes to degrade or defeat operation of such networks have been devised. In response, a host of techniques have been proposed to improve network security. U.S. Pat. No. 5,884,025 to Baehr et al.; U.S. Pat. No. 5,842,040 to Hughes et al.; U.S. Pat. No. 5,826,014 to Coley et al.; U.S. Pat. No. 5,822,434 to Caronni et al.; U.S. Pat. No. 5,604,803 to Aziz; U.S. Pat. No. 5,511,122 to Atkinson; and U.S. Pat. No. 5,481,611 to Owens et al. are cited as sources of additional background information regarding various attempts to improve network security.
One particular type of attack monopolizes available network resources in such a manner that legitimate users are denied service. This type of “denial of service attack” has been recognized in various contexts. One especially troublesome denial of service attack for Internet Protocol (IP) based networks is called “SYN flooding.” SYN flooding arises when an attacker sends many Transmission Control Protocol (TCP) connection requests, each initiated with a “SYNchronize” (also called SYN) packet, to a victim's machine. Each request causes the targeted host to instantiate data structures out of a limited pool of resources; however, because the source address for each of these SYN packets is illegitimate or “spoofed,” completion of a proper connection is impossible. Consequently, the limited resources of the targeted host are quickly used up in response to the spurious SYN packets so that no more incoming TCP connections can be established—thus denying further legitimate access. The SYN flooding attack exploits weaknesses with TCP/IP (Transmission Control Protocol/Internet Protocol) that cannot be corrected without significant protocol modifications. Moreover, this type of denial of service attack can be launched with little effort, and is difficult to trace back to its originator.
As a result, there is a need for protective techniques that reduce, if not eliminate, the impact of denial of service attacks, such as SYN flooding.
One form of the present invention includes a unique computer network monitoring technique. A further form of the present invention includes a unique defense for denial of service attacks.
In another form of the present invention, network messages passing to one or more hosts from an untrusted network are actively monitored. Suspect messages are identified. The behavior of each suspect message is tracked in terms of a number of conditionally coupled states to determine whether any of the suspect messages present a security threat requiring action.
In yet another form, network messages may be classified into one or more other categories besides the suspect category. By way of nonlimiting example, TCP packets may be categorized as having an unacceptable source address, suspect source address, or acceptable source address.
In an additional form, host resources allocated in response to connection initiation requests from an untrusted network are released by monitoring such requests, determining which requests are unacceptable or suspect, and selectively sending a command that changes the status of such requests from the perspective of the hosts. In one nonlimiting example, host resources dedicated to incomplete TCP connections that are quickly saturated by suspect SYN packets may be released by sending ACKnowledge packets (also called ACK packets) corresponding to the SYN packets. In another nonlimiting example, host resources may be relieved by closing spurious connections through transmission of a ReSeT packet (also called a RST packet).
In still another form, a technique of the present invention includes detecting a number of SYN packets sent from an untrusted network to a destination host to regulate spurious connection attempts. The corresponding source address of each SYN packet is classified in one of a plurality of different categories, the categories including a suspect source address category and an unacceptable source address category. TCP packet behavior is monitored for each address classified in the suspect source address category with a state machine process including at least three different conditionally coupled states, and a RST packet is sent to the destination host for any address classified in the unacceptable source address category.
Accordingly, it is one object of the present invention to provide a unique computer network monitoring technique.
It is another object of the present invention to provide a unique defense for denial of service attacks.
Further objects, forms, features, advantages, aspects, and benefits of the present invention will become apparent from the description and drawings provided herein.
FIG. 1 is a diagram illustrating a Transmission Control Protocol (TCP) three way handshake packet sequence.
FIG. 2 is a diagram illustrating a SYN flood packet sequence.
FIG. 3 is a schematic view of a network system.
FIG. 4 is a flow chart illustrating a routine performed by the system of FIG. 3.
FIG. 5 is a diagram of a first packet sequence illustrative of certain aspects of the routine of FIG. 4.
FIG. 6 is a diagram of a second packet sequence illustrative of certain aspects of the routine of FIG. 4.
FIG. 7 is a diagram illustrating a state machine process operated as part of the routine of FIG. 4.
FIG. 8 is a diagram of a third packet sequence illustrative of certain aspects of the routine of FIG. 4 and the state machine process of FIG. 7.
For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Any alterations and further modifications in the described embodiments, and any further applications of the principles of the invention as described herein are contemplated as would normally occur to one skilled in the art to which the invention relates.
The preferred embodiments of the present invention include an active monitor that performs a process to reduce service degradation caused by SYN flooding. In one form, the process includes classifying source addresses of SYN packets as being of an acceptable, unacceptable, or suspect type. Suspect source addresses may be further processed in accordance with a state machine having a number of conditionally linked states. The monitor selectively sends various packets to one or more hosts receiving the SYN packets to reduce or eliminate service denial.
To better explain various aspects of the preferred embodiments, certain features of the Transmission Control Protocol/Internet protocol (TCP/IP) are first described. The Internet Protocol (IP) is the standard network layer protocol of the Internet that provides a connectionless, best effort packet delivery service. IP defines the basic unit of the data transfer used throughout an IP network, called a datagram. The delivery of datagrams is not guaranteed. Datagrams may be lost, duplicated, delayed, or delivered out of order. IP is connectionless, because each packet is treated independently of the others—each may travel over different paths and some may be lost while others are delivered. IP provides best-effort delivery, because packets are not discarded unless resources are exhausted or underlying networks fail. Datagrams are routed towards their destination host. A set of rules characterizes how hosts and gateways should process packets, how and when error messages should be generated, and when packets should be discarded.
To ensure reliable communications for applications and services that need them, the Transmission Control Protocol (TCP) is available. It resides between IP and the application layer. TCP provides a reliable, connection-oriented data stream delivery service. As long as there is link layer communication between two communicating endpoints, TCP guarantees that datagrams will be delivered in order, without errors, and without duplication. It provides these services by using flow control mechanisms, such as the sliding window protocol, and adaptive retransmission techniques.
Referring to FIG. 1, a diagram is provided that illustrates the TCP packet sequence of a three-way handshake needed to establish a TCP connection. Before data can be transmitted between a source host S and a destination host D, TCP needs to establish a connection between source host S and destination host D. The connection establishment process is called the three-way handshake. The three-way handshake is established by exchanging certain TCP packet types between source host S and destination host D. The TCP packet types are distinguished by dedicated flag bits set in a TCP header code field and are listed in Table I as follows:
TCP Header Flag Bits
It should be appreciated that, under appropriate conditions, more than one of the flag bits may be set in the same TCP packet.
The first transmission in the three-way handshake is from source host S to destination host D in the form of a SYN packet (SYN flag bit set) while destination host D is in the LISTEN state. The second message, from destination host D to source host S, has both the SYN and ACK bit flags set (SYN+ACK) indicating that destination host D acknowledges the SYN packet and is continuing the handshake. At this point, destination host D is in the SYN_RECVD state. The third message, from source host S to destination host D has its ACK bit flag set, and is an indication to destination host D that both hosts S and D agree that a connection has been established, resulting in the CONNECTED state of destination host D. The third message may contain user payload data. Datagrams D1 and D2 represent data exchanges that take place after proper establishment-of the TCP connection.
The three-way handshake also initializes the sequence numbers for a new connection between source host S and destination host D. The sequence numbers are represented in FIG. 1 by subscripts to the packet abbreviations. Sequence numbers are needed by the TCP protocol to enable reliable packet delivery and retransmission. Source host S sends an initial sequence number x with the first datagram: SYNx. In the second message, destination host D acknowledges the first datagram with ACKx+1 and sends its own sequence number y: SYNy. Source host S acknowledges the destination host D's packet in the final message of the three-way handshake with ACKy+1.
For any TCP connection, there are memory structures that need to be allocated by both endpoints. For an example under the BSD style of network code, three memory structures need to be allocated at each endpoint. The socket structure (socket) holds information related to the local end of the communication link: protocol used, state information, addressing information, connection queues, buggers and flags. TCP uses the Internet protocol control block structure (inpcb) at the transport layer to hold information such as TCP state information, IP address information, port numbers, IP header prototype and options, and a pointer to a routing table entry for the destination address. The TCP control block structure (tcpcb) contains TCP specific information such as timer information, sequence number information, flow control status, and out-of-band data. The combined size of these data structures for a single TCP connection may typically exceed 280 bytes. Although the data structures and allocation schemes used to accommodate TCP connection formation differ with various types of operating systems, generally every TCP connection establishment requires an allocation of significant memory resources.
When a SYN packet arrives at a port on which a TCP server is listening, the above-mentioned data structures are allocated. There is a limit on the number of concurrent TCP connections that can be in a half-open connection state, called the SYN−RECVD state (i.e., SYN received). When the maximum number of half-open connections per port is reached, TCP discards all new incoming connection requests until it has either cleared or completed some of the half-open connections. Typically, several ports can be flooded in this manner, resulting in degraded service or worse. Moreover, it should be appreciated that without a limit on the number of half-open connections, a different denial of service attack would result in which an attacker could request so many connections that the target machine's memory is completely exhausted by allocating data structures for half-open TCP connections. Table II illustrates the half-open connection states that may be accommodated by various operating systems as follows:
Backlog + Grace
Windows NTs 3.51
Windows NTw 4.0
With reference to FIG. 1, detailed below is one typical example of what happens from the point of view of destination host D (alternatively designated as “server”):
1. A packet arrives at the destination machine when the TCP state machine is in the LISTEN state.
2. If the datagram checksum is incorrect, the packet will be discarded, and the client is expected to retransmit it.
3. The tcpcb associated with the connection is searched for. If it is not found, the server will discard the packet and will send a RST (i.e., inform the client that it reset the connection). If the tcpcb exists, but the TCP state machine is not in the LISTEN state, the server will discard the packet, but will not send a RST (this would, for example, be the case when the server is just coming up, but has not yet started listening).
4. If the SYN packet arrives for a socket that is in the LISTEN state, the above mentioned data structures will be allocated. However, the server will also set a flag indicating that it will destroy the connection and associated memory structures if it encounters an error. If the backlog queue is full, the server will consider this an error and will terminate the connection.
5. The packet will be ignored if it contains a RST. If it contains an ACK, it will be discarded and a RST sent to the other side. The packet will be discarded if the SYN bit is not set. Otherwise, the server copies information, such as the client's address information, into a buffer, connects its tcpcb to the client, and initializes its initial send sequence (ISS) number y.
6. The server now sends the second message of the three-way handshake (SYNx+1 and ACKy) to the client. The state changes to SYN−RECVD. A connection establishment timer is started for this half-open connection. The connection remains in the SYN−RECVD state until either an ACK (the third message of the handshake) is received, resulting in the CONNECTED state, or a timer expires. This timer is usually set to about 75 seconds. During this period of time retransmissions of the first and second message of the three-way handshake may occur. When the timer expires, all memory structures associated with the connection are deallocated, and the server goes back to the LISTEN state.
As previously described, TCP implementations are designed with a small limit on how many half-open connections per port are possible at any given time. With reference to FIG. 2, a SYN flood attack by attacker A is next described. Attacker A initiates a SYN flooding attack by sending many connection requests with spoofed source addresses to the victim machine, destination host D. In response, destination host D allocates resources to each half-opened connection. Once the limit of half-open connections is reached, destination host D refuses all successive connection establishment attempts—including any legitimate attempts. This condition exists until either the timer expires, or some connections are completed or reset. If the timer expires for a particular half-open connection, the host will reset the connection and release all the resources allocated for it. It should be appreciated that neither outgoing connection attempts nor connections that are already established are affected by this type of attack.
If a spoofed SYN packet contains the source address of a reachable IP source host S, that host will receive the second message of the three-way handshake generated by destination host D. Not expecting the SYN+ACK without having requested a connection, the source host S will send a RST packet to destination host D, and consequently cause destination host D to reset the connection. It is therefore in the interest of attacker A to forge source addresses that do not belong to hosts that are reachable from the victim destination host D.
If attacker A wants the denial of service condition to last longer than the timeout period, he needs to continuously keep requesting new connections from the victim destination host D. The amount of CPU and network bandwidth required by attacker A for a sustained attack is negligible.
Typical SYN flooding attacks can vary several parameters: the number of SYN packets per source address sent in a batch (=: batch size), the delay between successive batches (=: delay), and the mode of source address allocation (=: mode). For the purposes of SYN flooding, “spoofed” source addresses of the corresponding SYN packets generally include source addresses of source hosts S that are not reachable from destination host D, because the addresses are not yet allocated, assigned, or associated with source hosts S that are very slow in response, virtually or physically disconnected, or down. Possible modes of source address allocation include: a single address, a short list of addresses, or no list at all.
The single address approach takes as a parameter a single spoofed address that is used as the source address of all SYN packets. In the absence of any defense, this mode of attack is as effective as the other three modes described. For the short list mode, attacker A can generate a small pool of addresses and use them as source addresses to generate SYN packets. In the no list mode, attacker A can use a different, randomly generated source address for each successive batch of SYN packets.
Referring to FIG. 3, network system 20 of one embodiment of the present invention is illustrated. System 20 includes a trusted, local area network 22 operatively coupled to an untrusted network 24, such as the internet, by gateway 50. Untrusted network 24 includes an attacker 40 and an external source host 30. In practice, many more hosts would be present on network 24, but are not shown to preserve clarity.
In addition to gateway 50, monitoring resource 51 is also operatively coupled to network 22. A monitoring program, monitor 52, is configured for execution by monitoring resource 51 to protect other resources on network 22 from SYN flooding by sources from untrusted network 24, such as from attacker 40, and still facilitate establishment of connections with legitimate external sources, such as source host 30. Among the resources protected by monitor 52 are a number of destination hosts 54.
Destination hosts 54 are each operatively coupled to network 22. While only three destination hosts 54 are shown in FIG. 3, in practice many more destinations may be coupled to network 22 and correspondingly protected by monitor 52. Also operatively coupled to network 22 is local source host 56. In practice, many more source hosts may also be present on network 22, but are not illustrated to preserve clarity. Furthermore, with regard to network 22 and network 24, it should be understood that designations of a host as a source or destination type are for clarity of explanation, and that in practice equipment coupled to network 22 may typically operate as both a source and destination relative to another host. In one nonlimiting example, network 22 is Ethernet based.
It is preferred that monitoring resource 51 be in the form of a programmable digital computer that is operable to execute monitor 52. Monitoring resource 51 may be in the form of a single processing unit operatively coupled to network 22 or a distributed system of different units operatively coupled to network 22, as would occur to those skilled in the art. Resource 51 includes various hardware elements such as one or more Input/Output (I/O) devices 53 and memory 55. It is preferred I/O devices 53 include at least one means of administrative input to facilitate selective communication and control of monitor 52. I/O devices 53 may include a keyboard, mouse, visual display, and/or printer to name only a few possibilities.
Programming for resource 51, including monitor 52, is encoded on a computer readable medium, such as memory 55. Memory 55 may be of the random access, solid-state type, the optical type (such as a Compact Disk type), the electromagnetic type (such as a floppy or hard disk), or another type as would occur to those skilled in the art. Furthermore, memory 55 may be a combination of one or more of these types. As schematically shown in FIG. 3, at least a portion of memory 55 may be in the form of a removable computer readable medium 58, such as a disk or cartridge.
Also schematically represented in FIG. 3 is database 57 stored in memory 55. Database 57 may be accessed by monitor 52 and is preferably initially installed, updated, and maintained by administrative input via I/O devices 53.
Monitor 52 is preferably arranged to capture IP/TCP datagrams passing along network 22 regardless of source or destination, including any TCP packets involved in a three-way handshake with destinations 54. Preferably, monitor 52 does not block or interfere with the transmission of packets to destination hosts 54, but rather examines the packets and reacts by selectively generating packets for one or more of destination hosts 54. Further, when a destination host 54 responds with a packet, such as a SYN+ACK packet, monitor 52 permits it to proceed. Monitor 52 is also arranged to asynchronously time selected events and respond to administrative inputs.
FIG. 4 is a flow chart illustrating routine 60 of monitor 52. Routine 60 begins with stage 62. Stage 62 initiates the detection and examination of TCP packets sent to destination hosts 54 along network 22. After stage 62, conditional 63 is encountered. Conditional 63 tests whether a new TCP packet has been sent to one of destination hosts 54 along network 22. If a new TCP packet is not detected, then conditional 78 is encountered to determine whether monitoring is to continue. Generally, monitoring continues absent an administrative input to the contrary via I/O devices 53. If monitoring is to continue, control loops back to conditional 63 to continue packet detection. If monitoring is not continued, routine 60 halts.
When conditional 63 results in the detection of a TCP packet, conditional 64 is next encountered. Conditional 64 tests whether the newly detected packet is of the SYN variety. If the detected TCP packet is not of the SYN variety, the new packet is submitted to state machine 100 in stage 76. The operation of state machine 100 is described in detail in connection with FIG. 7 hereinafter.
If the newly detected TCP packet is of the SYN variety, then source address classification operation 65 is initiated. Operation 65 begins with accessing database 57 of monitor 52 at stage 66. After accessing database 57, operation 65 continues with conditional 68. At conditional 68, the source address of the newly detected TCP packet is compared to a set of entries in database 57 representative of acceptable addresses. If the source address of the newly detected packet is one of the acceptable addresses, classification operation 65 is exited and the acceptable source address is submitted to state machine 100 in stage 76 for continued monitoring. Correspondingly, routine 60 takes no further action for any packet having a source address classified as acceptable or “perfect,” and presumes the three way handshake illustrated in FIG. 1 will be completed in the usual manner.
If, on the other hand, the source address of a newly detected SYN packet is not one of the acceptable addresses, control flows to conditional 70 to test whether the newly detected SYN packet has a source address that is unacceptable or “evil” as represented by one of another set of entries in database 57. If so, classification operation 65 of routine 60 is exited and a RST packet is sent in stage 72 to the targeted destination host 54 that receives the SYN packet with an unacceptable address to close the corresponding TCP connection. By closing the connection, the RST packet frees resources of the targeted destination host 54. FIG. 5 is a diagram illustrating the packet sequence observed for processing through state 72 for a SYN packet with an unacceptable source address. Any subsequent RST packets are ignored with regard to the FIG. 5 packet sequence. From stage 72, routine 60 continues to stage 76.
The two sets of entries in database 57 corresponding to acceptable and unacceptable addresses, respectively, are preferably input via one or more I/O devices 53. These addresses may be updated as needs require. Preferably, the acceptable addresses include addresses of well-known, frequently used source hosts, such as local source host 56, and the unacceptable addresses include as a minimum those addresses (or address ranges) that are reserved, impossible (such as net 0.0.0.0 or 127.0.0.0), or confirmed spoof addresses (such as nets 10.0.0.0, 172.16.0.0, and 192.168.0.0).
Source addresses of SYN packets that are neither of the acceptable or unacceptable type, as determined by accessing database 57, are designated “suspect” addresses. For a suspect address, an ACK packet is sent to the targeted host destination 54 that has received the detected SYN packet. This ACK packet is arranged to appear as though is originates from the same source address as the detected SYN packet. Sending the ACK packet completes the three way handshake, moving the TCP connection from a half-open status (SYN−RECVD) to a completed status (CONNECTED). Changing a connection from half-open status to completed status removes it from the limited backlog queue of the targeted destination host 54 receiving the ACK packet, freeing it to establish another half-TCP connections. The diagram of FIG. 6 illustrates the sequence of packets corresponding to processing through stage 74 for a newly detected SYN packet with a suspect address. As shown in FIG. 6, if an ACK packet is later received by the targeted destination host 54 from a legitimate host, such as source host 30, it is simply ignored.
After stage 74, the suspect address is submitted to state machine 100 in stage 76. Referring to FIG. 7, state machine 100 is shown in greater detail. State machine 100 is a process of monitor 52 that further evaluates and reacts to selected TCP packets in accordance with source address classification by operation 65.
Referring to state machine 100, any detected TCP packet that has an acceptable source address is placed in acceptable address state 102. State 102 is not conditionally coupled to any other states of state machine 100—in other words, source addresses classified in state 102 remain in state 102. Condition loop 104 of state 102 is triggered when either an ACK packet, a RST packet, or a SYN packet with the acceptable address is detected with monitor 52 via routine 60. In response, the corresponding source address remains in state 102. Accordingly, state 102 signifies that monitoring routine 60 does not interfere with the usual handling of TCP packets with an acceptable source address.
Any detected TCP packet that has an unacceptable source address is placed in unacceptable address state 105. State 105 is not conditionally coupled to any other states of state machine 100—in other words, source addresses classified in state 105 remain in state 105. Conditional loop 106 is triggered whenever an ACK packet or a RST packet is detected that has an unacceptable address. In response, the corresponding source address remains in state 105. Conditional loop 107 is triggered whenever a SYN packet with an unacceptable address is detected. SYN packet detection causes the transmission of an appropriately configured RST packet to close the connection in stage 72 as described in connection with FIG. 4. Like loop 106, there is no change of state caused by loop 107. Accordingly, any attempts to request a connection with one of destinations 54 that has an unacceptable address result in closing the connection to release destination host 54 resources.
Generally, states 102 and 105 are symbolic of the manner in which each of two categories of addresses are treated after classification by operation 65, and do not involve any appreciable amount of processing beyond the stages shown in FIG. 4. The third category, suspect addresses, are further classified and processed in accordance with the conditionally coupled states 108 of state machine 100. States 108 are initially engaged at null address state 110. All source addresses that are not in state 102 or 105, that is not included in database 57, are initially considered to be in null address state 110. Unlike acceptable and unacceptable addresses, a database entry for every suspect addresses is preferably not kept to conserve storage resources.
From the null address state 110, transition path 112 is followed if a SYN packet for the suspect source address in the null state is detected and submitted to state machine 100 from routine 60. In response, the source address is placed in new address state 114 and a record of the corresponding datagram is established, including information such as IP addresses, ports, and sequence numbers. This information is saved in case a RST packet needs to be sent to the corresponding source address in response to a later condition. A timestamp for the given source address is also established when the transition from null address state 110 to new address state 114 occurs. This timestamp is used in connection with certain timer events described in connection with other states 108. New address state 114 corresponds to suspect source addresses for which there is too little information to determine if a connection with a destination host 54 should be allowed.
New address state 114 is coupled to conditional loop 116. Loop 116 is triggered by the receipt of further SYN packets, symbolizing that new address state 114 is maintained in response to multiple SYN packets. In response to the triggering of loop 116, current datagram information is recorded for use in case a RST packet needs to be sent to a corresponding destination host 54 in a different state. Transition path 118 conditionally couples new address state 114 and bad address state 120. If a given source address remains in state 114 for a time period T1 determined by monitor 52 relative to its timestamp, an “expiry” timer event is generated. A change of state from new address state 114 to bad address state 120 along transition path 118 is triggered by an expiry event.
Conditional loop 122 is triggered by the detection of any successive SYN packets with the suspect source address in bad address state 120. The triggering of conditional loop 122 causes a RST packet to be sent to the targeted destination host 54 in the manner described in connection with stage 72. Accordingly, the connection associated with the source address in state 120 is closed, freeing resources of the targeted destination host 54. Conditional loop 122 returns to bad address state 120 with each successive SYN packet corresponding to the suspect source address. As a result, suspect addresses that are likely to be spoofed reach bad address state 120 after first being monitored at the new address state 114 for the time period T1. The diagram of FIG. 8 illustrates the packet sequence for a suspect source address in bad address state 120 for which a RST packet is transmitted to the targeted destination host by triggering conditional loop 122 with another SYN packet. Preferably, time period T1 is set to a value significantly less than the default time-out duration commonly associated with the targeted destination host 54. However, it should be appreciated that a time period T1 that is too low may adversely impact the formation of relatively slow legitimate connections.
On the other hand, the detection of a ACK packet or a RST packet for the suspect address in the bad address state 120 triggers a change of state along transition path 124 to new address state 114. This change of state also causes the timestamp associated with the suspect source address undergoing the transition to be updated for timing another potential expiry timer event.
Besides bad address state 120, new address state 114 is also conditionally coupled to good address state 128. The good address state corresponds to suspect source addresses that are most likely legitimate. For a suspect address placed in the new address state 114, a change of state to good address state 128 via transition path 126 is triggered by detection of an ACK packet or RST packet with that suspect source address. This change of state also results in the updating of the timestamp associated with the suspect source address.
Once in the good address state 128, subsequent ACK or RST packets trigger conditional loop 130 which does not cause further changes of state. Subsequent SYN packets trigger conditional loop 132 that also does not cause a change of state. However, unlike conditional loop 130, conditional loop 132 updates the timestamp for the corresponding suspect source address in the good address state.
If a suspect source address remains in the good address state 128 for a predetermined time period T2 without any TCP packet traffic having this address, a “staleness” timer event is generated that triggers a change of state from good address state 128 to new address state 114 along transition path 134. Also, this event results in a fresh datagram information record and timestamp updating to prepare for the possibility of a later transition to bad address state 120 in response to generation of an expiry timer event while in new address state 114. Thus in accordance with state machine 100, a given suspect address that was once “good” can become “bad” in response to suspect TCP packet behavior.
Further, it should also be appreciated that the transition of a suspect address from null address state 110 to good address state 128 may occur directly when an associated ACK packet or a RST packet is detected, indicating a legitimate connection. This change of state is represented by transition path 136 and is also accompanied by timestamp updating. The operation of state machine 100 is arranged to halt in accordance with conditional 78 of routine 60.
It should be appreciated that routine 60 classifies source addresses into one of a number of categories. Classification operation 65 classifies the source IP addresses of TCP packets in one of three categories: (1) acceptable, (2) unacceptable, or (3) suspect. State machine 100 further classifies suspect addresses as: (1) never seen (=: null); (2) correctly behaving (=: good) hosts; (3) potentially spoofed (=: new), or (4) as most certainly spoofed (=: bad).
In accordance with these classifications, monitor 52 sends a RST packet to unacceptable or bad addresses, closing corresponding connections to free resources of destination hosts 54. Further, an ACK packet is sent for suspect source addresses to free resources of the destination hosts 54 by removing connections from a half-open backlog queue. Further, states 108 of state machine 100, conditionally coupled by transition paths 112, 118, 124, 126, 134, and 136, permit suspect address classification to change based on observed behavior of network traffic and asynchronous events, such as expiry and staleness event timers.
In other embodiments of the present invention, an ACK packet transmission in stage 74 may not be performed or may only be selectively performed for suspect addresses. Additionally or alternatively, in one further embodiment the acceptable address classification is not performed. In still another embodiment, all addresses are considered suspect and correspondingly submitted to a state machine process rather than each being initially classified into one of a plurality of different categories by operation 65. Furthermore, it is envisioned that other embodiments of the present invention may be applied to improve security of networks having a protocol other than TCP/IP.
Yet another embodiment of the present invention includes timing the frequency of unacceptable and/or bad source address SYN packets and using a conventional statistical model to predict arrival of the next spoofed SYN packet. A RST may be sent for any packets arriving in the spoofed time interval to enhance protection of destination hosts 54. In still another embodiment suited to SYN flooding based on pseudorandom number generated addresses, routines may be implemented that detect use of pseudorandom sequences generated by various conventional generators to identify spoofed SYN packets. In other embodiments, as trusted address ranges are identified, they may be incorporated into the acceptable address testing of classification operation 65. An additional embodiment of the present invention includes gathering statistics concerning good and bad address states to selectively add the corresponding good or bad source addresses as acceptable or unacceptable address entries in database 57, respectively.
Another embodiment of the present invention includes a monitoring resource responsive to TCP connection packets to detect a source address for each and determine if the source address is of a suspect type. The monitoring resource is operable to permit one or more hosts to receive the TCP connection packets and is programmed with a state machine having a number of conditionally coupled states to process an address of the suspect type. The states include a new address state, a good address state, and a bad address state.
An additional embodiment of the present invention includes a computer readable medium encoded with a monitoring program to reduce performance degradation of a network caused by a denial of service attack with SYN flooding. The program is operable to detect each of a plurality of SYN packets sent on the network to one or more hosts and classify a source address for each of the SYN packets in one of a plurality of categories. A first one of the categories corresponds to a suspect source address and a second one of the categories corresponds to an unacceptable source address. The program defines a state machine process to monitor any address in the first one of the categories in accordance with at least three conditionally coupled states. The program is operable to send a corresponding RST packet to any of the one or more hosts receiving a SYN packet with an address classified in the second one of the categories.
Other embodiments include monitoring TCP connection status from an untrusted network to a number of destinations operatively coupled to the untrusted network to reduce a performance degradation caused by SYN packet flooding from the untrusted network. A TCP connection source address is classified in a good address state when an ACK packet or a RST packet is received from the untrusted network with the source address. The source address is reclassified from the good address state to a new address state after a first predetermined time period passes without receiving the ACK packet or the RST packet from the untrusted network. Furthermore, the source address is reclassified from the new address state to a bad address state after a second predetermined time period passes without receiving the ACK packet or the RST packet from the untrusted network. A RST packet is sent to a corresponding one of the destinations to close a respective connection for a source address in the bad address state.
All publications, patents, and patent applications cited in this specification are herein incorporated by reference as if each individual publications, patent, or patent application were specifically and individually indicated to be incorporated by reference and set forth in its entirety herein. While the invention has been illustrated and described in detail in the figures and foregoing description, the same is to be considered as illustrative and not restrictive in character, it being understood that only the preferred embodiment has been shown and described and that all changes, equivalents, and modifications that come within the spirit of the invention as defined by the following claims are desired to be protected.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5481611||Dec 9, 1993||Jan 2, 1996||Gte Laboratories Incorporated||Method and apparatus for entity authentication|
|US5511122||Jun 3, 1994||Apr 23, 1996||The United States Of America As Represented By The Secretary Of The Navy||Intermediate network authentication|
|US5604803||Jun 3, 1994||Feb 18, 1997||Sun Microsystems, Inc.||Method and apparatus for secure remote authentication in a public network|
|US5606668||Dec 15, 1993||Feb 25, 1997||Checkpoint Software Technologies Ltd.||System for securing inbound and outbound data packet flow in a computer network|
|US5699513 *||Mar 31, 1995||Dec 16, 1997||Motorola, Inc.||Method for secure network access via message intercept|
|US5724425||Jun 10, 1994||Mar 3, 1998||Sun Microsystems, Inc.||Method and apparatus for enhancing software security and distributing software|
|US5751812||Aug 27, 1996||May 12, 1998||Bell Communications Research, Inc.||Re-initialization of an iterated hash function secure password system over an insecure network connection|
|US5822434||Jun 19, 1996||Oct 13, 1998||Sun Microsystems, Inc.||Scheme to allow two computers on a network to upgrade from a non-secured to a secured session|
|US5826014||Feb 6, 1996||Oct 20, 1998||Network Engineering Software||Firewall system for protecting network elements connected to a public network|
|US5828846 *||Nov 22, 1995||Oct 27, 1998||Raptor Systems, Inc.||Controlling passage of packets or messages via a virtual connection or flow|
|US5842040||Jun 18, 1996||Nov 24, 1998||Storage Technology Corporation||Policy caching method and apparatus for use in a communication device based on contents of one data unit in a subset of related data units|
|US5845068||Dec 18, 1996||Dec 1, 1998||Sun Microsystems, Inc.||Multilevel security port methods, apparatuses, and computer program products|
|US5850449||May 19, 1997||Dec 15, 1998||Sun Microsystems, Inc.||Secure network protocol system and method|
|US5884025||Feb 4, 1997||Mar 16, 1999||Sun Microsystems, Inc.||System for packet filtering of data packet at a computer network interface|
|US5991881 *||Nov 8, 1996||Nov 23, 1999||Harris Corporation||Network surveillance system|
|US5999932 *||Jan 13, 1998||Dec 7, 1999||Bright Light Technologies, Inc.||System and method for filtering unsolicited electronic mail messages using data matching and heuristic processing|
|US6061798 *||Oct 19, 1998||May 9, 2000||Network Engineering Software, Inc.||Firewall system for protecting network elements connected to a public network|
|US6070242 *||Dec 9, 1996||May 30, 2000||Sun Microsystems, Inc.||Method to activate unregistered systems in a distributed multiserver network environment|
|US6304975 *||Aug 2, 2000||Oct 16, 2001||Peter M. Shipley||Intelligent network security device and method|
|US6453345 *||May 7, 1997||Sep 17, 2002||Datadirect Networks, Inc.||Network security and surveillance system|
|1||Advisory CA-96.21; TCP SYN Flooding and IP Spoofing Attacks, CERT Advisory, Sep. 19, 1996.|
|2||Check Point Firewall-1 White Paper, Check Point Software Technologies, Ltd., Version 3.0 -Jun. 1997.|
|3||Defining Strategies to Protect Against TCP SYN Denial of Service Attacks, Security Advisory, Cisco Systems, Inc., 1996.|
|4||Firewalls fend off invasions from the Net, Steven W. Lodin and Christoph L. Schuba; IEEE Spectrum, Feb. 1998, pp. 26-34.|
|5||*||RFC 793, Transmission Control, Protocol, ilnformation Sciences Institute, University of Southern Califiornia, USA, 1981.*|
|6||SUN Microsystems Security Bulletin #00136; Oct. 9, 1996.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6947726 *||Nov 19, 2001||Sep 20, 2005||The Boeing Company||Network security architecture for a mobile network platform|
|US6983325 *||Dec 28, 2000||Jan 3, 2006||Mcafee, Inc.||System and method for negotiating multi-path connections through boundary controllers in a networked computing environment|
|US7039721 *||Jul 11, 2001||May 2, 2006||Mcafee, Inc.||System and method for protecting internet protocol addresses|
|US7043759||Aug 16, 2001||May 9, 2006||Mazu Networks, Inc.||Architecture to thwart denial of service attacks|
|US7047303 *||Jul 26, 2001||May 16, 2006||International Business Machines Corporation||Apparatus and method for using a network processor to guard against a “denial-of-service” attack on a server or server cluster|
|US7047564 *||Oct 31, 2001||May 16, 2006||Computing Services Support Solutions, Inc.||Reverse firewall packet transmission control system|
|US7120934 *||Mar 29, 2001||Oct 10, 2006||Ishikawa Mark M||System, method and apparatus for detecting, identifying and responding to fraudulent requests on a network|
|US7124440||Aug 16, 2001||Oct 17, 2006||Mazu Networks, Inc.||Monitoring network traffic denial of service attacks|
|US7137144 *||Feb 11, 2000||Nov 14, 2006||International Business Machines Corporation||Technique of defending against network connection flooding attacks|
|US7143180 *||Aug 16, 2001||Nov 28, 2006||International Business Machines Corporation||System and method for protecting a TCP connection serving system from high-volume of TCP connection requests|
|US7171688 *||Jun 25, 2001||Jan 30, 2007||Intel Corporation||System, method and computer program for the detection and restriction of the network activity of denial of service attack software|
|US7213264||Jan 31, 2002||May 1, 2007||Mazu Networks, Inc.||Architecture to thwart denial of service attacks|
|US7246376 *||Apr 3, 2002||Jul 17, 2007||Nortel Networks Limited||Method and apparatus for security management in a networked environment|
|US7254133 *||Jul 15, 2002||Aug 7, 2007||Intel Corporation||Prevention of denial of service attacks|
|US7254633 *||Feb 4, 2003||Aug 7, 2007||University Of Massachusetts Amherst||Probabilistic packet marking|
|US7278159||Aug 16, 2001||Oct 2, 2007||Mazu Networks, Inc.||Coordinated thwarting of denial of service attacks|
|US7284272 *||May 31, 2002||Oct 16, 2007||Alcatel Canada Inc.||Secret hashing for TCP SYN/FIN correspondence|
|US7298753 *||Feb 10, 2003||Nov 20, 2007||Cisco Technology, Inc.||Technique for managing heavy signaling traffic that is directed to a particular signaling control unit|
|US7299297 *||Jun 19, 2002||Nov 20, 2007||Lucent Technologies Inc.||Method and apparatus for protecting electronic commerce from distributed denial-of-service attacks|
|US7299489 *||May 25, 2000||Nov 20, 2007||Lucent Technologies Inc.||Method and apparatus for host probing|
|US7342926 *||Jun 20, 2002||Mar 11, 2008||Nokia Corporation||Prevention of spoofing in telecommunications systems|
|US7359962||Apr 30, 2002||Apr 15, 2008||3Com Corporation||Network security system integration|
|US7363656||Nov 3, 2003||Apr 22, 2008||Mazu Networks, Inc.||Event detection/anomaly correlation heuristics|
|US7391725||May 18, 2004||Jun 24, 2008||Christian Huitema||System and method for defeating SYN attacks|
|US7398317||Sep 5, 2001||Jul 8, 2008||Mazu Networks, Inc.||Thwarting connection-based denial of service attacks|
|US7415025||Dec 29, 2000||Aug 19, 2008||Cisco Technology, Inc.||Method and apparatus for clearing a large number of connections in an ATM network|
|US7418492||Jun 20, 2002||Aug 26, 2008||P-Cube Ltd.||System and a method for testing network communication devices|
|US7441272||Jun 9, 2004||Oct 21, 2008||Intel Corporation||Techniques for self-isolation of networked devices|
|US7451489||Aug 31, 2004||Nov 11, 2008||Tippingpoint Technologies, Inc.||Active network defense system and method|
|US7454499 *||Nov 7, 2002||Nov 18, 2008||Tippingpoint Technologies, Inc.||Active network defense system and method|
|US7454792||Aug 31, 2004||Nov 18, 2008||Tippingpoint Technologies, Inc.||Active network defense system and method|
|US7464410 *||Dec 11, 2001||Dec 9, 2008||At&T Corp.||Protection against flooding of a server|
|US7469418||Oct 1, 2003||Dec 23, 2008||Mirage Networks, Inc.||Deterring network incursion|
|US7490286 *||Sep 25, 2003||Feb 10, 2009||International Business Machines Corporation||Help option enhancement for interactive voice response systems|
|US7506360||Oct 1, 2003||Mar 17, 2009||Mirage Networks, Inc.||Tracking communication for determining device states|
|US7570584||Mar 29, 2002||Aug 4, 2009||Cisco Technology, Inc.||Network-wide congestion control of SPVC signaling messages|
|US7624447 *||Sep 8, 2005||Nov 24, 2009||Cisco Technology, Inc.||Using threshold lists for worm detection|
|US7657419||Nov 10, 2006||Feb 2, 2010||International Business Machines Corporation||Analytical virtual machine|
|US7657938||Oct 28, 2004||Feb 2, 2010||International Business Machines Corporation||Method and system for protecting computer networks by altering unwanted network data traffic|
|US7673137||Jan 3, 2003||Mar 2, 2010||International Business Machines Corporation||System and method for the managed security control of processes on a computer system|
|US7680062 *||Dec 1, 2005||Mar 16, 2010||Electronics And Telecommunications Research Institute||Apparatus and method for controlling abnormal traffic|
|US7702806 *||Aug 16, 2001||Apr 20, 2010||Riverbed Technology, Inc.||Statistics collection for network traffic|
|US7712138||Jun 21, 2007||May 4, 2010||International Business Machines Corporation||Method and system for configuring and scheduling security audits of a computer network|
|US7715819 *||Nov 19, 2001||May 11, 2010||The Boeing Company||Airborne security manager|
|US7725939||Aug 30, 2006||May 25, 2010||Baytsp.Com, Inc.||System and method for identifying an efficient communication path in a network|
|US7743134||Aug 16, 2001||Jun 22, 2010||Riverbed Technology, Inc.||Thwarting source address spoofing-based denial of service attacks|
|US7743415||Jan 31, 2002||Jun 22, 2010||Riverbed Technology, Inc.||Denial of service attacks characterization|
|US7760653||Oct 26, 2004||Jul 20, 2010||Riverbed Technology, Inc.||Stackable aggregation for connection based anomaly detection|
|US7770225||Feb 15, 2008||Aug 3, 2010||International Business Machines Corporation||Method and apparatus for auditing network security|
|US7774839||Nov 3, 2003||Aug 10, 2010||Riverbed Technology, Inc.||Feedback mechanism to minimize false assertions of a network intrusion|
|US7797443 *||Dec 3, 2003||Sep 14, 2010||Microsoft Corporation||System and method for detecting spam e-mail|
|US7797749||Nov 3, 2004||Sep 14, 2010||Intel Corporation||Defending against worm or virus attacks on networks|
|US7801106||Sep 11, 2007||Sep 21, 2010||Nokia Corporation||Prevention of spoofing in telecommunications system|
|US7865954||Aug 24, 2007||Jan 4, 2011||Louisiana Tech Research Foundation; A Division Of Louisiana Tech University Foundation, Inc.||Method to detect SYN flood attack|
|US7869368||May 3, 2005||Jan 11, 2011||France Telecom||Performance measuring in a packet transmission network|
|US7870611 *||Jul 1, 2008||Jan 11, 2011||Baytsp.Com, Inc.||System method and apparatus for service attack detection on a network|
|US7873991 *||Feb 11, 2000||Jan 18, 2011||International Business Machines Corporation||Technique of defending against network flooding attacks using a connectionless protocol|
|US7913303||Mar 27, 2003||Mar 22, 2011||International Business Machines Corporation||Method and system for dynamically protecting a computer system from attack|
|US7921459 *||Apr 27, 2001||Apr 5, 2011||International Business Machines Corporation||System and method for managing security events on a network|
|US7929534||Jun 28, 2004||Apr 19, 2011||Riverbed Technology, Inc.||Flow logging for connection-based anomaly detection|
|US7930740||Jul 7, 2005||Apr 19, 2011||International Business Machines Corporation||System and method for detection and mitigation of distributed denial of service attacks|
|US7934254 *||Sep 27, 2006||Apr 26, 2011||International Business Machines Corporation||Method and apparatus for providing network and computer system security|
|US7979575 *||Jan 31, 2007||Jul 12, 2011||Fujitsu Limited||Attack detecting system and attack detecting method|
|US7979694 *||Mar 2, 2004||Jul 12, 2011||Cisco Technology, Inc.||Using TCP to authenticate IP source addresses|
|US8001601||Jun 14, 2006||Aug 16, 2011||At&T Intellectual Property Ii, L.P.||Method and apparatus for large-scale automated distributed denial of service attack detection|
|US8006243||Dec 19, 2006||Aug 23, 2011||International Business Machines Corporation||Method and apparatus for remote installation of network drivers and software|
|US8046446||Oct 18, 2004||Oct 25, 2011||Symantec Operating Corporation||System and method for providing availability using volume server sets in a storage environment employing distributed block virtualization|
|US8136026||Dec 19, 2008||Mar 13, 2012||International Business Machines Corporation||Help option enhancement for interactive voice response systems|
|US8154987||Jun 9, 2004||Apr 10, 2012||Intel Corporation||Self-isolating and self-healing networked devices|
|US8156557||Jan 4, 2007||Apr 10, 2012||Cisco Technology, Inc.||Protection against reflection distributed denial of service attacks|
|US8161155||Sep 29, 2008||Apr 17, 2012||At&T Intellectual Property I, L.P.||Filtering unwanted data traffic via a per-customer blacklist|
|US8161182||Jan 26, 2000||Apr 17, 2012||Cisco Technology, Inc.||Managing network congestion using dynamically advertised congestion status|
|US8234707 *||Mar 13, 2006||Jul 31, 2012||Mci International, Inc.||Overlay network for tracking denial-of-service floods in unreliable datagram delivery networks|
|US8260961||Oct 1, 2003||Sep 4, 2012||Trustwave Holdings, Inc.||Logical / physical address state lifecycle management|
|US8370937||Dec 3, 2007||Feb 5, 2013||Cisco Technology, Inc.||Handling of DDoS attacks from NAT or proxy devices|
|US8375435||Dec 19, 2008||Feb 12, 2013||International Business Machines Corporation||Host trust report based filtering mechanism in a reverse firewall|
|US8391451 *||May 24, 2006||Mar 5, 2013||At&T Intellectual Property I, L.P.||Voice over IP method for developing interactive voice response system|
|US8397276 *||Mar 23, 2010||Mar 12, 2013||Genband Us Llc||Protecting a network from unauthorized access|
|US8479057 *||Nov 3, 2003||Jul 2, 2013||Riverbed Technology, Inc.||Aggregator for connection based anomaly detection|
|US8504879 *||Nov 3, 2003||Aug 6, 2013||Riverbed Technology, Inc.||Connection based anomaly detection|
|US8631484||Mar 14, 2008||Jan 14, 2014||The Trustees Of Columbia University In The City Of New York||Systems and methods for inhibiting attacks with a network|
|US8661205 *||Dec 10, 2007||Feb 25, 2014||Canon Kabushiki Kaisha||Communication apparatus and information transfer method|
|US8726382 *||Aug 20, 2008||May 13, 2014||The Boeing Company||Methods and systems for automated detection and tracking of network attacks|
|US8751627||May 5, 2009||Jun 10, 2014||Accenture Global Services Limited||Method and system for application migration in a cloud|
|US8762515||Aug 20, 2008||Jun 24, 2014||The Boeing Company||Methods and systems for collection, tracking, and display of near real time multicast data|
|US8799001||Nov 17, 2003||Aug 5, 2014||Nuance Communications, Inc.||Method and system for defining standard catch styles for speech application code generation|
|US8813220||Aug 20, 2008||Aug 19, 2014||The Boeing Company||Methods and systems for internet protocol (IP) packet header collection and storage|
|US8819285||Dec 31, 2003||Aug 26, 2014||Trustwave Holdings, Inc.||System and method for managing network communications|
|US8886806 *||Mar 24, 2011||Nov 11, 2014||Accenture Global Services Limited||Generic control layer in a cloud environment|
|US8925068 *||Dec 8, 2006||Dec 30, 2014||Samsung Sds Co., Ltd.||Method for preventing denial of service attacks using transmission control protocol state transition|
|US8953755||Jan 31, 2013||Feb 10, 2015||At&T Intellectual Property I, L.P.||Voice over IP method for developing interactive voice response system|
|US8978138 *||Mar 15, 2013||Mar 10, 2015||Mehdi Mahvi||TCP validation via systematic transmission regulation and regeneration|
|US8995274||Jul 2, 2009||Mar 31, 2015||The Trustees Of Columbia University In The City Of New York||Methods and systems for controlling traffic on a communication network|
|US9027121||Jul 13, 2007||May 5, 2015||International Business Machines Corporation||Method and system for creating a record for one or more computer security incidents|
|US9197362 *||Mar 17, 2014||Nov 24, 2015||Mehdi Mahvi||Global state synchronization for securely managed asymmetric network communication|
|US9215190 *||Oct 9, 2014||Dec 15, 2015||Accenture Global Services Limited||Generic control layer in a cloud environment|
|US9253323||Dec 12, 2014||Feb 2, 2016||At&T Intellectual Property I, L.P.||Voice over IP method for developing interactive voice response system|
|US9439237||Jan 7, 2011||Sep 6, 2016||Nokia Technologies Oy||Method and apparatus for statistical handling of connections|
|US9467393||Mar 10, 2016||Oct 11, 2016||Accenture Global Services Limited||Network component placement architecture|
|US9667589||Sep 4, 2012||May 30, 2017||Trustwave Holdings, Inc.||Logical / physical address state lifecycle management|
|US20010039623 *||Mar 29, 2001||Nov 8, 2001||Ishikawa Mark M.||System, method and apparatus for preventing transmission of data on a network|
|US20020019945 *||Apr 27, 2001||Feb 14, 2002||Internet Security System, Inc.||System and method for managing security events on a network|
|US20020032774 *||Aug 16, 2001||Mar 14, 2002||Kohler Edward W.||Thwarting source address spoofing-based denial of service attacks|
|US20020032880 *||Aug 16, 2001||Mar 14, 2002||Poletto Massimiliano Antonio||Monitoring network traffic denial of service attacks|
|US20020035628 *||Aug 16, 2001||Mar 21, 2002||Gil Thomer Michael||Statistics collection for network traffic|
|US20020035683 *||Aug 16, 2001||Mar 21, 2002||Kaashoek Marinus Frans||Architecture to thwart denial of service attacks|
|US20020056076 *||Jun 19, 2001||May 9, 2002||Vcis, Inc.||Analytical virtual machine|
|US20020078381 *||Apr 27, 2001||Jun 20, 2002||Internet Security Systems, Inc.||Method and System for Managing Computer Security Information|
|US20020095492 *||Aug 16, 2001||Jul 18, 2002||Kaashoek Marinus Frans||Coordinated thwarting of denial of service attacks|
|US20020103916 *||Sep 5, 2001||Aug 1, 2002||Benjie Chen||Thwarting connection-based denial of service attacks|
|US20020104014 *||Jan 31, 2002||Aug 1, 2002||Internet Security Systems, Inc.||Method and system for configuring and scheduling security audits of a computer network|
|US20020108059 *||Mar 1, 2001||Aug 8, 2002||Canion Rodney S.||Network security accelerator|
|US20020112061 *||Feb 9, 2001||Aug 15, 2002||Fu-Tai Shih||Web-site admissions control with denial-of-service trap for incomplete HTTP requests|
|US20020114522 *||Dec 21, 2000||Aug 22, 2002||Rene Seeber||System and method for compiling images from a database and comparing the compiled images with known images|
|US20020147803 *||Jan 31, 2002||Oct 10, 2002||Dodd Timothy David||Method and system for calculating risk in association with a security audit of a computer network|
|US20020163926 *||Apr 3, 2002||Nov 7, 2002||Moharram Omayma E.||Method and apparatus for security management in a networked environment|
|US20020181448 *||Jun 20, 2002||Dec 5, 2002||Sami Uskela||Prevention of spoofing in telecommunications systems|
|US20030023733 *||Jul 26, 2001||Jan 30, 2003||International Business Machines Corporation||Apparatus and method for using a network processor to guard against a "denial-of-service" attack on a server or server cluster|
|US20030027550 *||Nov 19, 2001||Feb 6, 2003||Rockwell Laurence I.||Airborne security manager|
|US20030027551 *||Nov 19, 2001||Feb 6, 2003||Rockwell Laurence I.||Network security architecture for a mobile network platform|
|US20030036970 *||Jun 19, 2002||Feb 20, 2003||Brustoloni Jose C.||Method and apparatus for protecting electronic commerce from distributed denial-of-service attacks|
|US20030037164 *||Aug 16, 2001||Feb 20, 2003||International Business Machines Corporation||System and method for protecting a TCP connection serving system from high-volume of TCP connection requests|
|US20030069933 *||Jul 12, 2002||Apr 10, 2003||Sung-Yeop Lim||Electronic mail service system and method that make use of dynamic IP filtering technology|
|US20030084317 *||Oct 31, 2001||May 1, 2003||Cohen Donald N.||Reverse firewall packet transmission control system|
|US20030086578 *||Nov 8, 2002||May 8, 2003||Lenart Hauptner||Circuit for setting a signal propagation time for a signal on a signal line and method for ascertaining timing parameters|
|US20030145232 *||Jan 31, 2002||Jul 31, 2003||Poletto Massimiliano Antonio||Denial of service attacks characterization|
|US20030149777 *||Feb 4, 2003||Aug 7, 2003||Micah Adler||Probabalistic packet marking|
|US20030152081 *||Jul 6, 2001||Aug 14, 2003||Johan Soderberg||Method and an arrangement relating to communications systems|
|US20030204632 *||Apr 30, 2002||Oct 30, 2003||Tippingpoint Technologies, Inc.||Network security system integration|
|US20030212902 *||May 13, 2002||Nov 13, 2003||Van Der Made Peter A.J.||Computer immune system and method for detecting unwanted code in a P-code or partially compiled native-code program executing within a virtual machine|
|US20030226034 *||May 31, 2002||Dec 4, 2003||Brett Howard||Secret hashing for TCP SYN/ FIN correspondence|
|US20040008681 *||Jul 15, 2002||Jan 15, 2004||Priya Govindarajan||Prevention of denial of service attacks|
|US20040025015 *||Jan 3, 2003||Feb 5, 2004||Internet Security Systems||System and method for the managed security control of processes on a computer system|
|US20040093513 *||Nov 7, 2002||May 13, 2004||Tippingpoint Technologies, Inc.||Active network defense system and method|
|US20040123142 *||Dec 18, 2002||Jun 24, 2004||Dubal Scott P.||Detecting a network attack|
|US20040128539 *||Dec 30, 2002||Jul 1, 2004||Intel Corporation||Method and apparatus for denial of service attack preemption|
|US20040205374 *||Nov 3, 2003||Oct 14, 2004||Poletto Massimiliano Antonio||Connection based anomaly detection|
|US20040221190 *||Nov 3, 2003||Nov 4, 2004||Roletto Massimiliano Antonio||Aggregator for connection based anomaly detection|
|US20040261030 *||Nov 3, 2003||Dec 23, 2004||Nazzal Robert N.||Feedback mechanism to minimize false assertions of a network intrusion|
|US20050021999 *||Mar 2, 2004||Jan 27, 2005||Riverhead Networks Inc.||Using TCP to authenticate IP source addresses|
|US20050028013 *||Aug 31, 2004||Feb 3, 2005||Craig Cantrell||Active network defense system and method|
|US20050044422 *||Aug 31, 2004||Feb 24, 2005||Craig Cantrell||Active network defense system and method|
|US20050081152 *||Sep 25, 2003||Apr 14, 2005||International Business Machines Corporation||Help option enhancement for interactive voice response systems|
|US20050108015 *||Nov 17, 2003||May 19, 2005||International Business Machines Corporation||Method and system for defining standard catch styles for speech application code generation|
|US20050120243 *||Oct 28, 2004||Jun 2, 2005||Internet Security Systems, Inc.||Method and system for protecting computer networks by altering unwanted network data traffic|
|US20050276228 *||Jun 9, 2004||Dec 15, 2005||Raj Yavatkar||Self-isolating and self-healing networked devices|
|US20050286423 *||Jun 28, 2004||Dec 29, 2005||Poletto Massimiliano A||Flow logging for connection-based anomaly detection|
|US20060005245 *||Jun 9, 2004||Jan 5, 2006||Durham David M||Techniques for self-isolation of networked devices|
|US20060095961 *||Oct 29, 2004||May 4, 2006||Priya Govindarajan||Auto-triage of potentially vulnerable network machines|
|US20060095970 *||Nov 3, 2004||May 4, 2006||Priya Rajagopal||Defending against worm or virus attacks on networks|
|US20060120284 *||Dec 1, 2005||Jun 8, 2006||Electronics And Telecommunications Research Institute||Apparatus and method for controlling abnormal traffic|
|US20060156402 *||Mar 13, 2006||Jul 13, 2006||Worldcom, Inc.||Overlay network for tracking denial-of-service floods in unreliable datagram delivery networks|
|US20060173992 *||Nov 3, 2003||Aug 3, 2006||Daniel Weber||Event detection/anomaly correlation heuristics|
|US20060210030 *||May 24, 2006||Sep 21, 2006||Sbc Properties, L.P.||Voice over IP method for developing interactive voice response system|
|US20060212572 *||Jul 14, 2005||Sep 21, 2006||Yehuda Afek||Protecting against malicious traffic|
|US20060280121 *||Sep 23, 2005||Dec 14, 2006||Fujitsu Limited||Frame-transfer control device, DoS-attack preventing device, and DoS-attack preventing system|
|US20070011740 *||Jul 7, 2005||Jan 11, 2007||International Business Machines Corporation||System and method for detection and mitigation of distributed denial of service attacks|
|US20070019565 *||Aug 30, 2006||Jan 25, 2007||Ishikawa Mark M||System and Method for Identifying an Efficient Communication Path in a Network|
|US20070022090 *||Sep 27, 2006||Jan 25, 2007||Network Ice Corporation, Inc.||Method and Apparatus for Providing Network and Computer System Security|
|US20070079367 *||Aug 30, 2006||Apr 5, 2007||Ishikawa Mark M||System, Method and Apparatus for Detecting, Identifying and Responding to Fraudulent Requests on a Network|
|US20070100936 *||Dec 19, 2006||May 3, 2007||Internet Security Systems, Inc.||Method and apparatus for remote installation of network drivers and software|
|US20070118350 *||Nov 10, 2006||May 24, 2007||Vcis, Inc.||Analytical virtual machine|
|US20070250935 *||Jun 21, 2007||Oct 25, 2007||Zobel Robert D||Method and system for configuring and scheduling security audits of a computer network|
|US20070274307 *||Apr 15, 2005||Nov 29, 2007||Shuichi Karino||Cluster System, Cluster Member, And Program|
|US20070283436 *||Jun 14, 2006||Dec 6, 2007||Nicholas Duffield||Method and apparatus for large-scale automated distributed denial of service attack detection|
|US20070297413 *||Sep 11, 2007||Dec 27, 2007||Nokia Corporation||Prevention of spoofing in telecommunications system|
|US20080052402 *||Jul 8, 2005||Feb 28, 2008||France Telecom||Method, a Computer Program, a Device, and a System for Protecting a Server Against Denial of Service Attacks|
|US20080056263 *||Sep 6, 2006||Mar 6, 2008||Vinit Jain||Efficient transport layer processing of incoming packets|
|US20080059596 *||Jan 31, 2007||Mar 6, 2008||Fujitsu Limited||Attack detecting system and attack detecting method|
|US20080137538 *||May 3, 2005||Jun 12, 2008||France Telecom||Performance Measuring in a Packet Transmission Network|
|US20080140977 *||Dec 10, 2007||Jun 12, 2008||Canon Kabushiki Kaisha||Communication apparatus and information transfer method|
|US20080141369 *||Jan 24, 2006||Jun 12, 2008||France Telecom||Method, Device and Program for Detecting Address Spoofing in a Wireless Network|
|US20080168559 *||Jan 4, 2007||Jul 10, 2008||Cisco Technology, Inc.||Protection against reflection distributed denial of service attacks|
|US20080189780 *||Aug 20, 2007||Aug 7, 2008||Noriaki Hashimoto||Method and system for preventing unauthorized access to a network|
|US20080216173 *||Feb 15, 2008||Sep 4, 2008||International Business Machines Corporation||Method and Apparatus for Auditing Network Security|
|US20080240140 *||Mar 29, 2007||Oct 2, 2008||Microsoft Corporation||Network interface with receive classification|
|US20080270601 *||Jul 1, 2008||Oct 30, 2008||Ishikawa Mark M||System method and apparatus for service attack detection on a network|
|US20090019537 *||Mar 14, 2008||Jan 15, 2009||The Trustees Of Columbia University In The City Of New York||Systems and methods for inhibiting attacks with a network|
|US20090100337 *||Dec 19, 2008||Apr 16, 2009||International Business Machines Corporation||Help option enhancement for interactive voice response systems|
|US20090144806 *||Dec 3, 2007||Jun 4, 2009||Cisco Technology, Inc.||Handling of DDoS attacks from NAT or proxy devices|
|US20100050084 *||Aug 20, 2008||Feb 25, 2010||Stephen Knapp||Methods and systems for collection, tracking, and display of near real time multicast data|
|US20100050256 *||Aug 20, 2008||Feb 25, 2010||Stephen Knapp||Methods and systems for internet protocol (ip) packet header collection and storage|
|US20100050262 *||Aug 20, 2008||Feb 25, 2010||Stephen Knapp||Methods and systems for automated detection and tracking of network attacks|
|US20100064366 *||Sep 9, 2009||Mar 11, 2010||Alibaba Group Holding Limited||Request processing in a distributed environment|
|US20100082811 *||Sep 29, 2008||Apr 1, 2010||Van Der Merwe Jacobus Erasmus||Filtering unwanted data traffic via a per-customer blacklist|
|US20100088763 *||Dec 8, 2006||Apr 8, 2010||Samsung Sds Co., Ltd.||Method for Preventing Denial of Service Attacks Using Transmission Control Protocol State Transition|
|US20100162381 *||Dec 19, 2008||Jun 24, 2010||International Business Machines Corporation||Host trust report based filtering mechanism in a reverse firewall|
|US20100175110 *||Mar 23, 2010||Jul 8, 2010||March Sean W||Protecting a network from unauthorized access|
|US20100287263 *||May 5, 2009||Nov 11, 2010||Huan Liu||Method and system for application migration in a cloud|
|US20110093946 *||Dec 18, 2009||Apr 21, 2011||Hon Hai Precision Industry Co., Ltd.||Router and method for protecting tcp ports utilizing the same|
|US20110107098 *||Jul 2, 2009||May 5, 2011||The Trustees Of Columbia University In The City Of New York||Methods and Systems for Controlling Traffic on a Communication Network|
|US20120072581 *||Mar 24, 2011||Mar 22, 2012||Tung Teresa S||Generic control layer in a cloud environment|
|US20140283057 *||Mar 15, 2013||Sep 18, 2014||Mehdi Mahvi||Tcp validation via systematic transmission regulation and regeneration|
|US20140286358 *||Mar 17, 2014||Sep 25, 2014||Mehdi Mahvi||Global state synchronization for securely managed asymmetric network communication|
|US20150026793 *||Jul 17, 2013||Jan 22, 2015||Cisco Technology, Inc.||Session initiation protocol denial of service attack throttling|
|US20150058489 *||Oct 9, 2014||Feb 26, 2015||Accenture Global Services Limited||Generic Control Layer In A Cloud Environment|
|CN101674312B||Oct 19, 2009||Dec 19, 2012||中兴通讯股份有限公司||Method for preventing source address spoofing in network transmission and device thereof|
|CN102045251B||Oct 20, 2009||Aug 22, 2012||国基电子（上海）有限公司||Router and TCP (Transmission Control Protocol) port defense method|
|CN102244663A *||Aug 16, 2011||Nov 16, 2011||山东盛世光明软件技术有限公司||User identification method and system based on transmission control protocol (TCP) data packet construction technology|
|CN102244663B||Aug 16, 2011||Dec 18, 2013||山东盛世光明软件技术有限公司||User identification method and system based on transmission control protocol (TCP) data packet construction technology|
|CN103220255A *||Jan 18, 2012||Jul 24, 2013||中兴通讯股份有限公司||Method and device for realizing unicast reverse path forwarding (URPF) examination|
|DE102005037968B4 *||Aug 11, 2005||Sep 11, 2014||D-Link Corporation||Schutzsystem für eine Netzwerkinformationssicherheitszone|
|EP1617595A1 *||May 24, 2005||Jan 18, 2006||Evolium S.A.S.||Network monitoring system based on conditional monitoring|
|WO2004045126A3 *||Nov 7, 2003||Dec 2, 2004||Craig Cantrell||Active network defense system and method|
|WO2004079497A2||Mar 3, 2004||Sep 16, 2004||Cisco Tecnhology Inc.||Using tcp to authenticate ip source addresses|
|WO2004079497A3 *||Mar 3, 2004||Dec 7, 2006||Cisco Tecnhology Inc||Using tcp to authenticate ip source addresses|
|WO2005112345A1 *||May 3, 2005||Nov 24, 2005||France Telecom||Performance measuring in a packet transmission network|
|WO2012093193A1 *||Jan 7, 2011||Jul 12, 2012||Nokia Corporation||Method and apparatus for statistical handling of connections|
|WO2016197498A1 *||Oct 15, 2015||Dec 15, 2016||中兴通讯股份有限公司||Method and device for preventing network attack, and storage medium|
|U.S. Classification||726/13, 709/206, 709/224, 709/223, 707/999.01|
|Cooperative Classification||H04L63/1458, H04L63/1408|
|European Classification||H04L63/14A, H04L63/14D2|
|Jul 12, 1999||AS||Assignment|
Owner name: PURDUE RESEARCH FOUNDATION, INDIANA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SCHUBA, CHRISTOPH L.;KRUSUL, IVAN V.;ZAMBONI, DIEGO;AND OTHERS;REEL/FRAME:010077/0642;SIGNING DATES FROM 19990615 TO 19990621
|Jul 26, 2007||FPAY||Fee payment|
Year of fee payment: 4
|Dec 5, 2011||REMI||Maintenance fee reminder mailed|
|Apr 5, 2012||SULP||Surcharge for late payment|
Year of fee payment: 7
|Apr 5, 2012||FPAY||Fee payment|
Year of fee payment: 8
|Nov 27, 2015||REMI||Maintenance fee reminder mailed|
|Apr 20, 2016||LAPS||Lapse for failure to pay maintenance fees|
|Jun 7, 2016||FP||Expired due to failure to pay maintenance fee|
Effective date: 20160420