US20050166049A1 - Upper-level protocol authentication - Google Patents
Upper-level protocol authentication Download PDFInfo
- Publication number
- US20050166049A1 US20050166049A1 US11/042,787 US4278705A US2005166049A1 US 20050166049 A1 US20050166049 A1 US 20050166049A1 US 4278705 A US4278705 A US 4278705A US 2005166049 A1 US2005166049 A1 US 2005166049A1
- Authority
- US
- United States
- Prior art keywords
- communication traffic
- message
- source address
- network
- level protocol
- 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.)
- Granted
Links
Images
Classifications
-
- 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/08—Network architectures or network communication protocols for network security for authentication of entities
-
- 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/145—Countermeasures against malicious traffic the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
-
- 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
- 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/1466—Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
-
- 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/141—Denial of service attacks against endpoints in a network
-
- 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/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
- H04L63/0236—Filtering by address, protocol, port number or service, e.g. IP-address or URL
Abstract
Description
- This application claims the benefit of U.S.
Provisional Patent Application 60/539,327, filed Jan. 26, 2004, and is related to the following co-pending applications: U.S. patent application Ser. No. 09/929,877, filed Aug. 14, 2001; U.S. patent application Ser. No. 10/232,993, filed Aug. 29, 2002; U.S. patent application Ser. No. 10/251,912, filed Sep. 20, 2002; and PCT Patent Application PCT/IL02/00996, filed Dec. 10, 2002. All of these related applications are assigned to the assignee of the present patent application and are incorporated herein by reference. - The present invention relates generally to computer networks, and specifically to methods and systems for protecting against denial of service and worm attacks in computer networks.
- In a Denial-of-Service (DoS) attack, an attacker bombards a victim network or server with a large volume of message traffic. The traffic overload consumes the victim's available bandwidth, CPU capacity, or other critical system resources, and eventually brings the victim to a situation in which it is unable to serve its legitimate clients. Distributed DoS (DDoS) attacks can be even more damaging, as they involve creating artificial network traffic from multiple sources simultaneously.
- In order to launch an, effective DDoS attack, an attacker typically attempts to control a large number of servers on the Internet. One approach to gaining such control is to use “worms,” which are malicious programs that self-replicate across the Internet by exploiting security flaws in widely-used services. Worm infections are often invisible to the user of an infected computer, and the worm may copy itself to other computers independently of any action taken by the computer user. After taking control of a computer, the worm often uses the computer to participate in a DDoS attack, without any knowing collaboration on the part of the computer user. Infected computers that participate in this sort of mass malicious activity are referred to herein as “zombies.”
- The present invention will be more fully understood from the following detailed description of the embodiments thereof, taken together with the drawings in which:
-
FIG. 1 is a block diagram that schematically illustrates a computer network system, in accordance with an embodiment of the present invention; -
FIG. 2 is a flow chart that schematically illustrates a method for protecting against DDoS attacks, in accordance with an embodiment of the present invention; and -
FIG. 3 is a message flow diagram that schematically shows details of a method for authenticating a source of incoming packet traffic, in accordance with an embodiment of the present invention. - Many DDoS attacks use “spoofed” IP packets—packets containing a bogus IP source address—making it difficult for the victim network to identify the source of the attack. In response to this problem, the above-mentioned related applications describe methods that may be used to determine whether the IP source address of an incoming packet is authentic or spoofed. Traffic from authentic IP addresses may then be passed on to its intended destination, while packets with spoofed addresses are blocked.
- Zombies, however, may have legitimate IP addresses (belonging to the infected source computer), and anti-spoofing measures may therefore fail to filter-out the packets generated by such zombies during a DDoS attack. Thus, in a typical attack, many zombies may succeed in establishing TCP connections with a victim server, and then may use these connections to bombard the server with messages, such as HTTP requests.
- Embodiments of the present invention provide methods for resisting this sort of attack, by distinguishing legitimate messages from messages sent by zombies. For this purpose, some embodiments of the present invention enable a network guard device to challenge sources of incoming packet traffic so as to determine whether the sources comply fully with higher-level communication protocols, such as HTTP (including features of HTML) or DNS, which operate above the transport layer (typically TCP or UDP). Failure of a computer at a given source IP address to comply with the higher-level protocol indicates that the source may be a zombie, and incoming packets from this source are therefore blocked.
-
FIG. 1 is a block diagram that schematically illustrates acomputer network system 20, in accordance with a preferred embodiment of the present invention. AWeb server 22 communicates withclients 24 via a wide-area network (WAN) 26, typically the Internet. To prevent DDoS attacks onserver 22, aguard device 27 intercepts incoming HTTP request packets fromnetwork 26 that are addressed toserver 22.Guard device 27 comprises aguard processor 28, which performs the various protection and authentication methods described herein, and anetwork interface 29, which communicates with other components ofsystem 20 and withWAN 26. The guard processor checks the IP source address of each packet that it intercepts against reference values stored in a,database 30 or other data structure. Methods for generating these reference values—indicating which requests are legitimate, and which may have originated from spoofed IP addresses or from zombies—are described further hereinbelow. The guard processor blocks illegitimate requests from passing through toserver 22. - The configuration and operation of
guard device 27 are shown and described herein by way of example, and alternative configurations and modes of operation will be apparent to those skilled in the art. For example, rather than being connected in-line withserver 22, as shown inFIG. 1 ,guard device 27 may be connected in other configurations, for example, by a “lollipop” connection to a router (not shown) that forwards packets to server 22. Alternatively, functions of the guard device may be integrated into the router or server or into other network equipment, such as a firewall. These and other possible operational configurations of the guard device are described in the above-mentioned related applications. Note that althoughguard device 27 is shown and described herein as protecting asingle server 22, in practice one or more guard devices of this sort may be deployed to protect a group of computers, such as a cluster of servers or an entire LAN. Additional deployment scenarios for the guard device(s) (not necessarily zombie-based) are described in the above-mentioned related applications. - Typically,
guard device 27 comprises a general-purpose computer, which is programmed in software to carry out the functions described herein. The software may be downloaded to the computer in electronic form, over a network, for example, or it may alternatively be supplied to the computer on tangible media, such as CD-ROM. Further alternatively,guard device 27 may be implemented in dedicated hardware logic, or using a combination of hardware and software elements. -
FIG. 2 is a flow chart that schematically illustrates a method that is carried out byguard processor 28 for protection against DDoS attacks, in accordance with an embodiment of the present invention. The guard processor may perform its packet screening and verification functions at all times, or it may alternatively filter packets only under stress conditions, in which a DDoS attack onserver 22 is suspected. In order to determine whether an attack may be in progress,guard processor 28 intercepts incoming traffic vianetwork interface 29 and monitors selected statistical characteristics of the incoming traffic that is directed toserver 22, at anattack detection step 50. For example, the guard processor may use one or more of the following criteria to detect a zombie-based DDoS attack: - Number and distribution of source IP addresses—A sudden change, such as an increase in the number of different source IP addresses attempting to communicate with the server, may be indicative of an attack.
- Distribution of user agents specified in HTTP requests—The agent field in the HTTP request is optional, but it is usually used to specify the type of browser submitting the request. A sudden change in the distribution of agents may indicate that a large fraction of the requests are being submitted by zombies, which specify a particular agent as dictated by the malicious program that is controlling them. (In order to limit the amount of malicious traffic that can reach
server 22,guard processor 28 may optionally determine, in the absence of an attack, a baseline percentage distribution of HTTP requests among the different possible user agents, and may then simply block all traffic specifying a particular user agent that is in excess of the baseline percentage for that agent.) Similarly a sudden change in the number of requests without the agent field, or with a bogus agent field, may be indicative of a zombie attack. - Occurrence of other regular patterns in the incoming traffic—Zombies tend to send many identical packets repeatedly, at regular intervals. Detection of this sort of repeating pattern may be indicative of an attack. Other attack detection criteria will be apparent to those skilled in the art. Additional criteria (not necessarily zombie-based) are described in the above-mentioned related applications.
- As long as no attack in progress,
guard processor 28 typically permits incoming packets to pass through toserver 22, at apacket delivery step 52. On the other hand, when an attack is believed to be in progress,guard processor 28 filters some or all of the incoming traffic, at a filteringstep 54. For this purpose, the guard processor maintains a record indatabase 30 of IP source addresses that are known to be legitimate (because of past communications with these source addresses, as described below).Database 30 may also contain a “blacklist” of addresses that are believed to be malicious. Guardprocessor 28 checks the source address of each incoming packet against the database record, at a sourceaddress checking step 56. If the address appears on the legitimate list, the packet is passed on toserver 22 atstep 52. (Additionally or alternatively, if the address appears on the blacklist, the packet may be discarded.) - If the IP source address of the incoming packet is unknown,
guard processor 28 tests the address to determine whether it is legitimate or spoofed, at aspoofing check step 58. Typically, the guard processor initiates a challenge/response routine, by sending a packet (the “challenge”) containing certain information to the IP source address of the incoming packet viainterface 29. The guard processor then checks that the response packet received from the IP source address contains appropriate matching information, at anIP authentication step 60. Various challenge/response methods that may be used for this purpose are described in the above-mentioned U.S. patent application Ser. No. 10/232,993. If the IP address is found to be bogus, the incoming packet is discarded, and the address may be entered in the blacklist indatabase 30, at a packet discardstep 62. -
FIG. 3 is a message flow diagram, which shows details ofspoofing check step 58, in accordance with one embodiment of the present invention. In this example, the TCP three-way handshake is used to authenticate the source IP address. The message flow begins whenguard processor 28 intercepts a TCP SYN packet sent from an IP source address that does not yet appear indatabase 30. The SYN packet has a certain packet sequence number (s#), in accordance with TCP convention. The guard processor sends back a TCP SYN-ACK packet to the IP source address of the SYN packet viainterface 29. The SYN-ACK packet contains an encoded cookie (c#), which is encoded in the sequence number (s#) of the packet. Any suitable method of cookie generation that is known in the art may be used for this purpose and for generating cookies in other embodiments of the present invention. In one embodiment, a hash generator implements a hash function for mapping packet attributes, such as the IP source address and port, to cookies. The hash generator calculates a hash value, which is used as a key for indexing a cookie table comprising a set of random cookies. The random cookie values are replaced after use to prevent an attacker who succeeds in discovering a legitimate cookie value from re-using the cookie. - If
guard processor 28 then receives a proper TCP ACK packet back from the same IP source address, identified by the proper sequence number and cookie, the guard processor is able to ascertain that the source address is legitimate, rather than spoofed. (Note, however, that the guard processor still does not know whether the computer at this source address is a zombie or not). Alternative anti-spoofing methods are described in the above-mentioned related applications. - Returning now to
FIG. 2 , afterguard processor 28 verifies that the IP source address of a given packet is authentic atstep 60, it may go on to test the legitimacy of the higher-level software running on the source computer, at aprotocol challenge step 64. In the present embodiment, it is assumed thatguard device 27 is protecting a Web server (as shown inFIG. 1 ), and that the guard processor has intercepted a HTTP request from an unknown source address.Step 64 tests whether the HTTP request was generated by a legitimate browser, complying with all the requirements of HTTP. Based on this test, the guard processor determines whether the source computer is legitimate or a zombie, at abrowser legitimation step 66. An exemplary test of this sort is described below with reference toFIG. 3 . - The test used at
step 64 is based on sending a HTTP response, containing a HTML directive (the challenge), back to the IP source address of the incoming HTTP request, and checking the next reply returned from this IP address. For the most part, zombies are driven by relatively simple programs, which may be capable of emulating certain basic aspects of HTTP, but do not implement all the specified functions of HTML (as required, for example, by IETF RFC 1866 and the applicable HTML specification, such as HTML 4.0). Therefore, if the source address returns the reply that is expected in compliance with the protocol,guard processor 28 may conclude that the computer at the IP source address is legitimate, and is not a zombie. In this case,guard processor 28 adds the IP address to the list of legitimate addresses indatabase 30, at anaddress approval step 68. Packets from this address may now be delivered toserver 22 atstep 52. Otherwise, if the computer at the IP source address failed to respond to the challenge or responded incorrectly, the incoming packet is discarded atstep 62, and its IP source address may be added to the blacklist. -
FIG. 3 illustrates one type of test that may be used atstep 64. In this example, it is assumed that after the source computer onnetwork 26 establishes its TCP connection with guard device 27 (at step 58), it submits a HTTP request for a certain URI onserver 22, for example, GET /index.html. As noted above, the request may also specify other HTTP fields, such as the user agent. The guard processor intercepts this request viainterface 29 and returns a response, which redirects the source computer to refresh its browser with a new URI (identified inFIG. 3 as URI′). Requests directed to the URI′ will also be intercepted by the guard processor, but URI′ contains information, such as a cookie, that will enable the guard processor to identify the source of the request. For example, the guard processor may return a response containing the HTML directive: <META HTTP-EQUIV=″Refresh CONTENT=″1; URL=cookie.index.html″>, wherein “cookie” is a unique string generated by the guard processor. - Normally, this response should cause the browser on the source computer to open a new TCP connection with
guard processor 28, and then resubmit its HTTP request to URI′, i.e., to “cookie.index.html”. (To open a new TCP connection, the source computer again sends a SYN packet, receives a SYN-ACK from the guard or the target, and then sends an ACK. These three-way exchanges associated with the HTTP GET URI′ and the final HTTP GET URI are omitted fromFIG. 3 for the sake of simplicity.) Upon receiving this new request, the guard processor is able to conclude that it is communicating with a legitimate browser on the source computer, and adds the IP address of the source computer to its approved list indatabase 30. The guard processor then redirects the source computer once again to the original URI=index.html. As a result, the source computer will attempt to open yet another TCP connection withserver 22. This time, however, the guard processor will recognize the IP source address of the TCP SYN packet from the source computer as legitimate, and will pass the packet through toserver 22. The server and source computer may then proceed to communicate in the normal fashion. - On the other hand, if the original HTTP request from the source computer was sent by a zombie, rather than by a legitimate browser, the source computer will be unable to parse the HTTP response sent back by
guard processor 28. Therefore, the source computer will not resubmit its request to “cookie.index.html”. Rather, the source computer will, in all likelihood, simply continue submitting further requests to the original URI. Since the guard processor will not have authenticated the IP source address, it will not permit these requests to pass through toserver 22. Furthermore, upon receiving multiple, repeated requests of this sort, the guard processor may conclude that the source of the requests is a zombie, and will then add the IP source address to the blacklist. - Various other methods may be used at
step 64 in order to verify that a legitimate browser is operating at a given IP source address. These methods may be based on encoding cookies in other parts of the HTTP response sent byguard processor 28, or by testing the source computer for compliance with other aspects of the applicable protocols, such as RFC 1866 or RFC 2616. For example, the guard processor may redirect the browser on the source computer by replying to the initial HTTP request with a HTTP redirect response (status code 307), redirecting the client browser to URI′, containing the encoded cookie. - Alternatively or additionally, the response sent by the guard processor may test whether the original HTTP request sent by the source computer was submitted in response to instructions of a human operator of the source computer. For example, the response may cause the browser on the source computer to display an image or play a sound, and prompt the human operator to type a corresponding word into the computer. The response causes the source computer to return the word that the user has typed, thus permitting the guard processor to verify the presence of a human user operating the browser on the source computer. A zombie, clearly, will fail this test. Challenge/response routines of this sort, for verifying the presence of a human user on the source computer, are described further in the above-mentioned U.S. patent application Ser. No. 09/929,877.
- Although the embodiment described above makes reference particularly to HTTP and its use in conjunction with
Web server 22, the principles of the present invention are generally applicable to authentication of incoming traffic using higher-level protocols of other types. In the context of the present patent application, the term “higher-level protocol” refers to protocols operating above the transport layer (layer 4), as defined by the well-known Open Systems Interconnection (OSI) Reference Model. Internet traffic generally uses TCP or UDP as its transport-layer protocol. Higher-level protocols that may operate over TCP or UDP include (but are not limited to) HTTP, FTP, DNS, RTP, POP/SMTP, SNMP, Usenet, Telnet and NFS. These protocols are generally classified as “presentation-layer” protocols, although this is a loose classification, and these protocols are also often referred to as “application-layer” protocols. - In any case, when clients attempt to communicate with a server according to any higher-level protocol such as these, a guard device protecting the server may use a challenge/response technique based on the requirements of the specific protocol in order to authenticate the sources of the communications. For example, the above-mentioned U.S. patent application Ser. No. 10/251,912 describes methods and devices for distinguishing between spoofed and authentic DNS requests. Many other higher-level protocols (in addition to those listed above) are known in the art, and are amenable to authentication by the methods of the present invention.
- Furthermore, although the embodiments described above are directed mainly to processing IP packet traffic sent over the Internet, the principles of the present invention are similarly applicable to networks of other types, using other protocol families. It will thus be appreciated that the embodiments described above are cited by way of example, and that the present invention is not limited to what has been particularly shown and described hereinabove. Rather, the scope of the present invention includes both combinations and subcombinations of the various features described hereinabove, as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not disclosed in the prior art.
Claims (26)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/042,787 US7536552B2 (en) | 2004-01-26 | 2005-01-24 | Upper-level protocol authentication |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US53932704P | 2004-01-26 | 2004-01-26 | |
US11/042,787 US7536552B2 (en) | 2004-01-26 | 2005-01-24 | Upper-level protocol authentication |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050166049A1 true US20050166049A1 (en) | 2005-07-28 |
US7536552B2 US7536552B2 (en) | 2009-05-19 |
Family
ID=34807258
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/042,787 Active 2027-05-13 US7536552B2 (en) | 2004-01-26 | 2005-01-24 | Upper-level protocol authentication |
Country Status (6)
Country | Link |
---|---|
US (1) | US7536552B2 (en) |
EP (1) | EP1719285A4 (en) |
CN (2) | CN101180826B (en) |
AU (1) | AU2005207632B2 (en) |
CA (1) | CA2548336A1 (en) |
WO (1) | WO2005069732A2 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070043947A1 (en) * | 2005-08-19 | 2007-02-22 | Mizikovsky Semyon B | Providing multimedia system security to removable user identity modules |
US20080120413A1 (en) * | 2006-11-16 | 2008-05-22 | Comcast Cable Holdings, Lcc | Process for abuse mitigation |
US20090144806A1 (en) * | 2007-12-03 | 2009-06-04 | Cisco Technology, Inc. | Handling of DDoS attacks from NAT or proxy devices |
CN103036741A (en) * | 2012-12-19 | 2013-04-10 | 北京神州绿盟信息安全科技股份有限公司 | Determination method and determination device of flow monitoring base line |
US8595477B1 (en) * | 2011-03-24 | 2013-11-26 | Google Inc. | Systems and methods for reducing handshake delay in streaming protocol web requests |
CN103997494A (en) * | 2014-05-22 | 2014-08-20 | 北京京东尚科信息技术有限公司 | Method and system for defending hacker attacks |
US8887280B1 (en) * | 2012-05-21 | 2014-11-11 | Amazon Technologies, Inc. | Distributed denial-of-service defense mechanism |
US20160065620A1 (en) * | 2014-02-21 | 2016-03-03 | The Regents Of The University Of Michigan | Network maliciousness susceptibility analysis and rating |
CN108400955A (en) * | 2017-02-06 | 2018-08-14 | 腾讯科技(深圳)有限公司 | A kind of means of defence and system of network attack |
US10432650B2 (en) | 2016-03-31 | 2019-10-01 | Stuart Staniford | System and method to protect a webserver against application exploits and attacks |
US10749896B2 (en) * | 2017-05-03 | 2020-08-18 | Red Button Ltd. | Method and system for determining a readiness of a computer network of an organization to denial of service (DoS) attacks |
US11196691B2 (en) * | 2013-09-09 | 2021-12-07 | At&T Mobility Ii Llc | Method and apparatus for distributing content to communication devices |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101136922B (en) * | 2007-04-28 | 2011-04-13 | 华为技术有限公司 | Service stream recognizing method, device and distributed refusal service attack defending method, system |
US9083556B2 (en) * | 2007-05-31 | 2015-07-14 | Rpx Clearinghouse Llc | System and method for detectng malicious mail from spam zombies |
US20110072515A1 (en) * | 2009-09-22 | 2011-03-24 | Electronics And Telecommunications Research Institute | Method and apparatus for collaboratively protecting against distributed denial of service attack |
CN101741862B (en) * | 2010-01-22 | 2012-07-18 | 西安交通大学 | System and method for detecting IRC bot network based on data packet sequence characteristics |
CN102316082A (en) * | 2010-07-06 | 2012-01-11 | 杭州华三通信技术有限公司 | Method and flow cleaning equipment for defensing website distributed denial of service (DDoS) attack |
CN102413105A (en) * | 2010-09-25 | 2012-04-11 | 杭州华三通信技术有限公司 | Method and device for preventing attack of challenge collapsar (CC) |
KR20120066465A (en) * | 2010-12-14 | 2012-06-22 | 한국전자통신연구원 | Method for blocking denial-of-service attack |
US20120174196A1 (en) | 2010-12-30 | 2012-07-05 | Suresh Bhogavilli | Active validation for ddos and ssl ddos attacks |
US9473530B2 (en) | 2010-12-30 | 2016-10-18 | Verisign, Inc. | Client-side active validation for mitigating DDOS attacks |
CN102143173A (en) * | 2011-03-23 | 2011-08-03 | 深信服网络科技(深圳)有限公司 | Method and system for defending distributed denial of service (Ddos) attacks and gateway equipment |
FI126032B (en) * | 2013-03-07 | 2016-05-31 | Airo Finland Oy | Detection of a threat in a telecommunications network |
CA2834565C (en) * | 2013-11-28 | 2016-01-19 | Solutioninc Limited | Vbn server clustering system, method of vbn server clustering, and vbn server for clustering |
TWI501105B (en) * | 2014-03-27 | 2015-09-21 | Neovue Inc | System for remotely controlling confidential file |
CN104092665A (en) * | 2014-06-19 | 2014-10-08 | 小米科技有限责任公司 | Access request filtering method, device and facility |
US9591021B2 (en) * | 2014-08-20 | 2017-03-07 | Mcafee, Inc. | Zero day threat detection using host application/program to user agent mapping |
CN105577627B (en) * | 2014-11-11 | 2020-08-28 | 腾讯数码(天津)有限公司 | Communication method, device, network equipment, terminal equipment and communication system |
US10402555B2 (en) | 2015-12-17 | 2019-09-03 | Google Llc | Browser attestation challenge and response system |
US10200375B2 (en) * | 2016-03-15 | 2019-02-05 | Sony Interactive Entertainment America Llc | Dynamic denial of service detection and automated safe mitigation |
CN107888546B (en) * | 2016-09-29 | 2021-10-01 | 腾讯科技(深圳)有限公司 | Network attack defense method, device and system |
CN108881226A (en) * | 2018-06-19 | 2018-11-23 | 北京云枢网络科技有限公司 | Means of defence, protective device and the electronic equipment of application layer attack |
CN112822262B (en) * | 2021-01-04 | 2022-11-22 | 北京知道创宇信息技术股份有限公司 | Message processing method and device, message processing equipment and storage medium |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6279113B1 (en) * | 1998-03-16 | 2001-08-21 | Internet Tools, Inc. | Dynamic signature inspection-based network intrusion detection |
US6397335B1 (en) * | 1998-02-12 | 2002-05-28 | Ameritech Corporation | Computer virus screening methods and systems |
US6487666B1 (en) * | 1999-01-15 | 2002-11-26 | Cisco Technology, Inc. | Intrusion detection signature analysis using regular expressions and logical operators |
US6513122B1 (en) * | 2001-06-29 | 2003-01-28 | Networks Associates Technology, Inc. | Secure gateway for analyzing textual content to identify a harmful impact on computer systems with known vulnerabilities |
US20040093513A1 (en) * | 2002-11-07 | 2004-05-13 | Tippingpoint Technologies, Inc. | Active network defense system and method |
US6907525B2 (en) * | 2001-08-14 | 2005-06-14 | Riverhead Networks Inc. | Protecting against spoofed DNS messages |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003050644A2 (en) | 2001-08-14 | 2003-06-19 | Riverhead Networks Inc. | Protecting against malicious traffic |
US20030200441A1 (en) * | 2002-04-19 | 2003-10-23 | International Business Machines Corporation | Detecting randomness in computer network traffic |
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 |
-
2005
- 2005-01-23 EP EP05703124A patent/EP1719285A4/en not_active Withdrawn
- 2005-01-23 CN CN200580001380XA patent/CN101180826B/en active Active
- 2005-01-23 CN CN2011100276075A patent/CN102098305A/en active Pending
- 2005-01-23 CA CA002548336A patent/CA2548336A1/en not_active Abandoned
- 2005-01-23 WO PCT/IL2005/000081 patent/WO2005069732A2/en active Application Filing
- 2005-01-23 AU AU2005207632A patent/AU2005207632B2/en not_active Ceased
- 2005-01-24 US US11/042,787 patent/US7536552B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6397335B1 (en) * | 1998-02-12 | 2002-05-28 | Ameritech Corporation | Computer virus screening methods and systems |
US6279113B1 (en) * | 1998-03-16 | 2001-08-21 | Internet Tools, Inc. | Dynamic signature inspection-based network intrusion detection |
US6487666B1 (en) * | 1999-01-15 | 2002-11-26 | Cisco Technology, Inc. | Intrusion detection signature analysis using regular expressions and logical operators |
US6513122B1 (en) * | 2001-06-29 | 2003-01-28 | Networks Associates Technology, Inc. | Secure gateway for analyzing textual content to identify a harmful impact on computer systems with known vulnerabilities |
US6907525B2 (en) * | 2001-08-14 | 2005-06-14 | Riverhead Networks Inc. | Protecting against spoofed DNS messages |
US20040093513A1 (en) * | 2002-11-07 | 2004-05-13 | Tippingpoint Technologies, Inc. | Active network defense system and method |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070043947A1 (en) * | 2005-08-19 | 2007-02-22 | Mizikovsky Semyon B | Providing multimedia system security to removable user identity modules |
US20080120413A1 (en) * | 2006-11-16 | 2008-05-22 | Comcast Cable Holdings, Lcc | Process for abuse mitigation |
US11120406B2 (en) * | 2006-11-16 | 2021-09-14 | Comcast Cable Communications, Llc | Process for abuse mitigation |
US20090144806A1 (en) * | 2007-12-03 | 2009-06-04 | Cisco Technology, Inc. | Handling of DDoS attacks from NAT or proxy devices |
US8370937B2 (en) | 2007-12-03 | 2013-02-05 | Cisco Technology, Inc. | Handling of DDoS attacks from NAT or proxy devices |
US8595477B1 (en) * | 2011-03-24 | 2013-11-26 | Google Inc. | Systems and methods for reducing handshake delay in streaming protocol web requests |
US8887280B1 (en) * | 2012-05-21 | 2014-11-11 | Amazon Technologies, Inc. | Distributed denial-of-service defense mechanism |
CN103036741A (en) * | 2012-12-19 | 2013-04-10 | 北京神州绿盟信息安全科技股份有限公司 | Determination method and determination device of flow monitoring base line |
US11196691B2 (en) * | 2013-09-09 | 2021-12-07 | At&T Mobility Ii Llc | Method and apparatus for distributing content to communication devices |
US9729558B2 (en) * | 2014-02-21 | 2017-08-08 | The Regents Of The University Of Michigan | Network maliciousness susceptibility analysis and rating |
US20160065620A1 (en) * | 2014-02-21 | 2016-03-03 | The Regents Of The University Of Michigan | Network maliciousness susceptibility analysis and rating |
CN103997494A (en) * | 2014-05-22 | 2014-08-20 | 北京京东尚科信息技术有限公司 | Method and system for defending hacker attacks |
US10432650B2 (en) | 2016-03-31 | 2019-10-01 | Stuart Staniford | System and method to protect a webserver against application exploits and attacks |
CN108400955A (en) * | 2017-02-06 | 2018-08-14 | 腾讯科技(深圳)有限公司 | A kind of means of defence and system of network attack |
US10749896B2 (en) * | 2017-05-03 | 2020-08-18 | Red Button Ltd. | Method and system for determining a readiness of a computer network of an organization to denial of service (DoS) attacks |
Also Published As
Publication number | Publication date |
---|---|
US7536552B2 (en) | 2009-05-19 |
AU2005207632A1 (en) | 2005-08-04 |
WO2005069732A2 (en) | 2005-08-04 |
WO2005069732A3 (en) | 2008-01-10 |
CN101180826A (en) | 2008-05-14 |
CN102098305A (en) | 2011-06-15 |
CA2548336A1 (en) | 2005-08-04 |
EP1719285A2 (en) | 2006-11-08 |
EP1719285A4 (en) | 2010-12-01 |
AU2005207632B2 (en) | 2010-04-29 |
CN101180826B (en) | 2012-09-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7536552B2 (en) | Upper-level protocol authentication | |
US7472414B2 (en) | Method of processing data traffic at a firewall | |
US7620733B1 (en) | DNS anti-spoofing using UDP | |
US8370937B2 (en) | Handling of DDoS attacks from NAT or proxy devices | |
US7478429B2 (en) | Network overload detection and mitigation system and method | |
US7171683B2 (en) | Protecting against distributed denial of service attacks | |
US7568224B1 (en) | Authentication of SIP and RTP traffic | |
US8181237B2 (en) | Method for improving security of computer networks | |
US7313815B2 (en) | Protecting against spoofed DNS messages | |
US6907525B2 (en) | Protecting against spoofed DNS messages | |
US6775704B1 (en) | System and method for preventing a spoofed remote procedure call denial of service attack in a networked computing environment | |
EP2343851B1 (en) | Network authentication method, corresponding system and client device | |
US20030065943A1 (en) | Method and apparatus for recognizing and reacting to denial of service attacks on a computerized network | |
Herzberg et al. | Socket overloading for fun and cache-poisoning | |
CN110784464B (en) | Client verification method, device and system for flooding attack and electronic equipment | |
Al‐Hammouri et al. | ReCAP: a distributed CAPTCHA service at the edge of the network to handle server overload | |
Carrier et al. | A recursive session token protocol for use in computer forensics and tcp traceback | |
Djalaliev et al. | Sentinel: hardware-accelerated mitigation of bot-based DDoS attacks | |
EP1459171B1 (en) | Protecting network traffic against spoofed domain name system (dns) messages | |
Yang | Introduction to TCP/IP network attacks | |
Guha et al. | ShutUp: End-to-end containment of unwanted traffic | |
Shields et al. | A recursive session token protocol for use in computer forensics and tcp traceback | |
Lammatha | Intrusion Detection System |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TOUITOU, DAN;ZADIKARIO, RAFI;REEL/FRAME:016223/0235 Effective date: 20050120 |
|
AS | Assignment |
Owner name: RIVERHEAD NETWORKS, INC.,CALIFORNIA Free format text: MERGER;ASSIGNOR:RAZOR ACQUISITON CORP.;REEL/FRAME:017065/0001 Effective date: 20040414 Owner name: CISCO SYSTEMS, INC.,CALIFORNIA Free format text: MERGER;ASSIGNOR:RIVERHEAD NETWORKS, INC.;REEL/FRAME:017065/0007 Effective date: 20040609 Owner name: CISCO SYSTEMS, INC., CALIFORNIA Free format text: MERGER;ASSIGNOR:RIVERHEAD NETWORKS, INC.;REEL/FRAME:017065/0007 Effective date: 20040609 Owner name: RIVERHEAD NETWORKS, INC., CALIFORNIA Free format text: MERGER;ASSIGNOR:RAZOR ACQUISITON CORP.;REEL/FRAME:017065/0001 Effective date: 20040414 |
|
AS | Assignment |
Owner name: CISCO TECHNOLOGY, INC.,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CISCO SYSTEMS, INC.;REEL/FRAME:017164/0886 Effective date: 20060131 Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CISCO SYSTEMS, INC.;REEL/FRAME:017164/0886 Effective date: 20060131 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |