Computer virus detection

[0001] 1. Field of the Invention

[0002] This invention relates to the field of data processing systems. More particularly, this invention relates to the detection of an outbreak of a computer virus on a data processing system.

[0003] 2. Description of the Prior Art

[0004] It is known to detect computer viruses using signature definitions of those viruses. In this technique, when a new virus is discovered, a characteristic pattern of computer instructions is identified associated with the virus and this characteristic pattern then added to a library of computer virus definitions so that a suspect file can be compared against this library of definitions to determine whether it contains one of the known computer viruses identified within the library.

[0005] An alternative approach to virus identification is heuristic testing in which types of activity associated with viruses are searched for and used to identify candidate viruses. As an example, an executable computer file that has at its start a call to a routine located at the end of the executable file is a strong candidate for having been infected with a virus.

[0006] A problem with both of the above techniques is that they are only generally capable of detecting known viruses or viruses behaving in known ways. As an example, it is only after a virus has been created, released and infected innocent users, that it will be drawn to the attention of anti-virus system makers who can then add a new virus definition to their library of definitions characteristic of the newly released virus to enable its detection by the library technique. Similarly, a virus with a new type of action, such as Word macro viruses when they were first released, present a problem for heuristic identification since their patterns of activity are not ones that are being tested for until after those new viruses have been created, released and infected innocent users.

[0007] It is known from Trend's Scan Mail Exchange Beta Release to provide a system in which a virus outbreak is notified if more than a threshold number of known viruses are detected within a 24 hour period. This technique does not address unknown viruses and types of virus behavior.

[0008] It is an object the present invention to provide improved anti-virus systems that are able to provide some defense against new viruses and new types of virus.

[0009] Viewed from one aspect the present invention provides a computer program product for detecting an outbreak of a computer virus on a computer apparatus, said computer program product comprising:

• • [0010] (i) measurement computer code operable to measure one or more measurement parameters indicative of non virus specific activity of said computer apparatus over a respective measurement period;
  • [0011] (ii) comparison computer code operable to compare said one or more measurement parameters with respective predetermined threshold levels; and
  • [0012] (iii) signal generating computer code operable to generate a signal indicative of an outbreak of a computer virus if one or more of said one or more measurement parameters crosses a respective predetermined threshold level.

[0013] The invention uses a new virus detection approach. In particular, the invention detects an outbreak of a computer virus by measuring parameters of the activity of the computer system as a whole over a measurement period. The technique does not seek to detect an individual virus by its fingerprint or characteristic manner of execution, but instead measures non virus specific activity. It has been found that when a computer system is subject to an outbreak of a computer virus, then it exhibits certain measurable characteristics that may be useful in detecting the occurrence of the virus outbreak. More particularly, since the technique of the invention is not looking for an individual virus or pattern of execution of a virus, it is able to more readily detect previously unknown viruses by the effect that they have on the activity of the computer system as a whole. The predetermined threshold levels may be manually set or may automatically vary in dependence upon detected long-term behaviour.

[0014] As preferred examples of the measurement parameters that may be used there are proposed:

• • [0015] 1. How many E-mail messages are sent having an identical message title.
  • [0016] 2. How many E-mail messages are sent identical file attachment.
  • [0017] 3. How many email messages are sent having a file attachment of a given file type.
  • [0018] 4. How many E-mail messages are sent having a file attachment that is an executable file.
  • [0019] 5. The E-mail through put within the computer system.
  • [0020] 6. The E-mail throughput measured in a form dependent upon a number of E-mails multiplied by a total size for the E-mails.

[0021] It will be appreciated by those in the field that the usage patterns of a computer system typically vary considerably with the time of day. In an office environment, there is usually considerably higher computer system usage during working hours than outside working hours. Even within working hours, there are often peaks in activity which can have corresponding effects upon the measurement parameters monitored by the invention, e.g. peaks in activity shortly before lunch and in mid afternoon.

