Patent Description:
The use of electronic mail (email) as a communications tools has proliferated over recent years. Due to its widespread use and popularity, email has become a target for spreading malicious software (malware). Malware may include software used to disrupt computer operations, gather sensitive information stored on computers, or gain access to private computer systems and networks. Malware may be any code that is surreptitiously provided to a user or which otherwise performs undisclosed/unauthorized functions. An email message containing malware or virus program can infect the recipient's computing device, as well as other computers and servers on the same network as the infected computing device. To prevent malware/virus attacks, recipients of suspicious email messages are encouraged to report such email messages to system administrators. System administrators are tasked with investigating, diagnosing and processing suspicious email messages in order to determine if they are legitimate or not, and, in the case of an illegitimate email message, to implement remedial measures, such as to prevent similar email messages from being received. A prior approach to analyzing suspicious email messages involves use of different tools to examine the contents, or specific portions thereof, of an email message, such as a web page, email message, file or universal resource locator included in the email message contents, often using a sandbox or isolated environment in order to prevent any active elements from being able to be effective.

<CIT> discloses an integrated environment for automated processing of reports, from users, of suspicious messages, and a network for distributing information about detected phishing attacks, and further includes simulated phishing attacks to test the user responses <CIT> also constitutes relevant prior art which has been used to draw up the European search report and examine the European patent application.

The disclosed systems and methods generally enable an administrator to safely examine email messages, including their contents, and in particular, to identify, but disable execution of, potentially malicious artifacts (e.g., Internet links, attachments, macros, headers) in an email message, and easily and conveniently investigate / handle each artifact. The disclosed email security system acts as an intermediary between an administrator user and an email message and modifies how an administrator interacts with the email message and manages how the email message may interact with the computer executing the disclosed email security system and its software, e.g., the system causes interactions with email messages to be manipulated to yield a desired result, namely, that all of the artifacts in an email message that could be malware are identified but disabled, and are further associated with a payload button for investigating the artifact. The email security system overrides the routine and conventional sequence of events ordinarily triggered by opening up an email message, clicking Internet hyperlinks and/or opening / inspecting attachments. The email security system changes the normal operation of an email message by decomposing the email message into its constituent parts, segregating any artifacts included therein and directing the administrator to an Artifact Dashboard that presents the artifacts of an email message (via descriptor objects) as well as payload buttons for investigating and processing each artifact's payload.

The described embodiments are to be considered only as illustrative and not restrictive. The scope of the invention is defined by the appended claims, the dependent claims define further embodiments of the invention. In one embodiment, the Artifact Dashboard is directly accessible via a button on the email client, such as Microsoft Outlook®. The Artifact Dashboard is integrated with the email client, and suspicious email messages received via the email client can be analyzed, classified and handled directly from the email client. The disclosed system accordingly facilitates administrator/analyst investigations by providing a safe and efficient application/framework/dashboard without needing to access disparate tools (which could lead to a disorganized / non-standardized workflow) to handle an email message that is received in the email client.

Because there are many legitimate uses for non-malicious artifacts, e.g., colleagues emailing each other attachments related to a work project, simply blocking all artifacts from all email messages is not possible or helpful. Moreover, it is often difficult to distinguish malicious from non-malicious artifacts. The email security system removes the interactivity associated with an artifact, and instead automatically decomposes and presents an artifact in an inert form without its associated payload. The email security system is a technology-based solution of analyzing suspicious email messages received over the Internet or other network that overcomes the risks, inconveniences and increased likelihood of error associated with existing systems.

Malware may be present on Internet webpages (accessible via Internet links) or in attachments. Some prior art systems disclose analyzing potential malware samples using secure isolated environments, such as sandboxes or virtual machines. See, e.g., <CIT>,<CIT>, <CIT>,<CIT>, and <CIT>, and <CIT>. For example, Internet links and/or attachments can be analyzed for suspicious content using secure sandboxed/virtual machine environments.

An unscrupulous email message can also be detected using email message headers. <CIT> describes analyzing/reading Internet message headers of email messages to identify the source of the email message and determining if the email messages pose a threat or are otherwise malicious based on the source of the email messages.

While the administrator computer preferably accesses the email security system directly from main memory or local storage, the email security system may, alternatively, be located remotely, e.g., on a server, and be accessed through the Internet or a separate computer network connecting the administrator computer to the email security system. In one embodiment, the systems and methods may be implemented at an email server before the email message is received by the recipient computer coupled therewith.

The disclosed embodiments may be implemented in a computing system and network. An exemplary network environment for implementing the disclosed systems and methods is shown in <FIG>. A computer system <NUM> may be coupled to computer devices <NUM>, <NUM>, <NUM>, <NUM> and <NUM> over a wide area network <NUM> and/or local area network <NUM>.

Herein, the phrase "coupled with" is defined to mean directly connected to or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware and software based components. Further, to clarify the use in the pending claims and to hereby provide notice to the public, the phrases "at least one of <A>, <B>,. and <N>" or "at least one of <A>, <B>,. <N>, or combinations thereof" are defined by the Applicant in the broadest sense, superseding any other implied definitions herebefore or hereinafter unless expressly asserted by the Applicant to the contrary, to mean one or more elements selected from the group comprising A, B,. and N, that is to say, any combination of one or more of the elements A, B,. or N including any one element alone or in combination with one or more of the other elements which may also include, in combination, additional elements not listed.

The computer system <NUM> may be implemented with one or more mainframe, desktop or other computers, such as the example computer <NUM> described herein with respect to <FIG>.

