E-mail virus protection system and method

[0001] The present application claims the benefit of U.S. Provisional Application No. 60/213,254, filed Jun. 22, 2000, whose disclosure is hereby incorporated by reference in its entirety into the present disclosure.

[0002] 1. Field of the Invention

[0003] The present invention relates generally to computer systems and computer networks. In particular, the present invention relates to a system and method for detecting and nullifying the effects of computer viruses. Still more particularly, the present invention relates to a system and method for detecting and nullifying the effects of computer viruses from messages and attachments delivered by electronic mail through a network.

[0004] 2. Description of the Related Art

[0005] Computer viruses are a destructive aspect of the computer revolution that threatens its potential growth and usability. Significant time and money are lost annually combating the effects of this insidious, and seemingly endemic, problem. A computer virus is actually just an unauthorized block of executable computer code purporting to be harmless or is hidden in another valid computer program. Once the valid program is executed, the unauthorized virus code is also activated. The effect of such viruses can be simple pranks, such as causing messages to be displayed on the screen, or more serious activities, such as destroying programs and data. Once executed, they often spread quickly by attaching themselves to other programs in the system. Infected programs may in turn continue the cancerous replication by copying the virus code to still other programs. The proliferation of Internet E-mail has only accelerated the problem in that local viruses can now spread internationally in a matter of hours.

[0006] Prior art attempts to reduce the effects of viruses and prevent their proliferation by using various virus detection schemes have been only marginally successful. The reason for the limited success is that the prior art methods attempt to identify the existence of a virus before taking steps to protect a user. For example, many virus detection programs use a method known as “behavior interception,” which monitors the computer or system for key system functions such as “write,” “erase,” “format disk,” etc. When such operations occur, the virus detection program prompts the user for input as to whether such an operation is expected. If the suspect operation was not expected (e.g., the user was not operating any program that employed such a function), the user can abort the operation. Another virus detection method, known as “signature scanning,” scans program code that is being copied onto the system. Again, the virus detector searches for recognizable patterns of program code, such as the program attempting to write into specific file or memory locations, that betray the possible existence of a virus. Yet another prior art approach to virus detection performs a checksum (mathematical signature) on critical programs stored on a system that are known to be free of viruses. If a virus later attaches itself to one of these programs, the checksum value—which is periodically recalculated—will be different and thus, the presence of a virus detected.

[0007] While all of these methods work to some degree, they tend to suffer from one critical drawback: They depend on recognizing the virus as a virus before instituting any protection for the user. All too often, new (unrecognized) viruses must first wreak havoc on a significant number of victims before the new virus' identifying characteristics are recognized and included in the (ever-lengthening) watch lists of the various virus protection programs available to government and industry.

[0008] The present invention overcomes the limitations of the prior art by implementing a system and method that eliminates the threat of viruses transmitted on a computer network by rendering any viruses inoperable. As discussed above, all viruses are programs. Like all programs, they are designed to run in a specific or predictable environment. Viruses depend on a host computer's operating system to recognize them as valid programs. They also depend on the host computer's central processing unit (CPU) to understand the virus' commands and obey them. Non executable entities are, by nature, incapable of launching a virus. Therefore, if a host computer converts all data received via e-mail (mail and attachments) to non-executable entities, any embedded virus is rendered inoperable. The present invention describes a method and system of virus protection that involves passing all e-mail and attachments through various conversion states that, while harmless to e-mail text and attachments, the conversions are lethal to executable code (viruses).

[0009] Even though the majority of e-mail received by a company or government agency should contain no valid executable components, a small percentage of e-mail attachments, such as “working drafts,” and standard contract templates may require user updating or valid executable macros. Therefore, the present invention also describes a system and method of identifying “Approved” embedded macros and—as long as they have not been modified-allowing them to survive the virus killing conversions.

[0010] Finally, the present invention also includes a unique “sacrificial PC” system and method capable of safely executing, detecting (via examination of the results of execution), and safely recovering from potentially virus-laden e-mails.

[0015] Though not essential to every embodiment of this invention, the preferred emodiment makes use of the following concepts and principles:

[0016] 1. Recipients of e-mails are ultimately more qualified to determine what information is acceptable than a generalized software program or system

[0017] 2. If given an opportunity, a user can clearly define which e-mail types and attachments he or she does or does not wish to receive.

[0018] 3. The ability of users to accept macros and other forms of executable code commonly used in modern computer generated business forms and templates must be maintained.

[0019] 4. All information is potentially important to a user. Therefore, software systems, including security programs, should not arbitrarily delete or withhold e-mail content without specific knowledge and authorization of the owner of the e-mail system.

