US 10,165,000 B1Grant
Systems and methods for malware attack prevention by intercepting flows of information
Issue Date:2018-12-25
•36 Claims
•8 Drawing Sheets
Abstract
Systems and methods for malware attack prevention are provided. The malware attack prevention system features a heuristic module, an analysis environment and an interception module. The heuristic module is configured to (i) receive incoming data from a particular source over a first communication path and (ii) analyze the incoming data to determine whether the incoming data is suspicious, where the suspicious incoming data represents a prescribed likelihood that the incoming data is associated with a malware attack. The analysis environment is configured to analyze the suspicious incoming data to identify whether the suspicious incoming data is associated with a malware attack. Lastly, the interception module is configured to redirect a subsequent flow of data from the particular source to the malware attack prevention system in response to determining, by at least the heuristic module, that the incoming data is suspicious.
Metadata
Assignee
- FireEye, Inc.
Inventors
- Ashar Aziz
- Wei-Lung Lai
- Jayaraman Manni
Application Information
Application Number:US 14/552,420
Filing Date:2014-11-24
Priority Date:0204-06-14
Art Unit:2433
Classifications
IPC:
G06F11/30H04L29/06
Field of Search:
H04L 63/145H04L 63/14H04L 63/1408
Patent Drawings (8 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent application Ser. No. 11/717,474, filed Mar. 12, 2017, entitled “Systems and Methods for Malware Attack Prevention”, now U.S. Pat. No. 8,898,788, which is a continuation-in-part of U.S. patent application Ser. No. 11/494,990, filed Jul. 28, 2006, entitled “Dynamic Signature Creation and Enforcement”, which is a continuation-in-part of U.S. patent application Ser. No. 11/471,072, filed Jun. 19, 2006, entitled “Virtual Machine with Dynamic Data Flow Analysis”, which is a continuation-in-part of U.S. patent application Ser. No. 11/409,355, filed Apr. 20, 2006, entitled “Heuristic Based Capture with Replay to Virtual Machine”, which claims benefit to U.S. patent application Ser. No. 11/096,287, filed Mar. 31, 2005, entitled “System and Method of Detecting Computer Worms,” U.S. patent application Ser. No. 11/151,812, filed Jun. 13, 2005, entitled “System and Method of Containing Computer Worms,” and U.S. patent application Ser. No. 11/152,286, Jun. 13, 2005, entitled “Computer Worm Defense System and Method” all of which are incorporated by reference herein.
[0002] U.S. patent application Ser. No. 11/096,287, filed Mar. 31, 2005, entitled “System and Method of Detecting Computer Worms,” claims benefit to provisional patent application No. 60/559,198, filed Apr. 1, 2004, entitled “System and Method of Detecting Computer Worms.” U.S. patent application Ser. No. 11/151,812, filed Jun. 13, 2005, entitled “System and Method of Containing Computer Worms,” claims benefit of provisional patent application No. 60/579,953, filed Jun. 14, 2004, entitled “System and Method of Containing Computer Worms.” U.S. patent application Ser. No. 11/152,286, filed Jun. 13, 2005, entitled “Computer Worm Defense System and Method,” claims benefit of provisional patent application No. 60/579,910, filed Jun. 14, 2004, entitled “Computer Worm Defense System and Method.” The above-referenced provisional patent applications are also incorporated by reference herein.
[0003] This application is also related to U.S. patent application Ser. No. 11/717,408, filed Mar. 12, 2007, entitled “Malware Containment and Security Analysis on Connection”, U.S. patent application Ser. No. 11/717,475, filed Mar. 12, 2007, entitled “Malware Containment on Connection”, and U.S. patent application Ser. No. 11/717,476, filed Mar. 12, 2007, entitled “Systems and Methods for Malware Attack Detection and Identification”. The above-referenced related nonprovisional patent applications are also incorporated by reference herein.
BACKGROUND OF THE INVENTION
Field of the Invention
[0004] The present invention relates generally to network security. More particularly, the present invention relates to malware attack prevention.
Background Art
[0005] Presently, malicious software (i.e., malware), can attack various devices via a network. For example, malware may include any program or file that is harmful to a computer user, such as computer viruses, worms, Trojan horses, spyware, or any programming that gathers information about a computer user without permission. Various processes and devices have been employed to prevent the problems that malware can cause.
[0006] For example, client devices often include malware scanning software that scans a particular client device for malware. The scanning may be performed based on a schedule specified by a user associated with the particular device, by a system administrator, and so forth. Unfortunately, by the time the malware is detected by the scanning software, some damage on the particular client device may have already occurred.
[0007] Another option for preventing malware is a honey pot. A honey pot is a computer system on the Internet that is expressly set up to attract and “trap” a user that attempts to penetrate other users' computer systems. The user can include a hacker, a cracker, or a script kiddy. The honey pot records the activities of the user invading the other users' computer systems. Disadvantageously, as the honey pot is being invaded, so too are other users' computer systems on the same network. Thus, other users' computer systems may be harmed while the honey pot determines the nature of the malware invading the honey pot's own computer system.
[0008] One disadvantage of the “honey pot” approach is the passive nature of the trap. Generally, honey pots comprise a static IP address. The user of the honey pot tries to attract attention to make the honey pot an attractive target to hackers, crackers, and script kiddies. The user of the honey pot will also reduce security on the machine as to allow attackers access so as to track the user's attack by recording the attack vector (i.e., vulnerability exploited to attack the honey pot) and the payload (i.e., damage caused by the attack.) Unfortunately, if the attack is aware of the honey pot, the honey pot can easily be avoided by simply not attacking the honey pot's IP address. Further, some attacks include scans for computers and open ports. A honey pot's existence and vulnerability to such a scanning attack may be lost in a list of other potential targets. As such, the honey pot may not be attacked, but rather other computers containing valuable data.
SUMMARY OF THE INVENTION
[0009] Systems and methods for malware attack prevention are provided. According to one method, network data is copied from a communication network. It is then determined if a possible malware attack is within the copied network data. The network data is intercepted based on the determination. The network data is then analyzed to identify a malware attack.
[0010] Intercepting the network data based on the determination can comprise identifying a source internet protocol address of the copied network data and intercepting the network data from the communication network transmitted from the source internet protocol address. Intercepting the network data based on the determination can also comprise identifying a target internet protocol address of the copied network data and intercepting the network data from the communication network transmitted to the target internet protocol address.
[0011] Analyzing the network data can comprise configuring a virtual machine to receive the network data and analyzing the response of the virtual machine to the network data to identify a malware attack. The method may further comprise generating an unauthorized activity signature based on the identification. Further, the method may also comprise storing the unauthorized activity signature and sending the unauthorized activity signature to another digital device.
[0012] Determining if a possible malware attack is within the copied network data can comprise analyzing the copied network data with a heuristic. Determining if a possible malware attack is within the copied network data can also comprise retrieving a virtual machine configured to receive the copied network data, configuring a replayer to transmit the copied network data to the virtual machine, and analyzing a response by the virtual machine to the copied network data to determine if the possible malware attack is within the copied network data. The copied network data may be transmitted between the replayer and the virtual machine over a virtual switch.
[0013] A malware attack prevention system can comprise a tap, a heuristic module, an interception module, and an analysis environment. The tap may be configured to copy network data from a communication network. The heuristic module may be configured to receive the copied network data from the tap and determine if a possible malware attack is within the copied network data. The interception module may be configured to intercept the network data based on the heuristic module determination. The analysis environment may be configured to analyze the network data to identify a malware attack.
[0014] A machine readable medium may have embodied thereon executable code, the executable code being executable by a processor for performing a method for malware prevention, the method comprising copying network data from a communication network, determining if a possible malware attack is within the copied network data, intercepting the network data based on the determination, and analyzing the network data to identify a malware attack.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] FIG. 1 is a diagram of a malware attack prevention environment in which embodiments of the present invention may be practiced.
[0016] FIG. 2 is a block diagram of an exemplary controller implementing embodiments of the present invention.
[0017] FIG. 3 is a block diagram of an exemplary analysis environment.
[0018] FIG. 4 is a flowchart of an exemplary method for malware attack prevention.
[0019] FIG. 5 is another flowchart of an exemplary method for malware attack prevention.
[0020] FIG. 6 is a flowchart of an exemplary method for transmitting a malware attack signature.
[0021] FIG. 7 is a block diagram of an exemplary controller in which embodiments of the present invention may be practiced.
DESCRIPTION OF EXEMPLARY EMBODIMENTS
[0022] Exemplary systems and methods for malware attack prevention are provided. A malware attack prevention system may include a dynamic honey pot. A dynamic honey pot can monitor network traffic to identify a malware attack. If a malware attack or a probable malware attack is identified, then the network data may be intercepted by the dynamic honey pot. The dynamic honey pot does not have to be directly attacked. Rather, the dynamic honey pot can detect possible malware attacks on other devices on the network and then intercept future network data to analyze the attack.
[0023] In exemplary embodiments, network data from a network may be copied and analyzed. If a malware attack or a possible malware attack is detected, related network data may be intercepted. The intercepted network data may continue to be analyzed. If the intercepted network data comprises a network attack, an unauthorized activity signature configured to identify the attack and/or attacker may be generated.
[0024] Malware is software created and distributed for malicious purposes and can take the form of viruses, worms, trojan horses or adware, for example. A virus is an intrusive program that infects a computer file by inserting a copy of itself in the file. The copy is usually executed when the file is loaded into memory, allowing the virus to infect other files. A worm is a program that propagates itself across multiple computers, usually by creating copies of itself in each computer's memory. A worm might duplicate itself in a computer so many times that it causes the computer to crash. A trojan horse is a destructive program disguised as a game, utility, or application. When run by a user or computer program, a trojan horse can harm the computer system while appearing to do something useful.
[0025] Malware may also include adware and spyware. Adware is a program configured to direct advertisements to a computer or a particular user. In one example, adware identifies the computer and/or the user to various websites visited by a browser on the computer. The website may then use the adware to either generate pop-up advertisements or otherwise direct specific advertisements to the user's browser. Spyware is a program configured to collect information regarding the user, the computer, and/or a user's network habits. In an example, spyware may collect information regarding the names and types of websites that the user browses and then transmit the information to another computer. Adware and spyware are often added to the user's computer after the user browses to a website that hosts the adware and/or spyware. The user is often unaware that these programs have been added and are similarly unaware of the adware and/or spyware's function.
[0026] FIG. 1 is a diagram of a malware attack prevention environment 100 in which embodiments of the present invention may be practiced. The malware prevention environment 100 comprises an infected device 105, a destination device 110, and a tap 115 each coupled to a communication network 120. The tap 115 is further coupled to a controller 125. Optionally, a router (not shown) may be provided for re-routing data from the communication network 120.
[0027] The infected device 105 and the destination device 110 are digital devices. Some examples of digital devices include computers, servers, laptops, personal digital assistants, and cellular telephones. The infected device 105 is configured to transmit network data over the communication network 120 to the destination device 110. The destination device is configured to receive the network data from the infected device 105. The infected device 105 may transmit malware or a malware attack to the destination device 110 via the communication network 120. The malware or malware attack may be transmitted unknowingly, such as when the infected device 105, itself, is infected with the malware or the malware attack may be transmitted knowingly, such as when a hacker utilizes the infected device 105 to perpetuate malware over the communication network 120.
[0028] The tap 115 is a digital data tap configured to monitor network data and provide a copy of the network data to the controller 125. In some embodiments, the tap 115 comprises a span port. The network data comprises signals and data that are transmitted over the communication network 120 including data flows from the infected device 105 to the destination device 110. As discussed herein, the network data may include malware and/or a malware attack transmitted from the infected device 105. In one example, the tap 115 copies the network data without an appreciable decline in performance of the infected device 105, the destination device 110, or the communication network 120. The tap 115 can copy any portion of the network data. For example, the tap 115 can receive and copy any number of data packets from the network data.
[0029] In some embodiments, the network data can be organized into one or more data flows and provided to the controller 125. In various embodiments, the tap 115 can sample the network data based on a sampling scheme. Data flows can then be reconstructed based on the network data samples.
[0030] The tap 115 can also capture metadata from the network data. The metadata can be associated with the infected device 105 and the destination device 110. The metadata can identify the infected device 105 and/or the destination device 110. In some embodiments, the infected device 105 transmits metadata, which is captured by the tap 115. In other embodiments, a heuristic module (described in association with FIG. 2 ) can determine the infected device 105 and the destination device 110 by analyzing data packets within the network data in order to generate the metadata.
[0031] The communication network 120 may comprise a public computer network such as the Internet, a private computer network such as a wireless telecommunication network, wide area network, or local area network.
[0032] Although FIG. 1 depicts data transmitted from the infected device 105 to the destination device 110, either device can transmit and receive data from the other. Similarly, although only two devices are depicted, any number of devices can send and/or receive data across the communication network 120. The tap 115 can monitor and copy data transmitted from multiple devices without appreciably effecting the performance of the communication network 120 or the devices coupled to the communication network 120.
[0033] The controller 125 includes any digital device or software configured to receive and analyze network data for the presence of malware. In exemplary embodiments, the controller 125 receives network data over the tap 115. If the controller 125 detects a malware attack in the network data, the controller 125 intercepts the associated network data. The associated network data can be network data from the same data flow as that which a malware attack was detected. Further, the associated network data can be network data sent from the same IP address as the device which sent the detected malware attack. The associated network data can also be network data sent to the same IP address as that device which was to receive the detected malware attack. When network data is intercepted, the network data is no longer received by the intended recipient but rather is received by the controller 125. In some embodiments, the associated network data is intercepted when network data is flagged as suspicious. The controller 125 is further discussed in FIG. 2 .
[0034] FIG. 2 is a block diagram of an exemplary controller 125 implementing embodiments. The controller 125 can be any digital device or software that receives network data. The controller 125 can comprise a heuristic module 205 discussed herein, a scheduler 210, a fingerprint module 215, a virtual machine pool 220, an analysis environment 225, a signature module 230, a policy engine 235, and an interceptor module 240. In some embodiments, the controller 125 comprises a tap which is further coupled to the communication network 120 (FIG. 1 ). In other embodiments, the controller 125 is coupled to an external tap or may be directly coupled to the communication network 120.
[0035] The interceptor module 240 may also be optionally coupled to the communication network 120 over a link. In some embodiments, network data directed to an IP address of the controller 125 is received over the link. The controller 125 can receive network data over the link and the tap in parallel (e.g., simultaneously.)
[0036] The heuristic module 205 receives the copy of the network data from the communication network 120 (FIG. 1 ). The heuristic module 205 applies heuristics and/or probability analysis to determine if the network data might contain suspicious activity. In one example, the heuristic module 205 flags network data as suspicious. The network data can then be buffered and organized into a data flow. The data flow is then provided to the scheduler 210. In some embodiments, the network data is provided directly to the scheduler 210 without buffering or organizing the data flow.
[0037] The heuristic module 205 can perform any heuristic and/or probability analysis. In one example, the heuristic module 205 performs a dark internet protocol (IP) heuristic. A dark IP heuristic can flag network data coming from a infected device 105 that has not previously been identified by the heuristic module 205. The dark IP heuristic can also flag network data going to an unassigned IP address. In an example, an attacker scans random IP addresses of a network to identify an active server or workstation. The dark IP heuristic can flag network data directed to an unassigned IP address.
[0038] The heuristic module 205 can also perform a dark port heuristic. A dark port heuristic can flag network data transmitted to an unassigned or unusual port address. Such network data transmitted to an unusual port can be indicative of a port scan by a worm or hacker. Further, the heuristic module 205 can flag network data from the infected device 105 (FIG. 1 ) that is significantly different than traditional data traffic transmitted by the infected device 105. For example, the heuristic module 205 can flag network data from a infected device 105 such as a laptop that begins to transmit network data that is common to a server.
[0039] The heuristic module 205 can retain data packets belonging to a particular data flow previously copied by the tap 115. In one example, the heuristic module 205 receives data packets from the tap 115 and stores the data packets within a buffer or other memory. Once the heuristic module 205 receives a predetermined number of data packets from a particular data flow, the heuristic module 205 performs the heuristics and/or probability analysis.
[0040] In some embodiments, the heuristic module 205 performs heuristic and/or probability analysis on a set of data packets belonging to a data flow and then stores the data packets within a buffer or other memory. The heuristic module 205 can then continue to receive new data packets belonging to the same data flow. Once a predetermined number of new data packets belonging to the same data flow are received, the heuristic and/or probability analysis can be performed upon the combination of buffered and new data packets to determine a likelihood of suspicious activity.
[0041] In some embodiments, an optional buffer receives the flagged network data from the heuristic module 205. The buffer can buffer and organize the flagged network data into one or more data flows before providing the one or more data flows to the scheduler 210. In various embodiments, the buffer can buffer network data and stall before providing the network data to the scheduler 210. In one example, the buffer stalls the network data to allow other components of the controller 125 time to complete functions or otherwise clear data congestion.
[0042] The scheduler 210 is a module that identifies the destination device 110 and retrieves a virtual machine associated with the destination device 110. A virtual machine may be software that is configured to mimic the performance of a device (e.g., the destination device 110). The virtual machine can be retrieved from the virtual machine pool 220.
[0043] In some embodiments, the heuristic module 205 transmits the metadata identifying the destination device 110 to the scheduler 210. In other embodiments, the scheduler 210 receives one or more data packets of the network data from the heuristic module 205 and analyzes the one or more data packets to identify the destination device 110. In yet other embodiments, the metadata can be received from the tap 115.
[0044] The scheduler 210 can retrieve and configure the virtual machine to mimic pertinent performance characteristics of the destination device 110. In one example, the scheduler 210 configures characteristics of the virtual machine to mimic only those features of the destination device 110 that are affected by the network data copied by the tap 115. The scheduler 210 can determine the features of the destination device 110 that are affected by the network data by receiving and analyzing the network data from the tap 115. Such features of the destination device 110 can include ports that are to receive the network data, select device drivers that are to respond to the network data and any other devices coupled to or contained within the destination device 110 that can respond to the network data. In other embodiments, the heuristic module 205 can determine the features of the destination device 110 that are affected by the network data by receiving and analyzing the network data from the tap 115. The heuristic module 205 can then transmit the features of the destination device to the scheduler 210.
[0045] The optional fingerprint module 215 is configured to determine the packet format of the network data to assist the scheduler 210 in the retrieval and/or configuration of the virtual machine. In one example, the fingerprint module 215 determines that the network data is based on a transmission control protocol/internet protocol (TCP/IP). Thereafter, the scheduler 210 will configure a virtual machine with the appropriate ports to receive TCP/IP packets. In another example, the fingerprint module 215 can configure a virtual machine with appropriate ports to receive user datagram protocol/internet protocol (UDP/IP) packets. The fingerprint module 215 can determine any type of packet format of the network data.
[0046] In other embodiments, the optional fingerprint module 215 passively determines a software profile of the network data to assist the scheduler 210 in the retrieval and/or configuration of the virtual machine. The software profile may comprise the operating system (e.g., Linux RH6.2) of the infected device 105 that generated the network data. The determination can be based on analysis of the protocol information of the network data. In an example, the optional fingerprint module 215 determines that the software profile of network data is Windows XP, SP1. The optional fingerprint module 215 can then configure a virtual machine with the appropriate ports and capabilities to receive the network data based on the software profile. In other examples, the optional fingerprint module 215 passes the software profile of the network data to the scheduler 210 and the scheduler 210 either selects or configures the virtual machine based on the profile.
[0047] The virtual machine pool 220 is configured to store virtual machines. The virtual machine pool 220 may include any storage capable of storing virtual machines. In one example, the virtual machine pool 220 stores a single virtual machine that can be configured by the scheduler 210 to mimic the performance of any destination device, such as the destination device 110 discussed in FIG. 1 , on the communication network 120. The virtual machine pool 220 can store any number of distinct virtual machines that can be configured to simulate the performance of any of the destination devices 110.
[0048] The analysis environment 225 is a module that simulates transmission of the network data between the infected device 105 and the destination device 110 to analyze the effects of the network data upon the destination device 110. The analysis environment 225 can identify the effects of malware or illegitimate computer users (e.g., a hacker, computer cracker, or other computer user) by analyzing the simulation of the effects of the network data upon the destination device 110 that is carried out on the virtual machine. There can be multiple analysis environments 225 to simulate multiple network data.
[0049] The analysis environment 225 simulates transmission of the network data between the infected device 105 (FIG. 1 ) and the destination device 110 to analyze the effects of the network data upon the destination device 110 to detect unauthorized activity. As the analysis environment 225 simulates the transmission of the network data, behavior of the virtual machine can be closely monitored for unauthorized activity. If the virtual machine crashes, performs illegal operations, performs abnormally, or allows access of data to an unauthorized computer user, the analysis environment 225 can react. In some embodiments, the analysis environment 225 performs dynamic taint analysis to identify unauthorized activity.
[0050] Once unauthorized activity is detected, the analysis environment 225 can generate the unauthorized activity signature configured to identify network data containing unauthorized activity. Since the unauthorized activity signature does not necessarily require probabilistic analysis to detect unauthorized activity within network data, unauthorized activity detection based on the unauthorized activity signature may be very fast and save computing time.
[0051] In various embodiments, the unauthorized activity signature may provide code that may be used to eliminate or “patch” portions of network data containing an attack. Further, in some embodiments, the unauthorized activity signature may be used to identify and eliminate (i.e., delete) the malware causing the attack. The unauthorized activity signature may also be used to configure digital devices to eliminate vulnerabilities (e.g., correct system settings such as disabling active-x controls in a browser or updating an operating system.)
[0052] The analysis environment 225 may store the unauthorized activity signature within the signature module 230. The analysis environment 225 may also transmit or command the transmission of the unauthorized activity signature to one or more other controllers 125, infected devices 105, destination devices 110, switches, and/or servers. By automatically storing and transmitting the unauthorized activity signature, known malware, previously unidentified malware, and the activities of illicit computer users can be quickly controlled and reduced before a computer system is damaged or compromised. The analysis environment 225 is further discussed with respect to FIG. 3 .
[0053] The signature module 230 receives, authenticates, and stores unauthorized activity signatures. The unauthorized activity signatures may be generated by the analysis environment 225 or another controller 125. The unauthorized activity signatures may then be transmitted to the signature module 230 of one or more controllers 125.
[0054] The policy engine 235 coupled to the heuristic module 205 and is a module that can identify network data as suspicious based upon policies contained within the policy engine 235. In one example, the destination device 110 can be a computer designed to attract hackers and/or worms (e.g., a “honey pot”). The policy engine 235 can contain a policy to flag any network data directed to the “honey pot” as suspicious since the “honey pot” should not be receiving any legitimate network data. In another example, the policy engine 235 can contain a policy to flag network data directed to any destination device 110 that contains highly sensitive or “mission critical” information.
[0055] The policy engine 235 can also dynamically apply a rule to copy all network data related to network data already flagged by the heuristic module 205. In one example, the heuristic module 205 flags a single packet of network data as suspicious. The policy engine 235 then applies a rule to flag all data related to the single packet (e.g., data flows) as suspicious. In some embodiments, the policy engine 235 flags network data related to suspicious network data until the analysis environment 225 determines that the network data flagged as suspicious is related to unauthorized activity.
[0056] The policy engine 235 may scan network data to detect unauthorized activity based upon an unauthorized activity signature. In some embodiments, the policy engine 235 retrieves the unauthorized activity signature from the signature module 230. The network data is then scanned for unauthorized activity based on the unauthorized activity signature.
[0057] The policy engine 235 can scan the header of a packet of network data as well as the packet contents for unauthorized activity. In some embodiments, the policy engine 235 scans only the header of the packet for unauthorized activity based on the unauthorized activity signature. If unauthorized activity is found, then no further scanning may be performed. In other embodiments, the policy engine 235 scans the packet contents for unauthorized activity.
[0058] Unauthorized activity may be found by scanning only the header of a packet, the contents of the packet, or both the header and the contents of the packet. As a result, unauthorized activity that might otherwise evade discovery can be detected. In one example, evidence of unauthorized activity may be located within the contents of the packet. By scanning only the contents of the packet, unauthorized activity may be detected.
[0059] If the packet contents or the packet header indicate that the network data contains unauthorized activity, then the policy engine 235, the heuristic module 205, or the signature module 230 may take action. In one example, the policy engine 235 may generate a rule or command the interceptor module 240 to intercept network data from the infected device 105 and delete or bar the packet from the communication network 120. The policy engine 235 and/or the interceptor module 240 may also quarantine, delete, or bar other packets belonging to the same data flow as the unauthorized activity packet.
[0060] Based on a determination that the network data is suspicious, the interceptor module 240 can re-route the associated network data to a virtual machine from the virtual machine pool 220. As discussed herein, the heuristic module 205 can provide information that the network data is suspicious. The interceptor module 240 can intercept all of the network data that is initially flagged by the heuristic module 205. In interceptor module can also base the interception of data on the detection of a malware attack by the analysis environment 225 or a policy or signature by the policy engine 235.
[0061] The interceptor module 240 can provide the intercepted data to the heuristic module 205 for analysis with a heuristic or to the analysis environment 225 to orchestrate the transmission of the intercepted data to detect a malware attack. If no malware attack is detected, the interceptor module 240 can transmit some or all of the intercepted data to the intended recipient (e.g., destination device 110.) If a malware attack is detected within the intercepted data, the unauthorized activity signature may be generated by the signature module 230 and transmitted to one or more controllers 125 or other digital devices.
[0062] The interceptor module 240 can redirect network data from the infected device 105 in any number of ways including, but not limited to, configuring a switch, Address Resolution Protocol (ARP) manipulation, or DHCP services.
[0063] The interceptor module 240 may send a request to a switch to redirect network data from any infected device 105 to the controller 125. The switch includes any device configured to receive and direct network data between one or more digital devices. Examples of a switch include, but is not limited to, a router, gateway, bridge, and, or server.
[0064] In some embodiments, executable code is loaded onto the switch. In one example, the executable code configures the switch to direct network data from any infected device 105 to the controller 125. In another example, the executable code allows the interceptor module 240 to transmit a request to the switch to direct network data from the infected device 105 to the controller 125. In some embodiments, the interceptor module 240 configures the router to intercept network data from the infected device 105 for a predetermined time. The predetermined time may be set by the interceptor module 240, preloaded into the switch, or configured by a user.
[0065] The interceptor module 240 may manipulate dynamic host configuration protocol (DHCP) services to intercept network data. As the infected device 105 transmits network data that is flagged as suspicious or otherwise identified as containing a malware attack. The interceptor module 240 may manipulate DHCP services to assign new IP addresses, associate the controller 125 MAC address with the IP address of the destination device 110, or otherwise redirect network data from the infected device 105 to the controller 125.
[0066] In various embodiments, the interceptor module 240 can manipulate the DHCP server to configure the infected device 105 with a gateway IP address which is the same as the controller's 125 IP address to send all network data to the controller 125. In other embodiments, the interceptor module 240 may perform DHCP services for the communication network 120 as a DHCP server.
[0067] In one example of ARP manipulation, the heuristic module 205 or the interceptor module 240 scans the copied network data flagged as suspicious to identify a source IP address and a target IP address. The source IP address is the IP address of the infected device 105. The target IP address is the IP address of the destination device 110. In some embodiments, the interceptor module 240 may send an ARP reply to the infected device 105. The ARP reply is configured to identify the MAC address of the controller 125 with the IP address of the destination device 110. When the infected device 105 receives the ARP reply, the infected device 105 may begin to send network data intended for the destination device to the controller 125.
[0068] In other embodiments, a policy within the policy engine may indicate which IP addresses are infected devices 105. Whenever an infected device 105 first sends network data to a destination device 110 that it has not sent network data to in the past, the infected device 105 may transmit an ARP request. The network data identifying the source IP address is copied by the tap 115 and the policy within the policy engine 235 can flag the source IP address as an infected device 105. Thereafter, the interceptor module 240 may store the ARP request, and provide the controller 125 MAC address in an ARP reply to the switch and/or the infected device 105. Once the switch and/or the infected device 105 receives the controller 125 MAC address in the ARP reply, the IP address of the digital device (e.g., destination device 110) will be associated with the controller 125 MAC address (e.g., in memory storage or cache). Network data intended for the destination device 110 may then be transmit from the infected device 105 to the controller 125.
[0069] The infected device 105 may send the network data to any number of digital devices. Before the attack can proceed, the infected device 105 may send a separate ARP request for the IP address of every other digital device the malware wishes to send data to. The controller 125 detects and responds to each ARP request by sending an ARP reply to each request with the controller 125 MAC address. The controller 125 MAC address may be associated with the IP address of the other digital devices on a table within the infected device 105, switch, and/or server (not depicted). The table may be within memory, storage, buffered, and/or cached. As a result, network data transmitted by the infected device 105 to multiple destination devices 110 may be intercepted by the controller 125.
[0070] Once the network data is intercepted, the network data is re-routed to the virtual machine, as discussed herein. Because the network data is re-routed, the actual machine or the destination device 110 for which the network data is intended may not receive the network data and is, as a result, unaffected. A plurality of the network data can be re-routed to more than one virtual machine at one time (e.g., in parallel.) Thus, if the network data intended for a plurality of the destination devices 110 is flagged as suspicious, or as coming from the infected device 105 that has previously been deemed suspicious, the interceptor module 240 can select a plurality of virtual machines on which to test the suspicious network data.
[0071] The policy engine 235 is coupled to the heuristic module 205 and can identify network data as unauthorized activity. The policy engine 235 may scan network data to detect unauthorized activity based upon an unauthorized activity signature. In some embodiments, the policy engine 235 retrieves the unauthorized activity signature from the signature module 230 (discussed herein). The network data is then scanned for unauthorized activity based on the unauthorized activity signature. The policy engine 235 can also flag network data as suspicious based on policies, as discussed herein.
[0072] The policy engine 235 can scan the header of a packet of network data as well as the packet contents for unauthorized activity. In some embodiments, the policy engine 235 scans only the header of the packet for unauthorized activity based on the unauthorized activity signature. If unauthorized activity is found, then no further scanning may be performed. In other embodiments, the policy engine 235 scans the packet contents for unauthorized activity. As discussed herein, in response to the identification of the unauthorized activity, the interceptor module 240 can re-route the network data that is the source of the unauthorized activity to the virtual machine to test the unauthorized activity utilizing the virtual machine as a dynamic honey pot.
[0073] Unauthorized activity may be found by scanning only the header of a packet, the contents of the packet, or both the header and the contents of the packet. As a result, unauthorized activity that might otherwise evade discovery can be detected. In one example, evidence of unauthorized activity may be located within the contents of the packet. By scanning only the contents of the packet, unauthorized activity may be detected.
[0074] If the packet contents or the packet header indicate that the network data contains unauthorized activity, then the policy engine 235, the heuristic module 205, or the signature module 230 may take action. In one example, the policy engine 235 may quarantine, delete, or bar the packet from the communications network. The policy engine 235 may also quarantine, delete, or bar other packets belonging to the same data flow as the unauthorized activity packet. Accordingly, the interceptor module 240 can then implement the quarantine, deletion, or barring of the packets by re-routing the packets away from the destination device 110 for which the packets are intended. Any type of action may be implemented by the interceptor module 240.
[0075] The signature module 230 receives, authenticates, and stores unauthorized activity signatures. The unauthorized activity signatures may be generated by the analysis environment 225 or another controller. The unauthorized activity signatures may then be transmitted to the signature module 230 of one or more controllers, such as the controller 125 discussed herein.
[0076] Although FIG. 2 depicts various modules comprising the controller 125, fewer or more modules can comprise the controller 125 and still fall within the scope of various embodiments.
[0077] FIG. 3 depicts an analysis environment 225, in accordance with one embodiment of the present invention. The analysis environment 225 comprises a replayer 305, a virtual switch 310, and a virtual machine 315. The replayer 305 is a module that receives network data that has been flagged by the heuristic module 205 and replays the network data in the analysis environment 225. In some embodiments, the replayer 305 mimics the behavior of the infected device 105 in transmitting the flagged network data. There can be any number of replayers 305 simulating the transmission of network data between the infected device 105 and the destination device 110. In a further embodiment, the replayer dynamically modifies session variables, as is appropriate, to emulate a “live” client or server of the protocol sequence being replayed. In one example, dynamic variables that may be dynamically substituted include dynamically assigned ports, transaction IDs, and any other variable that is dynamic to each protocol session. In other embodiments, the network data received from the heuristic module 205 is transmitted to the virtual machine 315 without a replayer 305.
[0078] In various embodiments, the controller 125 does not comprise a heuristic module 205 and the analysis environment 225 does not comprise a replayer 305. In one example, the copy of the network data received from the tap is received by the analysis environment which analyzes the response of the virtual machine to the copy of the network data to identify the malware attack.
[0079] The virtual switch 310 is a module that is capable of forwarding packets of flagged network data to the virtual machine 315. In one example, the replayer 305 simulates the transmission of the data flow by the infected device 105. The virtual switch 310 simulates the communication network 120 and the virtual machine 315 simulates the destination device 110. The virtual switch 310 can route the data packets of the data flow to the correct ports of the virtual machine 315.
[0080] The virtual machine 315 is a representation of the destination device 110 that can be provided to the analysis environment 225 by the scheduler 210. In one example, the scheduler 210 retrieves a virtual machine 315 from the virtual machine pool 220 and configures the virtual machine 315 to mimic the infected device 105. The configured virtual machine 315 is then provided to the analysis environment 225 where it can receive flagged network data from the virtual switch 310.
[0081] As the analysis environment 225 simulates the transmission of the network data, behavior of the virtual machine 315 can be closely monitored for unauthorized activity. If the virtual machine 315 crashes, performs illegal operations, performs abnormally, or allows access of data to an unauthorized computer user, the analysis environment 225 can react.
[0082] In some embodiments, the analysis environment 225 performs dynamic taint analysis to identify unauthorized activity. For a malware attack to change the execution of an otherwise legitimate program, the malware attack may cause a value that is normally derived from a trusted source to be derived from the user's own input. Program values (e.g., jump addresses and format strings) are traditionally supplied by a trusted program and not from external untrusted inputs. Malware, however, may attempt to exploit the program by overwriting these values.
[0083] In one example of dynamic taint analysis, all input data from untrusted or otherwise unknown sources are flagged. Program execution of programs with flagged input data is then monitored to track how the flagged data propagates (i.e., what other data becomes tainted) and to check when the flagged data is used in dangerous ways. For example, use of tainted data as jump addresses or format strings often indicates an exploit of a vulnerability such as a buffer overrun or format string vulnerability.
[0084] In some embodiments, the analysis environment 225 monitors and analyzes the behavior of the virtual machine 315 in order to determine a specific type of malware or the presence of an illicit computer user. The analysis environment 225 can also generate computer code configured to eliminate new viruses, worms, or other malware. In various embodiments, the analysis environment 225 can generate computer code configured to identify data within the network data indicative of a malware attack, repair damage performed by malware, or the illicit computer user. By simulating the transmission of suspicious network data and analyzing the response of the virtual machine, the analysis environment 225 can identify known and previously unidentified malware and the activities of illicit computer users before a computer system is damaged or compromised.
[0085] FIG. 4 is a flowchart of an exemplary method for malware attack prevention. At step 400, the network data is copied. As discussed herein, the network data from the infected device 105 may be copied by the tap 115. The network data is then sent from the tap 115 to the controller 125.
[0086] At step 405, it is determined whether the copied network data contains a possible malware attack. As discussed herein, the controller 125 utilizes various modules, such as the heuristic module 205 and the analysis environment 225 to determine whether the copied network data contains the possible malware attack or may otherwise be potentially harmful to the destination device 110 for which the copied network data is intended. The heuristic module 205 can flag the copied network data as suspicious. If the controller 125 does not identify the copied network data as possibly containing the malware attack, the network data continues to be transmitted to the destination device 110. New network data may then be copied in step 400.
[0087] In other embodiments, the policy engine 235 determines if the copy of the network data is suspicious. In one example, the policy engine 235 comprises a list of nonfunctional “dark” internet protocol (IP) addresses. A dark IP address is an unassigned IP address or an IP address that is not associated with the communication network 120. The policy engine 235 can determine the target IP address of the copy of the network data (e.g., by scanning the header within the network data). If the network data is transmitted to a dark IP address, the policy engine 235 can scan the network data to determine the IP address of the source of the network data and then generate a policy to watch network data from the source IP address.
[0088] If more network data is transmitted from the previously identified source IP address to one or more dark IP addresses, the policy engine 235 can flag the network data as suspicious and possibly contain a malware attack in step 405.
[0089] Any module of the controller 125 can also determine if the target IP address of the copy of the network data is directed towards a dark IP address. In one example, the heuristic module 205 retrieves the list of dark IP addresses from the policy engine 235 and determines if the copy of the network data is directed towards a dark IP address. In another example, the policy engine 235 comprises a list of active IP addresses and assumes (or the heuristic module 205 assumes) that any network data directed to an unidentified IP address is a dark IP address.
[0090] At step 410, the network data is intercepted. In some embodiments, network data is flagged as suspicious by the heuristic module 205. The interceptor module 240 may then intercept associated network data from the source IP address or receive network data transmitted to the destination device 110. In other embodiments, the network data is flagged as suspicious by the heuristic module 205 and then the transmission of the flagged network data is then orchestrated to a virtual machine to detect a malware attack in the analysis environment 225. If a malware attack is detected by the analysis environment 225, the interceptor module 240 may be directed to intercept the associated network data.
[0091] In some embodiments, the interceptor module 240 can notify a DHCP server to associate a given dark IP addresses (e.g., an unassigned IP address) to the controller 125. In one example, the DHCP server may comprise a list of unassigned IP addresses that may be assigned to the controller 125 as needed. The interceptor module 240 can assign the previously unassigned IP address to the controller 125.
[0092] In other embodiments, the interceptor module 240 can perform ARP manipulation or a proxy ARP to intercept network data. In one example, the interceptor module 240 can request that a router or DNS server forward network data to the controller 125 rather than the original destination device.
[0093] At step 415, the intercepted network data is analyzed to identify a malware attack within the network data. As discussed herein, the interceptor module 240 can intercept associated network data based on the determination that the copied network data is potentially dangerous to the destination device 110. Once the interceptor module 240 intercepts the network data that correlates with the copied network data, the network data can be forwarded to the analysis environment 225. The analysis environment 225 can test the intercepted network data by examining the response of the virtual machine to the intercepted network data.
[0094] If the test reveals that the network data is harmful or otherwise contains malware, the interceptor device 240 can quarantine the network data, delete the network data, and so forth. The interceptor device 240, or any other module associated with the controller 125, may send a notice to the destination device 110 informing the destination device 110 that corrupted data from the infected device 105 was sent to the destination device 110, according to some embodiments.
[0095] The interceptor device 240 can also clean the network data and send an uncorrupted version of the network data to the destination device. The interceptor device 240 can continue to intercept the network data from the infected device 105 that sent the network data containing the malware attack for a period of time, until a notice is received from the infected device 105 that the infected device 105 is no longer infected, until the interceptor device 240 determines that the network data from the infected device 105 is safe, and so on. Any type of determination of when to stop interception of the network data from the infected device 105 may be employed. According to some embodiments, the tap 115 implements a brief delay in the transmission of the network data being copied so the interceptor device 240 can intercept the network data determined by the controller 125 to be potentially harmful.
[0096] FIG. 5 is another flowchart of an exemplary method for malware attack prevention. At step 500, network data directed to a target IP address associated with the destination device 110 is copied. As discussed herein, the tap 115 or span port can copy the network data being transmitted via the communication network 120. The tap 115 can, according to some embodiments, copy only the network data intended for a particular set of IP addresses associated with a particular set of the destination devices 110. The copied network data is then analyzed based on a heuristic model associated with the heuristic module 205, at step 505.
[0097] Based on the heuristic model applied to the copied network data, a determination as to whether the network data contains a possible attack or corrupted data can be made at step 510. The determination may be made based on the heuristic model only or based on further analysis, as discussed herein. If the network data is not identified as possibly containing the attack, the network data continues to be transmitted to the IP address of the destination device 110.
[0098] However, if the network data is identified as possibly containing the attack, the network data is directed away from the destination device 110 (i.e., the target IP address). For example, as discussed herein, a router (not shown) may be configured to reroute network data from the infected device 105 to the controller 125. New network data may then be copied in step 500.
[0099] In various embodiments, network data from the infected device 105 is copied by the tap 115 and then received by the controller 125. If the controller 125 flags the network data as suspicious, the router (i.e., switch) may be configured to direct all data received from the infected device 105 (e.g., from the source IP address of the infected device 105) to the controller 125. As a result, all the network data from the infected device 105, and not only that which is transmitted to the destination device 110 may be intercepted.
[0100] At step 525, transmission of the network data is orchestrated to analyze the network data for unauthorized activity. As discussed herein, the virtual machine 315 that emulates or most closely emulates the destination device 110 for which the network data is intended is selected. The analysis environment 225 utilizes the intercepted network data to test the network data on the virtual machine 315. If the network data does not cause unauthorized activity on the virtual machine 315, the network data may be transmitted to the destination device 110. The signature module 230 can also assign a signature to the network data. If the network data does cause unauthorized activity on the virtual machine 315, the network data can be quarantined, deleted, cleaned, and so forth. The signature module 230 can assign a signature to the network data and the policy engine 235 can identify the IP address from the infected device 105 providing the network data as an infected, or otherwise potentially harmful, source.
[0101] In other embodiments, the controller 125 does not comprise a heuristic module 205. The analysis environment 225 can orchestrate the transmission of the network data by transmitting the copy of the network data to a virtual machine 315. The analysis environment 225 can then monitor the reaction of the virtual machine 315 to the copy of the network data to identify a malware attack. Upon the identification of a malware attack, the analysis environment 225 can direct the interceptor module 240 to intercept the network data going to the destination device 110 and/or transmitted from the infected device 105 associated with the source IP address of the network data containing the malware attack.
[0102] FIG. 6 is a flowchart of an exemplary method for transmitting a malware attack signature. At step 600, a virtual machine 315 is retrieved to mimic the destination device 110. As discussed herein, the virtual machine 315 is selected from the virtual machine pool 220. The virtual machine 315 is selected based on characteristics of the virtual machine 315 that most closely match characteristics associated with the destination device 110 for which the network data is intended to be transmitted.
[0103] At step 605, intercepted network data is transmitted to the virtual machine 315. The interceptor module 240 intercepts potentially harmful network data and transmits the intercepted network data to the virtual machine 315 for testing of the potentially harmful network data. According to alternative embodiments, the interceptor module 240 can intercept all of the network data being transmitted and test all of the network data before routing the network data to the destination device 110 for which the network data is intended.
[0104] In step 610, the analysis environment 225 analyzes the response of the virtual machine 315 to the network data to identify a malware attack. In one example, an optional replayer 305 is configured to perform similarly to the infected device 105 and transmit the network data over a virtual switch 310 to the virtual machine 315. In various embodiments, there may be any number of replayers 305 configured to transmit network data to different virtual machines 315 in parallel. Similarly, multiple analysis environments 225 may operate in parallel. The analysis environment 225 analyzes the response of the virtual machine 315 to the network data (e.g., with taint analysis).
[0105] If the network data does not contain unauthorized activity, then the method may end. If the network data contains unauthorized activity, then an unauthorized activity signature is generated based on the unauthorized activity in step 615. The unauthorized activity signature may be generated by the analysis environment 225 or the signature module 230.
[0106] In step 620, the unauthorized activity signature is transmitted to one or more other controllers 125 or any digital device (e.g., server or infected device 105). The receiving controller 125 can store the unauthorized activity signature within the receiving controller's signature module 230 or policy engine 235. The policy engine 235 may use the unauthorized activity signature to scan network data received by the controller 125 to flag the network data as suspicious or containing unauthorized activity without any further analysis (by either the heuristic module 205 or the analysis environment 225.)
[0107] Optionally the unauthorized activity signature may be authenticated. In some embodiments, the analysis environment 225 can generate an authentication code along with the unauthorized activity signature. The authentication code can then be scanned to determine that the unauthorized activity signature is verified. In one example, the analysis environment 225 generates the unauthorized activity signature and an authentication code. The analysis environment 225 transmits the unauthorized activity signature and the authentication code to another controller 125. The controller 125 verifies the authentication code to ensure that the unauthorized activity signature is genuine. If the unauthorized activity signature is authenticated, then the signature module 230 stores the unauthorized activity signature.
[0108] The unauthorized activity signature can also be encrypted. In one example, the controller 125 generates, encrypts, and transmits the unauthorized activity signature to another controller 125. The receiving controller 125 can decrypt the unauthorized activity signature and store the unauthorized activity signature within the signature module 230. In some embodiments, the controller 125 generates an authentication code and proceeds to encrypt the authentication code and the unauthorized activity signature prior to transmitting the authentication code and the unauthorized activity signature to another controller 125.
[0109] FIG. 7 is a block diagram of the controller 125 (FIG. 1 ), in accordance with one embodiment of the present invention. The controller 125 comprises a processor 700, a memory system 705, a storage system 710, an I/O interface 715, a communication network interface 720, and a display interface 725 which are all coupled to a system bus 730. The processor 700 is configured to execute executable instructions. In some embodiments, the processor 700 comprises circuitry or any one or more processors capable of processing the executable instructions.
[0110] The memory system 705 is any memory configured to store data. Some examples of the memory system 705 include storage devices, such as RAM or ROM.
[0111] The storage system 710 is any storage configured to retrieve and store data. Some examples of the storage system 710 are flash drives, hard drives, optical drives, and/or magnetic tape. The storage system 710 can comprise a database or other data structure configured to hold and organize data (e.g., network data, copies of network data, buffered data.) In some embodiments, the controller 125 includes memory 705 in the form of RAM and storage 710 in the form of flash data. The memory system 705 and/or the storage system 710 can comprise cache and buffers configured to retain network data or copies of network data.
[0112] The input/output (I/O) interface 715 is any device that can receive input and provide output to a user. The I/O interface 715 can be, but is not limited to, a keyboard, a mouse, a touchscreen, a keypad, a biosensor, or floppy disk drive.
[0113] The communication network interface 720 can be coupled to any user device via the link 735 through link 740. The communication network interface 720 may support communication over a USB connection, a firewire connection, an Ethernet connection, a serial connection, a parallel connection, or an ATA connection. The communication network interface 720 may also support wireless communication (e.g., 802.11a/b/g/n or wireless USB). It will be apparent to those skilled in the art that the communication network interface 720 can support many wired and wireless standards.
[0114] Although only two links (735 and 740) are depicted in FIG. 7 , there may be any number of links. In various embodiments, there may be one link 735 used by the tap 115 to transparently copy network data from the communication network 120. The other links may be used by the controller 125 (e.g., through the interceptor module 240) to intercept data from one or more infected devices 105 in parallel. In one example, the controller 125 comprises multiple IP addresses that may be broadcast from different links. Network data may be intercepted from different infected devices 105 by different links.
[0115] The display interface 725 is an interface configured to support a display, monitor, or screen. In some embodiments, the controller 125 comprises a graphical user interface to be displayed to a user over a monitor in order to allow the user to control the controller 125.
[0116] The above-described modules can be comprised of instructions that are stored on storage media. The instructions can be retrieved and executed by a processor (e.g., the processor 700). Some examples of instructions include software, program code, and firmware. Some examples of storage media comprise memory devices and integrated circuits. The instructions are operational when executed by the processor to direct the processor to operate in accordance with embodiments of the present invention. Those skilled in the art are familiar with instructions, processor(s), and storage media.
[0117] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. For example, any of the elements associated with the interceptor module 240 may employ any of the desired functionality set forth hereinabove. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments.
Claims
What is claimed is:
1. A malware attack prevention system to be communicatively coupled to a communication network, the malware attack prevention system comprising:
a policy engine, operating as a first component of a controller, to determine whether data or a copy of the data is suspicious, the policy engine to analyze the data or the copy of the data, determine that the data or the copy of the data is suspicious when the data or the copy of the data is directed to a targeted Internet Protocol (IP) address that is included in a predetermined set of unassigned IP addresses or IP addresses that are not associated with the communication network, determine a source of the data or the copy of the data, and generate a policy to monitor incoming data or a copy of the incoming data from the source;
a heuristic module, operating as a second component of the controller, to (i) receive the incoming data or the copy of the incoming data from the source over a first communication path and (ii) analyze the incoming data or the copy of the incoming data to determine whether the incoming data or the copy of the incoming data is suspicious, the suspicious incoming data or the copy of the suspicious incoming data represents a prescribed likelihood that the incoming data or the copy of the incoming data is associated with a malware attack; and
an analysis environment communicatively coupled to the heuristic module and operating as a third component of the controller, the analysis environment being configured to analyze the suspicious incoming data or the copy of the suspicious incoming data to identify whether the suspicious incoming data or the copy of the suspicious incoming data is associated with a malware attack by analyzing one or more behaviors of a virtual machine that is configured to operate as a device targeted to receive the incoming data or the copy of the incoming data from the source.
2. The malware attack prevention system of claim 1 further comprising an interceptor module configured to intercept the incoming data by at least identifying a source internet protocol address of the source and intercept the incoming data transmitted from the source internet protocol address.
3. The malware attack prevention system of claim 1, wherein the source is an infected device.
4. The malware attack prevention system of claim 1 further comprising an interceptor module to redirect a subsequent flow of data from the infected device to the malware attack prevention system by configuring a switch within a communication network that receives network data from the infected device to redirect the subsequent flow of data upon receipt from the infected device.
5. The malware attack prevention system of claim 1 further comprising an interceptor module to redirect a subsequent flow of data from the infected device to the malware attack prevention system by configuring a router within a communication network that receives network data from the infected device to redirect the subsequent flow of data upon receipt from the infected device.
6. The malware attack prevention system of claim 1 further comprising an interceptor module to redirect a subsequent flow of data from the infected device to the malware attack prevention system by altering a first Internet Protocol (IP) within a Dynamic Host Configuration Protocol (DHCP) server with a second IP address, the first IP address includes an address assigned to the infected device and the second IP address includes an address assigned to the malware attack prevention system.
7. The malware attack prevention system of claim 1 further comprising an interceptor module to redirect a subsequent flow of data from the infected device to the malware attack prevention system by controlling a Dynamic Host Configuration Protocol (DHCP) server to associate an address assigned to a destination device targeted to receive the subsequent flow of data with an address assigned to the malware attack prevention system.
8. The malware attack prevention system of claim 7, wherein the address assigned to the malware attack prevention system is a Media Access Control (MAC) address.
9. The malware attack prevention system of claim 1, wherein the signature module is separate from the analysis environment.
10. The malware attack prevention system of claim 1, wherein the signature module is further configured to:
store the signature; and
send the signature to another digital device.
11. The malware attack prevention system of claim 1, further comprising:
a signature module operating with the analysis environment to generate a signature in response to the suspicious incoming data or the copy of the suspicious incoming data being associated with the malware attack.
12. The malware attack prevention system of claim 1, further comprising:
an interceptor module configured to redirect a subsequent flow of data from the source to the malware attack prevention system in response to determining, by at least the heuristic module or the policy engine, that the incoming data or the copy of the incoming data is suspicious.
13. The malware attack prevention system of claim 12, wherein the interceptor module to route at least a portion of the suspicious incoming data or the copy of the suspicious incoming data to the device when no malware attack is detected.
14. The malware attack prevention system of claim 12, further comprising:
a signature module operating with the analysis module to generate a signature in response to the suspicious incoming data or the copy of the suspicious incoming data being associated with the malware attack.
15. A malware attack prevention system comprising:
a processor; and
a memory communicatively coupled to the processor, the memory comprises
a heuristic module, when executed by the processor, is configured to (i) receive incoming data from a source over a first communication path or a copy of the incoming data and (ii) analyze the incoming data or the copy of the incoming data to determine whether the incoming data or the copy of the incoming data is suspicious, the suspicious incoming data or the copy of the incoming data represents a prescribed likelihood that the incoming data or the copy of the incoming data is associated with a malware attack,
a policy engine operating with the heuristic module to determine whether data or a copy of the data is suspicious, the policy engine to analyze the data or the copy of the data, determine that the data or the copy of the data is suspicious when the data or the copy of the data is directed to a targeted internet protocol (IP) address that is included in a predetermined set of unassigned IP addresses or IP addresses that are not associated with a particular communication network, determine a source of the suspicious data or the copy of the suspicious data, and generate a policy to monitor the suspicious incoming data or the copy of the suspicious incoming data from the source;
an analysis module, when executed by the processor, is configured to analyze the suspicious incoming data or the copy of the suspicious incoming data to identify whether the suspicious incoming data or the copy of the suspicious incoming data is associated with a malware attack by analyzing one or more behaviors of a virtual machine that is configured to operate as a device targeted to receive the incoming data or the copy of the incoming data from the source.
16. The malware attack prevention system of claim 15, wherein the source is an infected device.
17. The malware attack prevention system of claim 16 further comprising an interceptor module, when executed by the processor, to intercept the incoming data or the copy of the incoming data by at least identifying a source internet protocol address of the source and intercept the incoming data or the copy of the incoming data transmitted from the source internet protocol address.
18. The malware attack prevention system of claim 16 further comprising an interceptor module, when executed by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by configuring a switch within a communication network that receives network data from the infected device to redirect the subsequent flow of data upon receipt from the infected device.
19. The malware attack prevention system of claim 16 further comprising an interceptor module, when executed by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by configuring a router within a communication network that receives network data from the infected device to redirect the subsequent flow of data upon receipt from the infected device.
20. The malware attack prevention system of claim 16 further comprising an interceptor module, when executed by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by altering a first Internet Protocol (IP) within a Dynamic Host Configuration Protocol (DHCP) server with a second IP address, the first IP address includes an address assigned to the infected device and the second IP address includes an address assigned to the malware attack prevention system.
21. The malware attack prevention system of claim 16 further comprising an interceptor module, when executed by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by controlling a Dynamic Host Configuration Protocol (DHCP) server to associate an address assigned to a destination device targeted to receive the subsequent flow of data with an address assigned to the malware attack prevention system.
22. The malware attack prevention system of claim 21, wherein the address assigned to the malware attack prevention system is a Media Access Control (MAC) address.
23. The malware attack prevention system of claim 16, wherein the signature module stored within the memory is separate from the analysis module.
24. The malware attack prevention system of claim 23, wherein the signature module is further configured to:
store the signature; and
send the signature to another digital device.
25. The malware attack prevention system of claim 15, further comprising:
an interceptor module, when executed by the processor, is configured to redirect a subsequent flow of data from the source to the malware attack prevention system in response to determining, by one or more of the heuristic module and the analysis module, that the incoming data is associated with a malware attack.
26. The malware attack prevention system of claim 25, wherein the interceptor module to route at least a portion of the suspicious incoming data or the copy of the suspicious incoming data to the device targeted to receive the incoming data or the copy of the incoming data when no malware attack is detected.
27. A malware attack prevention system to be communicatively coupled to a communication network, the malware attack prevention system comprising:
a processor; and
a data store operating as a memory system or a storage system, the data store comprises
a policy engine, executed by the processor, to determine whether data or a copy of the data is suspicious, the policy engine to analyze the data or the copy of the data, determine that the data or the copy of the data is suspicious when the data or the copy of the data is directed to a targeted Internet Protocol (IP) address that is included in a predetermined set of unassigned IP addresses or IP addresses that are not associated with the communication network, determine a source of the data or the copy of the data, and generate a policy to monitor incoming data from the source;
a heuristic module, executed by the processor, to (i) receive the incoming data from the source over a first communication path or a copy of the incoming data and (ii) analyze the incoming data or the copy of the incoming data to determine whether the incoming data is suspicious, the suspicious incoming data represents a prescribed likelihood that the incoming data is associated with a malware attack; and
a software module, executed by the processor, to analyze the suspicious incoming data to identify whether the suspicious incoming data is associated with a malware attack by analyzing one or more behaviors of a virtual machine that is configured to operate as a device targeted to receive the incoming data or a copy of the incoming data from the source.
28. The malware attack prevention system of claim 27 further comprising an interceptor module, upon execution by the processor, to intercept the incoming data by at least identifying a source internet protocol address of the source and intercept the incoming data transmitted from the source internet protocol address.
29. The malware attack prevention system of claim 27, wherein the source is an infected device.
30. The malware attack prevention system of claim 27 further comprising an interceptor module, upon execution by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by configuring a switch within a communication network that receives network data from the infected device to redirect the subsequent flow of data upon receipt from the infected device.
31. The malware attack prevention system of claim 27 further comprising an interceptor module, upon execution by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by configuring a router within a communication network that receives network data from the infected device to redirect the subsequent flow of data upon receipt from the infected device.
32. The malware attack prevention system of claim 27 further comprising an interceptor module, upon execution by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by altering a first Internet Protocol (IP) within a Dynamic Host Configuration Protocol (DHCP) server with a second IP address, the first IP address includes an address assigned to the infected device and the second IP address includes an address assigned to the malware attack prevention system.
33. The malware attack prevention system of claim 27 further comprising an interceptor module, upon execution by the processor, to redirect a subsequent flow of data from the infected device to the malware attack prevention system by controlling a Dynamic Host Configuration Protocol (DHCP) server to associate an address assigned to a destination device targeted to receive the subsequent flow of data with an address assigned to the malware attack prevention system.
34. The malware attack prevention system of claim 33, wherein the address assigned to the malware attack prevention system is a Media Access Control (MAC) address.
35. The malware attack prevention system of claim 27, wherein the signature module is separate from the analysis environment.
36. The malware attack prevention system of claim 27, wherein the signature module is further configured to:
store the signature; and
send the signature to another digital device.
Patent Citations (525)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4292580(A) | 1981-09-01 | Ott et al. | Applicant |
| US5175732(A) | 1992-12-01 | Hendel et al. | Applicant |
| US5440723(A) | 1995-08-01 | Arnold et al. | Applicant |
| US5490249(A) | 1996-02-01 | Miller | Applicant |
| US5657473(A) | 1997-08-01 | Killean et al. | Applicant |
| US5842002(A) | 1998-11-01 | Schnurer et al. | Applicant |
| US5978917(A) | 1999-11-01 | Chi | Applicant |
| US6088803(A) | 2000-07-01 | Tso et al. | Applicant |
| US6094677(A) | 2000-07-01 | Capek et al. | Applicant |
| US6108799(A) | 2000-08-01 | Boulay et al. | Applicant |
| US6269330(B1) | 2001-07-01 | Cidon et al. | Applicant |
| US6272641(B1) | 2001-08-01 | Ji | Applicant |
| US6279113(B1) | 2001-08-01 | Vaidya | Applicant |
| US6298445(B1) | 2001-10-01 | Shostack et al. | Applicant |
| US6357008(B1) | 2002-03-01 | Nachenberg | Applicant |
| US6424627(B1) | 2002-07-01 | Sørhaug et al. | Applicant |
| US6442696(B1) | 2002-08-01 | Wray et al. | Applicant |
| US6484315(B1) | 2002-11-01 | Ziese | Applicant |
| US6487666(B1) | 2002-11-01 | Shanklin et al. | Applicant |
| US6493756(B1) | 2002-12-01 | O'Brien et al. | Applicant |
| US6550012(B1) | 2003-04-01 | Villa et al. | Applicant |
| US6775657(B1) | 2004-08-01 | Baker | Applicant |
| US6831893(B1) | 2004-12-01 | Ben Nun et al. | Applicant |
| US6832367(B1) | 2004-12-01 | Choi et al. | Applicant |
| US6895550(B2) | 2005-05-01 | Kanchirayappa et al. | Applicant |
| US6898632(B2) | 2005-05-01 | Gordy et al. | Applicant |
| US6907396(B1) | 2005-06-01 | Muttik et al. | Applicant |
| US6941348(B2) | 2005-09-01 | Petry et al. | Applicant |
| US6971097(B1) | 2005-11-01 | Wallman | Applicant |
| US6981279(B1) | 2005-12-01 | Arnold et al. | Applicant |
| US7007107(B1) | 2006-02-01 | Ivchenko et al. | Applicant |
| US7028179(B2) | 2006-04-01 | Anderson et al. | Applicant |
| US7043757(B2) | 2006-05-01 | Hoefelmeyer et al. | Applicant |
| US7069316(B1) | 2006-06-01 | Gryaznov | Applicant |
| US7080407(B1) | 2006-07-01 | Zhao et al. | Applicant |
| US7080408(B1) | 2006-07-01 | Pak et al. | Applicant |
| US7093002(B2) | 2006-08-01 | Wolff et al. | Applicant |
| US7093239(B1) | 2006-08-01 | van der Made | Applicant |
| US7096498(B2) | 2006-08-01 | Judge | Applicant |
| US7100201(B2) | 2006-08-01 | Izatt | Applicant |
| US7107617(B2) | 2006-09-01 | Hursey et al. | Applicant |
| US7159149(B2) | 2007-01-01 | Spiegel et al. | Applicant |
| US7213260(B2) | 2007-05-01 | Judge | Applicant |
| US7231667(B2) | 2007-06-01 | Jordan | Applicant |
| US7240364(B1) | 2007-07-01 | Branscomb et al. | Applicant |
| US7240368(B1) | 2007-07-01 | Roesch et al. | Applicant |
| US7243371(B1) | 2007-07-01 | Kasper et al. | Applicant |
| US7249175(B1) | 2007-07-01 | Donaldson | Applicant |
| US7251215(B1) | 2007-07-01 | Turner et al. | Applicant |
| US7287278(B2) | 2007-10-01 | Liang | Applicant |
| US7308716(B2) | 2007-12-01 | Danford et al. | Applicant |
| US7328453(B2) | 2008-02-01 | Merkle, Jr. et al. | Applicant |
| US7346486(B2) | 2008-03-01 | Ivancic et al. | Applicant |
| US7356736(B2) | 2008-04-01 | Natvig | Applicant |
| US7386888(B2) | 2008-06-01 | Liang et al. | Applicant |
| US7392542(B2) | 2008-06-01 | Bucher | Applicant |
| US7418729(B2) | 2008-08-01 | Szor | Applicant |
| US7428300(B1) | 2008-09-01 | Drew et al. | Applicant |
| US7441272(B2) | 2008-10-01 | Durham et al. | Applicant |
| US7448084(B1) | 2008-11-01 | Apap et al. | Applicant |
| US7458098(B2) | 2008-11-01 | Judge et al. | Applicant |
| US7464404(B2) | 2008-12-01 | Carpenter et al. | Applicant |
| US7464407(B2) | 2008-12-01 | Nakae et al. | Applicant |
| US7467408(B1) | 2008-12-01 | O'Toole, Jr. | Applicant |
| US7478428(B1) | 2009-01-01 | Thomlinson | Applicant |
| US7480773(B1) | 2009-01-01 | Reed | Applicant |
| US7487543(B2) | 2009-02-01 | Arnold et al. | Applicant |
| US7496960(B1) | 2009-02-01 | Chen et al. | Applicant |
| US7496961(B2) | 2009-02-01 | Zimmer et al. | Applicant |
| US7519990(B1) | 2009-04-01 | Xie | Applicant |
| US7523493(B2) | 2009-04-01 | Liang et al. | Applicant |
| US7530104(B1) | 2009-05-01 | Thrower et al. | Applicant |
| US7540025(B2) | 2009-05-01 | Tzadikario | Applicant |
| US7546638(B2) | 2009-06-01 | Anderson et al. | Applicant |
| US7565550(B2) | 2009-07-01 | Liang et al. | Applicant |
| US7568233(B1) | 2009-07-01 | Szor et al. | Applicant |
| US7584455(B2) | 2009-09-01 | Ball | Applicant |
| US7603715(B2) | 2009-10-01 | Costa et al. | Applicant |
| US7607171(B1) | 2009-10-01 | Marsden et al. | Applicant |
| US7639714(B2) | 2009-12-01 | Stolfo et al. | Applicant |
| US7644441(B2) | 2010-01-01 | Schmid et al. | Applicant |
| US7657419(B2) | 2010-02-01 | van der Made | Applicant |
| US7676841(B2) | 2010-03-01 | Sobchuk et al. | Applicant |
| US7698548(B2) | 2010-04-01 | Shelest et al. | Applicant |
| US7707633(B2) | 2010-04-01 | Danford et al. | Applicant |
| US7712136(B2) | 2010-05-01 | Sprosts et al. | Applicant |
| US7730011(B1) | 2010-06-01 | Deninger et al. | Applicant |
| US7739740(B1) | 2010-06-01 | Nachenberg et al. | Applicant |
| US7779463(B2) | 2010-08-01 | Stolfo et al. | Applicant |
| US7784097(B1) | 2010-08-01 | Stolfo et al. | Applicant |
| US7832008(B1) | 2010-11-01 | Kraemer | Applicant |
| US7836502(B1) | 2010-11-01 | Zhao et al. | Applicant |
| US7849506(B1) | 2010-12-01 | Dansey et al. | Applicant |
| US7854007(B2) | 2010-12-01 | Sprosts et al. | Applicant |
| US7869073(B2) | 2011-01-01 | Oshima | Applicant |
| US7877803(B2) | 2011-01-01 | Enstone et al. | Applicant |
| US7904959(B2) | 2011-03-01 | Sidiroglou et al. | Applicant |
| US7908660(B2) | 2011-03-01 | Bahl | Applicant |
| US7930738(B1) | 2011-04-01 | Petersen | Applicant |
| US7937761(B1) | 2011-05-01 | Bennett | Applicant |
| US7949849(B2) | 2011-05-01 | Lowe et al. | Applicant |
| US7996556(B2) | 2011-08-01 | Raghavan et al. | Applicant |
| US7996836(B1) | 2011-08-01 | McCorkendale et al. | Applicant |
| US7996904(B1) | 2011-08-01 | Chiueh et al. | Applicant |
| US7996905(B2) | 2011-08-01 | Arnold et al. | Applicant |
| US8006305(B2) | 2011-08-01 | Aziz | Applicant |
| US8010667(B2) | 2011-08-01 | Zhang et al. | Applicant |
| US8020206(B2) | 2011-09-01 | Hubbard et al. | Applicant |
| US8028338(B1) | 2011-09-01 | Schneider et al. | Applicant |
| US8042184(B1) | 2011-10-01 | Batenin | Applicant |
| US8045094(B2) | 2011-10-01 | Teragawa | Applicant |
| US8045458(B2) | 2011-10-01 | Alperovitch et al. | Applicant |
| US8069484(B2) | 2011-11-01 | McMillan et al. | Applicant |
| US8087086(B1) | 2011-12-01 | Lai et al. | Applicant |
| US8171553(B2) | 2012-05-01 | Aziz et al. | Applicant |
| US8176049(B2) | 2012-05-01 | Deninger et al. | Applicant |
| US8176480(B1) | 2012-05-01 | Spertus | Applicant |
| US8204984(B1) | 2012-06-01 | Aziz et al. | Applicant |
| US8214905(B1) | 2012-07-01 | Doukhvalov et al. | Applicant |
| US8220055(B1) | 2012-07-01 | Kennedy | Applicant |
| US8225373(B2) | 2012-07-01 | Kraemer | Applicant |
| US8233882(B2) | 2012-07-01 | Rogel | Applicant |
| US8234640(B1) | 2012-07-01 | Fitzgerald et al. | Applicant |
| US8234709(B2) | 2012-07-01 | Viljoen et al. | Applicant |
| US8239944(B1) | 2012-08-01 | Nachenberg et al. | Applicant |
| US8260914(B1) | 2012-09-01 | Ranjan | Applicant |
| US8266091(B1) | 2012-09-01 | Gubin et al. | Applicant |
| US8286251(B2) | 2012-10-01 | Eker et al. | Applicant |
| US8291499(B2) | 2012-10-01 | Aziz et al. | Applicant |
| US8307435(B1) | 2012-11-01 | Mann et al. | Applicant |
| US8307443(B2) | 2012-11-01 | Wang et al. | Applicant |
| US8312545(B2) | 2012-11-01 | Tuvell et al. | Applicant |
| US8321936(B1) | 2012-11-01 | Green et al. | Applicant |
| US8321941(B2) | 2012-11-01 | Tuvell et al. | Applicant |
| US8332571(B1) | 2012-12-01 | Edwards, Sr. | Applicant |
| US8365286(B2) | 2013-01-01 | Poston | Applicant |
| US8365297(B1) | 2013-01-01 | Parshin et al. | Applicant |
| US8370938(B1) | 2013-02-01 | Daswani et al. | Applicant |
| US8370939(B2) | 2013-02-01 | Zaitsev et al. | Applicant |
| US8375444(B2) | 2013-02-01 | Aziz et al. | Applicant |
| US8381299(B2) | 2013-02-01 | Stolfo et al. | Applicant |
| US8402529(B1) | 2013-03-01 | Green et al. | Applicant |
| US8464340(B2) | 2013-06-01 | Ahn et al. | Applicant |
| US8479174(B2) | 2013-07-01 | Chiriac | Applicant |
| US8479276(B1) | 2013-07-01 | Vaystikh et al. | Applicant |
| US8479291(B1) | 2013-07-01 | Bodke | Applicant |
| US8510827(B1) | 2013-08-01 | Leake et al. | Applicant |
| US8510828(B1) | 2013-08-01 | Guo et al. | Applicant |
| US8510842(B2) | 2013-08-01 | Amit et al. | Applicant |
| US8516478(B1) | 2013-08-01 | Edwards et al. | Applicant |
| US8516590(B1) | 2013-08-01 | Ranadive et al. | Applicant |
| US8516593(B2) | 2013-08-01 | Aziz | Applicant |
| US8522348(B2) | 2013-08-01 | Chen et al. | Applicant |
| US8528086(B1) | 2013-09-01 | Aziz | Applicant |
| US8533824(B2) | 2013-09-01 | Hutton et al. | Applicant |
| US8539582(B1) | 2013-09-01 | Aziz et al. | Applicant |
| US8549638(B2) | 2013-10-01 | Aziz | Applicant |
| US8555391(B1) | 2013-10-01 | Demir et al. | Applicant |
| US8561177(B1) | 2013-10-01 | Aziz et al. | Applicant |
| US8566946(B1) | 2013-10-01 | Aziz et al. | Applicant |
| US8584094(B2) | 2013-11-01 | Dadhia et al. | Applicant |
| US8584234(B1) | 2013-11-01 | Sobel et al. | Applicant |
| US8584239(B2) | 2013-11-01 | Aziz et al. | Applicant |
| US8595834(B2) | 2013-11-01 | Xie et al. | Applicant |
| US8627476(B1) | 2014-01-01 | Satish et al. | Applicant |
| US8635696(B1) | 2014-01-01 | Aziz | Applicant |
| US8682054(B2) | 2014-03-01 | Xue et al. | Applicant |
| US8682812(B1) | 2014-03-01 | Ranjan | Applicant |
| US8689333(B2) | 2014-04-01 | Aziz | Applicant |
| US8695096(B1) | 2014-04-01 | Zhang | Applicant |
| US8713631(B1) | 2014-04-01 | Pavlyushchik | Applicant |
| US8713681(B2) | 2014-04-01 | Silberman et al. | Applicant |
| US8726392(B1) | 2014-05-01 | McCorkendale et al. | Applicant |
| US8739280(B2) | 2014-05-01 | Chess et al. | Applicant |
| US8776229(B1) | 2014-07-01 | Aziz | Applicant |
| US8782792(B1) | 2014-07-01 | Bodke | Applicant |
| US8789172(B2) | 2014-07-01 | Stolfo et al. | Applicant |
| US8789178(B2) | 2014-07-01 | Kejriwal et al. | Applicant |
| US8793787(B2) | 2014-07-01 | Ismael et al. | Applicant |
| US8805947(B1) | 2014-08-01 | Kuzkin et al. | Applicant |
| US8806647(B1) | 2014-08-01 | Daswani et al. | Applicant |
| US8832829(B2) | 2014-09-01 | Manni et al. | Applicant |
| US8850570(B1) | 2014-09-01 | Ramzan | Applicant |
| US8850571(B2) | 2014-09-01 | Staniford et al. | Applicant |
| US8881234(B2) | 2014-11-01 | Narasimhan et al. | Applicant |
| US8881282(B1) | 2014-11-01 | Aziz et al. | Applicant |
| US8898788(B1) | 2014-11-01 | Aziz et al. | Applicant |
| US8935779(B2) | 2015-01-01 | Manni et al. | Applicant |
| US8984638(B1) | 2015-03-01 | Aziz et al. | Applicant |
| US8990939(B2) | 2015-03-01 | Staniford et al. | Applicant |
| US8990944(B1) | 2015-03-01 | Singh et al. | Applicant |
| US8997219(B2) | 2015-03-01 | Staniford et al. | Applicant |
| US9009822(B1) | 2015-04-01 | Ismael et al. | Applicant |
| US9009823(B1) | 2015-04-01 | Ismael et al. | Applicant |
| US9027135(B1) | 2015-05-01 | Aziz | Applicant |
| US9071638(B1) | 2015-06-01 | Aziz et al. | Applicant |
| US9104867(B1) | 2015-08-01 | Thioux et al. | Applicant |
| US9106694(B2) | 2015-08-01 | Aziz et al. | Applicant |
| US9118715(B2) | 2015-08-01 | Staniford et al. | Applicant |
| US9159035(B1) | 2015-10-01 | Ismael et al. | Applicant |
| US9171160(B2) | 2015-10-01 | Vincent et al. | Applicant |
| US9176843(B1) | 2015-11-01 | Ismael et al. | Applicant |
| US9189627(B1) | 2015-11-01 | Islam | Applicant |
| US9195829(B1) | 2015-11-01 | Goradia et al. | Applicant |
| US9197664(B1) | 2015-11-01 | Aziz et al. | Applicant |
| US9223972(B1) | 2015-12-01 | Vincent et al. | Applicant |
| US9225740(B1) | 2015-12-01 | Ismael et al. | Applicant |
| US9241010(B1) | 2016-01-01 | Bennett et al. | Applicant |
| US9251343(B1) | 2016-02-01 | Vincent | Applicant |
| US9262635(B2) | 2016-02-01 | Paithane et al. | Applicant |
| US9282109(B1) | 2016-03-01 | Aziz et al. | Applicant |
| US9294501(B2) | 2016-03-01 | Mesdaq et al. | Applicant |
| US9300686(B2) | 2016-03-01 | Pidathala et al. | Applicant |
| US9306960(B1) | 2016-04-01 | Aziz | Applicant |
| US9306974(B1) | 2016-04-01 | Aziz et al. | Applicant |
| US9311479(B1) | 2016-04-01 | Manni et al. | Applicant |
| US2001/0005889(A1) | 2001-06-01 | Albrecht | Applicant |
| US2001/0047326(A1) | 2001-11-01 | Broadbent et al. | Applicant |
| US2002/0018903(A1) | 2002-02-01 | Kokubo et al. | Applicant |
| US2002/0038430(A1) | 2002-03-01 | Edwards et al. | Applicant |
| US2002/0091819(A1) | 2002-07-01 | Melchione et al. | Applicant |
| US2002/0095607(A1) | 2002-07-01 | Lin-Hendel | Applicant |
| US2002/0116627(A1) | 2002-08-01 | Tarbotton et al. | Applicant |
| US2002/0144156(A1) | 2002-10-01 | Copeland | Applicant |
| US2002/0162015(A1) | 2002-10-01 | Tang | Applicant |
| US2002/0166063(A1) | 2002-11-01 | Lachman et al. | Applicant |
| US2002/0169952(A1) | 2002-11-01 | DiSanto et al. | Applicant |
| US2002/0184528(A1) | 2002-12-01 | Shevenell | Examiner |
| US2002/0184533(A1) | 2002-12-01 | Fox | Examiner |
| US2002/0188887(A1) | 2002-12-01 | Largman et al. | Applicant |
| US2002/0194490(A1) | 2002-12-01 | Halperin et al. | Applicant |
| US2003/0021728(A1) | 2003-01-01 | Sharpe et al. | Applicant |
| US2003/0074578(A1) | 2003-04-01 | Ford et al. | Applicant |
| US2003/0084318(A1) | 2003-05-01 | Schertz | Applicant |
| US2003/0101381(A1) | 2003-05-01 | Mateev et al. | Applicant |
| US2003/0115483(A1) | 2003-06-01 | Liang | Applicant |
| US2003/0188190(A1) | 2003-10-01 | Aaron | Examiner |
| US2003/0191957(A1) | 2003-10-01 | Hypponen et al. | Applicant |
| US2003/0200460(A1) | 2003-10-01 | Morota et al. | Applicant |
| US2003/0212902(A1) | 2003-11-01 | van der Made | Applicant |
| US2003/0229801(A1) | 2003-12-01 | Kouznetsov et al. | Applicant |
| US2003/0237000(A1) | 2003-12-01 | Denton et al. | Applicant |
| US2004/0003323(A1) | 2004-01-01 | Bennett et al. | Applicant |
| US2004/0006473(A1) | 2004-01-01 | Mills et al. | Applicant |
| US2004/0015712(A1) | 2004-01-01 | Szor | Applicant |
| US2004/0019832(A1) | 2004-01-01 | Arnold et al. | Applicant |
| US2004/0047356(A1) | 2004-03-01 | Bauer | Applicant |
| US2004/0083408(A1) | 2004-04-01 | Spiegel et al. | Applicant |
| US2004/0088581(A1) | 2004-05-01 | Brawn et al. | Applicant |
| US2004/0093513(A1) | 2004-05-01 | Cantrell et al. | Applicant |
| US2004/0111531(A1) | 2004-06-01 | Staniford et al. | Applicant |
| US2004/0117478(A1) | 2004-06-01 | Triulzi et al. | Applicant |
| US2004/0117624(A1) | 2004-06-01 | Brandt et al. | Applicant |
| US2004/0128355(A1) | 2004-07-01 | Chao et al. | Applicant |
| US2004/0165588(A1) | 2004-08-01 | Pandya | Applicant |
| US2004/0236963(A1) | 2004-11-01 | Danford et al. | Applicant |
| US2004/0243349(A1) | 2004-12-01 | Greifeneder et al. | Applicant |
| US2004/0249911(A1) | 2004-12-01 | Alkhatib et al. | Applicant |
| US2004/0255161(A1) | 2004-12-01 | Cavanaugh | Applicant |
| US2004/0268147(A1) | 2004-12-01 | Wiederin et al. | Applicant |
| US2005/0005159(A1) | 2005-01-01 | Oliphant | Applicant |
| US2005/0021740(A1) | 2005-01-01 | Bar et al. | Applicant |
| US2005/0033960(A1) | 2005-02-01 | Vialen et al. | Applicant |
| US2005/0033989(A1) | 2005-02-01 | Poletto et al. | Applicant |
| US2005/0050148(A1) | 2005-03-01 | Mohammadioun et al. | Applicant |
| US2005/0060535(A1) | 2005-03-01 | Bartas | Examiner |
| US2005/0086499(A1) | 2005-04-01 | Hoefelmeyer | Examiner |
| US2005/0086523(A1) | 2005-04-01 | Zimmer et al. | Applicant |
| US2005/0091513(A1) | 2005-04-01 | Mitomo et al. | Applicant |
| US2005/0091533(A1) | 2005-04-01 | Omote et al. | Applicant |
| US2005/0091652(A1) | 2005-04-01 | Ross et al. | Applicant |
| US2005/0108562(A1) | 2005-05-01 | Khazan et al. | Applicant |
| US2005/0114663(A1) | 2005-05-01 | Cornell et al. | Applicant |
| US2005/0125195(A1) | 2005-06-01 | Brendel | Applicant |
| US2005/0149726(A1) | 2005-07-01 | Joshi et al. | Applicant |
| US2005/0157662(A1) | 2005-07-01 | Bingham et al. | Applicant |
| US2005/0183143(A1) | 2005-08-01 | Anderholm et al. | Applicant |
| US2005/0201297(A1) | 2005-09-01 | Peikari | Applicant |
| US2005/0210533(A1) | 2005-09-01 | Copeland et al. | Applicant |
| US2005/0238005(A1) | 2005-10-01 | Chen et al. | Applicant |
| US2005/0240781(A1) | 2005-10-01 | Gassoway | Applicant |
| US2005/0262562(A1) | 2005-11-01 | Gassoway | Applicant |
| US2005/0265331(A1) | 2005-12-01 | Stolfo | Applicant |
| US2005/0283839(A1) | 2005-12-01 | Cowburn | Applicant |
| US2006/0010495(A1) | 2006-01-01 | Cohen et al. | Applicant |
| US2006/0015416(A1) | 2006-01-01 | Hoffman et al. | Applicant |
| US2006/0015715(A1) | 2006-01-01 | Anderson | Applicant |
| US2006/0015747(A1) | 2006-01-01 | Van de Ven | Applicant |
| US2006/0021029(A1) | 2006-01-01 | Brickell et al. | Applicant |
| US2006/0021054(A1) | 2006-01-01 | Costa et al. | Applicant |
| US2006/0031476(A1) | 2006-02-01 | Mathes et al. | Applicant |
| US2006/0047665(A1) | 2006-03-01 | Neil | Applicant |
| US2006/0070130(A1) | 2006-03-01 | Costea et al. | Applicant |
| US2006/0075496(A1) | 2006-04-01 | Carpenter et al. | Applicant |
| US2006/0095968(A1) | 2006-05-01 | Portolani et al. | Applicant |
| US2006/0101516(A1) | 2006-05-01 | Sudaharan et al. | Applicant |
| US2006/0101517(A1) | 2006-05-01 | Banzhof et al. | Applicant |
| US2006/0117385(A1) | 2006-06-01 | Mester et al. | Applicant |
| US2006/0123477(A1) | 2006-06-01 | Raghavan et al. | Applicant |
| US2006/0143709(A1) | 2006-06-01 | Brooks et al. | Applicant |
| US2006/0150249(A1) | 2006-07-01 | Gassen | Examiner |
| US2006/0161983(A1) | 2006-07-01 | Cothrell et al. | Applicant |
| US2006/0161987(A1) | 2006-07-01 | Levy-Yurista | Applicant |
| US2006/0161989(A1) | 2006-07-01 | Reshef et al. | Applicant |
| US2006/0164199(A1) | 2006-07-01 | Gilde et al. | Applicant |
| US2006/0173992(A1) | 2006-08-01 | Weber | Applicant |
| US2006/0179147(A1) | 2006-08-01 | Tran et al. | Applicant |
| US2006/0184632(A1) | 2006-08-01 | Marino et al. | Applicant |
| US2006/0191010(A1) | 2006-08-01 | Benjamin | Applicant |
| US2006/0221956(A1) | 2006-10-01 | Narayan et al. | Applicant |
| US2006/0236393(A1) | 2006-10-01 | Kramer et al. | Applicant |
| US2006/0242709(A1) | 2006-10-01 | Seinfeld et al. | Applicant |
| US2006/0248519(A1) | 2006-11-01 | Jaeger et al. | Applicant |
| US2006/0248582(A1) | 2006-11-01 | Panjwani et al. | Applicant |
| US2006/0251104(A1) | 2006-11-01 | Koga | Applicant |
| US2006/0288417(A1) | 2006-12-01 | Bookbinder et al. | Applicant |
| US2007/0006288(A1) | 2007-01-01 | Mayfield et al. | Applicant |
| US2007/0006313(A1) | 2007-01-01 | Porras et al. | Applicant |
| US2007/0011174(A1) | 2007-01-01 | Takaragi et al. | Applicant |
| US2007/0016951(A1) | 2007-01-01 | Piccard et al. | Applicant |
| US2007/0019286(A1) | 2007-01-01 | Kikuchi | Applicant |
| US2007/0033645(A1) | 2007-02-01 | Jones | Applicant |
| US2007/0038943(A1) | 2007-02-01 | FitzGerald et al. | Applicant |
| US2007/0064689(A1) | 2007-03-01 | Shin et al. | Applicant |
| US2007/0074169(A1) | 2007-03-01 | Chess et al. | Applicant |
| US2007/0094730(A1) | 2007-04-01 | Bhikkaji et al. | Applicant |
| US2007/0101435(A1) | 2007-05-01 | Konanka et al. | Applicant |
| US2007/0128855(A1) | 2007-06-01 | Cho et al. | Applicant |
| US2007/0142030(A1) | 2007-06-01 | Sinha et al. | Applicant |
| US2007/0143827(A1) | 2007-06-01 | Nicodemus et al. | Applicant |
| US2007/0156895(A1) | 2007-07-01 | Vuong | Applicant |
| US2007/0157180(A1) | 2007-07-01 | Tillmann et al. | Applicant |
| US2007/0157306(A1) | 2007-07-01 | Elrod et al. | Applicant |
| US2007/0168988(A1) | 2007-07-01 | Eisner et al. | Applicant |
| US2007/0171824(A1) | 2007-07-01 | Ruello et al. | Applicant |
| US2007/0174915(A1) | 2007-07-01 | Gribble et al. | Applicant |
| US2007/0192500(A1) | 2007-08-01 | Lum | Applicant |
| US2007/0192858(A1) | 2007-08-01 | Lum | Applicant |
| US2007/0198275(A1) | 2007-08-01 | Malden et al. | Applicant |
| US2007/0208822(A1) | 2007-09-01 | Wang et al. | Applicant |
| US2007/0220607(A1) | 2007-09-01 | Sprosts et al. | Applicant |
| US2007/0240218(A1) | 2007-10-01 | Tuvell et al. | Applicant |
| US2007/0240219(A1) | 2007-10-01 | Tuvell et al. | Applicant |
| US2007/0240220(A1) | 2007-10-01 | Tuvell et al. | Applicant |
| US2007/0240222(A1) | 2007-10-01 | Tuvell et al. | Applicant |
| US2007/0250930(A1) | 2007-10-01 | Aziz et al. | Applicant |
| US2007/0256132(A2) | 2007-11-01 | Oliphant | Applicant |
| US2007/0271446(A1) | 2007-11-01 | Nakamura | Applicant |
| US2008/0005782(A1) | 2008-01-01 | Aziz | Applicant |
| US2008/0018122(A1) | 2008-01-01 | Zierler et al. | Applicant |
| US2008/0028463(A1) | 2008-01-01 | Dagon et al. | Applicant |
| US2008/0040710(A1) | 2008-02-01 | Chiriac | Applicant |
| US2008/0046781(A1) | 2008-02-01 | Childs et al. | Applicant |
| US2008/0066179(A1) | 2008-03-01 | Liu | Applicant |
| US2008/0072326(A1) | 2008-03-01 | Danford et al. | Applicant |
| US2008/0077793(A1) | 2008-03-01 | Tan et al. | Applicant |
| US2008/0080518(A1) | 2008-04-01 | Hoeflin et al. | Applicant |
| US2008/0086720(A1) | 2008-04-01 | Lekel | Applicant |
| US2008/0098476(A1) | 2008-04-01 | Syversen | Applicant |
| US2008/0120722(A1) | 2008-05-01 | Sima et al. | Applicant |
| US2008/0134178(A1) | 2008-06-01 | Fitzgerald et al. | Applicant |
| US2008/0134334(A1) | 2008-06-01 | Kim et al. | Applicant |
| US2008/0141376(A1) | 2008-06-01 | Clausen et al. | Applicant |
| US2008/0184373(A1) | 2008-07-01 | Traut et al. | Applicant |
| US2008/0189787(A1) | 2008-08-01 | Arnold et al. | Applicant |
| US2008/0201778(A1) | 2008-08-01 | Guo et al. | Applicant |
| US2008/0209557(A1) | 2008-08-01 | Herley et al. | Applicant |
| US2008/0215742(A1) | 2008-09-01 | Goldszmidt et al. | Applicant |
| US2008/0222729(A1) | 2008-09-01 | Chen et al. | Applicant |
| US2008/0263665(A1) | 2008-10-01 | Ma et al. | Applicant |
| US2008/0295172(A1) | 2008-11-01 | Bohacek | Applicant |
| US2008/0301810(A1) | 2008-12-01 | Lehane et al. | Applicant |
| US2008/0307524(A1) | 2008-12-01 | Singh et al. | Applicant |
| US2008/0313738(A1) | 2008-12-01 | Enderby | Applicant |
| US2008/0320594(A1) | 2008-12-01 | Jiang | Applicant |
| US2009/0003317(A1) | 2009-01-01 | Kasralikar et al. | Applicant |
| US2009/0007100(A1) | 2009-01-01 | Field et al. | Applicant |
| US2009/0013408(A1) | 2009-01-01 | Schipka | Applicant |
| US2009/0031423(A1) | 2009-01-01 | Liu et al. | Applicant |
| US2009/0036111(A1) | 2009-02-01 | Danford et al. | Applicant |
| US2009/0037835(A1) | 2009-02-01 | Goldman | Applicant |
| US2009/0044024(A1) | 2009-02-01 | Oberheide et al. | Applicant |
| US2009/0044274(A1) | 2009-02-01 | Budko et al. | Applicant |
| US2009/0064332(A1) | 2009-03-01 | Porras et al. | Applicant |
| US2009/0077666(A1) | 2009-03-01 | Chen et al. | Applicant |
| US2009/0083369(A1) | 2009-03-01 | Marmor | Applicant |
| US2009/0083855(A1) | 2009-03-01 | Apap et al. | Applicant |
| US2009/0089879(A1) | 2009-04-01 | Wang et al. | Applicant |
| US2009/0094697(A1) | 2009-04-01 | Provos et al. | Applicant |
| US2009/0113425(A1) | 2009-04-01 | Ports et al. | Applicant |
| US2009/0125976(A1) | 2009-05-01 | Wassermann et al. | Applicant |
| US2009/0126015(A1) | 2009-05-01 | Monastyrsky et al. | Applicant |
| US2009/0126016(A1) | 2009-05-01 | Sobko et al. | Applicant |
| US2009/0133125(A1) | 2009-05-01 | Choi et al. | Applicant |
| US2009/0144823(A1) | 2009-06-01 | Lamastra et al. | Applicant |
| US2009/0158430(A1) | 2009-06-01 | Borders | Applicant |
| US2009/0172815(A1) | 2009-07-01 | Gu et al. | Applicant |
| US2009/0187992(A1) | 2009-07-01 | Poston | Applicant |
| US2009/0193293(A1) | 2009-07-01 | Stolfo et al. | Applicant |
| US2009/0199296(A1) | 2009-08-01 | Xie et al. | Applicant |
| US2009/0228233(A1) | 2009-09-01 | Anderson et al. | Applicant |
| US2009/0241187(A1) | 2009-09-01 | Troyansky | Applicant |
| US2009/0241190(A1) | 2009-09-01 | Todd et al. | Applicant |
| US2009/0265692(A1) | 2009-10-01 | Godefroid et al. | Applicant |
| US2009/0271867(A1) | 2009-10-01 | Zhang | Applicant |
| US2009/0300415(A1) | 2009-12-01 | Zhang et al. | Applicant |
| US2009/0300761(A1) | 2009-12-01 | Park et al. | Applicant |
| US2009/0328185(A1) | 2009-12-01 | Berg et al. | Applicant |
| US2009/0328221(A1) | 2009-12-01 | Blumfield et al. | Applicant |
| US2010/0005146(A1) | 2010-01-01 | Drako et al. | Applicant |
| US2010/0011205(A1) | 2010-01-01 | McKenna | Applicant |
| US2010/0017546(A1) | 2010-01-01 | Poo et al. | Applicant |
| US2010/0031353(A1) | 2010-02-01 | Thomas et al. | Applicant |
| US2010/0037314(A1) | 2010-02-01 | Perdisci et al. | Applicant |
| US2010/0054278(A1) | 2010-03-01 | Stolfo et al. | Applicant |
| US2010/0077481(A1) | 2010-03-01 | Polyakov et al. | Applicant |
| US2010/0083376(A1) | 2010-04-01 | Pereira et al. | Applicant |
| US2010/0115621(A1) | 2010-05-01 | Staniford et al. | Applicant |
| US2010/0180344(A1) | 2010-07-01 | Malyshev et al. | Applicant |
| US2010/0192223(A1) | 2010-07-01 | Ismael et al. | Applicant |
| US2010/0220863(A1) | 2010-09-01 | Dupaquis et al. | Applicant |
| US2010/0235831(A1) | 2010-09-01 | Dittmer | Applicant |
| US2010/0251104(A1) | 2010-09-01 | Massand | Applicant |
| US2010/0281102(A1) | 2010-11-01 | Chinta et al. | Applicant |
| US2010/0281541(A1) | 2010-11-01 | Stolfo et al. | Applicant |
| US2010/0281542(A1) | 2010-11-01 | Stolfo et al. | Applicant |
| US2010/0287260(A1) | 2010-11-01 | Peterson et al. | Applicant |
| US2010/0299754(A1) | 2010-11-01 | Amit et al. | Applicant |
| US2010/0306173(A1) | 2010-12-01 | Frank | Applicant |
| US2011/0004737(A1) | 2011-01-01 | Greenebaum | Applicant |
| US2011/0047620(A1) | 2011-02-01 | Mahaffey et al. | Applicant |
| US2011/0055907(A1) | 2011-03-01 | Narasimhan et al. | Applicant |
| US2011/0078794(A1) | 2011-03-01 | Manni et al. | Applicant |
| US2011/0093951(A1) | 2011-04-01 | Aziz | Applicant |
| US2011/0099620(A1) | 2011-04-01 | Stavrou et al. | Applicant |
| US2011/0099633(A1) | 2011-04-01 | Aziz | Applicant |
| US2011/0113231(A1) | 2011-05-01 | Kaminsky | Applicant |
| US2011/0145918(A1) | 2011-06-01 | Jung et al. | Applicant |
| US2011/0145920(A1) | 2011-06-01 | Mahaffey et al. | Applicant |
| US2011/0145934(A1) | 2011-06-01 | Abramovici et al. | Applicant |
| US2011/0167493(A1) | 2011-07-01 | Song et al. | Applicant |
| US2011/0167494(A1) | 2011-07-01 | Bowen et al. | Applicant |
| US2011/0173460(A1) | 2011-07-01 | Ito et al. | Applicant |
| US2011/0219449(A1) | 2011-09-01 | St. Neitzel et al. | Applicant |
| US2011/0219450(A1) | 2011-09-01 | McDougal et al. | Applicant |
| US2011/0225624(A1) | 2011-09-01 | Sawhney et al. | Applicant |
| US2011/0225655(A1) | 2011-09-01 | Niemela et al. | Applicant |
| US2011/0247072(A1) | 2011-10-01 | Staniford et al. | Applicant |
| US2011/0265182(A1) | 2011-10-01 | Peinado et al. | Applicant |
| US2011/0289582(A1) | 2011-11-01 | Kejriwal et al. | Applicant |
| US2011/0302587(A1) | 2011-12-01 | Nishikawa et al. | Applicant |
| US2011/0307954(A1) | 2011-12-01 | Melnik et al. | Applicant |
| US2011/0307955(A1) | 2011-12-01 | Kaplan et al. | Applicant |
| US2011/0307956(A1) | 2011-12-01 | Yermakov et al. | Applicant |
| US2011/0314546(A1) | 2011-12-01 | Aziz et al. | Applicant |
| US2012/0023593(A1) | 2012-01-01 | Puder et al. | Applicant |
| US2012/0054869(A1) | 2012-03-01 | Yen et al. | Applicant |
| US2012/0066698(A1) | 2012-03-01 | Yanoo | Applicant |
| US2012/0079596(A1) | 2012-03-01 | Thomas et al. | Applicant |
| US2012/0084859(A1) | 2012-04-01 | Radinsky et al. | Applicant |
| US2012/0110667(A1) | 2012-05-01 | Zubrilin et al. | Applicant |
| US2012/0117652(A1) | 2012-05-01 | Manni et al. | Applicant |
| US2012/0121154(A1) | 2012-05-01 | Xue et al. | Applicant |
| US2012/0124426(A1) | 2012-05-01 | Maybee et al. | Applicant |
| US2012/0174186(A1) | 2012-07-01 | Aziz et al. | Applicant |
| US2012/0174196(A1) | 2012-07-01 | Bhogavilli et al. | Applicant |
| US2012/0174218(A1) | 2012-07-01 | McCoy et al. | Applicant |
| US2012/0198279(A1) | 2012-08-01 | Schroeder | Applicant |
| US2012/0210423(A1) | 2012-08-01 | Friedrichs et al. | Applicant |
| US2012/0222121(A1) | 2012-08-01 | Staniford et al. | Applicant |
| US2012/0255015(A1) | 2012-10-01 | Sahita et al. | Applicant |
| US2012/0255017(A1) | 2012-10-01 | Sallam | Applicant |
| US2012/0260342(A1) | 2012-10-01 | Dube et al. | Applicant |
| US2012/0266244(A1) | 2012-10-01 | Green et al. | Applicant |
| US2012/0278886(A1) | 2012-11-01 | Luna | Applicant |
| US2012/0297489(A1) | 2012-11-01 | Dequevy | Applicant |
| US2012/0330801(A1) | 2012-12-01 | McDougal et al. | Applicant |
| US2013/0014259(A1) | 2013-01-01 | Gribble et al. | Applicant |
| US2013/0036472(A1) | 2013-02-01 | Aziz | Applicant |
| US2013/0047257(A1) | 2013-02-01 | Aziz | Applicant |
| US2013/0074185(A1) | 2013-03-01 | McDougal et al. | Applicant |
| US2013/0086684(A1) | 2013-04-01 | Mohler | Applicant |
| US2013/0097699(A1) | 2013-04-01 | Balupari et al. | Applicant |
| US2013/0097706(A1) | 2013-04-01 | Titonis et al. | Applicant |
| US2013/0111587(A1) | 2013-05-01 | Goel et al. | Applicant |
| US2013/0117852(A1) | 2013-05-01 | Stute | Applicant |
| US2013/0117855(A1) | 2013-05-01 | Kim et al. | Applicant |
| US2013/0139264(A1) | 2013-05-01 | Brinkley et al. | Applicant |
| US2013/0160125(A1) | 2013-06-01 | Likhachev et al. | Applicant |
| US2013/0160127(A1) | 2013-06-01 | Jeong et al. | Applicant |
| US2013/0160130(A1) | 2013-06-01 | Mendelev et al. | Applicant |
| US2013/0160131(A1) | 2013-06-01 | Madou et al. | Applicant |
| US2013/0167236(A1) | 2013-06-01 | Sick | Applicant |
| US2013/0174214(A1) | 2013-07-01 | Duncan | Applicant |
| US2013/0185789(A1) | 2013-07-01 | Hagiwara et al. | Applicant |
| US2013/0185795(A1) | 2013-07-01 | Winn et al. | Applicant |
| US2013/0185798(A1) | 2013-07-01 | Saunders et al. | Applicant |
| US2013/0191915(A1) | 2013-07-01 | Antonakakis et al. | Applicant |
| US2013/0196649(A1) | 2013-08-01 | Paddon et al. | Applicant |
| US2013/0227691(A1) | 2013-08-01 | Aziz et al. | Applicant |
| US2013/0246370(A1) | 2013-09-01 | Bartram et al. | Applicant |
| US2013/0263260(A1) | 2013-10-01 | Mahaffey et al. | Applicant |
| US2013/0291109(A1) | 2013-10-01 | Staniford et al. | Applicant |
| US2013/0298243(A1) | 2013-11-01 | Kumar et al. | Applicant |
| US2014/0053260(A1) | 2014-02-01 | Gupta et al. | Applicant |
| US2014/0053261(A1) | 2014-02-01 | Gupta et al. | Applicant |
| US2014/0130158(A1) | 2014-05-01 | Wang et al. | Applicant |
| US2014/0137180(A1) | 2014-05-01 | Lukacs et al. | Applicant |
| US2014/0169762(A1) | 2014-06-01 | Ryu | Applicant |
| US2014/0179360(A1) | 2014-06-01 | Jackson et al. | Applicant |
| US2014/0328204(A1) | 2014-11-01 | Klotsche et al. | Applicant |
| US2014/0337836(A1) | 2014-11-01 | Ismael | Applicant |
| US2014/0351935(A1) | 2014-11-01 | Shao et al. | Applicant |
| US2015/0096025(A1) | 2015-04-01 | Ismael | Applicant |
| GB2439806(A) | 2008-01-01 | Applicant | |
| GB2490431(A) | 2012-10-01 | Applicant | |
| WO2/23805(A2) | 2002-03-01 | Applicant | |
| WO206928 | 2003-11-01 | Applicant | |
| WO2007117636(A2) | 2007-10-01 | Applicant | |
| WO2008041950(A2) | 2008-04-01 | Applicant | |
| WO2011084431(A2) | 2011-07-01 | Applicant | |
| WO2011/112348(A1) | 2011-09-01 | Applicant | |
| WO2012/075336(A1) | 2012-06-01 | Applicant | |
| WO2012145066(A1) | 2012-10-01 | Applicant | |
| WO2013/067505(A1) | 2013-05-01 | Applicant |
Non-Patent Literature (79)
- Cisco “Intrusion Prevention for the Cisco ASA 5500-x Series” Data Sheet (2012).Applicant
- Clark, John, Sylvian Leblanc,and Scott Knight. “Risks associated with usb hardware trojan devices used by insiders.” Systems Conference (SysCon), 2011 IEEE International. IEEE, 2011.Applicant
- FireEye Malware Analysis & Exchange Network, Malware Protection System, FireEye Inc., 2010.Applicant
- FireEye Malware Analysis, Modern Malware Forensics, FireEye Inc., 2010.Applicant
- FireEye v.6.0 Security Target, pp. 1-35, Version 1.1, FireEye Inc., May 2011.Applicant
- Gibler, Clint, et al. AndroidLeaks: automatically detecting potential privacy leaks in android applications on a large scale. Springer Berlin Heidelberg, 2012.Applicant
- Goel, et al., Reconstructing System State for Intrusion Analysis, Apr. 2008 SIGOPS Operating Systems Review, vol. 42 Issue 3, pp. 21-28.Applicant
- Gregg Keizer: “Microsoft's HoneyMonkeys Show Patching Windows Works”, Aug. 8, 2005, XP055143386, Retrieved from the Internet: URL:https://web.archive.org/web/20121022220617/http://www.informationweek- .com/microsofts-honeymonkeys-show-patching-wi/167600716 [retrieved on Sep. 29, 2014].Applicant
- Heng Yin et al, Panorama: Capturing System-Wide Information Flow for Malware Detection and Analysis, Research Showcase @ CMU, Carnegie Mellon University, 2007.Applicant
- Hjelmvik, Erik , “Passive Network Security Analysis with NetworkMiner”, (IN)Secure, Issue 18, (Oct. 2008), pp. 1-100.Applicant
- Idika et al., A-Survey-of-Malware-Detection-Techniques, Feb. 2, 2007, Department of Computer Science, Purdue University.Applicant
- Isohara, Takamasa, Keisuke Takemori, and Ayumu Kubota. “Kernel-based behavior analysis for android malware detection.” Computational intelligence and Security (CIS), 2011 Seventh International Conference on. IEEE, 2011.Applicant
- Kevin A Roundy et al: “Hybrid Analysis and Control of Malware”, Sep. 15, 2010, Recent Advances in Intrusion Detection, Springer Berlin Heidelberg, Berlin, Heidelberg, pp. 317-338, XP019150454 ISBN:978-3-642-15511-6.Applicant
- Leading Colleges Select FireEye to Stop Malware-Related Data Breaches, FireEye Inc., 2009.Applicant
- Li et al., A VMM-Based System Call Interposition Framework for Program Monitoring, Dec. 2010, IEEE 16th International Conference on Parallel and Distributed Systems, pp. 706-711.Applicant
- Lindorfer, Martina, Clemens Kolbitsch, and Paolo Milani Comparetti. “Detecting environment-sensitive malware.” Recent Advances in Intrusion Detection. Springer Berlin Heidelberg, 2011.Applicant
- Lok Kwong et al: “DroidScope: Seamlessly Reconstructing the OS and Dalvik Semantic Views for Dynamic Android Malware Analysis”, Aug. 10, 2012, XP055158513, Retrieved from the Internet: URL:https://www.usenix.org/system/files/conference/usenixsecurity12/sec12- -final107.pdf [retrieved on Dec. 15, 2014].Applicant
- Morales, Jose A., et al., ““Analyzing and exploiting network behaviors of malware.””, Security and Privacy in Communication Networks. Springer Berlin Heidelberg, 2010. 20-34.Applicant
- Mori, Detecting Unknown Computer Viruses, 2004, Springer-Verlag Berlin Heidelberg.Applicant
- Oberheide et al., CloudAV.sub.--N-Version Antivirus in the Network Cloud, 17th USENIX Security Symposium USENIX Security '08 Jul. 28-Aug. 1, 2008 San Jose, CA.Applicant
- U.S. Pat. No. 8,171,553 filed Apr. 20, 2006, Inter Parties Review Decision dated Jul. 10, 2015.Applicant
- U.S. Pat. No. 8,291,499 filed Mar. 16, 2012, Inter Parties Review Decision dated Jul. 10, 2015.Applicant
- Wahid et al., Characterising the Evolution in Scanning Activity of Suspicious Hosts, Oct. 2009, Third International Conference on Network and System Security, pp. 344-350.Applicant
- Yuhei Kawakoya et al: “Memory behavior-based automatic malware unpacking in stealth debugging environment”, Malicious and Unwanted Software (Malware), 2010 5th International Conference on, IEEE, Piscataway, NJ, USA, Oct. 19, 2010, pp. 39-46, XP031833827, ISBN:978-1-4244-8-9353-1.Applicant
- Zhang et al., The Effects of Threading, Infection Time, and Multiple-Attacker Collaboration on Malware Propagation, Sep. 2009, IEEE 28th International Symposium on Reliable Distributed Systems, pp. 73-82.Applicant
- “Network Security: NetDetector—Network Intrusion Forensic System (NIFS) Whitepaper”, (“NetDetector Whitepaper”), (2003).Applicant
- “Packet”, Microsoft Computer Dictionary, Microsoft Press, (Mar. 2002), 1 page.Applicant
- “When Virtual is Better Than Real”, IEEEXplore Digital Library, available at, http://ieeexplore.ieee.org/xpl/articleDetails.isp?reload=true&arnumbe- r=990073, (Dec. 7, 2013).Applicant
- Abdullah, et al., Visualizing Network Data for Intrusion Detection, 2005 IEEE Workshop on Information Assurance and Security, pp. 100-108.Applicant
- Adetoye, Adedayo , et al., “Network Intrusion Detection & Response System”, (“Adetoye”), (Sep. 2003).Applicant
- AltaVista Advanced Search Results. “attack vector identifier”. Http://www.altavista.com/web/results?ltag=ody&pg=aq&aqmode=aqa=Event+Orch- estrator . . . , (Accessed on Sep. 15, 2009).Applicant
- AltaVista Advanced Search Results. “Event Orchestrator”. Http://www.altavista.com/web/results?ltag=ody&pg=aq&aqmode=aqa=Event+Orch- esrator . . . , (Accessed on Sep. 3, 2009).Applicant
- Apostolopoulos, George; hassapis, Constantinos; “V-eM: A cluster of Virtual Machines for Robust, Detailed, and High-Performance Network Emulation”, 14th IEEE International Symposium on Modeling, Analysis, and Simulation of Computer and Telecommunication Systems, Sep. 11-14, 2006, pp. 117-126.Applicant
- Aura, Tuomas, “Scanning electronic documents for personally identifiable information”, Proceedings of the 5th ACM workshop on Privacy in electronic society. ACM, 2006.Applicant
- Baecher, “The Nepenthes Platform: An Efficient Approach to collect Malware”, Springer-verlag Berlin Heidelberg, (2006), pp. 165-184.Applicant
- Baldi, Mario; Risso, Fulvio; “A Framework for Rapid Development and Portable Execution of Packet-Handling Applications”, 5th IEEE International Symposium Processing and Information Technology, Dec. 21, 2005, pp. 233-238.Applicant
- Bayer, et al., “Dynamic Analysis of Malicious Code”, J Comput Virol, Springer-Verlag, France., (2006), pp. 67-77.Applicant
- Boubalos, Chris , “extracting syslog data out of raw pcap dumps, seclists.org, Honeypots mailing list archives”, available at http://seclists.org/honeypots/2003/q2/319 (“Boubalos”), (Jun. 5, 2003).Applicant
- Chaudet, C. , et al., “Optimal Positioning of Active and Passive Monitoring Devices”, International Conference on Emerging Networking Experiments and Technologies, Proceedings of the 2005 ACM Conference on Emerging Network Experiment and Technology, CoNEXT '05, Toulousse, France, (Oct. 2005), pp. 71-82.Applicant
- Chen, P. M. And Noble, B. D., “When Virtual is Better Than Real, Department of Electrical Engineering and Computer Science”, University of Michigan (“Chen”).Applicant
- Cisco, Configuring the Catalyst Switched Port Analyzer (SPAN) (“Cisco”), (1992-2003).Applicant
- Cohen, M.I. , “PyFlag—An advanced network forensic framework”, Digital investigation 5, Elsevier, (2008), pp. S112-S120.Applicant
- Costa, M. , et al., “Vigilante: End-to-End Containment of Internet Worms”, SOSP '05, Association for Computing Machinery, Inc., Brighton U.K., (Oct. 23-26, 2005).Applicant
- Crandall, J.R. , et al., “Minos:Control Data Attack Prevention Orthogonal to Memory Model”, 37th International Symposium on Microarchitecture, Portland, Oregon, (Dec. 2004).Applicant
- Deutsch, P. , “Zlib compressed data format specification version 3.3” RFC 1950, (1996).Applicant
- Distler, “Malware Analysis: An Introduction”, SANS Institute InfoSec Reading Room, SANS Institute, (2007).Applicant
- Dunlap, George W. , et al., “ReVirt: Enabling Intrusion Analysis through Virtual-Machine Logging and Replay”, Proceeding of the 5th Symposium on Operating Systems Design and Implementation, USENIX Association, (“Dunlap”), (Dec. 9, 2002).Applicant
- Excerpt regarding First Printing Date for Merike Kaeo, Designing Network Security (“Kaeo”), (2005).Applicant
- Filiol, Eric , et al., “Combinatorial Optimisation of Worm Propagation on an Unknown Network”, International Journal of Computer Science 2.2 (2007).Applicant
- IEEE Xplore Digital Library Sear Results for “detection of unknown computer worms”. Http//ieeexplore.ieee.org/searchresult.jsp?SortField=Score&SortOrder=desc- &ResultC . . . , (Accessed on Aug. 28, 2009).Applicant
- Kaeo, Merike , “Designing Network Security”, (“Kaeo”), (Nov. 2003).Applicant
- Kim, H. , et al., “Autograph: Toward Automated, Distributed Worm Signature Detection”, Proceedings of the 13th Usenix Security Symposium (Security 2004), San Diego, (Aug. 2004), pp. 271-286.Applicant
- King, Samuel T., et al., “Operating System Support for Virtual Machines”, (“King”) (2003).Applicant
- Krasnyansky, Max , et al., Universal TUN/TAP driver, available at https://www.kernel.org/doc/Documentation/networking/tuntap.txt (2002) (“Krasnyansky”).Applicant
- Kreibich, C. , et al., “Honeycomb-Creating Intrusion Detection Signatures Using Honeypots”, 2nd Workshop on Hot Topics in Networks (HotNets-11), Boston, USA, (2003).Applicant
- Kristoff, J. , “Botnets, Detection and Mitigation: DNS-Based Techniques”, NU Security Day, (2005), 23 pages.Applicant
- Liljenstam, Michael , et al., “Simulating Realistic Network Traffic for Worm Warning System Design and Testing”, Institute for Security Technology studies, Dartmouth College (“Liljenstam”), (Oct. 27, 2003).Applicant
- Marchette, David J., “Computer Intrusion Detection and Network Monitoring: A Statistical Viewpoint”, (“Marchette”), (2001).Applicant
- Margolis, P.E. , “Random House Webster's ‘Computer & Internet Dictionary 3rd Edition’”, ISBN 0375703519, (Dec. 1998).Applicant
- Moore, D. , et al., “Internet Quarantine: Requirements for Containing Self-Propagating Code”, INFOCOM, vol. 3, (Mar. 30-Apr. 3, 2003), pp. 1901-1910.Applicant
- Natvig, Kurt , “SANDBOXII: Internet”, Virus Bulletin Conference, (“Natvig”), (Sep. 2002).Applicant
- NetBIOS Working Group. Protocol Standard for a NetBIOS Service on a TCP/UDP transport: Concepts and Methods. STD 19, RFC 1001, Mar. 1987.Applicant
- Newsome, J. , et al., “Dynamic Taint Analysis for Automatic Detection, Analysis, and Signature Generation of Exploits on Commodity Software”, In Proceedings of the 12th Annual Network and Distributed System Security, Symposium (NDSS '05), (Feb. 2005).Applicant
- Newsome, J. , et al., “Polygraph: Automatically Generating Signatures for Polymorphic Worms”, In Proceedings of the IEEE Symposium on Security and Privacy, (May 2005).Applicant
- Nojiri, D. , et al., “Cooperation Response Strategies for Large Scale Attack Mitigation”, DARPA Information Survivability Conference and Exposition, vol. 1, (Apr. 22-24, 2003), pp. 293-302.Applicant
- PCT/US2012/021916 filed Jan. 19, 2012, International Search Report and Written Opinion dated May 10, 2012.Applicant
- PCT/US2012/026402 filed Feb. 23, 2012 International Search Report and Written Opinion dated May 25, 2012.Applicant
- Reiner Sailer, Enriquillo Valdez, Trent Jaeger, Roonald Perez, Leendert van Doom, John Linwood Griffin, Stefan Berger., sHype: Secure Hypervisor Appraoch to Trusted Virtualized Systems (Feb. 2, 2005) (“Sailer”).Applicant
- Silicon Defense, “Worm Containment in the Internal Network”, (Mar. 2003), pp. 1-25.Applicant
- Singh, S. , et al., “Automated Worm Fingerprinting”, Proceedings of the ACM/USENIX Symposium on Operating System Design and Implementation, San Francisco, California, (Dec. 2004).Applicant
- Spitzner, Lance , “Honeypots: Tracking Hackers”, (“Spizner”), (Sep. 17, 2002).Applicant
- The Sniffers's Guide to Raw Traffic available at: yuba.stanford.edu/.about.casado/pcap/section1.html, (Jan. 6, 2014).Applicant
- Thomas H. Ptacek, and Timothy N. Newsham , “Insertion, Evasion, and Denial of Service: Eluding Network Intrusion Detection”, Secure Networks, (“Ptacek”), (Jan. 1998).Applicant
- U.S. Appl. No. 11/717,474, filed Mar. 12, 2007 Final Office Action dated Feb. 2, 2011.Applicant
- U.S. Appl. No. 11/717,474, filed Mar. 12, 2007 Non-Final Office Action dated Dec. 19, 2013.Applicant
- U.S. Appl. No. 11/717,474, filed Mar. 12, 2007 Non-Final Office Action dated May 25, 2010.Applicant
- Venezia, Paul , “NetDetector Captures Intrusions”, InfoWorld Issue 27, (“Venezia”), (Jul. 14, 2003).Applicant
- Whyte, et al., “DNS-Based Detection of Scanning Works in an Enterprise Network”, Proceedings of the 12th Annual Network and Distributed System Security Symposium, (Feb. 2005), 15 pages.Applicant
- Williamson, Matthew M., “Throttling Viruses: Restricting Propagation to Defeat Malicious Mobile Code”, ACSAC Conference, Las Vegas, NV, USA, (Dec. 2002), pp. 1-9.Applicant