One skilled in the art will appreciate that the methods described herein may be implemented using, among other things, a tangible computer-readable medium comprising computer-executable instructions (e.g., executable software code). Alternatively, the methods may be implemented as software code, firmware code, specifically configured hardware or processors, and/or a combination of the aforementioned. As described herein, the disclosed embodiments may be implemented as a centrally accessible system or as a distributed system, e.g., where some of the disclosed functions are performed by different computer systems.

The network environment shown in <FIG> includes exemplary computer devices <NUM>, <NUM>, <NUM>, <NUM> and <NUM> which depict different exemplary methods or media by which a computer device may be coupled with the computer system <NUM> or by which a user may communicate. It should be appreciated that the types of computer devices deployed by users and the methods and media by which they communicate with the computer system <NUM> is implementation dependent and may vary and that not all of the depicted computer devices and/or means/media of communication may be used and that other computer devices and/or means/media of communications, now available or later developed may be used. Each computer device, which may comprise a computer <NUM> described in more detail with respect to <FIG>, may include a central processor, specifically configured or otherwise, that controls the overall operation of the computer and a system bus that connects the central processor to one or more conventional components, such as a network card or modem. Each computer device may also include a variety of interface units and drives for reading and writing data or files and communicating with other computer devices and with the computer system <NUM>. Depending on the type of computer device, a user can interact with the computer with a keyboard, pointing device, microphone, pen device or other input device now available or later developed.

An exemplary computer device <NUM> is shown directly connected to computer system <NUM>, such as via a T1 line, a common local area network (LAN) or other wired and/or wireless medium for connecting computer devices, such as the network <NUM> shown in <FIG> and described with respect thereto. The exemplary computer device <NUM> is further shown connected to a radio <NUM>. The user of radio <NUM>, which may include a cellular telephone, smart phone, or other wireless proprietary and/or non-proprietary device. The radio user may transmit orders or other information to the exemplary computer device <NUM> or a user thereof. The user of the exemplary computer device <NUM>, or the exemplary computer device <NUM> alone and/or autonomously, may then transmit the information to the computer system <NUM>.

Exemplary computer devices <NUM> and <NUM> are coupled with a local area network ("LAN") <NUM> which may be configured in one or more of the well-known LAN topologies, e.g., star, daisy chain, etc., and may use a variety of different protocols, such as Ethernet, TCP/IP, etc. The exemplary computer devices <NUM> and <NUM> may communicate with each other and with other computer and other devices which are coupled with the LAN <NUM>. Computer and other devices may be coupled with the LAN <NUM> via twisted pair wires, coaxial cable, fiber optics or other wired or wireless media. As shown in <FIG>, an exemplary wireless personal digital assistant device ("PDA") <NUM>, such as a mobile telephone, tablet based compute device, or other wireless device, may communicate with the LAN <NUM> and/or the Internet <NUM> via radio waves, such as via WiFi, Bluetooth and/or a cellular telephone based data communications protocol. PDA <NUM> may also communicate with computer system <NUM> via a conventional wireless hub <NUM>.

<FIG> also shows the LAN <NUM> coupled with a wide area network ("WAN") <NUM> which may be comprised of one or more public or private wired or wireless networks. In one embodiment, the WAN <NUM> includes the Internet <NUM>. The LAN <NUM> may include a router to connect LAN <NUM> to the Internet <NUM>. Exemplary computer device <NUM> is shown coupled directly to the Internet <NUM>, such as via a modem, DSL line, satellite dish or any other device for connecting a computer device to the Internet <NUM> via a service provider therefore as is known. LAN <NUM> and/or WAN <NUM> may be the same as the network <NUM> shown in <FIG> and described with respect thereto.

The operations of computer devices and systems shown in <FIG> may be controlled by computer-executable instructions stored on a non-transitory computer-readable medium.

Numerous additional servers, computers, handheld devices, personal digital assistants, telephones and other devices may also be connected to computer system <NUM>. Moreover, one skilled in the art will appreciate that the topology shown in <FIG> is merely an example and that the components shown in <FIG> may include other components not shown and be connected by numerous alternative topologies.

Referring now to <FIG>, an illustrative embodiment of a general computer system <NUM> is shown. The computer system <NUM> can include a set of instructions that can be executed to cause the computer system <NUM> to perform any one or more of the methods or computer based functions disclosed herein. The computer system <NUM> may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices. Any of the components discussed herein, such as processor <NUM>, may be a computer system <NUM> or a component in the computer system <NUM>.

In a networked deployment, the computer system <NUM> may operate in the capacity of a server or as a client user computer in a client-server user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system <NUM> can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system <NUM> can be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system <NUM> is illustrated, the term "system" shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.

As illustrated in <FIG>, the computer system <NUM> may include a processor <NUM>, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor <NUM> may be a component in a variety of systems. For example, the processor <NUM> may be part of a standard personal computer or a workstation. The processor <NUM> may be one or more general processors, digital signal processors, specifically configured processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data. The processor <NUM> may implement a software program, such as code generated manually (i.e., programmed).

The computer system <NUM> may include a memory <NUM> that can communicate via a bus <NUM>. The memory <NUM> may be a main memory, a static memory, or a dynamic memory. The memory <NUM> may include, but is not limited to, computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one embodiment, the memory <NUM> includes a cache or random access memory for the processor <NUM>. In alternative embodiments, the memory <NUM> is separate from the processor <NUM>, such as a cache memory of a processor, the system memory, or other memory. The memory <NUM> may be an external storage device or database for storing data. Examples include a hard drive, compact disc ("CD"), digital video disc ("DVD"), memory card, memory stick, floppy disc, universal serial bus ("USB") memory device, or any other device operative to store data. The memory <NUM> is operable to store instructions executable by the processor <NUM>. The functions, acts or tasks illustrated in the figures or described herein may be performed by the programmed processor <NUM> executing the instructions <NUM> stored in the memory <NUM>. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firm-ware, micro-code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.