[0020] 5. The value of information tends to decrease over time. Therefore, information contained in e-mails should not be unreasonably delayed.

[0021] The gatekeeper method and system described herein operate under the following rules and definitions:

[0022] 1. Any macro or executable code that alters the physical appearance of an e-mail or attachment is considered by the gatekeeper to be a customized form.

[0023] 2. All customized forms requiring user input must be authorized by the owner of the e-mail system.

[0024] In an effort to provide recipients with all of the contents of all e-mails and attachments (not prohibited by the owner of the e-mail system) all unauthorized form will be executed; however, the form's output (not the form itself) will be delivered to the user in a “safe” non-executable format.

[0025] The Gatekeeper method and system described defines and ability to authorize and authenticate all forms.

[0026] The virus detection system and method of the present invention preferably operates on a system as depicted in FIG. 1.

[0027] An intermediary E-mail security server (102), referred to as “the Gatekeeper” intercepts all e-mail messages and attachments sent by a sender (101) via a communications network, such as the Internet (109). The arriving unopened e-mail and attachments are archived and logged (202) with a date and time stamp, plus any routing information available. Address data is then stripped off of the e-mail (204) for attachment to the “safe” e-mail constructed at (210). The e-mail portion of the Internet e-mail received from (201) is passed through a conversion process (205) that eliminates all executable code leaving only alphanumeric message text. Any imbedded hyperlinks or email addresses, while still identifiable as links or addresses, are rendered inoperable as executable “links.” The Gatekeeper (102) then checks to see if the arriving e-mail contains an attachment (206). If the e-mail contains no attachment, processing continues at step (210).

[0028] If the e-mail contains an attachment, the attachment types (extensions) are validated against several lists provided by the client during the installation process. The e-mail attachment type is first checked against a list of client approved acceptable file extensions. If the attachment extension is not in the approved list, it is considered either disapproved or unknown. (212). If the attachment extension type is found in the disapproved list, a message is constructed indicating that “this e-mail contains a disapproved attachment.” The disapproval message is included in the safe e-mail constructed in step (210).

[0029] If the e-mail contains an attachment with an extension that is not in either the “disapproved” or “approved” lists, the entire attachment is passed through a conversion process (205) that eliminates all executable code leaving only alphanumeric message text. This process will generally create a readable copy of the attachment, but will not allow the attachment to open any processes or applications, including executable virus code. If the included attachment from (206) is of an approved extension type, attachment inspection processing continues at (208), which checks the approved attachment extension to see if it contains any executable code (macros). This process involves reading the attachment file's internal format and identifying any executable code, such as macros that may be present. Any executable code ound is noted and identified for authentication (209). An encrypted authentication identifier is created for the executable code by passing it through an algorithm such as, a checksum or hashing algorithm (213), that uniquely identifies the string of executable code. The unique identifier is then encrypted using a key known only to the Gatekeeper program or server. The authentication identifier is then compared to a list of approved code contained by the Gatekeeper and supplied by the Client (216). Since this system and method described validates only the executable code (macros), the non-executable data portion of the attachment can safely be changed or updated interactively. If the attachment contains approved macros, the original attachment is made available to the recipient. If the attachments contain unapproved macros, the attachment is forwarded to an available sacrificial PC processor (103) via data link (108) for conversion to a non-executable format and further detailed virus testing. The method just described for detecting, authenticating, and approving a macro can be used to authenticate and approve any form of executable code embedded in an attachment or in the body of an e-mail message. Such code can include compiled programs, interpretive code, scripts, batch language, markup language code, or the like located in any part of the e-mail message, including the body and the attachments.

[0030] Sacrificial PC processing begins with the original e-mail attachment being passed to an available sacrificial PC (105) via a data link (108) connecting the Gatekeeper server (102) with the sacrificial PC. Once the transfer of the attachment is complete the data link (108) is intentionally broken. This eliminates the possibility of any unintended communications back to the Gatekeeper. The original attachment is then opened using standard Windows application processing supplied by the client (303). The opened attachment is then passed through a process (304) which converts the attachment to a non-executable image format, such as Portable Document Format (PDF). Note there are many suitable image formats. The process would choose one selected by the client. The safe image format version of the attachment is then encrypted in the sacrificial PC's unique authentication key assigned by the Gatekeeper at startup. The data link (108) to the Gatekeeper is then re-established (306) and the encrypted non-executable attachment is returned to the Gatekeeper (307).

[0031] All communications from a sacrificial PC to the Gatekeeper are interrogated by the Gatekeeper's communications processor (220). Before being accepted by the Gatekeeper as a valid message, the data must pass a strict authentication test (219). The authentication process is as follows.

