Propagation of viruses through an information technology network

• US 20040083372A1
• Filed: 10/20/2003
• Published: 04/29/2004
• Est. Priority Date: 10/19/2002
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Norman, Andrew Patrick, Williamson, Matthew Murray
• Granted Patent: US 8,046,624 B2
• Time in Patent Office: Days
• US Class Current: 713/188
• CPC Class Codes: G06F 21/566 Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms

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

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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

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.

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

10. 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.

11. 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.

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

13. 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.

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

15. 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.

16. 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.

17. 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.

18. 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.

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

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

21. 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.

22. 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.

23. 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.

24. 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.

25. 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.

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

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

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

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.

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

31. 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.

32. 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.

33. 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.

34. 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.

35. 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.

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

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

38. 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.

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

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

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