As shown, the computer system <NUM> may further include a display unit <NUM>, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information. The display <NUM> may act as an interface for the user to see the functioning of the processor <NUM>, or specifically as an interface with the software stored in the memory <NUM> or in the drive unit <NUM>.

Additionally, the computer system <NUM> may include an input device <NUM> configured to allow a user to interact with any of the components of system <NUM>. The input device <NUM> may be a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device operative to interact with the system <NUM>.

In a particular embodiment, as depicted in <FIG>, the computer system <NUM> may also include a disk or optical drive unit <NUM>. The disk drive unit <NUM> may include a computer-readable medium <NUM> in which one or more sets of instructions <NUM>, e.g., software, can be embedded. Further, the instructions <NUM> may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions <NUM> may reside completely, or at least partially, within the memory <NUM> and/or within the processor <NUM> during execution by the computer system <NUM>. The memory <NUM> and the processor <NUM> also may include computer-readable media as discussed herein.

The present disclosure contemplates a computer-readable medium that includes instructions <NUM> or receives and executes instructions <NUM> responsive to a propagated signal, so that a device connected to a network <NUM> can communicate voice, video, audio, images or any other data over the network <NUM>. Further, the instructions <NUM> may be transmitted or received over the network <NUM> via a communication interface <NUM>. The communication interface <NUM> may be a part of the processor <NUM> or may be a separate component. The communication interface <NUM> may be created in software or may be a physical connection in hardware. The communication interface <NUM> is configured to connect with a network <NUM>, external media, the display <NUM>, or any other components in system <NUM>, or combinations thereof. The connection with the network <NUM> may be a physical connection, such as a wired Ethernet connection or may be established wirelessly. Likewise, the additional connections with other components of the system <NUM> may be physical connections or may be established wirelessly.

The network <NUM> may include wired networks, wireless networks, or combinations thereof. The wireless network may be a cellular telephone network, an <NUM>, <NUM>, <NUM>, or WiMax network. Further, the network <NUM> may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to, TCP/IP based networking protocols.

Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. While the computer-readable medium is shown to be a single medium, the term "computer-readable medium" includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term "computer-readable medium" shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, or a combination of one or more of them.

In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.

In an alternative embodiment, dedicated or otherwise specifically configured hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the methods described herein.

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and anyone or more processors of any kind of digital computer. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few.

As used herein, the terms "microprocessor" or "general-purpose processor" ("GPP") may refer to a hardware device that fetches instructions and data from a memory or storage device and executes those instructions (for example, an Intel Xeon processor or an AMD Opteron processor) to then, for example, process the data in accordance therewith. The term "reconfigurable logic" may refer to any logic technology whose form and function can be significantly altered (i.e., reconfigured) in the field post-manufacture as opposed to a microprocessor, whose function can change post-manufacture, e.g. via computer executable software code, but whose form, e.g. the arrangement/layout and interconnection of logical structures, is fixed at manufacture. The term "software" may refer to data processing functionality that is deployed on a GPP. The term "firmware" may refer to data processing functionality that is deployed on reconfigurable logic. One example of a reconfigurable logic is a field programmable gate array ("FPGA") which is a reconfigurable integrated circuit. An FPGA may contain programmable logic components called "logic blocks", and a hierarchy of reconfigurable interconnects that allow the blocks to be "wired together", somewhat like many (changeable) logic gates that can be inter-wired in (many) different configurations. Logic blocks may be configured to perform complex combinatorial functions, or merely simple logic gates like AND, OR, NOT and XOR. An FPGA may further include memory elements, which may be simple flip-flops or more complete blocks of memory.

Feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback. Input from the user can be received in any form, including acoustic, speech, or tactile input.

Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components.

It should be appreciated that the disclosed embodiments may be applicable to other types of messages depending upon the implementation. Further, the messages may comprise one or more data packets, datagrams or other collection of data formatted, arranged configured and/or packaged in a particular one or more protocols, e.g., the FIX protocol, TCP/IP, Ethernet, etc., suitable for transmission via a network <NUM> as was described, such as the message format and/or protocols described in <CIT> and <CIT>. Further, the disclosed message management system may be implemented using an open message standard implementation, such as FIX, FIX Binary, FIX/FAST, or by an exchange-provided API.

Referring now to <FIG> illustrates an example workflow <NUM> that an administrator may execute using a computer upon receiving an email message suspected of containing malware. For example, a system administrator may receive an email message that is suspected to be, include links to, or contain malware (step <NUM>). The email message may be forwarded to the administrator from a sender, who may have received the email message from another entity. For example, the administrator may be responsible for inspecting email messages received by the sender and for safeguarding the sender's computer system.