[0022] In preferred embodiments of the invention the predetermined threshold levels can be varied in dependence upon the time of day and the day of the week.

[0023] More generally, the measurement parameters monitored by the system may be selected by the user and the measurement periods over which activity is measured (using a variety of different statistical measurement techniques) may be user selected to adapt the anti-virus system to the particular computer system upon which it is operating.

[0024] The invention also provides a method of detecting an outbreak of a computer virus on a computer apparatus and an apparatus for detecting an outbreak of a computer virus on a computer apparatus.

[0025] The above, and other objects, features and advantages of this invention will be apparent from the following detailed description of illustrative embodiments which is to be read in connection with the accompanying drawings.

[0033] FIG. 1 shows a computer system 2 coupled to remote computer systems 4 and 6 via internet network links 8, 10. The computer system 2 comprises a local area network. The local area network 2 is formed of a file server 12 to which a plurality of client computers 14 are linked by conventional local network connections. The file server 12 is linked to the remote computers 4, 6 via a firewall server 16 that serves to resist hacking and other security attacks. A mail server 18 coupled to the file server 12 provides E-mail services to the local area network 2. More particularly, the mail server 18 receives E-mail messages with associated attachments from remote computers.

[0034] A remote computer 6 may be a virus source. The virus source 6 may be unwitting in that it is merely passing on an infection it has itself incurred. Alternatively, the virus source 6 could be controlled by the virus originator. A computer virus may be introduced into the local area network 2 from the virus source 6 via an E-mail attachment, a security breach of the firewall server 16, a removable media introduced by a user or in some other way.

[0035] The local area network 2 is also coupled to a remote computer 4 that is controlled by the anti-virus system provider. This remote computer 4 includes a library of virus definitions 20 and a repository for suspect files 22. The anti-virus provider will frequently update the virus definitions stored by the remote computer 4 to reflect the latest viruses that have been discovered. Computer files suspected by users of the anti-virus system as being infected with a computer virus can be automatically sent to the suspect files repository 22 by the user computers so that they may be analysed as rapidly as possible by the anti-virus system provider.

[0036] FIG. 2 schematically illustrates a general purpose computer of the type capable of executing the software which can embody the present invention. The computer includes a central processing unit 24, a working memory 26, a non-volatile memory 28 (such as a hard disk drive or an ROM), an external network link 30, a display driver 32, a user input interface 34 and an internal network link 36. The above items are linked via a common bus 38. A display monitor 40 is coupled to the display driver 32 and a keyboard 42 and a mouse 44 are coupled to the user input interface 34.

[0037] In operation, the computer system illustrated in FIG. 2 can execute a computer program stored within the non-volatile storage 28 using the working memory 26. The computer system may receive information or send information via either the external network link 30 or the internal network link 36. The computer software will control the display driver 32 to produce images and text upon the monitor 40 to enable a user manipulating the keyboard 42 and the mouse 44 to interact and control the computer program executing on the computer system.

[0038] The controlling computer program that controls the computer is stored in the non-volatile storage 28. The computer program may be recorded on a floppy disk, or a CD for distribution. Alternatively, the computer program may be obtained as a product by downloading via the external network link 30.

[0039] The computer program executing on the computer system of FIG. 2 seeks to detect a virus outbreak by monitoring one or more measurement parameters obtained over a measurement period against predetermined threshold levels. This process is illustrated in FIG. 3. FIG. 3 shows four measurement parameters with their associated (user controlled) threshold levels Th1, Th2, Th3 and Th4. The computer program periodically checks each of the measurement parameters against its respective threshold to determine if that threshold has been crossed. In the case of the measurement parameters 1, 2 and 4, the normal state for these measurement parameters is less than their respective threshold values. Conversely, the normal state for the measurement parameter 3 is greater than its threshold value. In the example illustrated in FIG. 3, the measurement parameters 1, 2 and 3 are all normal whilst the measurement parameter 4 has crossed (exceeded) its threshold value (Th4) resulting in generation of a signal indicating an outbreak of a computer virus. The measurement parameters can take many different forms. Examples of suitable measurement parameters are:

• • [0040] 1. How many E-mail messages are sent having an identical message title within a predetermined period;
  • [0041] 2. How many E-mail messages are sent having an identical file attachment within a predetermined period;
  • [0042] 3. How many E-mail messages are sent having a file attachment of a given file type (e.g. a EXE, COM or DOC) within a predetermined period;
  • [0043] 4. How many E-mail messages are sent having a file attachment that is an executable file within a predetermined period; and
  • [0044] 5. That the E-mail throughput measured as the number of messages multiplied by their size exceeds a predetermined level within a predetermined period.

[0045] It will be appreciated that the way in which the measurement parameters may be derived could take various different forms. The system could look at a rolling average over the measurement period, a peak value within a measurement period, a simple count of instances within a measurement period or various other measurements suited to the particular parameter concerned.

[0046] In the case of the above examples relating to E-mail behaviour on a computer system, existing computer E-mail program products, such as Microsoft Exchange Server (produced by Microsoft Corporation), already provide performance monitoring variables that may be read by other programs to gain information concerning the E-mail activity of the computer system. Similarly, many other measurement parameters are already available within computer systems as provided by operating systems or other computer programs executing on these systems. The computer program seeking to detect computer virus outbreaks can read and use these existing parameters. Alternatively, if desired, the computer program may include routines that themselves derive parameters indicative of the activity of the computer system. Conventional programming techniques may be used to derive these parameters.

[0047] FIG. 4 is a flow-diagram illustrating the computer virus outbreak detection technique of the present invention. At step 46 the system reads the current threshold levels and tests that are to be applied. The threshold levels and tests may be varied with the time of day and day of week in dependence upon a user defined schedule. As a simple example, a business hours and an out of hours set up may be configured with different tests and threshold levels being applied in these different respective periods. Step 46 serves to read the thresholds and tests that are to be applied at the current time and day.

[0048] Step 48 selects the first test from the list together with its associated threshold value and an indication of whether its normal state is above or below the threshold value.

[0049] Step 50 detects the measurement parameter MP_n associated with the currently selected test. As previously mentioned, this may be read from another computer program or derived by the anti-virus system itself.

[0050] At step 52 the detected measurement parameter MP_n is compared with its associated threshold value Th_n. If the threshold value is crossed, then processing proceeds to step 54 at which a signal indicating a virus outbreak is generated.

[0051] If the threshold value is not crossed, then processing proceeds to step 56 where a test is made to see if the last test has yet been reached. If the last test has not yet been reached, then the next test and threshold are selected at step 58 and processing is returned to step 50. If the last test has been reached, then processing terminates.

[0052] It will be appreciated that the process illustrated in the flow-diagram of FIG. 4 will be repeatedly executed at an interval that may be set so as to provide as rapid as needed detection of a virus outbreak without consuming an excessive amount of computer processing resources.

[0053] When a computer virus outbreak has been detected, then the system of the present invention provides an at least partially automated response to that detected outbreak following a predetermined sequence of actions. FIG. 5 illustrates this technique. Some of the steps require a user to confirm that they should be executed before they are executed. As shown in FIG. 5, steps 1, 3 and 4 execute automatically following expiry of their escalation time whereas steps 2 and 5 require user confirmation prior to being executed.

[0054] When the virus outbreak is detected, step 1 is immediately executed. If the virus outbreak is detected as persisting despite the execution of step 1 and after the expiry of the escalation time associated with step 1, then processing proceeds to seek confirmation that step 2 should be executed. Assuming such confirmation is received, then step 2 is executed and a determination made after an escalation time associated with step 2 as to whether or not the virus outbreak is still persisting. In this way, a predefined sequence of steps are executed spaced by appropriate escalation times set to allow the respective executed step to take effect in order that it may be determined whether or not the virus outbreak has been overcome. In general, the severity and adverse consequences of the various steps in the predefined sequence to the normal operation of the system upon which they reside increases as you progress through the sequence. Accordingly, it is desirable to check after the associated escalation time associated with each step as to whether or not it has been effective since this may avoid the need to execute a more severe counter-measure that would unnecessarily adversely affect the normal operation of the computer system.

