# US 2004/0083372 A1 · Propagation of viruses through an information technology network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0083372 A1
- Document ID: US20040083372A1
- Status: Published application
- Kind: A1
- Application number: 10/687,694
- Filed: 2003-10-20
- Published: 2004-04-29
- Earliest claimed: 2002-10-19
- Assignees: Hewlett-Packard Development Company, L.C.
- Inventors: Matthew Murray Williamson; Andrew Patrick Norman
- Web page: https://patentgrep.com/patent/US20040083372A1

## CPC

- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Requests to send data from a first host within a network of hosts are monitored against a record of destination hosts who have been sent data in accordance with a predetermined policy. Destination host identities not the record are stored in a buffer. The buffer size is monitored to establish whether requests from the first host are pursuant to viral activity therein.

## Claims

### Claim 1

A method of monitoring propagation of viruses within a network of hosts comprising the steps of:
establishing a record which is at least indicative of identities of hosts within the network to whom data has been sent by a first host (“destination hosts”);
during a first time interval, comparing (a) identities of destination hosts identified in requests to send data from the first host and (b) identities of destination hosts identified in the record;
transmitting all requests to send data;
storing in a buffer data relating to requests which identify a destination host not in the record.

### Claim 2 (depends on 1)

A method according to claim 1 wherein the record is established by monitoring identities of destination hosts to whom requests have been transmitted during a second time interval, which precedes the first time interval.

### Claim 3 (depends on 2)

A method according to claim 2, wherein the record contains a predetermined maximum number of destination host identities, the maximum number being defined in accordance with a policy.

### Claim 4 (depends on 3)

A method according to claim 3, wherein the policy additionally defines a maximum number of destination host identities not in the record, to whom requests may be legitimately transmitted in accordance with policy.

### Claim 5 (depends on 4)

A method according to claim 4 further comprising the step, at the end of any given time interval, of deleting from the buffer data relating to requests transmitted during the given time interval in accordance with policy.

### Claim 6 (depends on 5)

A method according to claim 5 further comprising the step, at the end of the given time interval, of updating the record to reflect identities of hosts identified in requests which are transmitted in accordance with policy during the given time interval.

### Claim 7 (depends on 6)

A method according to claim 6 further comprising the step of updating the record to reflect the identity of the predetermined maximum number of destination host identities to whom data has most recently been sent in accordance with policy.

### Claim 8

A method according to any one of the preceding claims, wherein the stored data is offered in a buffer and includes a copy of a socket created to send data in accordance with a request.

### Claim 9 (depends on 8)

A method according to claim 8 wherein the socket enables identification of at least one application program at whose behest the socket is created.

### Claim 10 (depends on 1)

A method according to claim 1 further comprising the steps of:
determining the value of parameter (“slack”) based upon a number of successive time periods that pass when no new requests are made to send data from the first host to hosts not in the record; and
slack exceeds a predetermined value, allowing the un-impeded passage of data from the first host to other hosts not in the record.

### Claim 11 (depends on 10)

A method as claimed in claim 10, wherein slack is determined based upon the number of successive time periods for which the buffer is empty.

### Claim 12 (depends on 10)

A method as claimed in claim 10, wherein slack has a predetermined maximum value.

### Claim 13 (depends on 10)

A method as claimed in claim 10, wherein the value of slack is decremented each time an un-impeded passage of data from the first host to a host not in the record is allowed.

### Claim 14 (depends on 10)

A method according to claim 10, wherein said time periods are of equal duration to at least one of said time intervals.

### Claim 15 (depends on 1)

A method according to claim 1 further comprising the step of monitoring the rate of increase in the size of the buffer, and in the event that the rate of increase in the size of the buffer exceeds a predetermined rate, generating a warning.

### Claim 16 (depends on 1)

A method according to claim 1 further comprising the step of monitoring the increase in the size of the buffer per time interval, and in the event that the increase in the size of the buffer in any given time interval exceeds the predetermined size, generating a warning.

### Claim 17 (depends on 1)

A method according to claim 1 further comprising the step of monitoring the size of the buffer, and in the event that the buffer exceeds a predetermined size for a predetermined number of successive time intervals, generating a warning.

