IP Library Granted Patent US 7,836,498
Granted Patent B2
US 7,836,498 · App. 09/931,344 · Granted Nov 16, 2010

Device to protect victim sites during denial of service attacks

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,836,498
App. No.
09/931,344
Granted
Nov 16, 2010
Kind
B2
Abstract

A system architecture for thwarting denial of service attacks on a victim data center is described. The system includes a first plurality of monitors that monitor network traffic flow through the network. The first plurality of monitors is disposed at a second plurality of points in the network. The system includes a central controller that receives data from the plurality of monitors, over a hardened, redundant network. The central controller analyzes network traffic statistics to identify malicious network traffic. In some embodiments of the system, a gateway device is disposed to pass network packets between the network and the victim site. The gateway is disposed to protect the victim site, and is coupled to the control center by the redundant hardened network.

Claims (71)

1. A gateway device disposed between a data center and a network for thwarting denial of service attacks on the data center, the gateway device comprising:

a computing device that performs:

a monitoring process that monitors network traffic through the gateway device;

a communication process that communicates statistics collected in the gateway from the monitoring process with a control center and that receives queries or instructions from the control center; and

a filtering process to insert filters on network devices to filter out packets that the gateway deems to be part of an attack.

2. The gateway of claim 1 wherein the communication process couples to a dedicated link to communicate with the control center over a hardened network.

3. The gateway of claim 1 wherein the monitoring process in the gateway samples network packet flow in the network.

4. The gateway of claim 1 wherein the gateway is adaptable to be physically deployed in line in the network.

5. The gateway of claim 1 wherein, the gateway is adaptable to dynamically install the filters on nearby routers.

6. The gateway of claim 1 wherein the monitoring process detects IP traffic and determines levels of unusual amounts of IP fragmentation or fragmented IP packets with bad or overlapping fragment offsets.

7. The gateway of claim 1 wherein the monitoring process detects Internet Protocol (IP) traffic and determines levels of IP packets that have bad source addresses or Internet Control Message Protocol (ICMP) packets with broadcast destination addersses.

8. The gateway of claim 1 wherein the monitoring process detects Internet Protocol (IP) traffic and determines levels of Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) packets to unused ports.

9. The gateway of claim 1 wherein the monitoring process detects IP traffic and determines levels of TCP segments advertising unusually small window sizes, which may indicate a load on the data center, or TCP ACK packets not belonging to a known connection.

10. The gateway of claim 1 wherein the monitoring process detects sustained rate higher than plausible for a human user over a persistent HTTP connection.

11. The gateway of claim 1 wherein the monitoring process maintains statistical summary information of traffic over different periods of time and at different levels of detail.

12. The gateway of claim 11 wherein the monitoring process maintains statistics on parameters including source and destination host or network addresses, protocols, types of packets, number of open connections or of packets sent in either direction.

13. The gateway of claim 12 wherein the monitoring process has configurable thresholds and issues a warning when one of the measured parameters exceeds the corresponding threshold.

14. The gateway of claim 13 wherein the monitoring process logs packets.

15. The gateway of claim 14 wherein the monitoring process logs specific packets identified as part of an attack to enable an administrator to identify important properties of the attack.

16. A method of protecting a victim site during a denial of service attack, comprising:

disposing a gateway device between the victim site and a network;

monitoring network traffic through the gateway device and measuring heuristics of the network traffic to provide statistics network traffic;

communicating the statistics collected in the gateway device to a control center; and

filtering out packets that the gateway or control center deems to be part of an attack.

17. The method of claim 16 wherein the communicating process occurs over a dedicated link to the control center via a hardened network.

18. The method of claim 16 wherein the monitoring process samples network packet flow in the network.

19. The method of claim 16 wherein the gateway is physically deployed in line in the network.

20. The method of claim 16 wherein the filtering process further comprises:

dynamically installing filters on nearby routers via an out of band connection.

21. The method of claim 16 wherein the monitoring process further comprises:

detecting IP traffic and determining levels of unusual amounts of IP fragmentation or fragmented IP packets with bad or overlapping fragment offsets.

22. The method of claim 16 wherein the monitoring process further comprises:

detecting Internet Protocol (IP) traffic and determining levels of IP packets that have bad source addresses or Internet Control Message Protocol (ICMP) packets with broadcast destination addresses.

23. The method of claim 16 wherein the monitoring process further comprises:

detecting Internet Protocol (IP) traffic and determining levels of Transport Control Protocol (TCP) or User Datagram Protocol UDP packets to unused ports.

24. The method of claim 16 wherein the monitoring process further comprises:

detecting IP traffic and determines levels of TCP segments advertising unusually small window sizes, which may indicate a load on the data center, or TCP ACK packets not belonging to a known connection.

25. The method of claim 16 wherein the monitoring process further comprises:

detecting a sustained rate of reload requests that is higher than plausible for a human user over a persistent HTTP connection.

26. The method of claim 16 wherein the monitoring process further comprises:

logging statistics on parameters including source and destination host or network addresses, protocols, types of packets, number of open connections or of packets sent in either direction.

27. The method of claim 16 wherein the monitoring process further comprises:

issuing a warning to the control center when one of the measured parameters exceeds a corresponding configurable threshold.

28. The method of claim 16 wherein the monitoring process further comprises:

logging specific packets identified as part of an attack to enable an administrator to identify important properties of the attack.

29. A computer program product residing on a non-transitory computer readable storage medium, storing instructions that when executed by a computer cause the computer to perform a method for protecting a victim site during a denial of service attack, the method comprising:

monitoring network traffic sent to the victim site and measuring heuristics of the network traffic to provide statistics on the network traffic;

communicating the statistics collected in the computer device to a control center; and

filtering out packets that the device or control center deems to be part of an attack.

30. The computer program product of claim 29 , wherein the monitoring process further comprises sampling network flow.

31. The computer program product of claim 29 , the filtering process further comprising:

dynamically installing filters on nearby routers via an out of band connection.

32. The computer program product of claim 29 , the monitoring process further comprising:

detecting IP traffic; and

determining levels of unusual amounts of IP fragmentation or fragmented IP packets with bad or overlapping fragment offsets.

33. The computer program product of claim 29 , the monitoring process further comprising:

detecting Internet Protocol (IP) traffic; and

determiing levels of IP packets that have bad source addresses or Internet Control Message Protocol (ICMP) packets with broadcast destination addresses.

34. The computer program product of claim 29 , the monitoring process further comprising:

detecting Internet Protocol (IP) traffic; and

determining levels of Transport Control Protocol (TCP) or User Datagram Protocol UDP packets to unused ports.

35. The computer program product of claim 29 , the monitoring process further comprising:

detecting IP traffic; and

determining levels of TCP segments advertising unusually small window sizes, which may indicate a load on the data center, or TCP ACK packets not belonging to a known connection.

36. The computer program product of claim 29 , the monitoring process further comprising:

detecting a sustained rate of reload requests that is higher than plausible for a human user over a persistent HTTP connection.

37. The computer program product of claim 29 , the monitoring process further comprising:

logging statistics on parameters including source and destination host or network addresses, protocols, types of packets, number of open connections or of packets sent in either direction.

38. The computer program product of claim 29 , the monitoring process further comprising:

issuing a warning to the control center when one of the measured parameters exceeds a corresponding configurable threshold.

39. The computer program of claim 29 , the communicating process further comprising receiving communications from the control center to deliver data pertaining to the types of traffic passing through the gateway.

Assignments (18)
RELEASE OF SECURITY INTEREST Recorded Aug 11, 2023
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC; RIVERBED HOLDINGS, INC.
Reel/Frame 064673/0739 →
CHANGE OF NAME Recorded Feb 18, 2022
From: RIVERBED TECHNOLOGY, INC.
To: RIVERBED TECHNOLOGY LLC
Reel/Frame 059232/0551 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0169 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0046 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0108 →
SECURITY INTEREST Recorded Dec 10, 2021
From: RIVERBED TECHNOLOGY LLC (FORMERLY RIVERBED TECHNOLOGY, INC.); ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
Reel/Frame 058486/0216 →
PATENT SECURITY AGREEMENT Recorded Oct 27, 2021
From: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 057943/0386 →
PATENT SECURITY AGREEMENT SUPPLEMENT - FIRST LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 057810/0502 →
PATENT SECURITY AGREEMENT SUPPLEMENT - SECOND LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 057810/0559 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORED AT REEL 056397, FRAME 0750 Recorded Oct 13, 2021
From: MACQUARIE CAPITAL FUNDING LLC
To: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 057983/0356 →
SECURITY INTEREST Recorded May 26, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MACQUARIE CAPITAL FUNDING LLC
Reel/Frame 056397/0750 →
PATENT SECURITY AGREEMENT Recorded Mar 5, 2021
From: RIVERBED TECHNOLOGY, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 055514/0249 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY NAME PREVIOUSLY RECORDED ON REEL 035521 FRAME 0069. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST IN PATENTS. Recorded Jun 2, 2015
From: JPMORGAN CHASE BANK, N.A.
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035807/0680 →
SECURITY INTEREST Recorded May 1, 2015
From: RIVERBED TECHNOLOGY, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 035561/0363 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 28, 2015
From: BARCLAYS BANK PLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035521/0069 →
PATENT SECURITY AGREEMENT Recorded Dec 27, 2013
From: RIVERBED TECHNOLOGY, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 032421/0162 →
RELEASE OF PATENT SECURITY INTEREST Recorded Dec 26, 2013
From: MORGAN STANLEY & CO. LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 032113/0425 →
SECURITY AGREEMENT Recorded Dec 20, 2012
From: RIVERBED TECHNOLOGY, INC.; OPNET TECHNOLOGIES, INC.
To: MORGAN STANLEY & CO. LLC
Reel/Frame 029646/0060 →