[0055] The counter-measures that may be taken in the predefined sequence can vary considerably. As examples, given in an order that has been found to provide an appropriate balance between effectiveness and impact upon normal operation, are as follows:

• • [0056] 1. Reducing virus detection notifications to reduce server workload;
  • [0057] 2. Switching from virus quarantining to virus deletion when a virus is detected;
  • [0058] 3. Increasing how thoroughly the computer system is scanned to detect computer viruses, e.g. the scanning options may be adjusted to scan all file types rather than just some file types, to scan files being read as well as files being written, or some other increase in the thoroughness of the scanning;
  • [0059] 4. Automatically sending a copy of detected computer virus to a remote site for analysis. Returning to FIG. 1, the local area network 2 may detect a computer virus outbreak and seek to deal with it via the automated response. At some stage in this response, the local area network 2 may send a copy of the computer virus across the internet link 8 to the suspect file repository 22 in the computer system 4 of the anti-virus system provider.

[0060] 5. Downloading a latest version of the virus definitions file from a remote site in order to increase the likelihood of success of the counter-measures by using the very latest virus definitions. This latest virus definition library may be downloaded from the computer system 4 of the anti-virus system provider via the internet link 8 in a similar way to the preceding step of uploading a copy of the suspect file.

[0061] 6. An “on demand” scan of all of the computer files stored on the file server 12, the firewall server 16, the mail server 18 and individual client computers 14 of the local area network 2 may be performed.

[0062] Such an on-demand scan represents a considerable processing load and is likely to degrade the performance of the local area network 2 while it is taking place, but this may nevertheless be desirable if the computer virus outbreak has persisted despite the preceding counter-measures.

[0063] 7. Blocking E-mail attachments that appear in excess of a threshold level or blocking all E-mail attachments. The measurement parameters of the E-mail system or bespoke routines within the anti-virus program may detect if particular files or types of files are associated with E-mails being sent or received upon the computer system that has the virus outbreak. If the number of attachments exceeds a predetermined threshold level, then the anti-virus system may interact with the E-mail systems to block further attachments of that file, that file type or all attachments.

[0064] 8. A recent common type of virus is one that automatically reads a computer user's E-mail address book and distribution lists and then sends itself to those identified E-mail addresses as a way of propagating itself. A counter-measure effective against such viruses is to automatically hide or render inoperative all users' address books or distribution lists such that they may not be read and used by this type of virus.

[0065] 9. A drastic step that may be taken against a sever virus outbreak is to shutdown the E-mail server 18 and either re-start it in Administrator only mode or not restart it at all. Such a drastic measure is highly likely to be effective against computer viruses using the E-mail services to propagate themselves, but clearly will have a severe adverse impact upon normal use of the computer system.

[0066] FIG. 6 is a flow-diagram illustrating the sequence of predetermined steps (that may be automatic or prompted, possibly selected in dependence upon time) that may be followed in response to a detected virus outbreak.

[0067] At step 60, the latest sequence of steps appropriate to the particular time of day and day of week is read. As with the measurement parameters and threshold levels, the predetermined sequence can be varied in dependence upon the time of day and day of week to more appropriately match the use of the system at these times and the availability of support staff to interact with the systems upon occurrence of a virus outbreak.

[0068] At step 62 the first counter-measure step is selected. At step 64 a test is made as to whether user confirmation is required prior to execution of the currently selected step. If user confirmation is required, then this is sought via step 66 before processing proceeds to step 68 at which the selected step is executed. If confirmation is not required, then processing proceeds directly from step 64 to step 68.