### Claim 18 (depends on 1)

A method as claimed in claim 1, wherein at least one parameter selected from the group consisting of: number of destination hosts in the record; threshold number of requests identifying destination hosts not in the record and defining a state of viral infection, is varied with time.

### Claim 19 (depends on 18)

A method as claimed in claim 18, wherein at least one parameter is varied as a function of the time of day

### Claim 20 (depends on 18)

A method as claimed in claim 18, wherein at least one of the parameters is varied in response to a perceived threat level.

### Claim 21 (depends on 18)

A method as claimed in claim 18, wherein at least one of the parameters is changed between a first set of values and a second set of values at a predetermined rate.

### Claim 22 (depends on 18)

A method as claimed in claim 18, wherein at least one of the value of at least one of the parameters is randomly changed according to a predetermined probability distribution as a function of time.

### Claim 23 (depends on 1)

A method as claimed in claim 1, wherein at least one parameter selected from the group consisting of: number of destination hosts in the record; threshold number of requests identifying destination hosts not in the record and defining a state of viral infection, is determined by performing an automated search on a set of data indicative of normal network traffic.

### Claim 24 (depends on 1)

A method according to claim 1 further comprising the steps of:
receiving a request to send a multiple recipient email;
determining the value of a parameter (“mslack”) based upon the number of successive time periods that pass when no multiple recipient emails are sent from the first host;
if mslack exceeds a predetermined value, allowing the unimpeded passage of the multiple recipient email.

### Claim 25 (depends on 24)

A method according to claim 24, wherein the multiple recipient email is allowed un-impeded passage if mslack is greater than or equal to the number of intended recipients of the email.

### Claim 26 (depends on 24)

A method as claimed in claim 24, wherein mslack is set to zero after the multiple recipient email has been sent.

### Claim 27 (depends on 24)

A method as claimed in claim 24, wherein mslack has a predetermined maximum value.

### Claim 28 (depends on 24)

A method according to claim 24, wherein said time periods are of equal duration to at least one of said time intervals.

### Claim 29

A method of operating a first host within a network of a plurality of hosts comprising the steps of:
over the course of a first time interval, monitoring creation of sockets within the first host to identify destination hosts identified therein;
comparing identities of destination hosts monitored during the first time interval with destination host identities in a record; and
storing data from all sockets which identify destination hosts not in the record.

### Claim 30 (depends on 29)

A method according to claim 29 wherein the stored socket data at least enables identification of the destination host identified therein.

### Claim 31 (depends on 29)

A method according to claim 29 wherein the record identifies a maximum number of destination hosts, the maximum number being determined in accordance with a policy.

### Claim 32 (depends on 31)

A method according to claim 31 wherein the record is established by monitoring creation of sockets during a time interval preceding the first time interval.

### Claim 33 (depends on 31)

A method according to claim 31 wherein the policy additionally specifies a maximum number of sockets identifying a destination host not in the record to be legitimately created in any given time interval.

### Claim 34 (depends on 33)

A method according to claim 33 wherein at the end of a time interval, socket data containing identities of destination hosts in respect of whom sockets have legitimately been created is deleted.

### Claim 35 (depends on 29)

A method according to claim 29 further comprising the step, in the event that the number of socket data items stored exceeds a predetermined value, of storing outgoing packets from the first host.

### Claim 36 (depends on 35)

A method according to claim 35 wherein packets having a designated destination IP address are stored.

### Claim 37 (depends on 36)

A method according to claim 36 further comprising the step of establishing the predetermined IP address from the stored socket data.

### Claim 38 (depends on 29)

A method according to claim 29 further comprising the step, in the event that the number of socket data items stored exceeds a predetermined value, of storing incoming packets to the first host.

### Claim 39 (depends on 38)

A method according to claim 38 wherein packets having a designated source IP address are stored.

### Claim 40 (depends on 39)

A method according to claim 39, further comprising the step of establishing the predetermined IP address from the stored socket data.

### Claim 41 (depends on 29)

A method according to claim 29 wherein socket data is stored in a buffer.