[0032] At System startup (and periodically, if desired) the Gatekeeper creates a randomly generated set of authentication parameters to be used by each sacrificial PC when communicating with the Gatekeeper. When a sacrificial PC wants to communicate with the Gatekeeper it first sends a handshake packet to the Gatekeeper identifying the specific PC requesting communication. It also sends a short (unencrypted) clear-text portion of the data to be communicated encapsulated within the handshake packet.

[0033] Once the Gatekeeper acknowledges the handshake, the sacrificial PC sends the full information packet to the Gatekeeper. A random amount of the packet has been encrypted in the sacrificial PC's unique key. The specific amount of data encrypted by the sacrificial PC was determined by one of the authentication parameters sent by the Gatekeeper at startup. The Gatekeeper decrypts all data packets it receives based on the assumed key of the specific sacrificial PC. In other words, “If you are who you say you are, you encrypted your data in the following way.” Once decrypted, the Gatekeeper compares the clear text portion of the data received in the handshake packet with the decrypted data packet (219). If they match, the data is accepted; if they do not, the data is not accepted. The authentication technique is based on known “challenge and response” authentication techniques.

[0034] Once the sacrificial PC has sent the read only “safe” attachment back to the Gatekeeper, a special validation process examines the sacrificial PC to determine if any unexpected changes have occurred (308) and (309) on the sacrificial PC. Unexpected changes could include the addition or deletion of files, files that change name, extension, or content unexpectedly, (including morphing of the tested attachment itself), attempted sensing of the date and time features of the sacrificial PC, etc.

[0035] Also, when the opportunity is available, as with attachments created using the Microsoft suite of office products, the sacrificial PC processor takes advantage of the “Enable Macros” “Disable Macros” feature. This built-in feature makes it possible to open a document without allowing any embedded code (macros) to execute. Two copies of the same document can then be created, one created with macros executed and one created without macros executed. The two copies of the same document can then be examined to determine if executing the macro had any effect on the information content of the document. By comparing the two documents, the sacrificial PC can determine whether or not the macro is relevant to the particular document being tested.

[0036] If execution of the macro was necessary to produce the information contained in the tested document, then the macro's contribution is contained in the print image copy of the document produced by the sacrificial PC when it executed the document with macros enabled. This is the copy that is sent to the recipient.

[0037] Similarly, if testing the document with “macros disabled” has no impact on the content of the document, then the suspect macro is not necessary. It logically follows then, that the suspect macro is either irrelevant to the content the particular version of the document being tested or, it is a virus. In either case, the sacrificial PC has intercepted and nullified the suspect macro's impact on the recipient.

[0038] Any unexpected changes in the system trigger a virus alert. Standard user security processes alert all authorized personnel (309). A special “ghosting” reload of the operating system then takes place. The process is as follows.

[0039] Each Sacrificial PC is configured with two hard drives. Each hard drive is configured with a single active partition and contains a safe copy of the operating system obtained from the read-only device (110). The designated active partition—defined at start-up—is “toggled” between the two physical hard drives. This is done to increase the speed of reloading and to maximize the availability of sacrificial PCs. The unused drive—which is the one used to test the last attachment—is re-loaded, via ghosting software (310), with a fresh copy of the operating system obtained from the read only CD ROM (110). The connection between the Gatekeeper (102) and the sacrificial PC (105) is then re-established.

[0040] Once the sacrificial PC is re-ghosted, it is brought back on line and the GateKeeper assigns it a new authentication Key and encryption length parameter.

[0041] Once the Gatekeeper sends data to a sacrificial PC, it notes the time the data was sent. If no data is received back from a sacrificial PC within a specified period of time (typically two minutes), the Gatekeeper assumes the sacrificial PC has become the victim of a virus and died. When this occurs, the Gatekeeper signals a virus alert and requests human intervention to recover the dead sacrificial PC.

[0042] The method and system described above can also be implemented with the sacrificial PC implemented as a virtual machine or environment in the operating system of another computer. This computer could be the gatekeeper, an e-mail server or any other computer.

[0043] The method and system described above also be implemented with the gatekeeper system implemented as part of another system, such as a component of an already existing e-mail server.

[0044] The gatekeeper system and method described uses the file and macro authentication and encrypted client approval techniques described above to protect itself from both internal and external “hacking” attacks that may attempt to substitute, modify, destroy or otherwise nullify gatekeeper files and programs.

[0045] While a preferred embodiment has been set forth in detail above, those skilled in the art who have reviewed the present disclosure will readily appreciate that other embodiments can be realized within the scope of the invention. For example, the use of certain hardware, operating systems, or the like should be construed as illustrative rather than limiting. Therefore, the present invention should be construed as limited only by the appended claims.