IP Library Granted Patent US 7,664,963
Granted Patent B2
US 7,664,963 · App. 10/702,073 · Granted Feb 16, 2010

Data collectors in connection-based intrusion detection

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,664,963
App. No.
10/702,073
Granted
Feb 16, 2010
Kind
B2
Abstract

A system for detecting network intrusions and other conditions in a network is described. The system includes a plurality of collector devices that are disposed to collect data and statistical information on packets that are sent between nodes on a network. An aggregator device is disposed to receive data and statistical information from the plurality of collector devices. The aggregator device produces a connection table that maps each node on the network to a record that stores information about traffic to or from the node. The aggregator runs processes that determine network events from aggregating of anomalies into network events.

Claims (51)

1. A collector device comprises:

a processor; and

a memory, the memory executing a computer program product to collect statistical information on packets that are sent between nodes on a network, including instructions to:

determine, which host in a host connection pair is performing a server process, and which host in the host connection pair is performing a client process, by determining what protocol was used in establishing a network connection for the host connection pair; and

if the protocol is not a connection based protocol and involves at least two ports, neither of which is known,

determine the ports that the hosts communicate over,

determine the port number for each of the at least two ports, and

report in the statistical information, the host that communicates using a lower port number of the two port numbers as performing the server process or the host that communicates using a higher port number of the two port numbers as performing the client process.

2. The device of claim 1 wherein if the protocol is a connection type protocol, then the device identifies which host sent a sync packet and which host sent a synch_ack packet.

3. The device of claim 2 wherein a source of the sync packet is the client and a source of the synch_ack is the server.

4. The device of claim 1 wherein if the hosts are transacting over a well know port, the instructions to determine, determines the server from a list of well known ports.

5. The device of claim 4 wherein the list of well known ports has identification of hosts based on previous sources of synch_ack packets, with the host that sent the synch_ack packet assumed to be the server.

6. The device of claim 1 wherein if the connection involves two ports, neither of which is known the instructions to report the host that connects to the lower port number as the server process and the host that connects to the higher port number as the client process.

7. The device of claim 1 wherein server/client statistics are used when attempting to identify worm intrusions.

8. A method executed on a computing device comprises:

collecting statistical information on packets that are sent between nodes on a network; and

determining which host in a host connection pair is performing a server process, and which host in the host connection pair is performing a client process, by determining what protocol was used in establishing a network connection for the host connection pair; and

determining whether the protocol is a connection based protocol, and if the protocol is not a connection based protocol and involves at least two ports, neither of which is known;

determining the ports that the hosts communicate over;

determining the port number for each of the at least two ports; and reporting in the statistical information, the host that communicates using the lower of the two port numbers as performing the server process or the host that communicates using the higher of the two port numbers as performing the client process.

9. The method of claim 8 wherein if determining determines that the protocol is a connection type protocol, the method identifies which host sent a sync packet and which host sent a synch_ack packet.

10. The method of claim 9 wherein determining, determines a source of the sync packet as the client and a source of the synch_ack as the server.

11. The method of claim 8 wherein if the hosts are transacting over a well known port, determining, determines the server from a list of well know ports.

12. The method of claim 11 wherein the list is populated with identification of hosts based on previous sources of synch_ack packets, with the host that sent the synch_ack packet assumed to be the server 8 .

13. The method of claim 8 wherein if the connection involves two ports, neither of which is known the reporting further includes reporting the host that connects to the lower port number as performing the server process and the host that connects to the higher port number as performing the client process.

14. The method of claim 8 wherein server/client statistics are used when attempting to identify worm intrusions.

15. A device comprises:

circuitry to collect statistical information on packets that are sent between nodes on a network;

circuitry to determine from the statistical information, which host in a host connection pair is performing a server process, and which host in the host connection pair is performing a client process,

circuitry to determine what protocol was used in establishing a network connection for the host connection pair; and

circuitry to determine whether the protocol is a connection based protocol, and

circuitry, responsive to an outcome from the circuitry to determine whether the protocol is connection based to determine the ports that the hosts communicate over if the protocol is not connection based and involves at least two ports, neither of which is known;

circuitry to determine the port number for each of the at least two ports; and

circuitry to report in the statistical information the host that communicates using the lower of the two port numbers as performing the server process or the host that communicates using the higher of the two port numbers as performing the client process.

16. The device of claim 15 wherein the circuitry to determine whether the protocol is a connection type protocol identifies which host sent a sync packet and which host sent a synch_ack packet.

17. The device of claim 16 wherein circuitry to determine, determines a source of the sync packet as the client and a source of the synch_ack as the server.

18. The device of claim 15 wherein if the hosts are transacting over a well known port, circuitry to determine, determines the server from a list of well know ports.

19. A computer readable medium tangible storing a computer program product for detecting intrusions in a network, comprises instructions for causing a processor to:

collect statistical information on packets that are sent between nodes on a network;

determine, which host in a host connection pair is performing a server process, and which host in the host connection pair is performing a client process, by determining what protocol was used in establishing a network connection for the host connection pair and wherein if the protocol is not a connection based protocol and involves at least two ports, neither of which is known the instructions to determine the ports that the hosts communicate over;

determining the port number for each of the at least two ports; and

report in the statistical information, the host that communicates using the lower of the two port numbers as performing the server process or the host that communicates using the higher of the two port numbers as performing the client process.

20. The product of claim 19 wherein if the protocol is a connection type protocol, then the instructions to determine identify which host sent a sync packet and which host sent a synch_ack packet, with the source of the sync packet being the client and the source of the synch_ack being the server.

21. The product of claim 19 wherein if the protocol is not a connection based protocol the instructions to determine the ports that the hosts communicate over.

22. The product of claim 21 further comprising instructions to:

determine if the hosts are transacting over a well know port; and

access a list of well-known ports to determine the server from the list of well known ports.

23. The product of claim 22 wherein the list of well known ports has identification of hosts based on previous sources of synch_ack packets, with the host that sent the synch_ack packet assumed to be the server.

24. The device of claim 22 wherein if a connection involves two ports, neither of which is known, the ports having port numbers with the host that connects to a lower port number of the port numbers of the two ports is reported as the server.

25. The device of claim 22 wherein server/client statistics are used when attempting to identify worm intrusions.

26. The device of claim 15 wherein circuitry to determine, determines if the connection involves two ports, neither of which is known and the circuitry to report, reports the host that connects to a lower port number of two ports numbers involving the two ports, as the server process, and the host that connects to a higher of the two port numbers, as the client process.

Assignments (21)
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: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0108 →
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 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 15, 2009
From: MAZU NETWORKS, LLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 022542/0800 →
CHANGE OF NAME Recorded Mar 30, 2009
From: MAZU NETWORKS, INC.
To: MAZU NETWORKS, LLC
Reel/Frame 022460/0886 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 25, 2004
From: KOHLER, EDWARD W., JR.; POLETTO, MASSIMILIANO ANTONIO; RATIN, ANDREW
To: MAZU NETWORKS, INC.
Reel/Frame 015497/0292 →