The administrator may then manually locate artifacts within the email message that may be, link to, or contain malware (step <NUM>). For example, the email message may include artifacts such as Internet links within the body of the email message that, if clicked, access a malicious website, or attachments that, if clicked or executed, harm the computer or perform an otherwise malicious action. Some email clients are configured to detect Internet links and format them so they appear to be underlined for ease of identification by a user. However, many email clients cannot detect all Internet links, and some text can be configured to prevent detection by email clients. Moreover, an email message may contain non-Internet link text that is also underlined, thus simply locating underlined text does not lead to locating all Internet links. In addition, hypertext markup language (HTML) allows the display text and the underlying link to be different. Accordingly, some Internet links may be disguised, e.g., the display text may appear to be one URL (e.g., a safe website) but the actual underlying link that is opened in the browser upon interacting with the display text may be, or link or malware. The administrator may need to visually inspect the text, or the underlying html code for indicators (such as www,. net, http://, https://, etc.) signaling that the email message contains an Internet link. The administrator may also hover over text (i.e., position the mouse cursor over text without clicking on the text) to confirm if text is an Internet link that, if clicked, will access the Internet using the computer's Internet browser, because some email clients are configured to display a full Internet address upon hovering over an Internet link. In one embodiment, the email security system identifies all underlying Internet links, regardless of what the display text is for an Internet link. In one embodiment, the Artifact Dashboard discussed below displays both the display text of the Internet link and the underlying link code of the Internet link.

For each Internet link that is identified by the administrator, the administrator copies the Internet link (step <NUM>) using a user interface device, which enables a copy function of the administrator's computer, so that the copied text can be stored in a temporary memory or buffer and pasted into a different application. As is known in the art, cut, copy and paste are common computer functions that allow a user to manipulate text and/or files in a computer environment. These computer functions allow the user to easily copy or move data between one application and another or copy and move files and directories from one location to another. For example, copied text or files may be stored in a temporary copy buffer. After the copied text or file is pasted, or otherwise used, in another application or location, the temporary buffer contents may be emptied.

The user interface device may be a mouse, or may be a touchscreen controlled by finger gestures by a user. The administrator must be sure to only copy, and not click on or activate, the Internet link using the user interface device. Clicking on, instead of copying, the Internet link could be a dangerous act that could compromise the administrator's computer and/or network. After copying the Internet link, the administrator may open up a separate sandbox tool or environment (step <NUM>) and paste the Internet link in the separate tool to check whether the Internet link causes harmful / malicious effects. A sandbox tool or environment on a computer allows a user to open up or test an application or browser in an isolated environment, so that any changes to the isolated environment are prevented from affecting the rest of the computer, and all changes/downloads associated with the sandboxed application are removed from the computer when the sandbox tool is closed or exited. A sandbox may be a separate server that the administrator needs to access.

The administrator analyzes the Internet link in the sandbox to check the effects, including any malicious activity, of the Internet link (<NUM>). Any malware that might have been downloaded and installed from the Internet link is discarded when the sandbox is exited. The administrator may then return (<NUM>) to the email client or to some other application, such as a notes or text editor, to document information about the Internet link.

The administrator may also access tools (step <NUM>) that maintain lists of Internet links known to be malicious. The administrator only has to paste the suspicious Internet link into such a tool to determine if the Internet link is known to be a malicious website. Such tools thus allow the administrator to determine if the Internet link is malicious without having to even open it, e.g., in a sandbox environment. Upon searching the tool for the target Internet link (step <NUM>), the administrator may return (<NUM>) to the email client or to a notes or text editor to document information about the Internet link.

If the email message contains attachments, the administrator may log in to a separate forensic server (step <NUM>) to examine the attachment. Logging into the forensic server requires the administrator to leave the email client. The forensic server may be similar to the sandbox discussed above, but may allow additional examining capabilities. In the forensic server, the administrator opens the email (step <NUM>), downloads the attachment (step <NUM>), and runs a script (step <NUM>) to examine the nature and the effects of the email message attachment. The administrator may also log into ThreatGuard® (step <NUM>) to examine the attachment. Attachments may also be checked in a variety of different tools that maintain lists of malicious attachments (steps <NUM> and <NUM>).

The administrator then returns (<NUM>) to the email client or to a notes or text editor to document information about the attachment. The administrator may also open up the header of the email message (step <NUM>), e.g., through the email client's menu options, to detect spoofing attempts. Or, the administrator may determine if the Internet header of an email message is a known malware source. An email client may allow the administrator to manually view the source of an email message to determine if the email message may contain malware. For example, <FIG> illustrates an example screen shot of a source screen <NUM> presented by an email client when the administrator uses the email client to view the source of an email message. The administrator manually inspects the contents of the source screen to attempt to determine the originator of the email, any Internet links in the email message, and any other artifact information about the email message.

The administrator may then manually categorize the email message (e.g., malicious, non-malicious, phishing, phishing test, spam, marketing) and send the email message submitter instructions for how to handle the email message.

Process <NUM> is inefficient because the administrator may need to access and utilize several different tools and secure servers just to respond to one email message. In cases where an email message includes multiple artifacts, the administrator has to manually keep track of each artifact, and address / consider each artifact before categorizing the email message and responding to the email message sender. An administrator could easily forget to check each artifact. Or, the administrator could fail to perform each of the steps for an artifact. For example, process <NUM> requires the administrator to open an Internet link in a sandbox, and check the Internet link against a known list of malicious Internet links. It should be appreciated that an administrator may overlook one of the recommended steps when analyzing an email message that includes many, e.g., dozens of Internet links.

Process <NUM> is also cumbersome for an administrator. Analyzing an artifact typically requires the administrator to open up a separate application, window or tool on the administrator's computer. In some cases, the administrator's computer screen may simultaneously display overlapping header windows, browsers, sandbox environments, virtual environments, and/or server access tools along with the email client and the email message being checked, resulting in a confusing and overwhelming user environment that may be susceptible to user confusion and error. For example, Microsoft Outlook's® header view is a small window that makes reading header information difficult.

Process <NUM> is also potentially dangerous because the administrator could, while copying a link or attachment, accidentally open the link or attachment and expose the administrator's computer to malware.

The disclosed email security system automatically identifies artifacts (e.g., Internet links, attachments and headers) from an email message, and displays descriptor objects of the artifacts to the administrator in a single window that preserves all of the relevant information along with associated action/payload buttons for managing various artifacts, while removing the functionality (e.g., payload) associated with an artifact. The payload buttons allow the administrator to process the artifact. The system removes the ability to execute/open any of the identified artifacts, thus eliminating the risk of infecting the administrator's computer. The tools invoked for, and actions performed on, an artifact's payload may be customizable by the administrator, increasing the flexibility and convenience of the email security system.

The system also allows administrators to categorize email messages, and send standard replies (based on templates) to the email message submitter containing instructions for how to handle the email message, based on the categorization.

The email security system automatically parses a suspicious / target email message and detects and identifies content within the email message, or attributes of the email message, and presents information about the email message in an Artifact Dashboard. The administrator can configure conditions that if met, determine whether email message content is identified as an artifact. For example, the email security system may be configured to automatically identify any text or underlying code beginning with "www" and ending with ". com" as an Internet link. In one embodiment, the email security system may automatically identify Uniform Resource Locator links (URLs) as Internet links.

The email security system can also use information from the email client to determine, for example, that an email message includes an attachment. In one embodiment, any attachment to the email message may be deemed an artifact, which is then processed/handled as discussed herein.

<FIG> block diagram illustrates an example email security system <NUM> that receives an email message <NUM> from a client computer <NUM>. The client computer <NUM>'s user may suspect the email message <NUM> to contain malware. The email security system <NUM> may be used by an administrator to determine whether the email message <NUM> contains malware and appropriately handle the potential malware threat.

Email security system <NUM> includes artifact detector <NUM>, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, e.g. computer program logic, stored in a memory <NUM>, or other non-transitory computer readable medium, and executable by a processor <NUM>, such as the processor <NUM> and memory <NUM> described with respect to <FIG>, to cause the processor <NUM> to identify artifacts such as Internet links, attachments, headers, macros, executable code, etc. For example, the artifact detector <NUM> may be configured to scan the email message and identify artifacts based on programmed rules, e.g., that an Internet link begins with text "www". Or, the artifact detector <NUM> may be in communication with the email client that receives the email message <NUM> and receive information about attachments to the email message <NUM>.

As discussed herein, each artifact carries with it the potential to harm the resident computer. Each artifact may be actionable, accessible or executable by a user of the computer using, for example, a user input device. Generally, the user may be able to perform some act or event on the artifact, or interact with the artifact. For example, if the artifact is an Internet link, the user may be able to click on, or touch (depending on the user input device), the Internet link. If the artifact is an attachment (e.g., Microsoft Word® file), the user may be able to double-click on, or touch (again, depending on the user input device), the attachment. Upon interacting with the artifact, the artifact causes another act or event to occur. For example, interacting with an Internet link on a computer may cause the computer to open or access an Internet website in the computer's browser, or download content to the computer. Or, interacting with an attachment may cause the computer to open up the attachment in some other program. If the website that is opened, or the attachment that is opened, are or contain malware, the website or attachment may then download harmful files to the computer, or cause other undesirable actions to be automatically performed on the computer (such as, for example, sending information about the recipient's computer, such as an Internet protocol (IP) address, to another location without the recipient's knowledge, consent, or approval).

The result of interacting with the artifact may be termed a payload. Thus, each artifact is associated with a payload, which is a result of activating, accessing, executing and/or interacting with an artifact. If the artifact is an Internet link, the payload is the address of the resultant website that is opened via the computer's browser upon clicking on/touching the Internet link, or the resultant content which is downloaded to the computer upon interfacing with the link, such as an image or file. In one embodiment, the payload may cover any additional actions that are performed (e.g., automatic download of trackers or other harmful files, e.g., spyware) automatically upon opening the resultant website.

An attachment artifact may have a payload that is an executable file (i.e., ending in ". exe") for the recipient computer's operating system. Interacting with the attachment could execute the payload executable file. An attachment artifact may have a payload that contains a macro (e.g., a Word document with an embedded Visual Basic® macro, etc.).

The artifact detector <NUM> may be configured to generate a descriptor object <NUM> of each artifact, which is separate from the payload <NUM>. For example, the descriptor object could be the name or title of the Internet link or attachment as it appears in the email message. The descriptor object functions to identify and represent the artifact, but does not include the payload functionality and cannot be interacted with.

In one embodiment, the artifact detector <NUM> separates or divides an artifact into a payload and a descriptor object. The artifact detector <NUM> may also store the payload and the descriptor object in separate data structures in memory. The separate data structures are then accessed by the email security system <NUM> when the Artifact Dashboard is presented on the display, as discussed below.

When the descriptor object is displayed on a display unit e.g., via an Artifact Dashboard, described below, the descriptor object may appear to look similar to the corresponding artifact. A user, e.g., administrator, may view the descriptor object which appears just like the corresponding artifact, but is prevented from interacting with the descriptor object and causing the results thereof, i.e., cannot result in the payload.

Email security system <NUM> includes payload responder <NUM>, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, e.g. computer program logic, stored in a memory <NUM>, or other non-transitory computer readable medium, and executable by a processor <NUM>, such as the processor <NUM> and memory <NUM> described with respect to <FIG>, to cause the processor <NUM> to generate a payload button based on the payload.

The payload responder <NUM> is configurable by the administrator to perform an action on the payload. For example, the payload responder <NUM> may provide action/payload buttons that correspond to actions that the administrator can perform on the payload. For example, if the artifact is an Internet link, and its payload is a URL / address, the payload responder <NUM> may provide one button for each action that can be performed on the URL. The email security system may be programmed to provide one button that, upon being clicked, causes the URL to be opened in a sandbox environment, and another button that, upon being clicked, causes the URL to be transmitted to a tool that maintains a list of malware URLs and checks whether the payload URL appears on the tool's list. The administrator can interact with the buttons, but not the payload associated with the buttons. The administrator only needs to interact with the buttons generated by the payload responder <NUM>, but does not need to interact with the payload itself, thus insulating the administrator's computer from the effects of the artifact / payload.

The email security system <NUM> does not merely filter or quarantine artifacts, but instead detects artifacts, separates the payload so it is not actionable, an selectively transmits the actionable payload upon user selection of a payload button for that artifact.

Email security system <NUM> may also be in communication with display unit <NUM>. Email security system <NUM> combines information and visual elements from the descriptor object <NUM> and payload responder <NUM> to generate an Artifact Dashboard <NUM> that is presented on the display unit <NUM>. The Artifact Dashboard displays the descriptor objects <NUM> and payload responders <NUM> for each artifact.

Email security system <NUM> may also be in communication with tools / environments <NUM>, which may include sandbox environments, Internet link testing tools, and/or virtual machines. Upon a user interacting with a payload responder <NUM>, the email security system transmits the payload <NUM> to the tools / environment <NUM>.

<FIG> illustrates an example screenshot <NUM> of an Artifact Dashboard generated by the disclosed email security system. The Artifact Dashboard <NUM> is configured to have the same "look and feel" as the email client. The email security system, and the Artifact Dashboard presented by the email security system, may be accessible via a button on the email client. For example, the email security system may be accessible as a plug-in, which is software that adds a specific feature to an existing computer program, to the email client, which may be Microsoft Outlook®. The plug-in may be software code written in the programming language C Sharp or C#. For example, referring to <FIG> illustrates an example screenshot <NUM> of an email client toolbar, such as the Microsoft Outlook toolbar. The email security system may be termed as a Built-In Email Analysis and Response ("BEAR") tool. Toolbar <NUM> includes a plug-in button <NUM> which allows the administrator to easily access the email security system from within the email client. Clicking on the plug-in button <NUM> sends an email message to the email security system <NUM>, and presents an Artifact Dashboard for the email message.

An email client, such as Microsoft Outlook, is an application on the administrator's computer. Depending on the configuration of the application, an application may have access to and / or store files on the computer running the application. Thus, an email message that contains malware may be downloaded to, or stored in the memory of, the computer running the email client application. Some applications have access to a separate temporary memory, such as RAM (random access memory). Some applications reserve an amount of memory in the computer. An email client may accordingly use some of the memory allocated to that email client to temporarily store email message, including email messages such as email message <NUM>. In one embodiment, the email security system <NUM> prevents a payload associated with email message <NUM> from leaving the memory allocated the email client and being stored on the administrator's computer's general / disk memory while the administrator is examining / analyzing the email message <NUM>. For example, the email security system may stream (using temporary memory / buffers) a payload from the email server or the email client to the tools associated with the payload buttons, without actually storing the payload on the administrator computer's disk.

Referring back to <FIG>, the email security system presents the sender and the subject of the email via fields <NUM> and <NUM>, respectively, of the Artifact Dashboard <NUM>. The email security system parses the email message and automatically detects Internet links in the email message, and presents each link in field <NUM> of the Artifact Dashboard.

The email security system also provides payload buttons <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> that correspond to actions that the administrator can take on each Internet link listed in field <NUM>. A payload button may send the Internet link to a separate tool or website for analysis of the Internet link. Or, a payload button may perform some other act on the Internet link. The payload buttons associated with the Internet link field <NUM> may be configurable by the administrator. By providing all of the payload buttons adjacent to the Internet link, the Artifact Dashboard enables the administrator to easily act on the Internet link without having to separately open-up or access a variety of different tools to analyze the Internet link.

Payload button <NUM> transmits a URL to a dynamic analysis solution ThreatGuard® without storing the artifact on disk. For example, payload button <NUM> may cause the administrator computer to stream the artifact to the analysis solution as discussed above.

Payload button <NUM> copies a selected Internet link <NUM> to the computer's copy buffer without risking accidental compromise / activation of the selected Internet link <NUM>.

Payload button <NUM> sends the artifact to host analysis solution (Carbon Black®) for evidence of prior visits to the selected Internet link <NUM> by other computers on the administrator's network.

Payload button <NUM> sends the artifact to a tool that searches proxy logs for evidence of network traffic to the selected Internet link <NUM>.

Payload button <NUM> sends the artifact to a tool that searches proxy classifications of the base domain in the selected Internet link <NUM>.

Payload button <NUM> sends the artifact to a tool that searches a proxy classification for the full Internet link <NUM>, not just the base domain.

Payload button <NUM> sends the artifact to public resource "Virus Total" to determine if an Internet link has been determined by popular security vendors to be malicious.

Payload button <NUM> sends the artifact to public resource "urlquery. net" to "visit" the site and view its contents or redirects in a safe, trusted environment.

Notably, unlike the payload buttons, the Internet link field <NUM> which displays the Internet link is not actionable. Thus, text displayed in the Internet link field <NUM> may appear to be an Internet link, but an administrator cannot interact with the text in the same way as a typical Internet link. The Artifact Dashboard <NUM> insulates the administrator's computer from any possibility of actually activating or executing the link.

The email security system also parses the email message and automatically detects the header of the email message, and presents payload buttons <NUM> which allow the administrator to copy the email header to the administrator computer's copy buffer clipboard so the administrator can then paste it or use it in another application, or view the header, or toggle between a full header and a condensed header.

The email security system also parses through the email message and identifies any attachments to the email message and presents them to the administrator via field <NUM>. Similar to field <NUM>, field <NUM> is not an actionable field, and the administrator cannot actually open the attachments listed in field <NUM>. Thus, an administrator is prevented from interacting with attachments in the normal, expected way. Accordingly, the Artifact Dashboard increases the security with which the administrator can interface with or manipulate contents of the email message by removing the functionality associated with, or rendering inert, the Internet links in field <NUM> or the attachments in field <NUM>. The Artifact Dashboard <NUM> also displays or presents to the administrator payload buttons <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> adjacent to field <NUM>. Payload buttons <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> enable the administrator to perform actions on the attachments in field <NUM>.

Payload button <NUM> transmits an attachment to a dynamic analysis solution ThreatGuard® without storing the artifact on disk. For example, payload button <NUM> may cause the administrator computer to stream the artifact to the analysis solution as discussed above.

Payload button <NUM> searches a public resource "Virus Total" to determine if an attachment has been determined by popular security vendors to be malicious.

Payload button <NUM> sends the artifact to host analysis solution (Carbon Black®) for evidence of prior instances of receiving the attachment <NUM> by other computers on the administrator's network.

Payload button <NUM> sends a hash and name of the selected attachment to a third party intelligence site to determine if the selected attachment is malicious.

Payload button <NUM> copies a selected attachment <NUM> to the computer's copy buffer without risking accidental compromise / activation of the selected attachment <NUM>.

Payload button <NUM> copies a hash of the selected attachment to the computer's copy buffer in one of the formats currently in use so that the administrator can use the hash in another application if desired.

The Artifact Dashboard also presents action buttons <NUM>, <NUM>, <NUM>, <NUM> and <NUM> that enable the administrator to quickly perform actions to process the email message or to follow a defined security workflow. Action buttons increase the convenience with which an administrator can process an email, after analyzing its artifacts/payloads. The action buttons may be configurable, allowing the administrator to flexibly handle different email messages. Action button <NUM> allows the administrator to classify the status of the email messages. Other administrators may be able to see the status of an email message being handled by an administrator. Action button <NUM> allows the administrator to classify, or categorize, an email message, e.g., malware, safe, etc..

Action button <NUM> causes the administrator computer to send a templated email message responsive to the submitter of the email message <NUM>. The templated email response may be tailored based on category / risk level of the email message submitted by the user.

Action button <NUM> causes the administrator computer to send a templated email message to an Email Service team to remove malicious email messages from the network.

Action button <NUM> causes the administrator computer to send a templated warning email message to the submitter of the email message <NUM>. The action buttons may be contextually associated with actions that the administrator can perform for the email message being analyzed. The buttons that are presented on the Artifact Dashboard depend on the artifacts that are detected by the Artifact Detector <NUM>. The Artifact Dashboard may be dynamic to only provide the buttons necessary to handle the email message <NUM> being analyzed.

In one embodiment, the payload buttons may have two visual states: one state before the button has been pressed / interacted with by the administrator, and another state (e.g., a depressed button icon) that is displayed after the administrator presses / interacts with the button. Accordingly, the Artifact Dashboard provides visual cues to the administrator that a button has or has not been pressed, so the administrator can visually ascertain whether a tool / action has been used or performed for an artifact.

In one embodiment, the email security system may not allow the administrator to dispose of, or mark the email message analysis as complete (e.g., in an email ticketing system) until specified buttons have been pressed or used. In other words, the email security system may require certain, or all, of the buttons associated with an artifact to be pressed before the email message can be marked as handled or analyzed.

For example, some of the action buttons may be dependent on the values selected by the administrator for the status/class action buttons <NUM> and <NUM>. As shown in <FIG>, which illustrates another screenshot <NUM> of the Artifact Dashboard, upon setting the status button <NUM> to "Escalated" and the class button <NUM> to "Phishing/Malicious", the Artifact Dashboard <NUM> presents the option to select / interact with action button <NUM>, which allows the administrator to open a new incident in a ticket management system used by email security teams. In comparison, button <NUM> was not an option that the administrator could select in <FIG>.

In one embodiment, the Artifact Dashboard may present an option to cause the administrator computer to send selected artifacts to a monitoring appliance that can generate alerts upon detecting the selected artifact in other email messages. In an embodiment, the email security system may search a database of previously processed email messages, and may present to the administrator, e.g., via a window within the Artifact Dashboard, information about other related email messages that contained artifacts detected in the current email message <NUM>.

<FIG> illustrates an example streamlined workflow <NUM> enabled by the email security system that is more efficient and safer than the workflow <NUM>. Upon receiving an email message that is suspected to contain malware (step <NUM>), the administrator / user simply has to open the email security system, which reformats and decomposes the email message and present the email message in the Artifact Dashboard (step <NUM>). The administrator does not have to leave the email client, but instead simply clicks on a button that is integrated within the email client to activate the email security system which, in turn, presents information within the Artifact Dashboard.

From the Artifact Dashboard, the administrator can analyze a header via the built-in payload buttons (step <NUM>), analyze Internet links via built-in payload buttons (step <NUM>), or analyze attachments via built-in payload buttons (step <NUM>). Because the user does not actually interact with any of the artifacts within the email message, streamlined workflow <NUM> is much more secure than previous workflows.

The administrator's computer is not exposed to any of the artifacts that may contain malicious content, yet the administrator is able to see all of the artifacts and perform actions on the artifacts. After analyzing the various artifacts presented in the Artifact Dashboard, the administrator can categorize the email message and send a templated response (step <NUM>) to the original submitter of the email message.

<FIG> illustrates an example flowchart of an example computer implemented method <NUM>. Embodiments may involve all, more or fewer actions than the illustrated actions. The actions may be performed in the order or sequence shown, or in a different sequence. The actions may be performed simultaneously, or in a parallel or overlapping fashion. The method may be performed by processing logic that may comprise hardware (circuitry, dedicated logic, etc.), software, or a combination of both. In one example, the method is performed by the computer system <NUM> of <FIG>, while in some other examples, some or all of the method may be performed by another machine.

At step <NUM>, method <NUM> includes, in response to receiving an email message, detecting one or more artifacts within the email message, wherein each of the artifacts is associated with a payload. For example, if the method <NUM> is implemented by an email security system <NUM>, the email security system may detect artifacts within the email message.

At step <NUM>, method <NUM> includes, for each artifact, generating: a descriptor object representing the artifact that does not include the payload, so that the processor is prevented from accessing the payload via the descriptor object; and at least one payload button based on the payload associated with the artifact for causing the payload to be transmitted to an external system for analysis of the payload. For example, the email security system may include an artifact detector <NUM> that generates a descriptor object and a payload for each artifact.

At step <NUM>, method <NUM> includes presenting an artifact dashboard in a graphical user interface (GUI) rendered on a display of the email security system, the artifact dashboard displaying, for each artifact: the descriptor object representing the artifact and the at least one payload button based on the payload associated with the artifact. For example, the email security system may present an Artifact Dashboard <NUM> on a display of the email security system.

As is known in the art, email messages are typically routed through an email server before being delivered to a recipient's computer. In one embodiment, the email security system <NUM> may be implemented on an email server that automatically intercepts email messages directed to recipients. <FIG> illustrates an example process <NUM> for processing email messages by email security system <NUM> at an email server. An email server receives an email message <NUM> before the email message is delivered to the recipient. Thus, process <NUM> does not require a user to even suspect that an email message may contain malware and thereafter forward the suspected email message to an administrator, e.g., an administrator in the information security department of a company. All email messages that are addressed to the recipient are automatically intercepted by the email security system before the recipient can even receive the email messages. If the email security system does not detect an artifact in the email message <NUM>, the email security system <NUM> transmits <NUM> or otherwise releases the email message to the recipient client computer. However, if the email security system detects an artifact in the email message <NUM>, the email security system <NUM> generates the Artifact Dashboard and transmits <NUM> only the Artifact Dashboard, and not the email message, to an administrator computer. The email security system <NUM> waits until it receives authorization <NUM> to forward the email message to the recipient client computer. The administrator reviewing the Artifact Dashboard may investigate the artifacts / payloads in the email message as described above, and then provide a response (e.g., in the form of authorization to release the email message) to the email security system <NUM>. If the administrator reviewing the Artifact Dashboard authorizes the email message to be forwarded to the recipient <NUM>, the email security system <NUM> transmits <NUM> the email message to the recipient client computer. If the administrator reviewing the Artifact Dashboard does not authorize the email message to be forwarded to the recipient, the email security system <NUM> quarantines the email message <NUM>. In one embodiment, if the administrator reviewing the Artifact Dashboard does not authorize the email message to be forwarded to the recipient, the email security system <NUM> deletes the email message, thereby preventing unauthorized, unsafe email messages from ever reaching the recipient's computer system.

In one embodiment, if the email security system <NUM> does not receive authorization within a threshold amount of time, the email security system <NUM> quarantines the email message after the expiration of the threshold amount of time.

In one embodiment, the email security system at step <NUM> transmits the Artifact Dashboard to the intended recipient (i.e., the recipient listed in the To field of the email) instead of the administrator. If the recipient, upon analyzing the Artifact Dashboard, authorizes the email security system <NUM> to release the email message, the email security system releases the email message to the intended recipient.

While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Moreover, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings and described herein in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.

The Abstract of the Disclosure is provided with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.

Claim 1:
A computer implemented method of an email security system for processing email messages, the method comprising:
intercepting, by an email server, an email message directed to a recipient prior to delivery thereto;
in response to receiving an email message, detecting, by a processor of the email security system, one or more artifacts within the email message, wherein each of the artifacts is associated with a payload;
for each artifact, generating, by the processor:
a descriptor object representing the artifact that does not include the payload, so that the processor is prevented from accessing the payload via the descriptor object; and
at least one payload button based on the payload associated with the artifact for causing the payload to be transmitted to an external system for analysis of the payload; and
generating, by the processor of the email security system, an artifact dashboard and transmitting only the artifact dashboard to an administrator computer operated by an administrator;
presenting, by a processor of the administrator computer, the artifact dashboard in a graphical user interface (GUI) rendered on a display of the administrator computer, the artifact dashboard displaying, for each artifact, the descriptor object representing the artifact and the at least one payload button based on the payload associated with the artifact,
determining, by the processor of the administrator computer, whether each of the at least one payload button has been interacted with by the administrator via the GUI to cause the associated payload to be transmitted to the external system for analysis,
marking as complete a review of the email message only once it has been determined that the administrator has interacted with all of the at least one payload buttons;
determining, by the email security system, whether a response has been received from the administrator, to authorize or not authorize forwarding of the email message to the recipient;
transmitting the email message to the recipient upon receiving the response authorizing forwarding of the email message to the recipient;
not transmitting and quarantining or deleting the email message to the recipient upon receiving the response not authorizing forwarding of the email message to the recipient; and
wherein, if the email security system does not receive a response authorizing forwarding of the email message to the recipient with a threshold amount of time, quarantining the email message upon expiration thereof.