[0069] Step 70 serves to wait for an escalation time associated with the current step after that step has been executed before a test is made at step 72 to determine whether the virus outbreak is continuing. The test applied at step 72 may comprise running the routine illustrated in FIG. 4.

[0070] If step 72 reveals that the outbreak has been stopped, then processing ends. If the outbreak is persisting, then processing proceeds to step 74 at which a determination is made as to whether or not the last step in the predetermined sequence of steps has yet been applied. If the last step has already been applied, then processing terminates. Alternatively, if the last step has not yet been applied, then processing proceeds to step 67 at which the next step is selected prior to returning processing to step 64.

[0071] A description of the set-up and user interaction with the computer program described above is given in the following description:

[0072] Configuration Wizard

[0073] The Configuration wizard User Interface (UI) is based on the approach taken in the Microsoft Outlook Rules wizard. The first dialog contains a list of user-defined events and re-actions (rules). These outbreak rules are listed in an order which determines the priority in which determination of an outbreak will occur. The user follows a set of wizard dialogs specifying the data they require for the outbreak event and action. The information is stored in an .INI file to aid in cross-platform portability.

[0074] The initial dialog for the wizard (see FIG. 7) allows the user to add, copy, modify, rename and delete Outbreak rules for the system. You are also able to order the rules by priority using the move up and move down buttons. When the outbreak service (for example NT Service) is checking if outbreaks are occurring, it works its way down the list from the top to the bottom. The dialog also has a description pane to describe the rule whenever one is highlighted in the outbreak list.

[0075] When the user presses new or modify they progress through the outbreak wizard pages starting with the one shown in FIG. 8.

[0076] Event Wizard Page

[0077] The wizard page functions similar to the Microsoft Outlook rules wizard. The user selects an event type in the event list and an English description appears below. There are a series of underlined words. The user clicks on these as if they were html links in a web browser. Upon clicking, a dialog appears asking them to enter a value (see FIG. 9). Once the value is entered it replaces the placeholder but is also underlined and clickable for the user to change/edit.

[0078] There is also a threshold event. This allows a user to set, for example, peak mail throughput thresholds for a period in the i.e. am, midday and pm (see FIG. 10).

[0079] Upon specifying the event required for an outbreak. The user can click next to move onto the next wizard page. They are not able to progress until the relevant event values have been filled out (in accordance with the table below).

[0080] Upon clicking the Next button, the wizard in FIG. 11 is displayed.

[0081]

	Name	Type	Details
	Number of hours	Numeric	0-23
	Number of minutes	Numeric	0-59
	Threshold minimum	Numeric	None
	Threshold maximum	Numeric	None
	Threshold value	Numeric	None

[0082] Reaction Type Wizard Page

[0083] The user is then able to specify the action they require upon an outbreak being detected. There are two categories of action, Manual and Automatic. Upon selection of Manual, the user can specify to be notified via email, network broadcast or pager. They then fill out any notification details using the html type links (See FIGS. 12, 13 and 14). Upon selecting out of office hours, the user enters the times they are out of the office during the week. FIG. 15 shows the selection control which functions in the same manner as the scheduling control in Microsoft Exchange Administrator for scheduling replication.

[0084] Once all the values have been filled out for manual notifications, the user continues to either the finish wizard page or the reactions page depending upon what has been selected. If manual reaction has been selected, the reaction page will only appear if they have selected “Use out of office hours”.

[0085] Data Validation for Notification

[0086]

Name	Type	Details
Email Address	Alpha Numeric	Valid Email Format i.e.
		Has . and @ symbols
Pager Numer	Numeric	None
Network Broadcast	Alpha Numeric	Valid Computer name

[0087] Automatic Virus Reaction Wizard Page

