CA2426451A1 - Method and system for detecting, tracking and blocking denial of serviceattacks over a computer network - Google Patents
Method and system for detecting, tracking and blocking denial of serviceattacks over a computer network Download PDFInfo
- Publication number
- CA2426451A1 CA2426451A1 CA002426451A CA2426451A CA2426451A1 CA 2426451 A1 CA2426451 A1 CA 2426451A1 CA 002426451 A CA002426451 A CA 002426451A CA 2426451 A CA2426451 A CA 2426451A CA 2426451 A1 CA2426451 A1 CA 2426451A1
- Authority
- CA
- Canada
- Prior art keywords
- data packet
- packet flow
- flow anomalies
- collector
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
- H04L63/1416—Event detection, e.g. attack signature detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/1458—Denial of Service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/146—Tracing the source of attacks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/04—Processing captured monitoring data, e.g. for logfile generation
- H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Human Computer Interaction (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A system and method is provided for detecting, tracking and blocking denial of service ("DoS") attacks, which can occur between local computer systems and/or between remote computer systems, network links, and/or routing systems over a computer network. The system includes a collector adapted to receive a plurality of data statistics from the computer network and to process the plurality of data statistics to detect one or more data packet flow anomalies.
The collector is further adapted to generate a plurality of signals representing the one or more data packet flow anomalies. The system further includes a controller that is coupled to the collector and is adapted to receive the plurality of signals from the collector. The controller is constructed and arranged to respond to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source, and to block the one or more data packet flow anomalies using a filtering mechanism executed in close proximity to the at least one source.
The collector is further adapted to generate a plurality of signals representing the one or more data packet flow anomalies. The system further includes a controller that is coupled to the collector and is adapted to receive the plurality of signals from the collector. The controller is constructed and arranged to respond to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source, and to block the one or more data packet flow anomalies using a filtering mechanism executed in close proximity to the at least one source.
Description
METHOD AND SYSTEM FOR DETECTING, TRACKING AND BLOCKING
DENIAL OF SERVICE ATTACKS OVER A COMPUTER NETWORK
STATEMENT REGARDING FEDERALLY SPONSORED
RESEARCH OR DEVELOPMENT
This invention was made with Government support under Contract No. F30602-99-1-0527 awarded by DARPA. The Government has certain rights to the invention.
BACKGROUND OF THE INVENTION
1. Field of the Invention The present invention relates generally to data processing systems and more particularly to a method and system for detecting, tracking and blocking denial of service attacks over a local or remote computer network.
DENIAL OF SERVICE ATTACKS OVER A COMPUTER NETWORK
STATEMENT REGARDING FEDERALLY SPONSORED
RESEARCH OR DEVELOPMENT
This invention was made with Government support under Contract No. F30602-99-1-0527 awarded by DARPA. The Government has certain rights to the invention.
BACKGROUND OF THE INVENTION
1. Field of the Invention The present invention relates generally to data processing systems and more particularly to a method and system for detecting, tracking and blocking denial of service attacks over a local or remote computer network.
2. Background Art Computer systems are often interconnected into vast computer networks. The computer systems connected on such networks communicate with each other by sending information through their electronic connections. The networks can be organized into various types of topologies. Figure 1 illustrates one such topology that includes a network 100 having several local area networks 102 and that are connected to a routing system 103. The computer systems of each local area network are connected to the communications link 101a-102a. When a source computer system on a local area network 101 or 102 sends information to a destination computer system on the same local area network 101 or 102, the source computer system prepares a packet that includes the address of the destination computer system and transmits the packet on the communications link 101a or 102a.
The other computer systems on that same local area network 101 or 102 (i. e. , connected to the communications link lOla .or 102a) read the packet that was transmitted. The destination computer system detects that its address is included in that packet, and its processes the packet accordingly. Because of geographic and speed considerations, local area networks 101-102 typically only include a limited number of computer systems that are in close proximity. For example, a company with offices in several locations may have a local area network at each location.
However, the users of the computer systems may need to send packets to one another regardless to which of local area networks 101-102 the users' computer systems are connected.
To allow packets to be sent from one local area network 101 or 102 to another local area network 101 or 102, routing systems 103 have been developed.
A routing system 103 is typically a dedicated special-purpose computer system to which each local area network 101-102 is connected. The routing system I03 maintains a cross-reference between computer system addresses and the local area network 101-102 to which each computer system is connected. The routing system 103 monitors the packets sent on each local area network 101-102 to detect (using the cross-reference) when a computer system on one local area network 101-102 is sending a packet to a computer system on another local area network 101 or 102.
When the routing system 103 detects such a packet, it forwards that packet onto the communications link 101a or 102a for the local area network 101 or 102 to which the destination computer system is connected. In this way, the routing system interconnects each of the local area networks 101 and 102 into an overall network 100. Similar routing techniques are used to interconnect networks other than local area networks 10I-102. For example, such routing techniques can be used on wide area networks (not shown) and on the Internet 104.
Many different protocols have been developed to allow two computer systems to exchange information. If two computer systems support the same protocol, then they can exchange information. Certain protocols have been tailored to support the exchange of certain types of information efficiently. For example, the Internet protocol ("IP") was specified by the Department of Defense to facilitate the exchange of information between geographically separated computer systems.
The IP specifies a destination in a packet format that identifies source and -2_ destination computer systems for data to exchange, but does not specify the format of the data itself. Several additional protocols may be used in conjunction with the IP to specify the format of the data. Two such additional protocols are the transmission control protocol ("TCP"), and the user datagram protocol ("UDP").
TCP and UDP further specify sub-protocols, such as the hyper-text transmission protocol ("HTTP") and the file transfer protocol ("FTP"), which specify the format of the data of the packet.
Figure 2 is a diagram illustrating a typical packet sent on a local area network. The packet includes a network routing header followed by protocol specific data. The network routing header may include the destination computer address, the source computer address, and the length of the packet. The protocol specific data includes identification of the protocol and the IP destination address, the IP source address, and the length of the IP portion of the packet. The data portion of the packet contains the sub-protocol identification plus other data of the packet. One specific field of the TCP and UDP sub-protocol is the port number.
This port number is used to identify application protocols, which define network services that are available to remote systems.
One problem occurs when a first computer system maliciously sends a flood of packets to a target or second computer system, routing system or network link to overwhelm the reception resources or capacity of the target, which can result in either loss of connectivity to or failure of the target. This flood of packets based attack is commonly known as a denial of service attack ("DoS").
The most insidious types of DoS attacks occur when the initiator or first computer system hides their origin by forging the source Internet Protocol (IP) address on the attack packets. As a result, administrators and security officers of the target cannot determine the origin of the DoS attack. Further, the administrators and security officers of the target will not likely be able to avoid or shut down the DoS attack.
The other computer systems on that same local area network 101 or 102 (i. e. , connected to the communications link lOla .or 102a) read the packet that was transmitted. The destination computer system detects that its address is included in that packet, and its processes the packet accordingly. Because of geographic and speed considerations, local area networks 101-102 typically only include a limited number of computer systems that are in close proximity. For example, a company with offices in several locations may have a local area network at each location.
However, the users of the computer systems may need to send packets to one another regardless to which of local area networks 101-102 the users' computer systems are connected.
To allow packets to be sent from one local area network 101 or 102 to another local area network 101 or 102, routing systems 103 have been developed.
A routing system 103 is typically a dedicated special-purpose computer system to which each local area network 101-102 is connected. The routing system I03 maintains a cross-reference between computer system addresses and the local area network 101-102 to which each computer system is connected. The routing system 103 monitors the packets sent on each local area network 101-102 to detect (using the cross-reference) when a computer system on one local area network 101-102 is sending a packet to a computer system on another local area network 101 or 102.
When the routing system 103 detects such a packet, it forwards that packet onto the communications link 101a or 102a for the local area network 101 or 102 to which the destination computer system is connected. In this way, the routing system interconnects each of the local area networks 101 and 102 into an overall network 100. Similar routing techniques are used to interconnect networks other than local area networks 10I-102. For example, such routing techniques can be used on wide area networks (not shown) and on the Internet 104.
Many different protocols have been developed to allow two computer systems to exchange information. If two computer systems support the same protocol, then they can exchange information. Certain protocols have been tailored to support the exchange of certain types of information efficiently. For example, the Internet protocol ("IP") was specified by the Department of Defense to facilitate the exchange of information between geographically separated computer systems.
The IP specifies a destination in a packet format that identifies source and -2_ destination computer systems for data to exchange, but does not specify the format of the data itself. Several additional protocols may be used in conjunction with the IP to specify the format of the data. Two such additional protocols are the transmission control protocol ("TCP"), and the user datagram protocol ("UDP").
TCP and UDP further specify sub-protocols, such as the hyper-text transmission protocol ("HTTP") and the file transfer protocol ("FTP"), which specify the format of the data of the packet.
Figure 2 is a diagram illustrating a typical packet sent on a local area network. The packet includes a network routing header followed by protocol specific data. The network routing header may include the destination computer address, the source computer address, and the length of the packet. The protocol specific data includes identification of the protocol and the IP destination address, the IP source address, and the length of the IP portion of the packet. The data portion of the packet contains the sub-protocol identification plus other data of the packet. One specific field of the TCP and UDP sub-protocol is the port number.
This port number is used to identify application protocols, which define network services that are available to remote systems.
One problem occurs when a first computer system maliciously sends a flood of packets to a target or second computer system, routing system or network link to overwhelm the reception resources or capacity of the target, which can result in either loss of connectivity to or failure of the target. This flood of packets based attack is commonly known as a denial of service attack ("DoS").
The most insidious types of DoS attacks occur when the initiator or first computer system hides their origin by forging the source Internet Protocol (IP) address on the attack packets. As a result, administrators and security officers of the target cannot determine the origin of the DoS attack. Further, the administrators and security officers of the target will not likely be able to avoid or shut down the DoS attack.
Conventional routing systems 103 have attempted to avoid DoS
attacks by employing various types of packet filtering techniques in the form of firewalls at the entrance to the local area network 101-102. Current implementations of packet filtering permit packets to be delivered to computer systems if the packet's format conforms to access list tables, which include a fixed format. This method is limited to the set of protocols and services defined in the particular access list table. Further, this method does not allow the introduction of different protocols or services which are not specified in the access list table.
Finally, while firewall solutions may reduce unauthorized information from accessing a target, the firewall solutions do not reduce the impact that denial of service attacks can have on the availability of the target's bandwidth.
Other packet filtering schemes include a network administrator configuring a routing system 103 to restrict the type and timing of packets that are sent over the network 100. For example, a network administrator may want to restrict packets that are generated by a computer game from being transmitted over the network 100 during normal business hours. A packet for a computer game may be identifiable, for example, by a TCP destination address, that indicates which application on the computer system identified by the IP destination address that is to receive the packet. Thus, the network administrator would configure the routing system 103 to not forward any such packets during normal business hours. Also, the network administrator may want to filter out packets based on their source and destination addresses. For example, a company CEO may only want to receive packets from certain source computer systems and not every computer system on the network 100.
Present known filtering systems, such as packet filtering described above, have often proven either to be ineffective in preventing DoS attacks, or have severely limited access to communication services for communicating with other networks. In general, existing filtering systems disable certain critical communication services between the computer systems that deteriorate inter and intra computer system communications. Moreover, identifying the characteristics related to the DoS attacks can be impractical for network engineers and operators to accomplish by inspection alone, because of the voluminous amount of information associated with the characteristics. Finally, solutions for filtering attack traffic close to the local area network do not affect denial of service attacks that are directed at the heart of a service provider's routing infrastructure, such as attacks on network links or the routing infrastructure directly.
Previously works in this area of technology includes the following:
~ MCI's DoS Tracker: The DoS tracker's approach was a recursive script that would iterate over a set of routers. Network operators would invoke this script when a DoS attack had already been detected and identified at a specific point in the network (a customer's access router for example). The script would login to a router over its command line interface (CLI), and then turn on debugging. It would then examine the router's debugging output to identify interfaces that were affected by the denial of service attack.
The work was abandoned due to the performance impact caused by using the debugging feature, and the inability to continue the tracking across a network's core.
~ UUNet's Center Track: The Center Track work involves building a measurement overlay network by building tunnels from each of a network's edge routers to a set of measurement routers. Center Track is only used once an attack is detected by an external tool (or a customer calling on the phone and complaining). All of the target's traffic is off ramped onto the Center Track overlay network, where its origin can be tracked using direct measurement or muter debugging tools.
~ Network-based Intrusion Detection: Network-based Intrusion Detection (NID) systems are systems that are similar in that they look at a copy of the data in a network and identify malicious attacks. NID systems use passive packet capture techniques to examine the contents of every packet on a network and recreate both transport and application layer information to identify well-known attacks. However, because NID systems detect a wide spectrum of attacks, they do not scale to the highest bandwidth areas, like network service provider networks.
U.S. Patent No. 4,817,080 to Soha discloses a system that measures traffic statistics by looking at packet contents. The system collects distributed measurements and forwards them to a centralized point.
U.S. Patent No. 5,781,534 to Perlman et al. discloses apparatus for determining characteristics of a path by utilizing active probing along a network path to determine its characteristics. These characteristics are added to the packet as it traverses the network.
U.S. Patent No. 5,968,176 to Nessett et al. discloses a system that utilizes many network elements to provide an umbrella countermeasure.
U.S. Patent No. 5,991,881 to Conklin et al. discloses a system which flags intrusions and updates the status of the intruder's progress. This system only stores the packets with the source address of the attacker.
U.S. Patent No. 6,078,953 to Vaid et al. discloses a system which classifies packets at the border of the network to provide quality of service.
It polices traffic at the edge of the network.
U.S. Patent No. 6,088,804 to Hill et al. discloses a system which correlates distributed attacks to build a path of the attack through the network. The system uses a training signature for attack identification. That is, the system is trained on attacks, and then compares current activity to this known misuse.
U.S. Patent No. 6,134,662 to Levy et al. discloses a physical layer security manager for memory-mapped serial communications interface.
attacks by employing various types of packet filtering techniques in the form of firewalls at the entrance to the local area network 101-102. Current implementations of packet filtering permit packets to be delivered to computer systems if the packet's format conforms to access list tables, which include a fixed format. This method is limited to the set of protocols and services defined in the particular access list table. Further, this method does not allow the introduction of different protocols or services which are not specified in the access list table.
Finally, while firewall solutions may reduce unauthorized information from accessing a target, the firewall solutions do not reduce the impact that denial of service attacks can have on the availability of the target's bandwidth.
Other packet filtering schemes include a network administrator configuring a routing system 103 to restrict the type and timing of packets that are sent over the network 100. For example, a network administrator may want to restrict packets that are generated by a computer game from being transmitted over the network 100 during normal business hours. A packet for a computer game may be identifiable, for example, by a TCP destination address, that indicates which application on the computer system identified by the IP destination address that is to receive the packet. Thus, the network administrator would configure the routing system 103 to not forward any such packets during normal business hours. Also, the network administrator may want to filter out packets based on their source and destination addresses. For example, a company CEO may only want to receive packets from certain source computer systems and not every computer system on the network 100.
Present known filtering systems, such as packet filtering described above, have often proven either to be ineffective in preventing DoS attacks, or have severely limited access to communication services for communicating with other networks. In general, existing filtering systems disable certain critical communication services between the computer systems that deteriorate inter and intra computer system communications. Moreover, identifying the characteristics related to the DoS attacks can be impractical for network engineers and operators to accomplish by inspection alone, because of the voluminous amount of information associated with the characteristics. Finally, solutions for filtering attack traffic close to the local area network do not affect denial of service attacks that are directed at the heart of a service provider's routing infrastructure, such as attacks on network links or the routing infrastructure directly.
Previously works in this area of technology includes the following:
~ MCI's DoS Tracker: The DoS tracker's approach was a recursive script that would iterate over a set of routers. Network operators would invoke this script when a DoS attack had already been detected and identified at a specific point in the network (a customer's access router for example). The script would login to a router over its command line interface (CLI), and then turn on debugging. It would then examine the router's debugging output to identify interfaces that were affected by the denial of service attack.
The work was abandoned due to the performance impact caused by using the debugging feature, and the inability to continue the tracking across a network's core.
~ UUNet's Center Track: The Center Track work involves building a measurement overlay network by building tunnels from each of a network's edge routers to a set of measurement routers. Center Track is only used once an attack is detected by an external tool (or a customer calling on the phone and complaining). All of the target's traffic is off ramped onto the Center Track overlay network, where its origin can be tracked using direct measurement or muter debugging tools.
~ Network-based Intrusion Detection: Network-based Intrusion Detection (NID) systems are systems that are similar in that they look at a copy of the data in a network and identify malicious attacks. NID systems use passive packet capture techniques to examine the contents of every packet on a network and recreate both transport and application layer information to identify well-known attacks. However, because NID systems detect a wide spectrum of attacks, they do not scale to the highest bandwidth areas, like network service provider networks.
U.S. Patent No. 4,817,080 to Soha discloses a system that measures traffic statistics by looking at packet contents. The system collects distributed measurements and forwards them to a centralized point.
U.S. Patent No. 5,781,534 to Perlman et al. discloses apparatus for determining characteristics of a path by utilizing active probing along a network path to determine its characteristics. These characteristics are added to the packet as it traverses the network.
U.S. Patent No. 5,968,176 to Nessett et al. discloses a system that utilizes many network elements to provide an umbrella countermeasure.
U.S. Patent No. 5,991,881 to Conklin et al. discloses a system which flags intrusions and updates the status of the intruder's progress. This system only stores the packets with the source address of the attacker.
U.S. Patent No. 6,078,953 to Vaid et al. discloses a system which classifies packets at the border of the network to provide quality of service.
It polices traffic at the edge of the network.
U.S. Patent No. 6,088,804 to Hill et al. discloses a system which correlates distributed attacks to build a path of the attack through the network. The system uses a training signature for attack identification. That is, the system is trained on attacks, and then compares current activity to this known misuse.
U.S. Patent No. 6,134,662 to Levy et al. discloses a physical layer security manager for memory-mapped serial communications interface.
Therefore, an unsolved need remains for a system and method for detecting, tracking and blocking DoS attacks which can occur between local computer systems and/or between remote computer systems over a computer network, that overcomes the above-described limitations and deficiencies of the prior art.
SUMMARY OF THE INVENTION
In accordance with principles of the present invention, a system and method is provided for detecting, tracking and blocking DoS attacks, which can occur between local computer systems and/or between remote computer systems, network links, and/or routing systems over a computer network.
In one embodiment of the present invention, a system includes a collector adapted to receive a plurality of data statistics from the computer network and to process the plurality of data statistics to detect one or more data packet flow anomalies and to generate a plurality of signals representing the one or more data packet flow anomalies. The system further includes a controller which is coupled to the collector. The controller is constructed and arranged to receive and respond to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source. The controller is further constructed and arranged to block the one or more data packet flow anomalies using one or more filtering mechanisms executed in close proximity to the at least one source.
The one or more filtering mechanisms can include a plurality of filter list entries, such as access control list entries as well as firewall filter entries, and/or a plurality of rate limiting entries, such as committed access rate (CAR) entries.
In aspect of the present invention, the collector includes a buffer coupled to the computer network and a detector coupled to the buffer. The collector further includes a profiler coupled to the buffer and to the detector. The buffer is adapted to receive and process the plurality of data statistics to generate at least one record that is communicated to the profiler. The profiler processes the record to generate a predetermined threshold. The detector is adapted to receive and process the predetermined threshold and the at least one record to detect if attributes associated with the record exceed the predetermined threshold, which represents the one or more data packet flow anomalies.
The profiler may include means for aggregating the data statistics to obtain a traffic profile of network flows.
The data statistics may be aggregated based on at least one invariant feature of the network flows.
The data statistics may also be aggregated based on temporal, static network and dynamic routing parameters.
The at least one invariant feature may include source and destination endpoints.
The collector further includes a local controller coupled to the detector and to the profiler. The local controller is adapted to receive and respond to the one or more data packet flow anomalies by generating the plurality of signals, which represents the one or more data packet flow anomalies.
The detector includes a database for storing the at least one record, predetermined threshold, the one or more data packet flow anomalies, and related information. Similarly, the profiler includes a database for storing a plurality of data packet flow profiles and related information.
In an aspect of the present invention, the controller includes a correlator coupled to the collector. The correlator is adapted to receive and normalize the plurality of signals representing the one or more data packet flow anomalies. The correlator is further adapted to generate an anomaly table including the attributes related to the one or more data packet flow anomalies. The correlator includes a database for storing the anomaly table. Additionally, the correlator _g_ includes an adapter that is constructed and arranged to communicate the anomaly table to a computer device for further processing.
The controller further includes a web server and access scripts that cooperate with the web server to enable the computing device to access the database defined on the controller to view the anomaly table.
In accordance with the present invention, the method for detecting, tracking and blocking one or more denial of service attacks over a computer network includes the steps of collecting a plurality of data statistics from the computer network; processing the plurality of data statistics to detect one or more data packet flow anomalies; generating a plurality of signals representing the one or more data packet flow anomalies; and receiving and responding to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source.
The method further includes the step of blocking the one or more data packet flow anomalies in close proximity to the at least one source.
The step of collecting the plurality of data statistics includes buffering the plurality of data statistics; processing the plurality of data statistics to generate at least one record; and receiving and profiling the at least one record to generate a predetermined threshold.
The step of collecting the plurality of data statistics further includes detecting if attributes related to the at least one record exceed the predetermined threshold representing the one or more data packet flow anomalies.
The step of collecting the plurality of data statistics further includes responding locally to the one or more data packet flow anomalies by generating the plurality of signals representing the one or more data packet flow anomalies.
The step of receiving and responding to the plurality of signals includes correlating the plurality of signals representing the one or more data packet flow anomalies; and generating an anomaly table including the attributes related to the one or more data packet flow anomalies.
The step of receiving and responding to the plurality of signals further includes the step of communicating the anomaly table to a computing device for further processing.
The above objects and other objects, features, and advantages of the present invention are readily apparent from the following detailed description of the best mode for carrying out the invention when taken in connection with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FIGURE 1 is a high level block diagram of a conventional computer network system;
FIGURE 2 is an exemplary data packet format which can be adapted for communication over the conventional computer network system shown in Figure 1;
FIGURE 3 is a high level block diagram of a computer network system according to one embodiment of the present invention;
FIGURE 4 is a partially exploded view of the computer network system shown in Figure 3;
FIGURE 5 is a high level block diagram of the collector shown in Figure 4;
FIGURE 6 is a high level block diagram of the controller shown in Figure 4; and FIGURE 7 is a high level block diagram exemplifying a DoS attack.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS) For purposes of illustration and to facilitate a further understanding of the present invention, described below is a reference to an Internet-based computer network system and a method for processing data. However, as understood by one skilled in the art, the present invention is not limited to Internet-based systems and can include systems employing other computer networks as well as stand alone systems.
In accordance with principles of the present invention, a system and method is set forth for detecting, tracking and blocking DoS attacks, which can occur between local computer systems and/or between remote computer systems, network links, and/or routing systems over a computer network.
Referring to Fig. 3, a system 5 for detecting, tracking and blocking DoS attacks is incorporated in the computer network system 10 in accordance with one embodiment of the present invention. The system 5 can be located on a single server computer (not shown), which is in communication with components of the computer network system 10 or distributed over a plurality of server computers (not shown), which are also in communication with components of the computer network system 10.
The computer network system 10 includes a plurality of Internet Service Provider computer networks 14a, 14b and 14c (hereinafter ISP computer networks)") coupled over a computer network 18. The ISP computer networks 14a, 14b and 14c can also be coupled directly to each other. Each of the ISP
computer networks 14a, 14b and/or 14c can include a plurality of computer network zones. As exemplified in Fig. 3, the ISP computer network 14a includes computer network Zone X, Zone Y and Zone Z. The ISP computer network 14b includes computer network Zone U and Zone V. The ISP computer network 14c includes computer network Zone W.
Fig. 4 shows a partially expanded view of the system 5, which is incorporated in the partially expanded view of the computer network system 10.
In Fig, 4, Zone X of the ISP computer network 14a includes a number of local area networks ("LAN(s) ") coupled to a central routing system 22. Each LAN is coupled with a plurality of computer systems 16a, 16b, 16c, 16e, 16f, 16g, 16h, 16i and 16j (hereinafter collectively referred to as "computer systems) 16"). The computer network Zones Y and Z, which are also located on the ISP computer network 14a, can be similarly constructed and arranged as computer network Zones X.
Further, the computer network Zones U and V, which are located on the ISP computer network 14b and the computer network Zone W, which is located on the ISP
computer network 14c, can also be similarly constructed and arranged as computer network Zones X.
The system 5 includes a collector 20, an optional collector 20b and a zone controller 24. In Zone X, the collector 20 is coupled to the central routing system 22. The collector 20 is further coupled to a zone controller 24, which provides a primary interface to Zone X of the ISP computer network 14a. The computer network Zones Y and Z, which are also located on the ISP computer network 14a can be similarly constructed and arranged as computer network Zone X. Further, the computer network Zones U and V, which are located on the ISP
computer network 14b and the computer network Zone W, which is located on the ISP computer network 14c, can also be similarly constructed and arranged as computer network Zones X.
In another embodiment, the collector 20 can be coupled to one or more other router systems, such as the routing system 22b, as exemplified in Fig.
4. In addition, the zone controller 24 can be coupled to one or more other collectors, such as the collector 20b, as also exemplified in Fig. 4. Further, the collector 20b, can be coupled to one or more other routing systems, such as the routing system 22c.
The zone controller 24 located in Zone X of the ISP Computer network 14a provides a primary interface to the computer network Zone Y and to the computer network Zone Z, which are both located on the ISP computer network 14a. The zone controller 24 further provides a primary interface to the computer network Zone U and the computer network Zone V, which are located on the ISP
computer network 14b, over the computer network 18. Similarly, the zone controller 24 further provides a primary interface to computer network Zone W, which is located on the ISP computer network 14c, over the computer network 18.
In an embodiment of the present invention, the computer systems 16 located in computer network Zone X of the ISP computer network 14a can each comprise a conventional computer server such as an "NT-Server" which can be provided by Microsoft of Richmond, Washington or a "Unix Solaris Server" which can be provided by Sun Micro Systems of Palo Alto, California. These computer systems 16 can be programmed with conventional Web-page interface software such as: "Visual Basic", "Java", "JavaScript", "HTML/DHTML", "C++", "J+", "Pert" or "Perlscript", or "ASP". These computer systems can further be programmed with an operating system, Web server software, Web Application software, such as an e-commerce application and computer network interface software.
Each of the routing systems 22, 22b and 22c, as shown in Fig. 4, can be a conventional router, such as a "Cisco 12000", available from Cisco Corporation of San Jose, California. Further, each of the routing systems can be adapted to run data packet flow statistical software, such as Netflow'~
software, also available from Cisco Corporation of San Jose, California. Alternatively, each of the routing systems, as shown in Fig. 4, can be another conventional router, such as an "M-40", available from Juniper Corporation of Sunnyvale, California.
Further, each of the routing systems can be adapted to run data packet flow statistical software, such as Juniper Cflowdl'"s software, also available from Juniper Corporation of Sunnyvale, California. The packet flow statistical software running on each of the routing systems 22, 22b and 22c enable each of the routing systems 22, 22b and 22c to gather and store data packet flow statistical information.
The data packet flow statistical information can include the number of packets which have been communicated between computer systems 16, the duration of communication between each of the computer systems 16, the total number of packets communicated over each LAN (which is typically used for capacity planning) as well as other various data packet flow statistical information.
Fig. 5 shows the collector 20 in detail. The collector includes an input buffer 20a coupled to the routing system 22. The input buffer is coupled to a storm detector 20b and to a storm profiler 20d. The storm detector 20b includes a detector database and the storm profiler 20d includes a profiler database 20e. The collector 20 further includes a local controller 20f, which is coupled to the storm detector 20b and to a storm profiler 20d. The local controller 20f is further coupled to the zone controller 24.
The collector 20 is adapted to receive the data packet flow statistical information from the routing system 22 and to process the data packet flow statistical information to detect data packet flow anomalies. The collector 22b of Zone X, as well as other various collectors (not shown), which are included in the other various Zones U, V, W, Y and Z are similarly constructed and arranged as the collector 20 of Zone X.
The input buffer 20a, located on collector 20, is adapted to normalize or categorize the data packet flow statistical information and to generate a number of records including the normalized data packet flow statistical information.
The storm detector 20b is adapted to detect the data packet flow anomalies by comparing the records to an anomaly pattern and/or a predetermined threshold. If components of the normalized data packet flow statistical information exceed the predetermined threshold, a data packet flow anomaly is detected. Thereafter, the detected data packet flow anomaly and data associated with the data packet flow anomaly, such as the source and destination addresses of the flow information can be stored in the detector database 20c.
The storm profiler module 20d is adapted to receive the normalized data packet flow statistical information or records from the input buffer 20a and to generate the predetermined threshold, which is concomitantly communicated to the storm detector module 20b. In this configuration, the predetermined threshold defined in the storm detector is adaptively adjusted based on changing trends or profiles of the normalized data packet flow statistical information received by the storm profiler 20d. The changing trends or profiles of the normalized data packet flow statistical information, for example, can include changes in the average bandwidth allocated to each of the computer systems 16 during a particular period of time or changes to the number of computer systems 16 communicating information at the same instant of time.
The local controller 20f, which is coupled to both the storm detector 20b and to the storm profiler 20f, is adapted to receive the data packet flow anomaly from the storm detector 20b, as well as data associated with the data packet flow anomaly, as previously described. After receiving the data packet flow anomaly and the associated data from the storm detector, the local controller 20f generates a signal or an alert message. The alert message can include pertinent information related to the anomaly. The pertinent information related to the anomaly can include the characteristics of the anomaly, the source and destination of the anomaly, the protocols involved and their sub-protocols, the detection mechanism used to identify the anomaly, the predetermined threshold, routing systems in the path of the anomaly, as well as the magnitude or severity of the anomaly. The alert message is communicated to the zone controller 24 to enable the zone controller 24 to further process the alert message and to enable the zone controller 24 to communicate the alert message to other Zones U, V, W, X, Y and Z and/or ISPs 14b and 14c.
In an embodiment, the collector takes samples of several types of statistics, which are obtained by the router 22, such as single packet statistics and flow-based statistics. Single packet statistics provide essential information about a set of packets entering a forwarding node or router 22. Some of the single packet statistics can include: destination and source IP addresses, incoming interface, protocol, ports, and length. After collection of these single-packet statistics, the collector can process the statistics as described above to adaptively adjust the predetermined threshold defined in the storm detector, which detects the packet anomalies.
Flow-based statistics include a set of packets that are related to the same logical traffic flow. The concept of flow-based statistics is generally defined as a stream of packets that all have the same characteristics, such as, source address, destination address, protocol type, source port, and destination port. The flow-based statistics may be either uni-directional or bidirectional. Single-packet statistics can be aggregated to generate a single flow-based statistic. An example of the single flow-based statistic can include a flow duration, number of packets included over a predetermined duration, mean bytes per packet, etc.
Referring further to Fig. 6, the zone controller 24 includes a correlator 24a coupled to the collector 20. The correlator 24a includes a communication interface adapter 24e. The zone controller 24 further includes an alert message database 24b, which is coupled to the correlator module 24a. A
web server 24c and access scripts software 24d are also defined on the controller 24.
The zone controller 24 is adapted to receive a plurality of alert messages from the collector 20, and to process the alert messages by aggregating the alert messages based on the pertinent information related to the anomaly, as described above. The zone controller 24 of Zone X, as well as other various controllers (not shown), which are included in the other various Zones U, V, W, Y and Z are similarly constructed and arranged as the controller 24 of Zone X.
More precisely, the correlator 24a is adapted to receive and categorize the alert messages and to generate a number of tables including the categorized alert messages. The tables including the categorized alert messages are stored in the alert message database 24b, which is coupled to the correlator module 24a. The correlator module 24a is further adapted to compare the alert messages to determine if trends exist. One example of a trend can be a plurality of alert messages that are traceable through the computer network system 10 to a particular computer system 16. Another example of trend can be a plurality of alert messages that include similar characteristics.
The communication interface adapter 24e operates to provide a communication interface to an external computer device 30, such as a notebook computer, desktop computer, server or personal digital assistant ("PDA"). The personal computing device 30 can be adapted to run network management interface software 30a, such as HP Openview'~, which can be obtained from Hewlett-Packard Company of Palo Alto, California. The network management interface software 30a is adapted to interface with the alert message database 24b and to provide a graphical user interface ("GUI") on the display 30b of the computing device 30.
Thereafter, a network administrator can view and respond to the alert messages.
Alternatively, the personal computing device 30 can include a conventional web browser 30c, which is similarly adapted to interface with the alert message database 24b via a web server 24c and access scripts module 24d and to provide a graphical user interface ("GUI") on the display 30b of the computing device 30. Similar to that described above, the network administrator can view and respond to the alert messages.
Once the controller has received the alert message from the collector 20, the controller 24 can apply several approaches to trace the DoS attack back to its origin, such as, directed tracing or distributed correlation. In directed tracing, information related to the computer network system topology is processed to work backwards towards the source or origin of the DoS attack. Directed tracing relies on the fact that both the muter system's incoming interface statistic for a DoS attack and information related to the computer network system 10 topology are known to determine what routers are upstream on a particular link that carried the DoS
attack packet. With this knowledge, upstream routers (not shown) can then be queried for their participation in transiting the attack packet. It is useful to note that since these upstream routers are looking for a specific attack signature, it is much easier to find the statistics related to the attack packet.
In distributed correlation, the controller 24 compares the attack signature or characteristic information related to the DoS attack with similar information detected at other routers 22b and 22c in the computer network system 10. DoS attack signatures that substantially match are grouped and implicitly form the path from the source of the DoS attack to the target. This contrasts with the directed tracing approach, as previously described, where a general attack profile is extracted from every router's statistics to uncover the global path for the DoS
attack packet.
After detection and tracing of the DoS attack packet, the controller 24 blocks DoS attacks as close to their Source as possible. By taking a global view of the ISP computer networks 14a, 14b and 14c, the controller 24 is able to coordinate the configuration of the routing systems 22, 22b and/or 22c to filter certain types of traffic by employing either custom filtering hardware (not shown) or filtering mechanisms included in the routing systems. The custom filtering hardware can be incrementally deployed in tile network. Example filtering mechanisms can include Access Control List entries ("ACLs"), and Committed Access Rate ("CAR") limiters, which can be provided by Cisco Systems Corporation of San Jose, California. An example of filtering hardware can include Internet Processor 11, which can be provided by Juniper Networks Corporation of Sunnyvale, California, which can be utilized to download coarse-grained filters that will remove unwanted DoS attacks in real-time.
Referring again to Fig. 4, in one specific example, a DoS attack from a computer system 17 located in Zone U of ISP computer network 14b to one specific computer system 16a of Zone X can be detected, tracked and blocked by the system 5 of the present invention.
In this example, the DoS attack executed by the computer system 17 includes a SYN-packet flood DoS attack with spoofed source addresses. SYN-packets are TCP/IP packets that initiate data transfer sessions. As such, a SYN-packet flood denies legitimate traffic access to the targeted computer system 16a, because it uses up available bandwidth and consumes predefined computer system 16a resources. A spoofed source addresses is one in which the attacking computer system 17 hides it actual computer network location from the targeted computer system 16a by forging the return address on the TCP/IP data packet (Fig. 2).
This makes it difficult to identify the source of the traffic when examining forensic data at the targeted computer system 16a.
Referring further to Fig. 7, the specific trajectory of the SYN-packet flood attack from the computer system 17 of Zone U located in the ISP-2 computer network 14b to computer system 16a of Zone X located in the ISP-1 computer network 14a is illustrated by the DoS attack path 100. The DoS attack path 100 commences at the attacking computer system 17 and extends through the routing system 22d, through the collector 20c, through the controller 24b, through the computer network 18, through the controller 24, through the collector 20, through the routing system 22 and to the targeted computer system 16a.
After the SYN-packets flow through the routing system 22, the routing system 22 generates flow statistics, which are exported to the collector 20.
These flow statistics describe the traffic flow characteristics between computer system 17 (DoS attacker) and the computer system 16a (target of DoS attack).
The SYN-packet flood attack is represented in these exported flow statistics as the computer system 16a receiving an unusually high number of TCP sessions. This anomalous traffic is detected at the collector 20 and an alert message is communicated to the controller 24. After the controller 24 receives the alert message, it schedules a periodic sampling of anomaly statistics from collector 20, which can be represented by a pair of request and reply messages communicated between the collector 20 and the controller 24.
Referring again to Fig. 5, during this SYN-packet flood attack, the collector 20 collects flow statistics related to the SYN-packets and stores the flow statistics in the buffer 20a, which is located on the collector 20. The buffer 20a normalizes the incoming flow-statistics to form records. The records are places into a shared table. The storm detector module 20b analyzes the records in this shared table and detects anomalous traffic. In this example, the storm detector 20b detects the pattern of records as a SYN-packet flood attack, because the number of records exceeds a predetermined threshold defined on the storm detector 20b. The storm profiler 20d also analyzes the records and based on this analysis, the storm profiler 20d adaptively adjusts the predetermined threshold defined on the storm detector 20b. After detecting the SYN-packet flood attack, the storm detector 20b sends an alert message along with a signature (e.g. a fingerprint of the alert) to the local controller 20f. The local controller 20f adds the signature of the alert to a table in memory, which represents the on-going local anomalies. When one of these local ongoing anomalies reaches a significant level of interest (e.g. a second predetermined threshold), such as a long duration or high severity, the local controller 20f notifies an anomaly-profiler module (not shown) to add a new anomaly to the set of current-anomalies that it measures. Thereafter, the anomaly-profiler module analyzes the normalized flow statistics in buffer 20a that are related to the anomaly and begins to collect long-term statistics about the anomaly.
Furthermore, the anomaly-profiler places periodic snapshots of these long-term statistics into the storm profiler database 20e, which is located on the collector 20.
At the same time, the local controller forwards the alert to the controller 24 as an alert message. The controller 24 can periodically request updated anomaly information, which in this example relates to a SYN-packet flood attack, from the local controller 20. The local controller 20 can respond by providing the controller 24 with the most recently collected long-term statistics related to the anomaly.
As shown in Fig. 6, the specific operation of the controller 24 includes receiving the alert messages, anomaly fingerprints and anomaly statistical summaries from the collector 20 at the correlator 24a located on the controller 24.
Upon receipt of the alert message from collector 20, the correlator 24a schedules a periodic request for updated anomaly statistical summaries. The correlator 24a translates the updated anomaly statistical summaries and correlates their features using attributes in the anomaly fingerprint to identify system-wide anomalies.
These controller-specific anomaly statistics are then translated into system-wide representation anomalies, which are subsequently stored in the database 24b.
In the SYN-packet flood based attack example, the correlator 24a located on the controller 24 sends a simple network management protocol ("SNMP") alert message to the network management interface 30a located on the personal computing device 30. This alert message notifies the network administrator and/or security operators as to the presence of the SYN-packet based flood attack. Included in this alert message is the network address, such as the universal resource locator ("URL") that describes the anomaly's location in the database 24b of the controller 24. The network management interface 30a can share the URL associated with the SYN-packet based flood attack with the web browser 30c also located on the personal computing device 30. The browser 30c can use a hyper text transfer protocol ("HTTP") type transfer using the URL to visualize the statistics related to the SYN-packet based flood attack, and to generate ACL
and CAR entries for remediation of the SYN-packet based flood attack. When the web server 24c receives the URL from the browser 30c, the web server 24c invokes server-side access scripts 24d, which generates queries to the database 24b for generating a dynamic HTML web page. The network administrator and/or security operators can view the SYN-packet based flood attack anomalies on the web page, which is displayed on the display 30b of the computing device 30.
Although not shown, in an embodiment, the system 5 for detecting, tracking and blocking denial of service attacks can be located on a removable storage medium. The removable storage medium can be transported and selectively loaded onto the routing systems 22, 22b and/or 22c. Alternatively, the system 5 for detecting, tracking and blocking denial of service attacks can be partially located on the routing systems 22, 22b and/or 22c and partially located on other servers (not shown). For example, the collector 20 can be located on routing system 22 and the collector 20b can be located on routing system 22c. Further, zone controller 24 can be co-located with either the collector 20, the collector 20b, or , zone controller 24 can be located on another server (not shown).
Having thus described at least one illustrative embodiment of the invention, various alterations, modifications and improvements will readily occur to those skilled in the art. Such alterations, modifications and improvements are intended to be within the scope and spirit of the invention. Accordingly, the foregoing description is by way of example only and is not intended as limiting.
The invention's limit is defined only in the following claims and the equivalents thereto.
SUMMARY OF THE INVENTION
In accordance with principles of the present invention, a system and method is provided for detecting, tracking and blocking DoS attacks, which can occur between local computer systems and/or between remote computer systems, network links, and/or routing systems over a computer network.
In one embodiment of the present invention, a system includes a collector adapted to receive a plurality of data statistics from the computer network and to process the plurality of data statistics to detect one or more data packet flow anomalies and to generate a plurality of signals representing the one or more data packet flow anomalies. The system further includes a controller which is coupled to the collector. The controller is constructed and arranged to receive and respond to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source. The controller is further constructed and arranged to block the one or more data packet flow anomalies using one or more filtering mechanisms executed in close proximity to the at least one source.
The one or more filtering mechanisms can include a plurality of filter list entries, such as access control list entries as well as firewall filter entries, and/or a plurality of rate limiting entries, such as committed access rate (CAR) entries.
In aspect of the present invention, the collector includes a buffer coupled to the computer network and a detector coupled to the buffer. The collector further includes a profiler coupled to the buffer and to the detector. The buffer is adapted to receive and process the plurality of data statistics to generate at least one record that is communicated to the profiler. The profiler processes the record to generate a predetermined threshold. The detector is adapted to receive and process the predetermined threshold and the at least one record to detect if attributes associated with the record exceed the predetermined threshold, which represents the one or more data packet flow anomalies.
The profiler may include means for aggregating the data statistics to obtain a traffic profile of network flows.
The data statistics may be aggregated based on at least one invariant feature of the network flows.
The data statistics may also be aggregated based on temporal, static network and dynamic routing parameters.
The at least one invariant feature may include source and destination endpoints.
The collector further includes a local controller coupled to the detector and to the profiler. The local controller is adapted to receive and respond to the one or more data packet flow anomalies by generating the plurality of signals, which represents the one or more data packet flow anomalies.
The detector includes a database for storing the at least one record, predetermined threshold, the one or more data packet flow anomalies, and related information. Similarly, the profiler includes a database for storing a plurality of data packet flow profiles and related information.
In an aspect of the present invention, the controller includes a correlator coupled to the collector. The correlator is adapted to receive and normalize the plurality of signals representing the one or more data packet flow anomalies. The correlator is further adapted to generate an anomaly table including the attributes related to the one or more data packet flow anomalies. The correlator includes a database for storing the anomaly table. Additionally, the correlator _g_ includes an adapter that is constructed and arranged to communicate the anomaly table to a computer device for further processing.
The controller further includes a web server and access scripts that cooperate with the web server to enable the computing device to access the database defined on the controller to view the anomaly table.
In accordance with the present invention, the method for detecting, tracking and blocking one or more denial of service attacks over a computer network includes the steps of collecting a plurality of data statistics from the computer network; processing the plurality of data statistics to detect one or more data packet flow anomalies; generating a plurality of signals representing the one or more data packet flow anomalies; and receiving and responding to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source.
The method further includes the step of blocking the one or more data packet flow anomalies in close proximity to the at least one source.
The step of collecting the plurality of data statistics includes buffering the plurality of data statistics; processing the plurality of data statistics to generate at least one record; and receiving and profiling the at least one record to generate a predetermined threshold.
The step of collecting the plurality of data statistics further includes detecting if attributes related to the at least one record exceed the predetermined threshold representing the one or more data packet flow anomalies.
The step of collecting the plurality of data statistics further includes responding locally to the one or more data packet flow anomalies by generating the plurality of signals representing the one or more data packet flow anomalies.
The step of receiving and responding to the plurality of signals includes correlating the plurality of signals representing the one or more data packet flow anomalies; and generating an anomaly table including the attributes related to the one or more data packet flow anomalies.
The step of receiving and responding to the plurality of signals further includes the step of communicating the anomaly table to a computing device for further processing.
The above objects and other objects, features, and advantages of the present invention are readily apparent from the following detailed description of the best mode for carrying out the invention when taken in connection with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FIGURE 1 is a high level block diagram of a conventional computer network system;
FIGURE 2 is an exemplary data packet format which can be adapted for communication over the conventional computer network system shown in Figure 1;
FIGURE 3 is a high level block diagram of a computer network system according to one embodiment of the present invention;
FIGURE 4 is a partially exploded view of the computer network system shown in Figure 3;
FIGURE 5 is a high level block diagram of the collector shown in Figure 4;
FIGURE 6 is a high level block diagram of the controller shown in Figure 4; and FIGURE 7 is a high level block diagram exemplifying a DoS attack.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS) For purposes of illustration and to facilitate a further understanding of the present invention, described below is a reference to an Internet-based computer network system and a method for processing data. However, as understood by one skilled in the art, the present invention is not limited to Internet-based systems and can include systems employing other computer networks as well as stand alone systems.
In accordance with principles of the present invention, a system and method is set forth for detecting, tracking and blocking DoS attacks, which can occur between local computer systems and/or between remote computer systems, network links, and/or routing systems over a computer network.
Referring to Fig. 3, a system 5 for detecting, tracking and blocking DoS attacks is incorporated in the computer network system 10 in accordance with one embodiment of the present invention. The system 5 can be located on a single server computer (not shown), which is in communication with components of the computer network system 10 or distributed over a plurality of server computers (not shown), which are also in communication with components of the computer network system 10.
The computer network system 10 includes a plurality of Internet Service Provider computer networks 14a, 14b and 14c (hereinafter ISP computer networks)") coupled over a computer network 18. The ISP computer networks 14a, 14b and 14c can also be coupled directly to each other. Each of the ISP
computer networks 14a, 14b and/or 14c can include a plurality of computer network zones. As exemplified in Fig. 3, the ISP computer network 14a includes computer network Zone X, Zone Y and Zone Z. The ISP computer network 14b includes computer network Zone U and Zone V. The ISP computer network 14c includes computer network Zone W.
Fig. 4 shows a partially expanded view of the system 5, which is incorporated in the partially expanded view of the computer network system 10.
In Fig, 4, Zone X of the ISP computer network 14a includes a number of local area networks ("LAN(s) ") coupled to a central routing system 22. Each LAN is coupled with a plurality of computer systems 16a, 16b, 16c, 16e, 16f, 16g, 16h, 16i and 16j (hereinafter collectively referred to as "computer systems) 16"). The computer network Zones Y and Z, which are also located on the ISP computer network 14a, can be similarly constructed and arranged as computer network Zones X.
Further, the computer network Zones U and V, which are located on the ISP computer network 14b and the computer network Zone W, which is located on the ISP
computer network 14c, can also be similarly constructed and arranged as computer network Zones X.
The system 5 includes a collector 20, an optional collector 20b and a zone controller 24. In Zone X, the collector 20 is coupled to the central routing system 22. The collector 20 is further coupled to a zone controller 24, which provides a primary interface to Zone X of the ISP computer network 14a. The computer network Zones Y and Z, which are also located on the ISP computer network 14a can be similarly constructed and arranged as computer network Zone X. Further, the computer network Zones U and V, which are located on the ISP
computer network 14b and the computer network Zone W, which is located on the ISP computer network 14c, can also be similarly constructed and arranged as computer network Zones X.
In another embodiment, the collector 20 can be coupled to one or more other router systems, such as the routing system 22b, as exemplified in Fig.
4. In addition, the zone controller 24 can be coupled to one or more other collectors, such as the collector 20b, as also exemplified in Fig. 4. Further, the collector 20b, can be coupled to one or more other routing systems, such as the routing system 22c.
The zone controller 24 located in Zone X of the ISP Computer network 14a provides a primary interface to the computer network Zone Y and to the computer network Zone Z, which are both located on the ISP computer network 14a. The zone controller 24 further provides a primary interface to the computer network Zone U and the computer network Zone V, which are located on the ISP
computer network 14b, over the computer network 18. Similarly, the zone controller 24 further provides a primary interface to computer network Zone W, which is located on the ISP computer network 14c, over the computer network 18.
In an embodiment of the present invention, the computer systems 16 located in computer network Zone X of the ISP computer network 14a can each comprise a conventional computer server such as an "NT-Server" which can be provided by Microsoft of Richmond, Washington or a "Unix Solaris Server" which can be provided by Sun Micro Systems of Palo Alto, California. These computer systems 16 can be programmed with conventional Web-page interface software such as: "Visual Basic", "Java", "JavaScript", "HTML/DHTML", "C++", "J+", "Pert" or "Perlscript", or "ASP". These computer systems can further be programmed with an operating system, Web server software, Web Application software, such as an e-commerce application and computer network interface software.
Each of the routing systems 22, 22b and 22c, as shown in Fig. 4, can be a conventional router, such as a "Cisco 12000", available from Cisco Corporation of San Jose, California. Further, each of the routing systems can be adapted to run data packet flow statistical software, such as Netflow'~
software, also available from Cisco Corporation of San Jose, California. Alternatively, each of the routing systems, as shown in Fig. 4, can be another conventional router, such as an "M-40", available from Juniper Corporation of Sunnyvale, California.
Further, each of the routing systems can be adapted to run data packet flow statistical software, such as Juniper Cflowdl'"s software, also available from Juniper Corporation of Sunnyvale, California. The packet flow statistical software running on each of the routing systems 22, 22b and 22c enable each of the routing systems 22, 22b and 22c to gather and store data packet flow statistical information.
The data packet flow statistical information can include the number of packets which have been communicated between computer systems 16, the duration of communication between each of the computer systems 16, the total number of packets communicated over each LAN (which is typically used for capacity planning) as well as other various data packet flow statistical information.
Fig. 5 shows the collector 20 in detail. The collector includes an input buffer 20a coupled to the routing system 22. The input buffer is coupled to a storm detector 20b and to a storm profiler 20d. The storm detector 20b includes a detector database and the storm profiler 20d includes a profiler database 20e. The collector 20 further includes a local controller 20f, which is coupled to the storm detector 20b and to a storm profiler 20d. The local controller 20f is further coupled to the zone controller 24.
The collector 20 is adapted to receive the data packet flow statistical information from the routing system 22 and to process the data packet flow statistical information to detect data packet flow anomalies. The collector 22b of Zone X, as well as other various collectors (not shown), which are included in the other various Zones U, V, W, Y and Z are similarly constructed and arranged as the collector 20 of Zone X.
The input buffer 20a, located on collector 20, is adapted to normalize or categorize the data packet flow statistical information and to generate a number of records including the normalized data packet flow statistical information.
The storm detector 20b is adapted to detect the data packet flow anomalies by comparing the records to an anomaly pattern and/or a predetermined threshold. If components of the normalized data packet flow statistical information exceed the predetermined threshold, a data packet flow anomaly is detected. Thereafter, the detected data packet flow anomaly and data associated with the data packet flow anomaly, such as the source and destination addresses of the flow information can be stored in the detector database 20c.
The storm profiler module 20d is adapted to receive the normalized data packet flow statistical information or records from the input buffer 20a and to generate the predetermined threshold, which is concomitantly communicated to the storm detector module 20b. In this configuration, the predetermined threshold defined in the storm detector is adaptively adjusted based on changing trends or profiles of the normalized data packet flow statistical information received by the storm profiler 20d. The changing trends or profiles of the normalized data packet flow statistical information, for example, can include changes in the average bandwidth allocated to each of the computer systems 16 during a particular period of time or changes to the number of computer systems 16 communicating information at the same instant of time.
The local controller 20f, which is coupled to both the storm detector 20b and to the storm profiler 20f, is adapted to receive the data packet flow anomaly from the storm detector 20b, as well as data associated with the data packet flow anomaly, as previously described. After receiving the data packet flow anomaly and the associated data from the storm detector, the local controller 20f generates a signal or an alert message. The alert message can include pertinent information related to the anomaly. The pertinent information related to the anomaly can include the characteristics of the anomaly, the source and destination of the anomaly, the protocols involved and their sub-protocols, the detection mechanism used to identify the anomaly, the predetermined threshold, routing systems in the path of the anomaly, as well as the magnitude or severity of the anomaly. The alert message is communicated to the zone controller 24 to enable the zone controller 24 to further process the alert message and to enable the zone controller 24 to communicate the alert message to other Zones U, V, W, X, Y and Z and/or ISPs 14b and 14c.
In an embodiment, the collector takes samples of several types of statistics, which are obtained by the router 22, such as single packet statistics and flow-based statistics. Single packet statistics provide essential information about a set of packets entering a forwarding node or router 22. Some of the single packet statistics can include: destination and source IP addresses, incoming interface, protocol, ports, and length. After collection of these single-packet statistics, the collector can process the statistics as described above to adaptively adjust the predetermined threshold defined in the storm detector, which detects the packet anomalies.
Flow-based statistics include a set of packets that are related to the same logical traffic flow. The concept of flow-based statistics is generally defined as a stream of packets that all have the same characteristics, such as, source address, destination address, protocol type, source port, and destination port. The flow-based statistics may be either uni-directional or bidirectional. Single-packet statistics can be aggregated to generate a single flow-based statistic. An example of the single flow-based statistic can include a flow duration, number of packets included over a predetermined duration, mean bytes per packet, etc.
Referring further to Fig. 6, the zone controller 24 includes a correlator 24a coupled to the collector 20. The correlator 24a includes a communication interface adapter 24e. The zone controller 24 further includes an alert message database 24b, which is coupled to the correlator module 24a. A
web server 24c and access scripts software 24d are also defined on the controller 24.
The zone controller 24 is adapted to receive a plurality of alert messages from the collector 20, and to process the alert messages by aggregating the alert messages based on the pertinent information related to the anomaly, as described above. The zone controller 24 of Zone X, as well as other various controllers (not shown), which are included in the other various Zones U, V, W, Y and Z are similarly constructed and arranged as the controller 24 of Zone X.
More precisely, the correlator 24a is adapted to receive and categorize the alert messages and to generate a number of tables including the categorized alert messages. The tables including the categorized alert messages are stored in the alert message database 24b, which is coupled to the correlator module 24a. The correlator module 24a is further adapted to compare the alert messages to determine if trends exist. One example of a trend can be a plurality of alert messages that are traceable through the computer network system 10 to a particular computer system 16. Another example of trend can be a plurality of alert messages that include similar characteristics.
The communication interface adapter 24e operates to provide a communication interface to an external computer device 30, such as a notebook computer, desktop computer, server or personal digital assistant ("PDA"). The personal computing device 30 can be adapted to run network management interface software 30a, such as HP Openview'~, which can be obtained from Hewlett-Packard Company of Palo Alto, California. The network management interface software 30a is adapted to interface with the alert message database 24b and to provide a graphical user interface ("GUI") on the display 30b of the computing device 30.
Thereafter, a network administrator can view and respond to the alert messages.
Alternatively, the personal computing device 30 can include a conventional web browser 30c, which is similarly adapted to interface with the alert message database 24b via a web server 24c and access scripts module 24d and to provide a graphical user interface ("GUI") on the display 30b of the computing device 30. Similar to that described above, the network administrator can view and respond to the alert messages.
Once the controller has received the alert message from the collector 20, the controller 24 can apply several approaches to trace the DoS attack back to its origin, such as, directed tracing or distributed correlation. In directed tracing, information related to the computer network system topology is processed to work backwards towards the source or origin of the DoS attack. Directed tracing relies on the fact that both the muter system's incoming interface statistic for a DoS attack and information related to the computer network system 10 topology are known to determine what routers are upstream on a particular link that carried the DoS
attack packet. With this knowledge, upstream routers (not shown) can then be queried for their participation in transiting the attack packet. It is useful to note that since these upstream routers are looking for a specific attack signature, it is much easier to find the statistics related to the attack packet.
In distributed correlation, the controller 24 compares the attack signature or characteristic information related to the DoS attack with similar information detected at other routers 22b and 22c in the computer network system 10. DoS attack signatures that substantially match are grouped and implicitly form the path from the source of the DoS attack to the target. This contrasts with the directed tracing approach, as previously described, where a general attack profile is extracted from every router's statistics to uncover the global path for the DoS
attack packet.
After detection and tracing of the DoS attack packet, the controller 24 blocks DoS attacks as close to their Source as possible. By taking a global view of the ISP computer networks 14a, 14b and 14c, the controller 24 is able to coordinate the configuration of the routing systems 22, 22b and/or 22c to filter certain types of traffic by employing either custom filtering hardware (not shown) or filtering mechanisms included in the routing systems. The custom filtering hardware can be incrementally deployed in tile network. Example filtering mechanisms can include Access Control List entries ("ACLs"), and Committed Access Rate ("CAR") limiters, which can be provided by Cisco Systems Corporation of San Jose, California. An example of filtering hardware can include Internet Processor 11, which can be provided by Juniper Networks Corporation of Sunnyvale, California, which can be utilized to download coarse-grained filters that will remove unwanted DoS attacks in real-time.
Referring again to Fig. 4, in one specific example, a DoS attack from a computer system 17 located in Zone U of ISP computer network 14b to one specific computer system 16a of Zone X can be detected, tracked and blocked by the system 5 of the present invention.
In this example, the DoS attack executed by the computer system 17 includes a SYN-packet flood DoS attack with spoofed source addresses. SYN-packets are TCP/IP packets that initiate data transfer sessions. As such, a SYN-packet flood denies legitimate traffic access to the targeted computer system 16a, because it uses up available bandwidth and consumes predefined computer system 16a resources. A spoofed source addresses is one in which the attacking computer system 17 hides it actual computer network location from the targeted computer system 16a by forging the return address on the TCP/IP data packet (Fig. 2).
This makes it difficult to identify the source of the traffic when examining forensic data at the targeted computer system 16a.
Referring further to Fig. 7, the specific trajectory of the SYN-packet flood attack from the computer system 17 of Zone U located in the ISP-2 computer network 14b to computer system 16a of Zone X located in the ISP-1 computer network 14a is illustrated by the DoS attack path 100. The DoS attack path 100 commences at the attacking computer system 17 and extends through the routing system 22d, through the collector 20c, through the controller 24b, through the computer network 18, through the controller 24, through the collector 20, through the routing system 22 and to the targeted computer system 16a.
After the SYN-packets flow through the routing system 22, the routing system 22 generates flow statistics, which are exported to the collector 20.
These flow statistics describe the traffic flow characteristics between computer system 17 (DoS attacker) and the computer system 16a (target of DoS attack).
The SYN-packet flood attack is represented in these exported flow statistics as the computer system 16a receiving an unusually high number of TCP sessions. This anomalous traffic is detected at the collector 20 and an alert message is communicated to the controller 24. After the controller 24 receives the alert message, it schedules a periodic sampling of anomaly statistics from collector 20, which can be represented by a pair of request and reply messages communicated between the collector 20 and the controller 24.
Referring again to Fig. 5, during this SYN-packet flood attack, the collector 20 collects flow statistics related to the SYN-packets and stores the flow statistics in the buffer 20a, which is located on the collector 20. The buffer 20a normalizes the incoming flow-statistics to form records. The records are places into a shared table. The storm detector module 20b analyzes the records in this shared table and detects anomalous traffic. In this example, the storm detector 20b detects the pattern of records as a SYN-packet flood attack, because the number of records exceeds a predetermined threshold defined on the storm detector 20b. The storm profiler 20d also analyzes the records and based on this analysis, the storm profiler 20d adaptively adjusts the predetermined threshold defined on the storm detector 20b. After detecting the SYN-packet flood attack, the storm detector 20b sends an alert message along with a signature (e.g. a fingerprint of the alert) to the local controller 20f. The local controller 20f adds the signature of the alert to a table in memory, which represents the on-going local anomalies. When one of these local ongoing anomalies reaches a significant level of interest (e.g. a second predetermined threshold), such as a long duration or high severity, the local controller 20f notifies an anomaly-profiler module (not shown) to add a new anomaly to the set of current-anomalies that it measures. Thereafter, the anomaly-profiler module analyzes the normalized flow statistics in buffer 20a that are related to the anomaly and begins to collect long-term statistics about the anomaly.
Furthermore, the anomaly-profiler places periodic snapshots of these long-term statistics into the storm profiler database 20e, which is located on the collector 20.
At the same time, the local controller forwards the alert to the controller 24 as an alert message. The controller 24 can periodically request updated anomaly information, which in this example relates to a SYN-packet flood attack, from the local controller 20. The local controller 20 can respond by providing the controller 24 with the most recently collected long-term statistics related to the anomaly.
As shown in Fig. 6, the specific operation of the controller 24 includes receiving the alert messages, anomaly fingerprints and anomaly statistical summaries from the collector 20 at the correlator 24a located on the controller 24.
Upon receipt of the alert message from collector 20, the correlator 24a schedules a periodic request for updated anomaly statistical summaries. The correlator 24a translates the updated anomaly statistical summaries and correlates their features using attributes in the anomaly fingerprint to identify system-wide anomalies.
These controller-specific anomaly statistics are then translated into system-wide representation anomalies, which are subsequently stored in the database 24b.
In the SYN-packet flood based attack example, the correlator 24a located on the controller 24 sends a simple network management protocol ("SNMP") alert message to the network management interface 30a located on the personal computing device 30. This alert message notifies the network administrator and/or security operators as to the presence of the SYN-packet based flood attack. Included in this alert message is the network address, such as the universal resource locator ("URL") that describes the anomaly's location in the database 24b of the controller 24. The network management interface 30a can share the URL associated with the SYN-packet based flood attack with the web browser 30c also located on the personal computing device 30. The browser 30c can use a hyper text transfer protocol ("HTTP") type transfer using the URL to visualize the statistics related to the SYN-packet based flood attack, and to generate ACL
and CAR entries for remediation of the SYN-packet based flood attack. When the web server 24c receives the URL from the browser 30c, the web server 24c invokes server-side access scripts 24d, which generates queries to the database 24b for generating a dynamic HTML web page. The network administrator and/or security operators can view the SYN-packet based flood attack anomalies on the web page, which is displayed on the display 30b of the computing device 30.
Although not shown, in an embodiment, the system 5 for detecting, tracking and blocking denial of service attacks can be located on a removable storage medium. The removable storage medium can be transported and selectively loaded onto the routing systems 22, 22b and/or 22c. Alternatively, the system 5 for detecting, tracking and blocking denial of service attacks can be partially located on the routing systems 22, 22b and/or 22c and partially located on other servers (not shown). For example, the collector 20 can be located on routing system 22 and the collector 20b can be located on routing system 22c. Further, zone controller 24 can be co-located with either the collector 20, the collector 20b, or , zone controller 24 can be located on another server (not shown).
Having thus described at least one illustrative embodiment of the invention, various alterations, modifications and improvements will readily occur to those skilled in the art. Such alterations, modifications and improvements are intended to be within the scope and spirit of the invention. Accordingly, the foregoing description is by way of example only and is not intended as limiting.
The invention's limit is defined only in the following claims and the equivalents thereto.
Claims (33)
1. A system for detecting, tracking and blocking one or more denial of service attacks over a computer network, the system comprising:
a collector adapted to receive a plurality of data statistics from the computer network and to process the plurality of data statistics to detect one or more data packet flow anomalies and to generate a signal representing the one or more data packet flow anomalies; and a controller coupled to the collector to receive the signal;
wherein the controller is constructed and arranged to respond to the signal by tracking attributes related to the one or more data packet flow anomalies to at least one source, and wherein the controller is constructed and arranged to block the one or more data packet flow anomalies.
a collector adapted to receive a plurality of data statistics from the computer network and to process the plurality of data statistics to detect one or more data packet flow anomalies and to generate a signal representing the one or more data packet flow anomalies; and a controller coupled to the collector to receive the signal;
wherein the controller is constructed and arranged to respond to the signal by tracking attributes related to the one or more data packet flow anomalies to at least one source, and wherein the controller is constructed and arranged to block the one or more data packet flow anomalies.
2. The system of claim 1, wherein the collector includes a buffer coupled to the computer network and being adapted to process the plurality of data statistics to generate at least one record.
3. The system of claim 2, wherein the collector further includes a profiler coupled to the buffer and being adapted to receive and process the record to generate a predetermined threshold.
4. The system of claim 3, wherein the profiler includes means for aggregating the data statistics to obtain a traffic profile of network flows.
5. The system of claim 4, wherein the data statistics are aggregated based on at least one invariant feature of the network flows.
6. The system of claim 4, wherein data statistics are aggregated based on temporal, static network and dynamic routing parameters.
7. The system of claim 5, wherein the at least one invariant feature includes source and destination endpoints.
8. The system of claim 3, wherein the collector further includes a detector coupled to the buffer and to the profiler, the collector being adapted to receive and process the record and the predetermined threshold to detect if attributes associated with the record exceed the predetermined threshold representing the one or more data packet flow anomalies.
9. The system of claim 8, wherein the collector further includes a local controller coupled to the detector and to the profiler and being adapted to receive and respond to the one or more data packet flow anomalies by generating the signal representing the one or more data packet flow anomalies.
10. The system of claim 9, wherein the detector includes a database for storing the at least one record, predetermined threshold, the one or more data packet flow anomalies, and related information.
11. The system of claim 10, wherein the profiler includes a database for storing a plurality of data packet flow profiles and related information.
12. The system of claim 1, wherein the controller includes a filtering mechanism for blocking the one or more data packet flow anomalies.
13. The system of claim 12, wherein the filtering mechanism includes a plurality of filter list entries.
14. The system of claim 12, wherein the filtering mechanism includes a plurality of rate limiting entries.
15. The system of claim 1, wherein the controller includes a correlator coupled to the collector and being adapted to receive and normalize the plurality of signals representing the one or more data packet flow anomalies and to generate an anomaly table including the attributes related to the one or more data packet flow anomalies.
16. The system of claim 15, wherein the correlator includes a database for storing the anomaly table.
17. The system of claim 16, wherein the correlator further includes an adapter that is constructed and arranged to communicate the anomaly table to a computing device for further processing.
18. The system of claim 16, wherein the controller further includes:
a web server; and access scripts that cooperate with the web server to enable the computing device to access the database defined on the controller to view the anomaly table.
a web server; and access scripts that cooperate with the web server to enable the computing device to access the database defined on the controller to view the anomaly table.
19. A system comprising:
at least one routing system;
a plurality of computer systems coupled to the routing system; and means for detecting one or more denial of service attacks communicated to the plurality of computer systems over the at least one routing system.
at least one routing system;
a plurality of computer systems coupled to the routing system; and means for detecting one or more denial of service attacks communicated to the plurality of computer systems over the at least one routing system.
20. The system of claim 19, further including a means for tracking the one or more denial of service attacks communicated to the plurality of computer systems over the at least one routing system.
21. The system of claim 20, further including a means for blocking the one or more denial of service attacks communicated to the plurality of computer systems over the at least one routing system.
22. The system of claim 21, wherein the means for detecting includes a means for collecting a plurality of data statistics from the at least one routing system.
23. The system of claim 22, wherein the means for detecting further includes a means for processing the plurality of data statistics to detect one or more data packet flow anomalies.
24. The system of claim 23, wherein the means for detecting further includes a means of generating a plurality of signals representing the one or more data packet flow anomalies.
25. The system of claim 24, wherein the means for tracking includes a means for receiving and responding to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source.
26. The system of claim 19, further including a means for communicating the one or more denial of service attacks to a computing device for further processing.
27. A method for detecting, tracking and blocking one or more denial of service attacks over a computer network, the system comprising the steps of:
collecting a plurality of data statistics from the computer network;
processing the plurality of data statistics to detect one or more data packet flow anomalies;
generating a plurality of signals representing the one or more data packet flow anomalies; and receiving and responding to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source.
collecting a plurality of data statistics from the computer network;
processing the plurality of data statistics to detect one or more data packet flow anomalies;
generating a plurality of signals representing the one or more data packet flow anomalies; and receiving and responding to the plurality of signals by tracking attributes related to the one or more data packet flow anomalies to at least one source.
28. The method of claim 27, further including the step of blocking the one or more data packet flow anomalies in close proximity to the at least one source.
29. The method of claim 28, wherein the step of collecting the plurality of data statistics includes:
buffering the plurality of data statistics;
processing the plurality of data statistics to generate at least one record; and receiving and profiling the at least one record to generate a predetermined threshold.
buffering the plurality of data statistics;
processing the plurality of data statistics to generate at least one record; and receiving and profiling the at least one record to generate a predetermined threshold.
30. The method of claim 29, wherein the step of collecting the plurality of data statistics further includes;
detecting if attributes related to the at least one record exceed the predetermined threshold representing the one or more data packet flow anomalies.
detecting if attributes related to the at least one record exceed the predetermined threshold representing the one or more data packet flow anomalies.
31. The method of claim 30, wherein the step of collecting the plurality of data statistics further includes:
responding locally to the one or more data packet flow anomalies by generating the plurality of signals representing the one or more data packet flow anomalies.
responding locally to the one or more data packet flow anomalies by generating the plurality of signals representing the one or more data packet flow anomalies.
32. The method of claim 27, wherein the step of receiving and responding to the plurality of signals includes:
correlating the plurality of signals representing the one or more data packet flow anomalies; and generating an anomaly table including the attributes related to the one or more data packet flow anomalies.
correlating the plurality of signals representing the one or more data packet flow anomalies; and generating an anomaly table including the attributes related to the one or more data packet flow anomalies.
33. The method of claim 32, wherein the step of receiving and responding to the plurality of signals further includes the step of communicating the anomaly table to a computing device for further processing.
Applications Claiming Priority (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US23148000P | 2000-09-08 | 2000-09-08 | |
US23148100P | 2000-09-08 | 2000-09-08 | |
US23147900P | 2000-09-08 | 2000-09-08 | |
US60/231,481 | 2000-09-08 | ||
US60/231,479 | 2000-09-08 | ||
US60/231,480 | 2000-09-08 | ||
US09/855,808 US20020032871A1 (en) | 2000-09-08 | 2001-05-15 | Method and system for detecting, tracking and blocking denial of service attacks over a computer network |
US09/855,808 | 2001-05-15 | ||
PCT/US2001/015696 WO2002021800A1 (en) | 2000-09-08 | 2001-05-16 | Method and system for detecting, tracking and blocking denial of service attacks over a computer network |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2426451A1 true CA2426451A1 (en) | 2002-03-14 |
Family
ID=27499608
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002426451A Abandoned CA2426451A1 (en) | 2000-09-08 | 2001-05-16 | Method and system for detecting, tracking and blocking denial of serviceattacks over a computer network |
Country Status (5)
Country | Link |
---|---|
US (1) | US20020032871A1 (en) |
EP (1) | EP1317835A1 (en) |
AU (1) | AU2001266580A1 (en) |
CA (1) | CA2426451A1 (en) |
WO (1) | WO2002021800A1 (en) |
Families Citing this family (240)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6184961B1 (en) * | 1997-07-07 | 2001-02-06 | Lg Electronics Inc. | In-plane switching mode liquid crystal display device having opposite alignment directions for two adjacent domains |
US7062782B1 (en) * | 1999-12-22 | 2006-06-13 | Uunet Technologies, Inc. | Overlay network for tracking denial-of-service floods in unreliable datagram delivery networks |
US20040073617A1 (en) | 2000-06-19 | 2004-04-15 | Milliken Walter Clark | Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail |
AU2001266174A1 (en) * | 2000-06-30 | 2002-01-14 | British Telecommunications Public Limited Company | Packet data communications |
US7278159B2 (en) * | 2000-09-07 | 2007-10-02 | Mazu Networks, Inc. | Coordinated thwarting of denial of service attacks |
US7043759B2 (en) | 2000-09-07 | 2006-05-09 | Mazu Networks, Inc. | Architecture to thwart denial of service attacks |
US7251692B1 (en) * | 2000-09-28 | 2007-07-31 | Lucent Technologies Inc. | Process to thwart denial of service attacks on the internet |
US7170860B2 (en) | 2000-10-23 | 2007-01-30 | Bbn Technologies Corp. | Method and system for passively analyzing communication data based on frequency analysis of encrypted data traffic, and method and system for deterring passive analysis of communication data |
US20030097439A1 (en) * | 2000-10-23 | 2003-05-22 | Strayer William Timothy | Systems and methods for identifying anomalies in network data streams |
US7970886B1 (en) * | 2000-11-02 | 2011-06-28 | Arbor Networks, Inc. | Detecting and preventing undesirable network traffic from being sourced out of a network domain |
US6789190B1 (en) * | 2000-11-16 | 2004-09-07 | Computing Services Support Solutions, Inc. | Packet flooding defense system |
US20020069367A1 (en) * | 2000-12-06 | 2002-06-06 | Glen Tindal | Network operating system data directory |
US7054946B2 (en) * | 2000-12-06 | 2006-05-30 | Intelliden | Dynamic configuration of network devices to enable data transfers |
US7249170B2 (en) * | 2000-12-06 | 2007-07-24 | Intelliden | System and method for configuration, management and monitoring of network resources |
US6978301B2 (en) | 2000-12-06 | 2005-12-20 | Intelliden | System and method for configuring a network device |
US8219662B2 (en) * | 2000-12-06 | 2012-07-10 | International Business Machines Corporation | Redirecting data generated by network devices |
US7389354B1 (en) * | 2000-12-11 | 2008-06-17 | Cisco Technology, Inc. | Preventing HTTP server attacks |
US7200105B1 (en) * | 2001-01-12 | 2007-04-03 | Bbn Technologies Corp. | Systems and methods for point of ingress traceback of a network attack |
US7150037B2 (en) * | 2001-03-21 | 2006-12-12 | Intelliden, Inc. | Network configuration manager |
AU2002322109A1 (en) * | 2001-06-13 | 2002-12-23 | Intruvert Networks, Inc. | Method and apparatus for distributed network security |
ATE406026T1 (en) * | 2001-06-14 | 2008-09-15 | Ibm | INTRUSION DETECTION IN DATA PROCESSING SYSTEMS |
GB2376854A (en) * | 2001-06-19 | 2002-12-24 | Hewlett Packard Co | Centralised security service for ISP environment |
KR20030009887A (en) * | 2001-07-24 | 2003-02-05 | 주식회사 케이티 | A system and method for intercepting DoS attack |
US8296400B2 (en) * | 2001-08-29 | 2012-10-23 | International Business Machines Corporation | System and method for generating a configuration schema |
US20030084349A1 (en) * | 2001-10-12 | 2003-05-01 | Oliver Friedrichs | Early warning system for network attacks |
US7574597B1 (en) | 2001-10-19 | 2009-08-11 | Bbn Technologies Corp. | Encoding of signals to facilitate traffic analysis |
US20030084148A1 (en) * | 2001-10-19 | 2003-05-01 | Cousins David Bruce | Methods and systems for passive information discovery using cross spectral density and coherence processing |
US7263479B2 (en) * | 2001-10-19 | 2007-08-28 | Bbn Technologies Corp. | Determining characteristics of received voice data packets to assist prosody analysis |
US7283475B2 (en) * | 2001-10-19 | 2007-10-16 | Bbn Technologies Corp. | Fractal dimension analysis for data stream isolation |
US7200656B1 (en) | 2001-10-19 | 2007-04-03 | Bbn Technologies Corp. | Methods and systems for simultaneously detecting short and long term periodicity for traffic flow identification |
US7320142B1 (en) * | 2001-11-09 | 2008-01-15 | Cisco Technology, Inc. | Method and system for configurable network intrusion detection |
US7065562B2 (en) * | 2001-11-26 | 2006-06-20 | Intelliden, Inc. | System and method for generating a representation of a configuration schema |
US7761605B1 (en) | 2001-12-20 | 2010-07-20 | Mcafee, Inc. | Embedded anti-virus scanner for a network adapter |
US8185943B1 (en) * | 2001-12-20 | 2012-05-22 | Mcafee, Inc. | Network adapter firewall system and method |
US7225343B1 (en) * | 2002-01-25 | 2007-05-29 | The Trustees Of Columbia University In The City Of New York | System and methods for adaptive model generation for detecting intrusions in computer systems |
US7213264B2 (en) * | 2002-01-31 | 2007-05-01 | Mazu Networks, Inc. | Architecture to thwart denial of service attacks |
US7174566B2 (en) * | 2002-02-01 | 2007-02-06 | Intel Corporation | Integrated network intrusion detection |
US8561167B2 (en) * | 2002-03-08 | 2013-10-15 | Mcafee, Inc. | Web reputation scoring |
US7458098B2 (en) * | 2002-03-08 | 2008-11-25 | Secure Computing Corporation | Systems and methods for enhancing electronic communication security |
US7693947B2 (en) * | 2002-03-08 | 2010-04-06 | Mcafee, Inc. | Systems and methods for graphically displaying messaging traffic |
US20030172291A1 (en) * | 2002-03-08 | 2003-09-11 | Paul Judge | Systems and methods for automated whitelisting in monitored communications |
US7124438B2 (en) * | 2002-03-08 | 2006-10-17 | Ciphertrust, Inc. | Systems and methods for anomaly detection in patterns of monitored communications |
US7694128B2 (en) * | 2002-03-08 | 2010-04-06 | Mcafee, Inc. | Systems and methods for secure communication delivery |
US6941467B2 (en) * | 2002-03-08 | 2005-09-06 | Ciphertrust, Inc. | Systems and methods for adaptive message interrogation through multiple queues |
US8132250B2 (en) * | 2002-03-08 | 2012-03-06 | Mcafee, Inc. | Message profiling systems and methods |
US7870203B2 (en) * | 2002-03-08 | 2011-01-11 | Mcafee, Inc. | Methods and systems for exposing messaging reputation to an end user |
US7903549B2 (en) * | 2002-03-08 | 2011-03-08 | Secure Computing Corporation | Content-based policy compliance systems and methods |
US20060015942A1 (en) * | 2002-03-08 | 2006-01-19 | Ciphertrust, Inc. | Systems and methods for classification of messaging entities |
US8578480B2 (en) * | 2002-03-08 | 2013-11-05 | Mcafee, Inc. | Systems and methods for identifying potentially malicious messages |
US7140041B2 (en) * | 2002-04-11 | 2006-11-21 | International Business Machines Corporation | Detecting dissemination of malicious programs |
US7042852B2 (en) * | 2002-05-20 | 2006-05-09 | Airdefense, Inc. | System and method for wireless LAN dynamic channel change with honeypot trap |
US7277404B2 (en) * | 2002-05-20 | 2007-10-02 | Airdefense, Inc. | System and method for sensing wireless LAN activity |
US7532895B2 (en) * | 2002-05-20 | 2009-05-12 | Air Defense, Inc. | Systems and methods for adaptive location tracking |
US20040203764A1 (en) * | 2002-06-03 | 2004-10-14 | Scott Hrastar | Methods and systems for identifying nodes and mapping their locations |
US7058796B2 (en) * | 2002-05-20 | 2006-06-06 | Airdefense, Inc. | Method and system for actively defending a wireless LAN against attacks |
US7383577B2 (en) | 2002-05-20 | 2008-06-03 | Airdefense, Inc. | Method and system for encrypted network management and intrusion detection |
US7086089B2 (en) * | 2002-05-20 | 2006-08-01 | Airdefense, Inc. | Systems and methods for network security |
US7322044B2 (en) * | 2002-06-03 | 2008-01-22 | Airdefense, Inc. | Systems and methods for automated network policy exception detection and correction |
US20030232598A1 (en) * | 2002-06-13 | 2003-12-18 | Daniel Aljadeff | Method and apparatus for intrusion management in a wireless network using physical location determination |
US7788718B1 (en) * | 2002-06-13 | 2010-08-31 | Mcafee, Inc. | Method and apparatus for detecting a distributed denial of service attack |
US20040143670A1 (en) * | 2002-07-02 | 2004-07-22 | Pratik Roychowdhury | System, method and computer program product to avoid server overload by controlling HTTP denial of service (DOS) attacks |
FR2842000B1 (en) * | 2002-07-02 | 2004-09-24 | Mathematiques Appliquees S A | METHOD AND SYSTEM FOR DETECTING INTRUSION INTO A COMPUTER NETWORK |
US7464145B2 (en) * | 2002-07-11 | 2008-12-09 | Intelliden, Inc. | Repository-independent system and method for asset management and reconciliation |
US7752665B1 (en) * | 2002-07-12 | 2010-07-06 | TCS Commercial, Inc. | Detecting probes and scans over high-bandwidth, long-term, incomplete network traffic information using limited memory |
US7254133B2 (en) * | 2002-07-15 | 2007-08-07 | Intel Corporation | Prevention of denial of service attacks |
ATE255800T1 (en) * | 2002-07-22 | 2003-12-15 | Evolium Sas | METHOD FOR PROVIDING SERVICE MANAGEMENT FOR NETWORK ELEMENTS OF A CELLURAR COMMUNICATIONS NETWORK |
US20040030771A1 (en) * | 2002-08-07 | 2004-02-12 | John Strassner | System and method for enabling directory-enabled networking |
US20040028069A1 (en) * | 2002-08-07 | 2004-02-12 | Tindal Glen D. | Event bus with passive queuing and active routing |
US7418733B2 (en) * | 2002-08-26 | 2008-08-26 | International Business Machines Corporation | Determining threat level associated with network activity |
US8201252B2 (en) * | 2002-09-03 | 2012-06-12 | Alcatel Lucent | Methods and devices for providing distributed, adaptive IP filtering against distributed denial of service attacks |
US7185107B1 (en) * | 2002-10-02 | 2007-02-27 | Cisco Technology Inc. | Redirecting network traffic through a multipoint tunnel overlay network using distinct network address spaces for the overlay and transport networks |
US8909926B2 (en) * | 2002-10-21 | 2014-12-09 | Rockwell Automation Technologies, Inc. | System and methodology providing automation security analysis, validation, and learning in an industrial controller environment |
US20040078457A1 (en) * | 2002-10-21 | 2004-04-22 | Tindal Glen D. | System and method for managing network-device configurations |
US9009084B2 (en) | 2002-10-21 | 2015-04-14 | Rockwell Automation Technologies, Inc. | System and methodology providing automation security analysis and network intrusion protection in an industrial environment |
US8090809B2 (en) * | 2002-11-04 | 2012-01-03 | Riverbed Technology, Inc. | Role grouping |
US20050033989A1 (en) * | 2002-11-04 | 2005-02-10 | Poletto Massimiliano Antonio | Detection of scanning attacks |
US7827272B2 (en) * | 2002-11-04 | 2010-11-02 | Riverbed Technology, Inc. | Connection table for intrusion detection |
US7774839B2 (en) * | 2002-11-04 | 2010-08-10 | Riverbed Technology, Inc. | Feedback mechanism to minimize false assertions of a network intrusion |
US7461404B2 (en) * | 2002-11-04 | 2008-12-02 | Mazu Networks, Inc. | Detection of unauthorized access in a network |
US8191136B2 (en) * | 2002-11-04 | 2012-05-29 | Riverbed Technology, Inc. | Connection based denial of service detection |
US8479057B2 (en) * | 2002-11-04 | 2013-07-02 | Riverbed Technology, Inc. | Aggregator for connection based anomaly detection |
US7716737B2 (en) * | 2002-11-04 | 2010-05-11 | Riverbed Technology, Inc. | Connection based detection of scanning attacks |
US7363656B2 (en) * | 2002-11-04 | 2008-04-22 | Mazu Networks, Inc. | Event detection/anomaly correlation heuristics |
US8504879B2 (en) * | 2002-11-04 | 2013-08-06 | Riverbed Technology, Inc. | Connection based anomaly detection |
US7664963B2 (en) * | 2002-11-04 | 2010-02-16 | Riverbed Technology, Inc. | Data collectors in connection-based intrusion detection |
US7454499B2 (en) * | 2002-11-07 | 2008-11-18 | Tippingpoint Technologies, Inc. | Active network defense system and method |
US20040230681A1 (en) * | 2002-12-06 | 2004-11-18 | John Strassner | Apparatus and method for implementing network resources to provision a service using an information model |
US20040128539A1 (en) * | 2002-12-30 | 2004-07-01 | Intel Corporation | Method and apparatus for denial of service attack preemption |
US7269850B2 (en) * | 2002-12-31 | 2007-09-11 | Intel Corporation | Systems and methods for detecting and tracing denial of service attacks |
US8161145B2 (en) * | 2003-02-27 | 2012-04-17 | International Business Machines Corporation | Method for managing of denial of service attacks using bandwidth allocation technology |
FR2852754B1 (en) * | 2003-03-20 | 2005-07-08 | At & T Corp | SYSTEM AND METHOD FOR PROTECTING AN IP TRANSMISSION NETWORK AGAINST SERVICE DENI ATTACKS |
US8468234B1 (en) * | 2003-04-16 | 2013-06-18 | Verizon Corporate Services Group Inc. | Methods and systems for tracking file routing on a network |
US7359676B2 (en) * | 2003-04-21 | 2008-04-15 | Airdefense, Inc. | Systems and methods for adaptively scanning for wireless communications |
US7522908B2 (en) * | 2003-04-21 | 2009-04-21 | Airdefense, Inc. | Systems and methods for wireless network site survey |
US7355996B2 (en) * | 2004-02-06 | 2008-04-08 | Airdefense, Inc. | Systems and methods for adaptive monitoring with bandwidth constraints |
US20040210654A1 (en) * | 2003-04-21 | 2004-10-21 | Hrastar Scott E. | Systems and methods for determining wireless network topology |
US7324804B2 (en) * | 2003-04-21 | 2008-01-29 | Airdefense, Inc. | Systems and methods for dynamic sensor discovery and selection |
US7426634B2 (en) * | 2003-04-22 | 2008-09-16 | Intruguard Devices, Inc. | Method and apparatus for rate based denial of service attack detection and prevention |
US7308716B2 (en) * | 2003-05-20 | 2007-12-11 | International Business Machines Corporation | Applying blocking measures progressively to malicious network traffic |
US7464404B2 (en) * | 2003-05-20 | 2008-12-09 | International Business Machines Corporation | Method of responding to a truncated secure session attack |
US7246156B2 (en) * | 2003-06-09 | 2007-07-17 | Industrial Defender, Inc. | Method and computer program product for monitoring an industrial network |
US7996544B2 (en) * | 2003-07-08 | 2011-08-09 | International Business Machines Corporation | Technique of detecting denial of service attacks |
US7260833B1 (en) * | 2003-07-18 | 2007-08-21 | The United States Of America As Represented By The Secretary Of The Navy | One-way network transmission interface unit |
US7472418B1 (en) * | 2003-08-18 | 2008-12-30 | Symantec Corporation | Detection and blocking of malicious code |
US8788823B1 (en) | 2003-09-03 | 2014-07-22 | Cisco Technology, Inc. | System and method for filtering network traffic |
US7343485B1 (en) | 2003-09-03 | 2008-03-11 | Cisco Technology, Inc. | System and method for maintaining protocol status information in a network device |
US7487541B2 (en) * | 2003-12-10 | 2009-02-03 | Alcatel Lucent | Flow-based method for tracking back single packets |
US7814546B1 (en) * | 2004-03-19 | 2010-10-12 | Verizon Corporate Services Group, Inc. | Method and system for integrated computer networking attack attribution |
US8154987B2 (en) | 2004-06-09 | 2012-04-10 | Intel Corporation | Self-isolating and self-healing networked devices |
US7441272B2 (en) | 2004-06-09 | 2008-10-21 | Intel Corporation | Techniques for self-isolation of networked devices |
US7929534B2 (en) * | 2004-06-28 | 2011-04-19 | Riverbed Technology, Inc. | Flow logging for connection-based anomaly detection |
WO2006017291A2 (en) * | 2004-07-12 | 2006-02-16 | Nfr Security | Intrusion management system and method for providing dynamically scaled confidence level of attack detection |
US8176126B2 (en) | 2004-08-26 | 2012-05-08 | International Business Machines Corporation | System, method and program to limit rate of transferring messages from suspected spammers |
US8943241B1 (en) * | 2004-09-09 | 2015-01-27 | Hewlett-Packard Development Company, L.P. | Communication device ingress information management system and method |
US7478429B2 (en) * | 2004-10-01 | 2009-01-13 | Prolexic Technologies, Inc. | Network overload detection and mitigation system and method |
US8196199B2 (en) * | 2004-10-19 | 2012-06-05 | Airdefense, Inc. | Personal wireless monitoring agent |
US20060123133A1 (en) * | 2004-10-19 | 2006-06-08 | Hrastar Scott E | Detecting unauthorized wireless devices on a wired network |
US7760653B2 (en) | 2004-10-26 | 2010-07-20 | Riverbed Technology, Inc. | Stackable aggregation for connection based anomaly detection |
US20060095961A1 (en) * | 2004-10-29 | 2006-05-04 | Priya Govindarajan | Auto-triage of potentially vulnerable network machines |
US7797749B2 (en) | 2004-11-03 | 2010-09-14 | Intel Corporation | Defending against worm or virus attacks on networks |
US8635690B2 (en) * | 2004-11-05 | 2014-01-21 | Mcafee, Inc. | Reputation based message processing |
US8458467B2 (en) * | 2005-06-21 | 2013-06-04 | Cisco Technology, Inc. | Method and apparatus for adaptive application message payload content transformation in a network infrastructure element |
US7610610B2 (en) | 2005-01-10 | 2009-10-27 | Mcafee, Inc. | Integrated firewall, IPS, and virus scanner system and method |
US20060174324A1 (en) * | 2005-01-28 | 2006-08-03 | Zur Uri E | Method and system for mitigating denial of service in a communication network |
US8839427B2 (en) * | 2005-04-13 | 2014-09-16 | Verizon Patent And Licensing Inc. | WAN defense mitigation service |
US8704668B1 (en) * | 2005-04-20 | 2014-04-22 | Trevor Darrell | System for monitoring and alerting based on animal behavior in designated environments |
US20060256814A1 (en) * | 2005-05-13 | 2006-11-16 | Lockheed Martin Corporation | Ad hoc computer network |
US20060256770A1 (en) * | 2005-05-13 | 2006-11-16 | Lockheed Martin Corporation | Interface for configuring ad hoc network packet control |
US20060256717A1 (en) * | 2005-05-13 | 2006-11-16 | Lockheed Martin Corporation | Electronic packet control system |
US7599289B2 (en) * | 2005-05-13 | 2009-10-06 | Lockheed Martin Corporation | Electronic communication control |
US7937480B2 (en) * | 2005-06-02 | 2011-05-03 | Mcafee, Inc. | Aggregation of reputation data |
US9286469B2 (en) * | 2005-12-16 | 2016-03-15 | Cisco Technology, Inc. | Methods and apparatus providing computer and network security utilizing probabilistic signature generation |
US8495743B2 (en) * | 2005-12-16 | 2013-07-23 | Cisco Technology, Inc. | Methods and apparatus providing automatic signature generation and enforcement |
US7882560B2 (en) * | 2005-12-16 | 2011-02-01 | Cisco Technology, Inc. | Methods and apparatus providing computer and network security utilizing probabilistic policy reposturing |
US8413245B2 (en) * | 2005-12-16 | 2013-04-02 | Cisco Technology, Inc. | Methods and apparatus providing computer and network security for polymorphic attacks |
US7577424B2 (en) | 2005-12-19 | 2009-08-18 | Airdefense, Inc. | Systems and methods for wireless vulnerability analysis |
US7793138B2 (en) * | 2005-12-21 | 2010-09-07 | Cisco Technology, Inc. | Anomaly detection for storage traffic in a data center |
US20070143846A1 (en) * | 2005-12-21 | 2007-06-21 | Lu Hongqian K | System and method for detecting network-based attacks on electronic devices |
US8151339B2 (en) * | 2005-12-23 | 2012-04-03 | Avaya, Inc. | Method and apparatus for implementing filter rules in a network element |
US7715800B2 (en) | 2006-01-13 | 2010-05-11 | Airdefense, Inc. | Systems and methods for wireless intrusion detection using spectral analysis |
US7971251B2 (en) * | 2006-03-17 | 2011-06-28 | Airdefense, Inc. | Systems and methods for wireless security using distributed collaboration of wireless clients |
US20070218874A1 (en) * | 2006-03-17 | 2007-09-20 | Airdefense, Inc. | Systems and Methods For Wireless Network Forensics |
KR100748246B1 (en) * | 2006-03-29 | 2007-08-10 | 한국전자통신연구원 | Multi-step integrated security monitoring system and method using intrusion detection system log collection engine and traffic statistic generation engine |
EP1850253A1 (en) * | 2006-03-31 | 2007-10-31 | Nokia Siemens Networks Gmbh & Co. Kg | Method for mitigating a DoS attack |
US20090021343A1 (en) * | 2006-05-10 | 2009-01-22 | Airdefense, Inc. | RFID Intrusion Protection System and Methods |
WO2007149725A2 (en) * | 2006-06-09 | 2007-12-27 | The Arizona Board Of Regents, On Behalf Of The University Of Arizona | Method and system for autonomous control and protection of computer systems |
US7970013B2 (en) | 2006-06-16 | 2011-06-28 | Airdefense, Inc. | Systems and methods for wireless network content filtering |
US8477614B2 (en) | 2006-06-30 | 2013-07-02 | Centurylink Intellectual Property Llc | System and method for routing calls if potential call paths are impaired or congested |
US7948909B2 (en) * | 2006-06-30 | 2011-05-24 | Embarq Holdings Company, Llc | System and method for resetting counters counting network performance information at network communications devices on a packet network |
US8289965B2 (en) | 2006-10-19 | 2012-10-16 | Embarq Holdings Company, Llc | System and method for establishing a communications session with an end-user based on the state of a network connection |
US9094257B2 (en) | 2006-06-30 | 2015-07-28 | Centurylink Intellectual Property Llc | System and method for selecting a content delivery network |
US8000318B2 (en) * | 2006-06-30 | 2011-08-16 | Embarq Holdings Company, Llc | System and method for call routing based on transmission performance of a packet network |
US8717911B2 (en) | 2006-06-30 | 2014-05-06 | Centurylink Intellectual Property Llc | System and method for collecting network performance information |
US8194643B2 (en) * | 2006-10-19 | 2012-06-05 | Embarq Holdings Company, Llc | System and method for monitoring the connection of an end-user to a remote network |
US8488447B2 (en) | 2006-06-30 | 2013-07-16 | Centurylink Intellectual Property Llc | System and method for adjusting code speed in a transmission path during call set-up due to reduced transmission performance |
US8281392B2 (en) * | 2006-08-11 | 2012-10-02 | Airdefense, Inc. | Methods and systems for wired equivalent privacy and Wi-Fi protected access protection |
US8619600B2 (en) | 2006-08-22 | 2013-12-31 | Centurylink Intellectual Property Llc | System and method for establishing calls over a call path having best path metrics |
US8189468B2 (en) | 2006-10-25 | 2012-05-29 | Embarq Holdings, Company, LLC | System and method for regulating messages between networks |
US8576722B2 (en) | 2006-08-22 | 2013-11-05 | Centurylink Intellectual Property Llc | System and method for modifying connectivity fault management packets |
US8194555B2 (en) * | 2006-08-22 | 2012-06-05 | Embarq Holdings Company, Llc | System and method for using distributed network performance information tables to manage network communications |
US8307065B2 (en) | 2006-08-22 | 2012-11-06 | Centurylink Intellectual Property Llc | System and method for remotely controlling network operators |
US8199653B2 (en) | 2006-08-22 | 2012-06-12 | Embarq Holdings Company, Llc | System and method for communicating network performance information over a packet network |
US8125897B2 (en) * | 2006-08-22 | 2012-02-28 | Embarq Holdings Company Lp | System and method for monitoring and optimizing network performance with user datagram protocol network performance information packets |
US9479341B2 (en) | 2006-08-22 | 2016-10-25 | Centurylink Intellectual Property Llc | System and method for initiating diagnostics on a packet network node |
US7684332B2 (en) | 2006-08-22 | 2010-03-23 | Embarq Holdings Company, Llc | System and method for adjusting the window size of a TCP packet through network elements |
US8015294B2 (en) * | 2006-08-22 | 2011-09-06 | Embarq Holdings Company, LP | Pin-hole firewall for communicating data packets on a packet network |
US8064391B2 (en) | 2006-08-22 | 2011-11-22 | Embarq Holdings Company, Llc | System and method for monitoring and optimizing network performance to a wireless device |
US7889660B2 (en) | 2006-08-22 | 2011-02-15 | Embarq Holdings Company, Llc | System and method for synchronizing counters on an asynchronous packet communications network |
US8228791B2 (en) | 2006-08-22 | 2012-07-24 | Embarq Holdings Company, Llc | System and method for routing communications between packet networks based on intercarrier agreements |
US20080049629A1 (en) * | 2006-08-22 | 2008-02-28 | Morrill Robert J | System and method for monitoring data link layer devices and optimizing interlayer network performance |
US7808918B2 (en) | 2006-08-22 | 2010-10-05 | Embarq Holdings Company, Llc | System and method for dynamically shaping network traffic |
US8130793B2 (en) * | 2006-08-22 | 2012-03-06 | Embarq Holdings Company, Llc | System and method for enabling reciprocal billing for different types of communications over a packet network |
US7940735B2 (en) * | 2006-08-22 | 2011-05-10 | Embarq Holdings Company, Llc | System and method for selecting an access point |
US8743703B2 (en) | 2006-08-22 | 2014-06-03 | Centurylink Intellectual Property Llc | System and method for tracking application resource usage |
US8407765B2 (en) | 2006-08-22 | 2013-03-26 | Centurylink Intellectual Property Llc | System and method for restricting access to network performance information tables |
US8107366B2 (en) * | 2006-08-22 | 2012-01-31 | Embarq Holdings Company, LP | System and method for using centralized network performance tables to manage network communications |
US8223655B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for provisioning resources of a packet network based on collected network performance information |
US8224255B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for managing radio frequency windows |
US8537695B2 (en) * | 2006-08-22 | 2013-09-17 | Centurylink Intellectual Property Llc | System and method for establishing a call being received by a trunk on a packet network |
US20080052206A1 (en) * | 2006-08-22 | 2008-02-28 | Edwards Stephen K | System and method for billing users for communicating over a communications network |
US7843831B2 (en) | 2006-08-22 | 2010-11-30 | Embarq Holdings Company Llc | System and method for routing data on a packet network |
US8750158B2 (en) | 2006-08-22 | 2014-06-10 | Centurylink Intellectual Property Llc | System and method for differentiated billing |
US8238253B2 (en) | 2006-08-22 | 2012-08-07 | Embarq Holdings Company, Llc | System and method for monitoring interlayer devices and optimizing network performance |
US8274905B2 (en) | 2006-08-22 | 2012-09-25 | Embarq Holdings Company, Llc | System and method for displaying a graph representative of network performance over a time period |
US8549405B2 (en) | 2006-08-22 | 2013-10-01 | Centurylink Intellectual Property Llc | System and method for displaying a graphical representation of a network to identify nodes and node segments on the network that are not operating normally |
US8531954B2 (en) | 2006-08-22 | 2013-09-10 | Centurylink Intellectual Property Llc | System and method for handling reservation requests with a connection admission control engine |
US8144586B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for controlling network bandwidth with a connection admission control engine |
US8144587B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for load balancing network resources using a connection admission control engine |
US8098579B2 (en) | 2006-08-22 | 2012-01-17 | Embarq Holdings Company, LP | System and method for adjusting the window size of a TCP packet through remote network elements |
US8102770B2 (en) * | 2006-08-22 | 2012-01-24 | Embarq Holdings Company, LP | System and method for monitoring and optimizing network performance with vector performance tables and engines |
US8040811B2 (en) * | 2006-08-22 | 2011-10-18 | Embarq Holdings Company, Llc | System and method for collecting and managing network performance information |
US7949745B2 (en) * | 2006-10-31 | 2011-05-24 | Microsoft Corporation | Dynamic activity model of network services |
US20080103729A1 (en) * | 2006-10-31 | 2008-05-01 | Microsoft Corporation | Distributed detection with diagnosis |
US7779156B2 (en) * | 2007-01-24 | 2010-08-17 | Mcafee, Inc. | Reputation based load balancing |
US8214497B2 (en) * | 2007-01-24 | 2012-07-03 | Mcafee, Inc. | Multi-dimensional reputation scoring |
US7949716B2 (en) | 2007-01-24 | 2011-05-24 | Mcafee, Inc. | Correlation and analysis of entity attributes |
US8763114B2 (en) | 2007-01-24 | 2014-06-24 | Mcafee, Inc. | Detecting image spam |
US8179798B2 (en) * | 2007-01-24 | 2012-05-15 | Mcafee, Inc. | Reputation based connection throttling |
US7821947B2 (en) * | 2007-04-24 | 2010-10-26 | Microsoft Corporation | Automatic discovery of service/host dependencies in computer networks |
US8111692B2 (en) * | 2007-05-31 | 2012-02-07 | Embarq Holdings Company Llc | System and method for modifying network traffic |
US8185930B2 (en) | 2007-11-06 | 2012-05-22 | Mcafee, Inc. | Adjusting filter or classification control settings |
US8045458B2 (en) * | 2007-11-08 | 2011-10-25 | Mcafee, Inc. | Prioritizing network traffic |
US8160975B2 (en) * | 2008-01-25 | 2012-04-17 | Mcafee, Inc. | Granular support vector machine with random granularity |
US7817636B2 (en) * | 2008-01-30 | 2010-10-19 | Cisco Technology, Inc. | Obtaining information on forwarding decisions for a packet flow |
US8589503B2 (en) | 2008-04-04 | 2013-11-19 | Mcafee, Inc. | Prioritizing network traffic |
US8068425B2 (en) | 2008-04-09 | 2011-11-29 | Embarq Holdings Company, Llc | System and method for using network performance information to determine improved measures of path states |
US8561179B2 (en) * | 2008-07-21 | 2013-10-15 | Palo Alto Research Center Incorporated | Method for identifying undesirable features among computing nodes |
US8009559B1 (en) * | 2008-08-28 | 2011-08-30 | Juniper Networks, Inc. | Global flow tracking system |
US8850571B2 (en) * | 2008-11-03 | 2014-09-30 | Fireeye, Inc. | Systems and methods for detecting malicious network content |
US8082333B2 (en) * | 2008-11-10 | 2011-12-20 | Cisco Technology, Inc. | DHCP proxy for static host |
US20100125663A1 (en) * | 2008-11-17 | 2010-05-20 | Donovan John J | Systems, methods, and devices for detecting security vulnerabilities in ip networks |
CN102859934B (en) * | 2009-03-31 | 2016-05-11 | 考持·维 | Access-in management and safety system and the method for the accessible Computer Service of network |
US9497039B2 (en) | 2009-05-28 | 2016-11-15 | Microsoft Technology Licensing, Llc | Agile data center network architecture |
US8359652B2 (en) * | 2009-10-31 | 2013-01-22 | Microsoft Corporation | Detecting anomalies in access control lists |
US9391716B2 (en) | 2010-04-05 | 2016-07-12 | Microsoft Technology Licensing, Llc | Data center using wireless communication |
US8621638B2 (en) | 2010-05-14 | 2013-12-31 | Mcafee, Inc. | Systems and methods for classification of messaging entities |
US8689328B2 (en) * | 2011-02-11 | 2014-04-01 | Verizon Patent And Licensing Inc. | Maliciouis user agent detection and denial of service (DOS) detection and prevention using fingerprinting |
US9122877B2 (en) | 2011-03-21 | 2015-09-01 | Mcafee, Inc. | System and method for malware and network reputation correlation |
KR20130017333A (en) * | 2011-08-10 | 2013-02-20 | 한국전자통신연구원 | Attack decision system of slow distributed denial of service based application layer and method of the same |
US20140244650A1 (en) * | 2011-11-04 | 2014-08-28 | Yizheng Zhou | Distributed event processing |
US9237082B2 (en) * | 2012-03-26 | 2016-01-12 | Hewlett Packard Enterprise Development Lp | Packet descriptor trace indicators |
US8931043B2 (en) | 2012-04-10 | 2015-01-06 | Mcafee Inc. | System and method for determining and using local reputations of users and hosts to protect information in a network environment |
FI20125761A (en) * | 2012-06-29 | 2013-12-30 | Tellabs Oy | Method and apparatus for detecting sources of data frame storms |
US9197362B2 (en) | 2013-03-15 | 2015-11-24 | Mehdi Mahvi | Global state synchronization for securely managed asymmetric network communication |
US8978138B2 (en) | 2013-03-15 | 2015-03-10 | Mehdi Mahvi | TCP validation via systematic transmission regulation and regeneration |
US9172721B2 (en) | 2013-07-16 | 2015-10-27 | Fortinet, Inc. | Scalable inline behavioral DDOS attack mitigation |
US9507847B2 (en) | 2013-09-27 | 2016-11-29 | International Business Machines Corporation | Automatic log sensor tuning |
US9954751B2 (en) | 2015-05-29 | 2018-04-24 | Microsoft Technology Licensing, Llc | Measuring performance of a network using mirrored probe packets |
US10735455B2 (en) * | 2015-06-04 | 2020-08-04 | Dark3, LLC | System for anonymously detecting and blocking threats within a telecommunications network |
EP3122016B1 (en) * | 2015-07-22 | 2020-01-08 | Siemens Aktiengesellschaft | Automation network and method of surveillance for security of the transmission of data packets |
US9509710B1 (en) | 2015-11-24 | 2016-11-29 | International Business Machines Corporation | Analyzing real-time streams of time-series data |
US9973528B2 (en) | 2015-12-21 | 2018-05-15 | Fortinet, Inc. | Two-stage hash based logic for application layer distributed denial of service (DDoS) attack attribution |
CN107645478B (en) * | 2016-07-22 | 2020-12-22 | 阿里巴巴集团控股有限公司 | Network attack defense system, method and device |
CN107395596B (en) * | 2017-07-24 | 2018-05-18 | 南京邮电大学 | A kind of refusal service attack defending method based on redundant manipulator switching |
US11750622B1 (en) | 2017-09-05 | 2023-09-05 | Barefoot Networks, Inc. | Forwarding element with a data plane DDoS attack detector |
US11108812B1 (en) | 2018-04-16 | 2021-08-31 | Barefoot Networks, Inc. | Data plane with connection validation circuits |
US11165791B2 (en) * | 2019-03-13 | 2021-11-02 | Microsoft Technology Licensing, Llc | Cloud security using multidimensional hierarchical model |
US11438361B2 (en) * | 2019-03-22 | 2022-09-06 | Hitachi, Ltd. | Method and system for predicting an attack path in a computer network |
CN113132308B (en) * | 2019-12-31 | 2022-05-17 | 华为技术有限公司 | Network security protection method and protection equipment |
US11831671B2 (en) * | 2021-04-08 | 2023-11-28 | Nozomi Networks Sagl | Method for automatic derivation of attack paths in a network |
Family Cites Families (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4756019A (en) * | 1986-08-27 | 1988-07-05 | Edmund Szybicki | Traffic routing and automatic network management system for telecommunication networks |
US4817080A (en) * | 1987-02-24 | 1989-03-28 | Digital Equipment Corporation | Distributed local-area-network monitoring system |
US5179549A (en) * | 1988-11-10 | 1993-01-12 | Alcatel N.V. | Statistical measurement equipment and telecommunication system using same |
CA2041992A1 (en) * | 1990-05-18 | 1991-11-19 | Yeshayahu Artsy | Routing objects on action paths in a distributed computing system |
DE69020899T2 (en) * | 1990-09-28 | 1995-12-07 | Hewlett Packard Co | Network monitoring system and device. |
US5231593A (en) * | 1991-01-11 | 1993-07-27 | Hewlett-Packard Company | Maintaining historical lan traffic statistics |
US5243543A (en) * | 1991-01-17 | 1993-09-07 | Hewlett-Packard Company | Remote LAN segment traffic monitor |
KR960009474B1 (en) * | 1993-11-29 | 1996-07-19 | 양승택 | Fast traffic statistics processing unit using memory |
US5606668A (en) * | 1993-12-15 | 1997-02-25 | Checkpoint Software Technologies Ltd. | System for securing inbound and outbound data packet flow in a computer network |
US5835726A (en) * | 1993-12-15 | 1998-11-10 | Check Point Software Technologies Ltd. | System for securing the flow of and selectively modifying packets in a computer network |
FR2717334B1 (en) * | 1994-03-11 | 1996-04-19 | Pierre Rolin | Integrity check of data exchanged between two telecommunications network stations. |
US5511122A (en) * | 1994-06-03 | 1996-04-23 | The United States Of America As Represented By The Secretary Of The Navy | Intermediate network authentication |
US5864683A (en) * | 1994-10-12 | 1999-01-26 | Secure Computing Corporartion | System for providing secure internetwork by connecting type enforcing secure computers to external network for limiting access to data based on user and process access rights |
US5623601A (en) * | 1994-11-18 | 1997-04-22 | Milkway Networks Corporation | Apparatus and method for providing a secure gateway for communication and data exchanges between networks |
US5550984A (en) * | 1994-12-07 | 1996-08-27 | Matsushita Electric Corporation Of America | Security system for preventing unauthorized communications between networks by translating communications received in ip protocol to non-ip protocol to remove address and routing services information |
US5570346A (en) * | 1994-12-08 | 1996-10-29 | Lucent Technologies Inc. | Packet network transit delay measurement system |
US5802320A (en) * | 1995-05-18 | 1998-09-01 | Sun Microsystems, Inc. | System for packet filtering of data packets at a computer network interface |
JP3262689B2 (en) * | 1995-05-19 | 2002-03-04 | 富士通株式会社 | Remote control system |
US5961645A (en) * | 1995-10-02 | 1999-10-05 | At&T Corp. | Filtering for public databases with naming ambiguities |
US5781534A (en) * | 1995-10-31 | 1998-07-14 | Novell, Inc. | Method and apparatus for determining characteristics of a path |
CA2196622C (en) * | 1996-02-06 | 2001-10-16 | Hiroshi Jinzenji | Network data distribution system |
US5898830A (en) * | 1996-10-17 | 1999-04-27 | Network Engineering Software | Firewall providing enhanced network security and user transparency |
US5673322A (en) * | 1996-03-22 | 1997-09-30 | Bell Communications Research, Inc. | System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks |
US5774667A (en) * | 1996-03-27 | 1998-06-30 | Bay Networks, Inc. | Method and apparatus for managing parameter settings for multiple network devices |
US6243667B1 (en) * | 1996-05-28 | 2001-06-05 | Cisco Systems, Inc. | Network flow switching and flow data export |
US5805820A (en) * | 1996-07-15 | 1998-09-08 | At&T Corp. | Method and apparatus for restricting access to private information in domain name systems by redirecting query requests |
US5828833A (en) * | 1996-08-15 | 1998-10-27 | Electronic Data Systems Corporation | Method and system for allowing remote procedure calls through a network firewall |
US5878143A (en) * | 1996-08-16 | 1999-03-02 | Net 1, Inc. | Secure transmission of sensitive information over a public/insecure communications medium |
US6119236A (en) * | 1996-10-07 | 2000-09-12 | Shipley; Peter M. | Intelligent network security device and method |
US5764191A (en) * | 1996-10-07 | 1998-06-09 | Sony Corporation | Retractable antenna assembly for a portable radio device |
US5944823A (en) * | 1996-10-21 | 1999-08-31 | International Business Machines Corporations | Outside access to computer resources through a firewall |
US5991881A (en) * | 1996-11-08 | 1999-11-23 | Harris Corporation | Network surveillance system |
US5778174A (en) * | 1996-12-10 | 1998-07-07 | U S West, Inc. | Method and system for providing secured access to a server connected to a private computer network |
US5864666A (en) * | 1996-12-23 | 1999-01-26 | International Business Machines Corporation | Web-based administration of IP tunneling on internet firewalls |
US5996011A (en) * | 1997-03-25 | 1999-11-30 | Unified Research Laboratories, Inc. | System and method for filtering data received by a computer system |
US5805803A (en) * | 1997-05-13 | 1998-09-08 | Digital Equipment Corporation | Secure web tunnel |
US5968176A (en) * | 1997-05-29 | 1999-10-19 | 3Com Corporation | Multilayer firewall system |
US6134658A (en) * | 1997-06-09 | 2000-10-17 | Microsoft Corporation | Multi-server location-independent authentication certificate management system |
US6067569A (en) * | 1997-07-10 | 2000-05-23 | Microsoft Corporation | Fast-forwarding and filtering of network packets in a computer system |
US6067545A (en) * | 1997-08-01 | 2000-05-23 | Hewlett-Packard Company | Resource rebalancing in networked computer systems |
US6377993B1 (en) * | 1997-09-26 | 2002-04-23 | Mci Worldcom, Inc. | Integrated proxy interface for web based data management reports |
US6076168A (en) * | 1997-10-03 | 2000-06-13 | International Business Machines Corporation | Simplified method of configuring internet protocol security tunnels |
US6003133A (en) * | 1997-11-17 | 1999-12-14 | Motorola, Inc. | Data processor with a privileged state firewall and method therefore |
US6078953A (en) * | 1997-12-29 | 2000-06-20 | Ukiah Software, Inc. | System and method for monitoring quality of service over network |
US6088804A (en) * | 1998-01-12 | 2000-07-11 | Motorola, Inc. | Adaptive system and method for responding to computer network security attacks |
US6134662A (en) * | 1998-06-26 | 2000-10-17 | Vlsi Technology, Inc. | Physical layer security manager for memory-mapped serial communications interface |
US6061331A (en) * | 1998-07-28 | 2000-05-09 | Gte Laboratories Incorporated | Method and apparatus for estimating source-destination traffic in a packet-switched communications network |
US6088796A (en) * | 1998-08-06 | 2000-07-11 | Cianfrocca; Francis | Secure middleware and server control system for querying through a network firewall |
US6446200B1 (en) * | 1999-03-25 | 2002-09-03 | Nortel Networks Limited | Service management |
US6625657B1 (en) * | 1999-03-25 | 2003-09-23 | Nortel Networks Limited | System for requesting missing network accounting records if there is a break in sequence numbers while the records are transmitting from a source device |
US6789203B1 (en) * | 2000-06-26 | 2004-09-07 | Sun Microsystems, Inc. | Method and apparatus for preventing a denial of service (DOS) attack by selectively throttling TCP/IP requests |
US6772334B1 (en) * | 2000-08-31 | 2004-08-03 | Networks Associates, Inc. | System and method for preventing a spoofed denial of service attack in a networked computing environment |
-
2001
- 2001-05-15 US US09/855,808 patent/US20020032871A1/en not_active Abandoned
- 2001-05-16 CA CA002426451A patent/CA2426451A1/en not_active Abandoned
- 2001-05-16 EP EP01944141A patent/EP1317835A1/en not_active Withdrawn
- 2001-05-16 WO PCT/US2001/015696 patent/WO2002021800A1/en not_active Application Discontinuation
- 2001-05-16 AU AU2001266580A patent/AU2001266580A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
US20020032871A1 (en) | 2002-03-14 |
AU2001266580A1 (en) | 2002-03-22 |
WO2002021800A1 (en) | 2002-03-14 |
EP1317835A1 (en) | 2003-06-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20020032871A1 (en) | Method and system for detecting, tracking and blocking denial of service attacks over a computer network | |
CA2499938C (en) | Network bandwidth anomaly detector apparatus and method for detecting network attacks using correlation function | |
Jafarian et al. | A survey and classification of the security anomaly detection mechanisms in software defined networks | |
EP1742416B1 (en) | Method, computer readable medium and system for analyzing and management of application traffic on networks | |
Ellens et al. | Flow-based detection of DNS tunnels | |
Gao et al. | A dos resilient flow-level intrusion detection approach for high-speed networks | |
EP1678615A2 (en) | Policy-based network security management | |
WO2014052756A2 (en) | Apparatus, system and method for identifying and mitigating malicious network threats | |
Lu et al. | An easy defense mechanism against botnet-based DDoS flooding attack originated in SDN environment using sFlow | |
Amini et al. | Botnet detection using NetFlow and clustering | |
CA2564615A1 (en) | Self-propagating program detector apparatus, method, signals and medium | |
Mongelli et al. | Detection of DoS attacks through Fourier transform and mutual information | |
Zhenqi et al. | Netflow based intrusion detection system | |
US8281400B1 (en) | Systems and methods for identifying sources of network attacks | |
KR20030016500A (en) | Policy-based Network Security System and Method for Security and Security Policy | |
KR101772292B1 (en) | Software Defined Network based Network Flooding Attack Detection/Protection Method and System | |
Pao et al. | Netflow based intrusion detection system | |
Deri et al. | Practical network security: experiences with ntop | |
Bakhareva et al. | SDN-based firewall implementation for large corporate networks | |
Bou-Harb et al. | On detecting and clustering distributed cyber scanning | |
KR100604638B1 (en) | Intrusion detection system and method based on hierarchical analysis | |
Sardana et al. | Honeypot based routing to mitigate ddos attacks on servers at isp level | |
Ghosh et al. | Managing high volume data for network attack detection using real-time flow filtering | |
Kotsokalis et al. | Router-based detection of DoS and DDoS attacks | |
Priescu et al. | Design of traceback methods for tracking DoS attacks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FZDE | Discontinued |