[0088] Upon completing the reaction type, the user is presented with the wizard page shown in FIG. 16. The user then has the ability to add and remove items from the list using the buttons at the bottom of the list. The add button will bring up a dialog displaying a choice of available actions to take as in FIG. 17. The move up and move down buttons allow the user to specify the order in which the reactions are carried out. They are then able to specify a time period in which to escalate to the next item in the list. The user can have one or more reaction types in the list. Escalations work down the list from top to bottom. Upon reaching the last item and the event still firing, then notifications will be sent to an administrator via e-mail. An escalation occurs if the event is still firing after the time period for the current action has been exceeded.

[0089] The user is also able to specify an outbreak report created (in a file on the hard disk) upon an outbreak being detected. This provides a history of what has happened during detection and automated reaction (an audit trail). The report option defaults to on.

[0090] For any action that is considered extreme, the user will be warned via a message box to ensure that they are aware of the data entered.

[0091] Data validation for escalation.

[0092]

	Name	Type	Details
	Escalation hours	Numeric	None
	Escalation minutes	Numeric	0-59

[0093] Outbreak Summary Wizard Page

[0094] Lastly the summary wizard page shows what has been completed during the earlier pages. When the user clicks finish they will return to the dialog shown in FIG. 7.

[0095] Outbreak Wizard Flowchart

[0096] See FIG. 19.

[0097] Outbreak Service

[0098] The outbreak service runs as an NT service and can be stopped and started using the services applet in the control panel. The service runs under the system account and therefore can interact with the desktop. There is an icon added to the task bar tray (see FIG. 20) which provides a popup menu (see FIG. 21).

[0099] The popup menu provides the ability to view general statistics (i.e. when outbreak thresholds were exceeded and what actions were taken) and outbreak event specific statistics (see FIG. 22). The outbreak event statistics display enough information to the user to be able to intelligently set the outbreak thresholds for the event.

[0100] The outbreak service upon a manual event displays the lock down dialog (see FIG. 23) with a list of actions to take. This is also available from the popup menu whenever the user requires. They are then able to select the required action. The UI will only appear on the server that is running the outbreak service.

[0101] Outbreak events are also enabled/disabled via the popup menu. A tick is placed along side each event that is currently enabled. The popup menu is also able to spawn the performance monitor along with the relevant perfmon work spaces. This will allow the application performance counters to be loaded and configured in performance monitor.

[0102] The configuration of the app can also be started from the popup menu. In this case it will load Microsoft Exchange admin.exe.

[0103] Appendix A

• • [0104] Events and actions are described below for the Microsoft Exchange version of the product.

[0105] Events

• • [0106] Number of viruses over a time period
  • [0107] Number of identical viruses over a time period
  • [0108] Number of identical attachments over a time period
  • [0109] Number of identical attachment types over a time period
  • [0110] Number of viruses per user over time (On-demand scan only???)
  • [0111] Throughput>Threshold
  • [0112] Delta from previous 24 hours (Number of virus over twenty four hours)

[0113] Actions

Actions will be Manual or Automatic. Manual will notify the user only and not perform any actions unless “Use out of office hours” is specified and the event is triggered during the specified out of office hours.

• • [0114] Notify user (e-mail, pager, network broadcast).
  • [0115] Reduce notifications to reduce server load.
  • [0116] Set to delete on infection instead of current quarantining setting to reduce load.
  • [0117] Increase the scan options—scan all files, enable all heuristics.
  • [0118] Perform a DAT update.
  • [0119] Perform an on-demand scan.
  • [0120] Block the items that caused the event (i.e. 500 docs in an hour triggered an event, so block all doc files.
  • [0121] Block all attachments.
  • [0122] Hide Distribution lists to prevent E-mail enabled viruses from E-mailing themselves to large groups of people.
  • [0123] Hide Mailboxes to prevent E-mail enabled viruses from E-mailing themselves to your users.
  • [0124] Down the Exchange server and bring back up only allowing the admin to log on.
  • [0125] Down Exchange and leave it down.

[0126] Although illustrative embodiments of the invention have been described in detail herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments, and that various changes and modifications can be effected therein by one skilled in the art without departing from the scope and spirit of the invention as defined by the appended claims.