US20140373144A9 - System and method for analyzing unauthorized intrusion into a computer network - Google Patents

System and method for analyzing unauthorized intrusion into a computer network Download PDF

Info

Publication number
US20140373144A9
US20140373144A9 US11/788,795 US78879507A US2014373144A9 US 20140373144 A9 US20140373144 A9 US 20140373144A9 US 78879507 A US78879507 A US 78879507A US 2014373144 A9 US2014373144 A9 US 2014373144A9
Authority
US
United States
Prior art keywords
attack
system
network
operating system
signature
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/788,795
Other versions
US20080016570A1 (en
Inventor
Alen Capalik
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
COUNTERTACK Inc
Original Assignee
COUNTERTACK Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US80254306P priority Critical
Priority to US11/488,743 priority patent/US8429746B2/en
Application filed by COUNTERTACK Inc filed Critical COUNTERTACK Inc
Priority to US11/788,795 priority patent/US20140373144A9/en
Publication of US20080016570A1 publication Critical patent/US20080016570A1/en
Assigned to NEURALIQ, INC. reassignment NEURALIQ, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CAPALIK, ALEN
Publication of US20140373144A9 publication Critical patent/US20140373144A9/en
Assigned to COUNTERTACK INC. reassignment COUNTERTACK INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: NEURALIQ, INC.
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441Countermeasures against malicious traffic
    • H04L63/145Countermeasures against malicious traffic the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55Detecting local intrusion or implementing counter-measures
    • G06F21/552Detecting local intrusion or implementing counter-measures involving long-term monitoring or reporting
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55Detecting local intrusion or implementing counter-measures
    • G06F21/56Computer malware detection or handling, e.g. anti-virus arrangements
    • G06F21/566Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H04L63/1416Event detection, e.g. attack signature detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441Countermeasures against malicious traffic
    • H04L63/1491Countermeasures against malicious traffic using deception as countermeasure, e.g. honeypots, honeynets, decoys or entrapment
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2123Dummy operation

Abstract

The method analyzes unauthorized intrusion into a computer network. Access is allowed through one or more open ports to one or more virtualized decoy operating systems running on a hypervisor operating system hosted on a decoy network device. This may be done by opening a port on one of the virtualized decoy operating systems. A network attack on the virtualized operating system is then intercepted by an introspection module running on the hypervisor operating system. The attack-identifying information is communicated through a private network interface channel and stored on a database server as forensic data. A signature-generation engine uses this forensic data to generate a signature of the attack. An intrusion prevention system then uses the attack signature to identify and prevent subsequent attacks. A web-based visualization interface facilitates configuration of the system and analysis of (and response to) forensic data generated by the introspection module and the signature generation engine, as well as that stored in the processing module's relational databases.

Description

  • This is a Continuation-In-Part, and claims priority to and the benefit of: U.S. Ser. No. 11/488,743, entitled “Decoy Network Technology With Automatic Signature Generation for Intrusion Detection and Intrusion Prevention Systems” filed on Jul. 17, 2006, the entire disclosure of which is incorporated herein by reference.
  • FIELD
  • The invention relates to the field of methods and systems for protecting computer networks and is more particularly, but not by way of limitation, directed to decoy network technology with automatic signature generation for intrusion detection and intrusion prevention systems.
  • BACKGROUND
  • Computer networks typically interface with the Internet or other public computer systems and are thus vulnerable to attacks, unwanted intrusions and unauthorized access. One threat to networks is the so-called zero-day attack that exploits security vulnerabilities unknown to the system operators.
  • Conventional network security systems include a firewall that generally prevents unauthorized access to the network or its computers. Conventional systems also include intrusion detection systems (IDS) and intrusion prevention systems (IPS) that typically contain a library of signatures of malware payloads, which enable them to detect those defined exploits attempting to access production systems. When a connection is attempted to a network port, the IDS or IPS examines the low-level IP data packets and compares them to its library of signatures for a match. When a match is identified the IDS or IPS provides notification of the match.
  • The problem lies in the static nature of the conventional IDS and IPS signatures coupled with the ability of determined attackers to launch new undefined or zero-day automated attacks to gain access to the network. While an intrusion prevention system (IPS) equipped with behavioral signatures providing the ability to capture behavioral patterns offers a higher level of protection, these have similar drawbacks in that behavioral signatures are still static in nature and limited in their ability to stop zero-day attacks.
  • Still another type of network security systems utilizes a honeynet arrangement to attract and then trap a suspected attacker. A honeynet is made up of two or more honeypots on a network. Such measures typically are made up of a computer, data or network site that appears to be part of the network and appears to be one or more valuable targets, but which is actually an isolated component located away from production networks. These are typically passive measures effective against spammers and other low-level attacks. Such systems typically run emulated operating systems and services and are generally not useful against sophisticated attackers who can detect and effectively avoid the honeynet, never unloading their zero-day attack or payload for the honeynet to capture and analyze. Also, if the conventional honeynet configuration is not sufficiently separated from the network system, an attacker can use the honeynet to gain access to the network. Examples of emulated or software based honeypots include “honeyd” which is a GPL licensed daemon that is utilized to simulate network structures. Another example of emulated software based honeypots include “mwcollect” and “nepenthes” which are also released under the GPL license and which are utilized to collect malware. The “mwcollect” and “nepenthes” packages extract information on obtaining the malware binaries from the exploit payload.
  • Because each of the problems and limitations discussed above exist in the prior art devices and systems, there is a need for methods and systems that adequately protect networks from new and undefined attacks and that allow for real-time updates to a network's library of attack signatures.
  • SUMMARY
  • One or more embodiments of the invention are directed to an improved method and system for protecting computer networks. In one embodiment, the invention comprises a modular decoy network appliance, which runs fully functional operating systems on client hardware modules. The modular arrangement comprises front-end fully functional operating system modules and a separate processing back-end module.
  • The front-end presents a standard fully functional operating system, such as Windows® or a flavor of Linux®, or Sun Microsystems Solaris® that returns a standard operating system fingerprint when it is scanned by tools that attackers typically use to identify vulnerable systems. The attacker is thus lured into accessing the identified operating system and running custom or known exploits on that system.
  • The front-end module includes a sentinel kernel driver (or a more generalized executable module) that is hidden from system scanners as it is removed from kernel module listings or registry in Windows. Thus, the kernel does not indicate the sentinel kernel driver is running. The sentinel kernel driver monitors connections to the operating system as well as activity on the operating system and activity on services running on the operating system. When an attacker connects to a port, the sentinel kernel driver captures the data coming through the socket. Generally all relevant data coming through the socket is captured. In most cases this means whatever data is received as part of an incoming attack is captured by the sentinel driver. Captured data is sent as a slew of common UDP packets to the back end processing module over the fabric network connection separate from the vulnerable front-end modules. In this manner, there is no way for the intruder to know that his or her communications with the operating system are being analyzed.
  • The captured data, which contains the attack-identifying information, is sent to the back-end or processing module though the backplane fabric of the appliance using Layer 2 Ethernet communication protocol. The processing module is separate and independent from the client operating system modules and communicates the processed information to security administrators through a network port connected to the private and secure VLAN. Unbeknownst to the intruder, the exploit is thus captured, transferred and analyzed.
  • With the received data, the processing module generates a report of the attack. The report consists of user-friendly information that paints a picture of the attack for a system administrator. This may include information on which sockets were accessed, what happened at a particular socket, the key strokes entered or bytes transferred to the port, what files were transferred, registry changes, how the attack was run, what happened on the primary network, on its servers or how the network services were affected. The report may also include information on the location of the attacker or the attacker's service provider. Graphical representations of key information and interactive mapping of the attack locales by region or country may be utilized in one or more embodiments of the invention.
  • The processing module is used to generate an attack signature by analyzing all the data passed through the socket. The signature is generated by analyzing the attack payload including the keystrokes or transferred bytes and any files uploaded to the client operating system of an ASCII or binary nature. The files uploaded are assumed to be of a malicious nature created to deliver a malicious payload in the form of a compiled program or an interpreted script. In the event that no malicious files are uploaded to the operating system, the signature generation engine analyzes all the keystrokes or bytes delivered through the socket and creates a pattern signature which when applied to an IDS or IPS system, enables the IDS or IPS systems to detect the attack if repeated on production systems. Once generated, the attack signatures can be viewed by a system administrator to determine the appropriate course of action. The system administrator can instruct the signature to be uploaded to the intrusion detection system (IDS) or intrusion prevention system (IPS) for the protected network where it is added to the IDS's or IPS's library of signatures to protect production systems. In one or more embodiments of the invention, the signature may be uploaded or saved in a third party system that maintains all known exploits. In this manner, other systems may be notified through secure channels of an impending threat. For example, by transferring the signature to a centralized server that communicates with multiple installations, the intruder may be thwarted before attacking other systems in other companies.
  • A production network's library of signatures can be updated in real-time as the attacker modifies its illicit activity or a new attack is launched. The embodiment can also maintain a database of any and all attack signatures generated. Other and further advantages will be disclosed and identified in the description and claims and will be apparent to persons skilled in the art.
  • Another embodiment provides a system and method for analyzing unauthorized intrusion into a computer network. Access is allowed through one or more open ports to one or more virtualized decoy operating systems running on a hypervisor operating system hosted on a decoy network device. This may be done by opening a port on one of the virtualized decoy operating systems. A network attack on the virtualized operating system is then intercepted by a virtual-machine-based rootkit module running on the hypervisor operating system. The attack-identifying information is communicated through a private network interface channel and stored on a database server as forensic data. A signature generation engine uses this forensic data to generate a signature of the attack. An intrusion prevention system then uses the attack signature to identify and prevent subsequent attacks
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 illustrates a block diagram of an embodiment of the system;
  • FIG. 2 illustrates a flow chart of an embodiment of the processing that occurs on processing module 40;
  • FIG. 3 illustrates a human readable summary of an example attack;
  • FIG. 4 illustrates an XML formatted attack signature generated from the attack summarized in FIG. 3 for transmittal to an IDS or IPS; and
  • FIG. 5 illustrates a block diagram of another embodiment of the system.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
  • The following descriptions of embodiments of the invention are exemplary, rather than limiting, and many variations and modifications are within the scope and spirit of the invention. Although numerous specific details are set forth in order to provide a thorough understanding of the present invention, it will be apparent to one of ordinary skill in the art, that embodiments of the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail in order to avoid unnecessarily obscuring the present invention.
  • One or more embodiments of the invention are directed to an improved method and system for protecting computer networks. One embodiment is illustrated in FIG. 1, which illustrates attacker activity 10 directed at protected computer network 20. As in a typical attack, attack 10 is scanning for an open port on computer network 20 in an attempt to make a connection and then access one or more protected network devices 20 a on network 20.
  • Attack 10 is monitored by decoy 100 that includes at least one monitor/intercept module 30. Monitor/intercept module 30 comprises fully functioning decoy operating system 32 that monitors each of the access ports for network 20. Any operating system may be used as decoy operating system 32 including Windows®, Sun Microsystems Solaris® or any version of Linux® known to persons skilled in the art. All known operating systems are within the scope of the present invention. FIG. 1 shows one monitoring/intercept module 30 in the foreground, however any number of homogeneous or heterogeneous monitoring/intercept modules may be utilized (shown as a stack behind monitor/intercept module 30). For example, in one embodiment of the invention a Windows® monitoring/intercept module 30 and LINUX® monitoring/intercept module 30 may be employed. There is no limit to the number of monitoring/intercept modules that may be utilized in the system and other embodiments may employ homogeneous decoy operating systems 32 that are of the same or of different versions. Monitoring/intercept module 30 also includes sentinel kernel driver 34 which will be described in further detail below. Protected network devices 20 a are accessed through IDS/IPS with Library of Signatures 62 in one or more embodiments of the invention. The system also includes processing module 40 for obtaining and analyzing exploits.
  • When attack 10 connects to an access port of network 20, the fully functional decoy operating system 32 intercepts the connection and returns a standard operating system fingerprint. For example when connecting to an address that does not exist on protected network 20, decoy 30 may be configured to respond to any such incorrect address since the connection is assumed to be malicious as there is no hardware on protected network 20 at that address. The response may be configured to utilize any existing hardware module having a given operating system and version within monitoring/intercept module 30. For example, an FTP port access for Windows® may return a particular character sequence that is different than an FTP response for LINUX®. An FTP access to a Windows® port for example may return a response “>ftp: connect: Connection refused”. This characters sequence may be slightly different on LINUX® and hence allows the intruder to determine what type of operating system is at a particular network address. In addition, different versions of Windows® may respond with slightly different character sequences which allows the intruder to determine the specific version of the operating system or to determine a possible range of versions for the responding operating system. The instigator of attack 10 is thus lured into accessing decoy 100, which includes monitor/intercept module 30, and running custom or known exploits for the observed operating system. When attacker activity proceeds to interact with decoy 100, the attacker provides decoy 100 with the data used to obtain control of decoy 100, which is recorded and analyzed without knowledge of the attacker.
  • All scans by attack 10 receive real-world operating system information, thus leading the instigator of the attack 10 to believe that there is a potentially vulnerable system responding and thus luring attack 10 into communicating with monitor/intercept module 30. Since real hardware is utilized, the attacker is attacking an actual physical system and thus has no idea that the system is actually an instrumented honeypot that monitors the attackers every move.
  • Monitor/intercept module 30 includes sentinel kernel driver 34. In one embodiment, sentinel kernel driver 34 is a combination of custom root-kit code that on Windows® based operating systems removes pointers from Microsoft® client/server runtime server subsystem (CSRSS.exe). This coupled with removing sentinel kernel driver 34 from the Windows® registry effectively hides sentinel kernel driver 34 and all its drivers from attack 10. On Unix® based operating systems, the kernel pointers are removed making the kernel unable to link to a running process, effectively hiding sentinel kernel driver 34 and all its libraries from attack 10. Sentinel kernel driver 34 monitors all data coming through the socket and is derived from an open source code, such as libpcap, known to persons skilled in the art.
  • When an attacker connects to a port, and begins interacting with decoy operating system 32, sentinel 34 monitors and captures information from the connection including port numbers, data streams, keystrokes, file uploads and any other data transfers.
  • The captured information, or attack-identifying information, is then sent for processing to processing module 40 as illustrated in FIG. 1. Processing module 40 may optionally include a sentinel server that receives information from the sentinel kernel driver and deposits the information in a database for later analysis. In one embodiment, the monitor/intercept module 30 is a front-end module or series of modules and the captured data is sent to processing module 40 though the backplane of the appliance or appliances through a layer 2 Ethernet communications link not available to the attacker such as an IP connection or any other hardware dependent custom communication protocol known to persons skilled in the art. Processing module 40 is part of a secure and separate administrative network 42. In one or more embodiments the signature may be sent from the back end processing module 40 to IDS/IPS 62 through a second network connection which is used by the processing module 40 to directly interact with IDS/IPS 62. The sentinel kernel driver may utilize replay functionality to replay the attacks on the operating system in reverse to clean up the operating system to its pre-attack state. In this manner, the attack can be thwarted and the operating system thus does not become a tool of the hacker.
  • As shown in FIG. 2, processing starts at 200 and waits for activity from sentinel kernel driver 34 at step 43. In step 44, processing module 40 generates a report of the attack that includes attack-identifying information (See FIG. 3). This report is for the use and review by a system administrator who is responsible for administering protected network 20. The attack may contain one or more data transfers or keystrokes for example, which are analyzed at step 46. By observing whether the attacker is successful in interacting with the system, i.e., if the system is responding in a manner that shows that the attacker has gained access, then determination whether to generate an attack signature is made at step 48 and the attack signature is generated at step 52 (See FIG. 4). If the attacker for example is unsuccessful at gaining access or if there is no data transfer for example, then the attack inquiry may be ended at step 50. Any generated attack signature is sent to the IDS/IPS at step 56 and processing continues at step 43.
  • In one embodiment of the invention, the report is written, and is displayed in an web-based visualization interface and can include information about which sockets were accessed by attack 10, what happened at a particular socket, the key strokes entered or data transferred, what files were transferred, how the attack 10 was run, what happened on monitor/intercept module 30 and how decoy operating system 32 and any related network services were affected. The report may also include information on the location of the instigator of attack 10 or the service provider used for attack 10. Graphical representations of key information and interactive mapping of attack locales by region or country may also be included in the report.
  • In step 46, the attack-identifying information is analyzed for known attack patterns and non-standard patterns such as repeating binary patterns, keystroke patterns, downloaded daemons or errors such as buffer overflow attempts. By observing the operations performed on decoy operating system 32 the attack may be categorized and analyzed to determine for example how an attack gains control of decoy operating system 32. Any method of analyzing the incoming data such as binary matching, neural network matching or keyword matching or any other method of matching attack-identifying information is in keeping with the spirit of the invention.
  • In step 48, a decision is made as to whether to generate an attack signature. If no harmful operations occurred as a result of attack 10 or when no known attack patterns are found, then no further attack inquiry would be needed as shown in step 50. The processing module 40 can then take on the next input of captured information from the monitor/intercept module 30.
  • If a determination is made that attack signature generation is warranted, an attack signature is generated as illustrated in step 52. Processing module 40 may generate a signature whenever data is found to be transferred through the socket in one or more embodiments of the invention. Alternatively, if the attack signature already exists or if the data transfer is of a nature that indicates probing rather than attack, then the attack signature may not be generated. For example, processing module 40 may not generate a signature when it is found that no data has been transferred through the socket even though the socket may have been opened and closed without data transfer. Once the attack signature is generated, the signature can be reviewed by the system administrator who decides to send the attack signature, shown in step 56, to the intrusion detection system (IDS) or intrusion prevention system (IPS) for the protected network 20 through a standard network connection including a wireless connection that is generally not sent on protected network 20 or any other network that the attacker may observe. This is accomplished by applying the generated attack signature to the IDS/IPS library of signatures to update the information contained in the library of signatures to prevent the attacker from accessing the primary network with a zero-day attack.
  • Embodiments of step 56 may save the generated attack signatures in a database for future use or further analysis by system administrators. The signatures may also be sent to a proprietary global database of attack signatures for further analysis. Any IDS/IPS may be utilized in one or more embodiments of the invention. Existing IDS/IPS systems for example may be interfaced with in order to integrate with existing solutions.
  • FIG. 3 illustrates a human readable summary of an example attack. Line 300 shows that the file “msprexe.exe” is copied into the “System” directory. Line 301 shows a first registry entry created by the attack. Line 302 shows a second registry entry created by the attack. Any other changes to the system may be shown, as part of the attack-identifying information and the information shown in FIG. 3 is exemplary only.
  • FIG. 4 illustrates an XML formatted attack signature generated from the attack summarized in FIG. 3 for transmittal to an IDS or IPS. XML block 400 includes tags that define the attack signature in the format of the particular IDS or IPS. Any tags used by any IDS or IPS are in keeping with the spirit of the invention and the tags shown in FIG. 4 are exemplary only. For example any ports, protocols, severity levels, alarm levels, signature name or any other quantity may be utilized to inform an IDS or IPS of an attack signature.
  • Another embodiment of a system for analyzing and preventing unauthorized intrusion into a computer network is shown in FIG. 5. This embodiment is directed to an improved method and system for analyzing unauthorized intrusion into a decoy computer network, the analysis of which is used to prevent unauthorized access into a protected computer network. An embodiment of such a system is illustrated in FIG. 5, while the method remains as shown in the flowchart in FIG. 2 above.
  • The system 500, as shown in FIG. 5, includes a decoy computer network 502 and a protected computer network 504, each comprising one or more separate computing devices. The decoy computer network 502 includes a virtualized operating system module 506 for monitoring the decoy network 502, and a processing module 508 for obtaining, analyzing, and responding to exploits.
  • These modules may be hosted on the same computing device or on separate computing devices. However, for ease of explanation, these modules will be described below as being hosted on separate computing devices. Furthermore, although not shown, one skilled in the art will appreciate that each of these computing devices may include one or more processors, input/output devices, communication circuitry, power sources, memory (both physical, e.g., RAM, and disks, e.g., hard disk drives), and any other physical hardware necessary for hosting and running the aforementioned modules. In some embodiments, the modules 506 and 508 are as present in physical memory once the system has been booted and is operational.
  • The virtualized operating system module 506 includes a hypervisor operating system 510 (also known as a virtual machine monitor operating system) that provides a virtualization platform that allows multiple virtual operating systems to be run on a host computing device at the same time. In some embodiments, the hypervisor operating system 510 is a LINUX-based system. One or more fully-functioning “guest” virtualized operating systems 512 are run on the hypervisor operating system 510 at a level above the hardware. As will be described in detail below, these virtualized operating systems 512 act as decoy operating systems to attract attacker activity 550. Any operating system may be used as guest decoy operating system 512, including but not limited to WINDOWS, SUN MICROSYSTEMS, SOLARIS, or any version of LINUX known to persons skilled in the art, as well as any combination of the aforementioned. It should be appreciated that all known operating systems are within the scope of the present invention. There is also no limit to either the number of virtualized guest decoy operating systems 512 or the number of virtualized guest operating system modules 506 that may be utilized.
  • Also running on the hypervisor operating system 510 are normal hypervisor operating system userland processes 514. The hypervisor operating system 510 includes a hypervisor kernel 516, which in some embodiments is also Linux-based. The hypervisor kernel 516 is that part of the hypervisor operating system 510 that resides in physical memory at all times and provides the basic services to the hypervisor operating system 510. The hypervisor kernel 516 is the part of the operating system that activates the hardware directly or interfaces with another software layer that, in turn, drives the hardware. The virtualized decoy operating systems 512 access the physical memory assigned to them by the hypervisor operating system via the hypervisor kernel 516.
  • The hypervisor kernel 516 includes a hypervisor virtual machine kernel module 518 that supports virtualization of the “guest” decoy operating systems 512. The hypervisor kernel 516 also includes virtual-machine-based rootkit module 520 coupled to the hypervisor virtual machine kernel module 516. The virtual-machine-based rootkit module 520 is a set of software tools that conceal running processes, files or system data from the virtualized decoy operating systems 512. As described in further detail below, the virtual-machine-based rootkit module 520 is part of introspection module 538, which performs introspection into the physical memory segments assigned to each of the virtualized decoy operating systems 512.
  • Virtual-machine-based rootkit userland processes 522 run on top of the virtual-machine-based rootkit module 520. Together, the rootkit module 520 and its associated userland processes 522 constitute the system's introspection module 538 (described further below). Virtual-machine-based rootkit userland processes 522 also pass data from the introspection module 538 to the processing module 508.
  • In use, attacker activity 550 is directed at the decoy computer network 502 through one or more ports of each of the virtualized decoy operating systems 512 that are left open as a gateway for attacker activity 550. For example, the decoy network 502 can be configured to respond to connection attempts made at network addresses that do not exist on the protected network 504. Connections to these non-existent network addresses are assumed to be malicious, since no production hardware exists on the protected network 504 at these addresses. Decoys 512 (in the form of a virtualized operating system) may be configured to respond to any such non-existent network address. As in a typical attack, the attacker activity 550 scans for an open port, ostensibly in an attempt to make a network connection and then access one or more computing devices on the protected computer network 504. When the attacker activity 550 scans for open ports at non-existent network addresses, however, the attacker is presented with a virtualized decoy operating system 512 instead.
  • When the attacker activity 550 connects to a virtualized decoy operating system 512 through an open port, the attacker sees a fully-functional standard operating system fingerprint. Since the virtualized operating system module 506 can be configured to present any operating system as a fully-functional virtualized decoy 512, responses to connection requests from attacker activity 550 are guaranteed to be authentic for the operating system running on that decoy. For example, an FTP port access request for WINDOWS may return a specific character sequence that differs from an FTP response for LINUX. Similarly, an FTP access request to a WINDOWS port may return a response “>ftp: connect: Connection refused.” This character sequence may be slightly different from that generated by LINUX. Further, different versions of WINDOWS may respond with slightly different, version-specific character sequences. Since attackers often use these sequences to identify what type of operating system is at a particular network address and the version (or range of possible versions) for that operating system, the fact that virtualized decoy operating systems 512 generate authentic responses makes them realistic decoys and encourages intruders to access them. The instigator of the attack 550 is thus lured into accessing the decoy 512, which is overseen by the hypervisor operating system 510 running on the hardware-based, virtualized operating system module 506. Attacker activity 550 may then initiate custom or known exploits for the observed operating system. When the attacker activity 550 proceeds to interact with the decoy 512, the attacker provides the decoy 512 with the data used to obtain control of the decoy 512. These data are recorded and analyzed without the knowledge of the attacker, as described further below.
  • All scans by the attacker activity 550 receive real-world operating system and service information, leading the instigator of the attack 550 to believe that there is a potentially vulnerable system responding. The attacker is thus lured into communicating with virtualized operating system module 506 and its virtualized decoy operating systems and services. Since real hardware is utilized, the attacker is essentially attacking an actual physical system and, therefore, cannot tell that the system is actually an instrumented honeypot that monitors the attacker activity 550 from the introspection module 538 described below.
  • As described above, the virtualized guest operating system module 506 includes the virtual machine-based rootkit module 520 and its associated userland processes 522. Since both the virtual machine-based rootkit module 520 and its associated userland processes 522 run completely outside the virtualized decoy operating systems 512, they remain hidden from the instigator of the attack, with no discoverable impact on the decoy operating systems' 512 performance. In one embodiment, the virtual machine-based rootkit module 520 and its associated userland processes 522 constitute an introspection module 538 (also known as a virtual machine-based memory introspection analysis tool) that monitors and introspects into the virtualized decoy operating systems' memory segments. This occurs from within the hypervisor operating system 510. The introspection module 538 introspects and gathers information on any virtualized operating system supported by the hypervisor operating system 510.
  • The introspection module 538 comprising the virtual-machine-based rootkit module 520 and its associated userland processes 522 examines the memory assigned to virtualized decoy operating systems 512 in order to acquire low-level data about the interaction between the decoy operating systems and attack activity 500. The introspection module 538 examines the memory of virtualized decoy operating systems 512 by means of three functional components: a code region selector, a trace instrumentor, and a trace analyzer. Regular expressions (also known as ‘regex’) are used throughout the process to identify, describe, and profile the contents of the virtualized decoy's memory segments. The code selector identifies regions of code in memory that are of interest for further introspection. Regions of interest may include, but are not limited to, system calls, the arguments of system calls, the returns of system calls, device and memory input-output, driver information, library calls, branching information, instruction pointer jumps, and raw network information. The instrumentor copies the memory traces of interest identified by the code selector and then profiles and instruments them. The trace analyzer takes the instrumented traces and uses them to replay the memory behavior of the decoy operating system 512. In this manner, the introspection module 538 examines the contents of the decoy operating systems' 512 memory segments in an instrumented context that generates and retrieves forensic data for analysis by the processing module 508.
  • When an attacker connects to a network port and begins interacting with a virtualized decoy operating system 512, the introspection module 538 monitors and captures information from the connection, including port numbers, data streams, file uploads, keystrokes, ASCII or binary files, malicious payloads, memory manipulation attempts, and any other data transfers or malicious attempts.
  • The captured information, containing attack-identifying information, is then sent from the introspection module 538 to the processing module 508 by means of a virtual machine-based rootkit userland process 522.
  • The processing module 508 includes an operating system kernel 526, which in some embodiments is also LINUX based. The processing module 508 also includes a database, such as a relational database server 528, and a signature-generation engine 530. In some embodiments, the signature-generation engine 530 communicates with the introspection module 538 over a private network interface communications channel 534 and accepts custom-formatted protocol packets named BAT (Blade Activity Transfer). The private network interface communications channel 524 may be a persistent Layer 3 TCP socket communications link that cannot be seen or accessed by the attacker (such as an IP connection or any other hardware-dependent custom communication protocol known to persons skilled in the art). Thus, the processing module 508 is part of a secure and separate administrative network.
  • In use, the introspection module 538 captures (through introspection) attack information. The attack information is then communicated through the private network interface channel 524 and stored on the relational database server 528 as forensic data for later analysis. The signature-generation engine 530 then uses this forensic data to generate a signature of the attack. The entire process from attack detection through signature generation may occur automatically, i.e., without any human intervention, at a timescale ranging from nearly immediate to several minutes. The intrusion prevention system (described below) uses the attack signature to identify and prevent subsequent attacks.
  • The protected computer network 504 includes an IDS/IPS library of signatures 534 and an IDS/IPS system 542 coupled to multiple protected network devices 536. Suitable IDS/IPS systems 542 include Cisco Systems' IPS 4200 Series, Juniper's IDP 200, and Enterasys' Dragon IDS Network Sensor.
  • In one or more embodiments, the signature may be sent from the back-end processing module 508 to the intrusion detection and/or prevention (IDS/IPS) signature library 534 through a second network connection 540, which is used by the processing module 508 to directly interact with the IDS/IPS system 542. The virtual-machine-based rootkit module 520 may easily clean the virtualized decoy operating system 512 at any time by removing the running system image of the compromised virtualized decoy operating system and replacing it with a pre-attack system image. Thus the virtual-machine-based rootkit module 520 can cleanse or reset the virtualized decoy operating system of any malicious software or payload, removing the possibility that attacker(s) can use that virtualized decoy operating system 512 for further attacks on other networks. In this manner, the attack can be thwarted, and the operating system does not become a tool of the attacker(s). This procedure may also be automated, i.e., may occur without further human intervention.
  • As shown in FIG. 2, processing starts at Step 200 and waits for activity from the introspection module 538 at Step 43. At Step 44, the processing module 508 generates a report of the attack that includes attack-identifying information (See FIG. 3). This report is for review and use by a system administrator responsible for the security of a protected network 504. The attack may contain, but is not limited to, one or more data transfers or keystrokes, which are analyzed at Step 46. By observing whether the attacker is successful in interacting with the system (i.e., if the system is responding in a manner that shows that the attacker has gained access), a determination can be made at Step 48 as to whether an attack signature should be generated, and the attack signature is created at step 52 (See FIG. 4). If the attacker, for example, is unsuccessful at gaining access, or if there is no data transfer, the attack inquiry may be ended at Step 50. Any attack signature generated is sent to the IDS/IPS signature library 534 at Step 56, and processing continues at Step 43.
  • In one embodiment of the invention, the report of the attack is written and then displayed via a visualization interface 532 and can include information about which sockets were accessed by the attack 550, what happened at a particular socket, the keystrokes entered or data transferred, what files were transferred, how the attack 550 was run, what happened on the virtualized operating system module 506, and how the virtualized decoy operating systems 512 running on the hypervisor operating system 510 and any related network services were affected. In some embodiments, the visualization interface 532 is AJAX- and/or FLASH-based. The report may also include information on the location of the instigator of the attack 550 or the service provider used for the attack. Graphical representations of key information and interactive mapping of attack locales by region or country may also be included in the report. The visualization interface may also be used to analyze, configure, and automate the system's response to attack activity 550 on timescales ranging from near-immediate to several minutes from the initiation of an attack.
  • At Step 46, the attack-identifying information is analyzed for known attack patterns as well as non-standard patterns, such as repeating binary patterns, keystroke patterns, downloaded daemons, or errors (such as buffer overflow attempts, malicious payloads attempting to execute arbitrary code on the system, memory overwriting attempts, stack attacks, and heap attacks). By observing the operations performed on the decoy operating system(s) 512, the attack 550 may be categorized and analyzed to determine, for example, how an attack gained control of the decoy operating system(s) 512. Any method of analyzing the incoming data such as binary matching, neural-network matching, keyword matching, or any other method of matching attack-identifying information is in keeping with the spirit of the invention. Pattern-matching techniques involving neural networks, for example, are characterized in Carl Looney's Pattern Recognition Using Neural Networks. Theory and Algorithms for Engineers and Scientists (Oxford University Press USA, New York, N.Y., 1997) and Christopher Bishop's Neural Networks for Pattern Recognition (Oxford University Press USA, New York, N.Y., 1995), among other sources familiar to those skilled in the art.
  • At Step 48, a decision is made as to whether to generate an attack signature. If no harmful operations occurred as a result of an attack, or when no known attack patterns are found, then no further attack inquiry would be needed (as shown at Step 50). The processing module 508 may then take on the next input of captured information from the introspection module 538 running on the hardware-based, virtualized operating system module 506.
  • If a determination is made that attack signature generation is warranted, an attack signature is generated as illustrated in Step 52. In one or more embodiments of the invention, the processing module 508 may generate a signature whenever data is found to be transferred through the socket. Alternatively, if the attack signature already exists, or if the data transfer is of a nature that indicates probing rather than attack, then the attack signature may not be generated. For example, the processing module 508 may not generate a signature when it is found that no data has been transferred through the socket, even though the socket may have been opened and closed. The conditions under which the processing module 508 generates an attack can be configured and automated by an administrator. Once the attack signature is generated, the signature can be reviewed by the system administrator, who decides whether to send the attack signature (shown at Step 56) to the intrusion detection system (IDS) or intrusion prevention system (IPS) for the protected network 504. The attack signature is sent through a standard network connection or via a wireless connection and is generally sent on a private portion of the protected network 504 that the attacker cannot observe. The generated attack signature is thus applied to the IDS/IPS library of signatures 534, thereby updating the information contained in the signature library and preventing the attacker from accessing the protected network 504.
  • Embodiments of the invention may save the attack signatures created at Step 52 in a relational database server 528 for future use or analysis by system administrators. The signatures may also be sent to a proprietary global database of attack signatures for further analysis, storage, and distribution. Any IDS/IPS system may be utilized in one or more embodiments of the invention. The invention may be interfaced with existing IDS/IPS systems, for example to integrate it with existing solutions.
  • As explained above, FIG. 3 illustrates a human-readable summary of an example attack. Line 300 shows that the file “msprexe.exe” is copied into the “System” directory. Line 301 shows a first registry entry created by the attack. Line 302 shows a second registry entry created by the attack. Any other changes to the system may be shown as part of the attack-identifying information, and the information shown in FIG. 3 is exemplary only.
  • As explained above, FIG. 4 illustrates an attack signature generated from the attack summarized in FIG. 3 and formatted in XML for transmission to an IDS or IPS. XML Block 400 includes tags that define the attack signature in the format of the particular IDS or IPS. Any tags used by any IDS or IPS are in keeping with the spirit of the invention, and the tags shown in FIG. 4 are exemplary only. For example, any ports, protocols, severity levels, alarm levels, signature name, or any other quantity, may be utilized to inform an IDS or IPS of an attack signature.
  • While embodiments and alternatives have been disclosed and discussed, the invention herein is not limited to the particular disclosed embodiments or alternatives but encompasses the full breadth and scope of the invention including equivalents, and the invention is not limited except as set forth in and encompassed by the full breadth and scope of the claims herein.

Claims (23)

What is claimed is:
1. A method for analyzing unauthorized intrusion into a computer network, the method comprising:
allowing access to an apparently vulnerable virtualized decoy operating system running on a hypervisor operating system hosted on a decoy network device;
using an introspection module comprising a virtual-machine-based rootkit module and its associated userland processes running on the hypervisor operating system to intercept a network attack on the virtualized operating system, wherein the network attack includes attack-identifying information; and
generating forensic data on the network attack from the attack-identifying information.
2. The method of claim 1, further comprising:
generating an attack signature from the forensic data; and
providing the attack signature to an intrusion prevention system configured to control access to a protected network using the attack signature to identify subsequent attacks.
3. The method of claim 2, further comprising controlling access to the protected network using the attack signature.
4. The method of claim 2, wherein the attack signature is automatically generated by the system without human intervention.
5. The method of claim 1, further comprising, before the allowing, opening a port on the virtualized decoy operating system through which the network attack is made.
6. The method of claim 1, further comprising:
allowing access to an additional virtualized decoy operating system running on the hypervisor operating system;
using the virtual-machine-based rootkit module to intercept an additional network attack on the additional virtualized operating system, wherein the additional network attack includes additional attack-identifying information; and
generating additional forensic data on the additional network attack from the additional attack-identifying information.
7. The method of claim 6, further comprising:
generating an additional attack signature from the additional forensic data; and
providing the additional attack signature to an intrusion prevention system configured to control access to a protected network using the attack-identifying information.
8. The method of claim 1, wherein the virtualized decoy operating system and the additional virtualized decoy operating system are different types of operating systems.
9. The method of claim 1, wherein said forensic data is generated based on an attack payload including keystrokes, ASCII, or binary files.
10. The method of claim 1, wherein the attack forensics are generated if an attacker is able to successfully gain access to the virtualized decoy operating system.
11. The method of claim 1, further comprising providing a report of said network attack to a network administrator.
12. The method of claim 1, further comprising storing the attack forensics in a database.
13. A system for analyzing unauthorized intrusion into a computer network, the system comprising:
a virtualized operating system module comprising:
a hypervisor operating system comprising:
at least one virtualized decoy operating system;
a virtual-machine-based rootkit configured to intercept a network attack on the virtualized operating system, wherein the network attack includes transmission of attack-identifying information; and
a processing module electrically coupled to the introspection module via a network interface communication channel, wherein the processing module comprises: a database configured to store forensic data on the network attack.
14. The system of claim 13, wherein the processing module further comprises an attack signature-generation engine configured to generate an attack signature from the forensic data on the network attack, wherein attack signatures may be generated on a timescale ranging from near-immediate to several minutes after initiation of an attack.
15. The system of claim 14, wherein the processing module further comprises a web-based visualization interface that facilitates configuration of the system and forensic analysis of captured attack information by administrators.
16. The system of claim 15, further comprising an intrusion prevention system electrically coupled to the signature-generation engine.
17. The system of claim 13, wherein the intrusion detection system is configured to prevent unauthorized intrusion into a protected computer network.
18. The system of claim 13, wherein the network interface communication channel is a private channel.
19. The system of claim 13, wherein the virtualized operating system module includes multiple virtualized decoy operating systems on the hypervisor operating system.
20. The system of claim 13, wherein the attack forensics are based on an attack payload including keystrokes or ASCII or binary files.
21. The system of claim 13, wherein the virtualized operating system module and the processing module are contained in memory on the same or separate computing devices that each includes a processor.
22. A computing device configured for analyzing unauthorized intrusion into a computer network, the device comprising:
a processor; and
memory coupled to the processor, wherein the memory comprises procedures for:
allowing access to a virtualized decoy operating system running on a hypervisor operating system hosted on a decoy network device;
using an introspection module running on the hypervisor operating system to intercept a network attack on the virtualized operating system, wherein the network attack includes attack-identifying information; and
generating forensic data on the network attack from the attack-identifying information.
23. The computing device of claim 22, further comprising a web-based visualization module comprising procedures for:
analyzing forensic data generated by the introspection module and the signature generation engine, as well as that stored in the processing module's relational databases; and
configuring the system, wherein an administrator can tune the system's behavior, including its pattern matching facilities, as well as automate the system's response to attack-identifying information captured by the introspection module and automate its response to forensic data generated by the signature-generation engine and any information stored on the processing module's relational databases.
US11/788,795 2006-05-22 2007-04-20 System and method for analyzing unauthorized intrusion into a computer network Abandoned US20140373144A9 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US80254306P true 2006-05-22 2006-05-22
US11/488,743 US8429746B2 (en) 2006-05-22 2006-07-17 Decoy network technology with automatic signature generation for intrusion detection and intrusion prevention systems
US11/788,795 US20140373144A9 (en) 2006-05-22 2007-04-20 System and method for analyzing unauthorized intrusion into a computer network

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US11/788,795 US20140373144A9 (en) 2006-05-22 2007-04-20 System and method for analyzing unauthorized intrusion into a computer network
CA2689126A CA2689126C (en) 2007-04-20 2008-04-15 System and method for analyzing unauthorized intrusion into a computer network
CA3013171A CA3013171A1 (en) 2007-04-20 2008-04-15 System and method for analyzing unauthorized intrusion into a computer network
EP15174670.8A EP2953049B1 (en) 2007-04-20 2008-04-15 System and method for analyzing unathorized intrusion into a computer network
PCT/US2008/060336 WO2008130923A1 (en) 2007-04-20 2008-04-15 System and method for analyzing unauthorized intrusion into a computer network
JP2010504185A JP5351883B2 (en) 2007-04-20 2008-04-15 System and method for analyzing unauthorized intrusion into a computer network
EP08745858.4A EP2149087B1 (en) 2007-04-20 2008-04-15 System and method for analyzing unauthorized intrusion into a computer network
AU2008242296A AU2008242296B2 (en) 2007-04-20 2008-04-15 System and method for analyzing unauthorized intrusion into a computer network
JP2013173175A JP5579907B2 (en) 2007-04-20 2013-08-23 System and method for analyzing unauthorized intrusion into a computer network
US14/542,376 US9866584B2 (en) 2006-05-22 2014-11-14 System and method for analyzing unauthorized intrusion into a computer network

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/488,743 Continuation-In-Part US8429746B2 (en) 2006-05-22 2006-07-17 Decoy network technology with automatic signature generation for intrusion detection and intrusion prevention systems

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/542,376 Continuation US9866584B2 (en) 2006-05-22 2014-11-14 System and method for analyzing unauthorized intrusion into a computer network

Publications (2)

Publication Number Publication Date
US20080016570A1 US20080016570A1 (en) 2008-01-17
US20140373144A9 true US20140373144A9 (en) 2014-12-18

Family

ID=38950746

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/788,795 Abandoned US20140373144A9 (en) 2006-05-22 2007-04-20 System and method for analyzing unauthorized intrusion into a computer network
US14/542,376 Active US9866584B2 (en) 2006-05-22 2014-11-14 System and method for analyzing unauthorized intrusion into a computer network

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/542,376 Active US9866584B2 (en) 2006-05-22 2014-11-14 System and method for analyzing unauthorized intrusion into a computer network

Country Status (6)

Country Link
US (2) US20140373144A9 (en)
EP (2) EP2149087B1 (en)
JP (2) JP5351883B2 (en)
AU (1) AU2008242296B2 (en)
CA (2) CA3013171A1 (en)
WO (1) WO2008130923A1 (en)

Families Citing this family (107)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007050244A2 (en) 2005-10-27 2007-05-03 Georgia Tech Research Corporation Method and system for detecting and responding to attacking networks
US20120144485A9 (en) 2005-12-12 2012-06-07 Finjan Software, Ltd. Computer security method and system with input parameter validation
US8009566B2 (en) 2006-06-26 2011-08-30 Palo Alto Networks, Inc. Packet classification in a network security device
US8949827B2 (en) * 2007-06-22 2015-02-03 Red Hat, Inc. Tracking a virtual machine
US8127290B2 (en) * 2007-06-22 2012-02-28 Red Hat, Inc. Method and system for direct insertion of a virtual machine driver
US8984504B2 (en) * 2007-06-22 2015-03-17 Red Hat, Inc. Method and system for determining a host machine by a virtual machine
US9678803B2 (en) 2007-06-22 2017-06-13 Red Hat, Inc. Migration of network entities to a cloud infrastructure
US8539570B2 (en) 2007-06-22 2013-09-17 Red Hat, Inc. Method for managing a virtual machine
US9495152B2 (en) 2007-06-22 2016-11-15 Red Hat, Inc. Automatic baselining of business application service groups comprised of virtual machines
US8429748B2 (en) * 2007-06-22 2013-04-23 Red Hat, Inc. Network traffic analysis using a dynamically updating ontological network description
US9727440B2 (en) 2007-06-22 2017-08-08 Red Hat, Inc. Automatic simulation of virtual machine performance
US8191141B2 (en) * 2007-06-22 2012-05-29 Red Hat, Inc. Method and system for cloaked observation and remediation of software attacks
US8336108B2 (en) * 2007-06-22 2012-12-18 Red Hat, Inc. Method and system for collaboration involving enterprise nodes
US9569330B2 (en) 2007-06-22 2017-02-14 Red Hat, Inc. Performing dependency analysis on nodes of a business application service group
US8122505B2 (en) * 2007-08-17 2012-02-21 International Business Machines Corporation Method and apparatus for detection of malicious behavior in mobile ad-hoc networks
US8156541B1 (en) * 2007-10-17 2012-04-10 Mcafee, Inc. System, method, and computer program product for identifying unwanted activity utilizing a honeypot device accessible via VLAN trunking
US8806629B1 (en) * 2008-01-02 2014-08-12 Cisco Technology, Inc. Automatic generation of policy-driven anti-malware signatures and mitigation of DoS (denial-of-service) attacks
JP4983671B2 (en) * 2008-03-19 2012-07-25 沖電気工業株式会社 Traffic analyzer traffic analysis methods and traffic analysis system
US9264441B2 (en) 2008-03-24 2016-02-16 Hewlett Packard Enterprise Development Lp System and method for securing a network from zero-day vulnerability exploits
US7844744B2 (en) * 2008-04-25 2010-11-30 International Business Machines Corporation Providing server security via a security sensor application shared by multiple operating system partitions
US10027688B2 (en) 2008-08-11 2018-07-17 Damballa, Inc. Method and system for detecting malicious and/or botnet-related domain names
US9117078B1 (en) * 2008-09-17 2015-08-25 Trend Micro Inc. Malware behavior analysis and policy creation
US8484739B1 (en) * 2008-12-15 2013-07-09 Symantec Corporation Techniques for securely performing reputation based analysis using virtualization
US8474044B2 (en) * 2009-01-05 2013-06-25 Cisco Technology, Inc Attack-resistant verification of auto-generated anti-malware signatures
US9231964B2 (en) * 2009-04-14 2016-01-05 Microsoft Corporation Vulnerability detection based on aggregated primitives
US8578497B2 (en) * 2010-01-06 2013-11-05 Damballa, Inc. Method and system for detecting malware
US8826438B2 (en) 2010-01-19 2014-09-02 Damballa, Inc. Method and system for network-based detecting of malware from behavioral clustering
US9369437B2 (en) 2010-04-01 2016-06-14 Cloudflare, Inc. Internet-based proxy service to modify internet responses
US9049247B2 (en) 2010-04-01 2015-06-02 Cloudfare, Inc. Internet-based proxy service for responding to server offline errors
CN102947814B (en) * 2010-06-10 2016-08-03 惠普发展公司,有限责任合伙企业 virtual machine
US20120023572A1 (en) * 2010-07-23 2012-01-26 Q-Track Corporation Malicious Attack Response System and Associated Method
US8752174B2 (en) 2010-12-27 2014-06-10 Avaya Inc. System and method for VoIP honeypot for converged VoIP services
US9354960B2 (en) 2010-12-27 2016-05-31 Red Hat, Inc. Assigning virtual machines to business application service groups based on ranking of the virtual machines
JP5697206B2 (en) * 2011-03-31 2015-04-08 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation System for protection against unauthorized access, method and program
US8285808B1 (en) 2011-05-20 2012-10-09 Cloudflare, Inc. Loading of web resources
US8695096B1 (en) 2011-05-24 2014-04-08 Palo Alto Networks, Inc. Automatic signature generation for malicious PDF files
US9047441B2 (en) * 2011-05-24 2015-06-02 Palo Alto Networks, Inc. Malware analysis system
JP5713445B2 (en) * 2011-06-24 2015-05-07 日本電信電話株式会社 Communication monitoring system and method and a communication monitoring device and the virtual host apparatus and communication monitoring program
US10356106B2 (en) 2011-07-26 2019-07-16 Palo Alto Networks (Israel Analytics) Ltd. Detecting anomaly action within a computer network
CN103034806B (en) * 2011-09-30 2016-08-10 腾讯科技(深圳)有限公司 The method of processing operation of the terminal and
US9792430B2 (en) * 2011-11-03 2017-10-17 Cyphort Inc. Systems and methods for virtualized malware detection
US10326778B2 (en) 2014-02-24 2019-06-18 Cyphort Inc. System and method for detecting lateral movement and data exfiltration
US10095866B2 (en) 2014-02-24 2018-10-09 Cyphort Inc. System and method for threat risk scoring of security threats
US9749285B2 (en) * 2011-12-08 2017-08-29 Honeywell International Inc. Connected home control system with auto router port configuration and DDNS registration
US8881145B2 (en) * 2011-12-15 2014-11-04 Industrial Technology Research Institute System and method for generating application-level dependencies in one or more virtual machines
US9922190B2 (en) 2012-01-25 2018-03-20 Damballa, Inc. Method and system for detecting DGA-based malware
JP2013236687A (en) * 2012-05-11 2013-11-28 We Are Engineering Kk Computer game
WO2014004747A2 (en) 2012-06-26 2014-01-03 Lynuxworks, Inc. Systems and methods involving features of hardware virtualization such as separation kernel hypervisors, hypervisors, hypervisor guest context, hypervisor context, rootkit detection/prevention, and/or other features
US9894088B2 (en) 2012-08-31 2018-02-13 Damballa, Inc. Data mining to identify malicious activity
US10084806B2 (en) 2012-08-31 2018-09-25 Damballa, Inc. Traffic simulation to identify malicious activity
US8955143B1 (en) * 2012-09-04 2015-02-10 Amazon Technologies, Inc. Use of decoy data in a data store
US9292688B2 (en) 2012-09-26 2016-03-22 Northrop Grumman Systems Corporation System and method for automated machine-learning, zero-day malware detection
US9003088B2 (en) * 2012-12-06 2015-04-07 Dell Products L.P. Mapping virtual devices to computing nodes
EP2946332B1 (en) 2013-01-16 2018-06-13 Palo Alto Networks (Israel Analytics) Ltd Automated forensics of computer systems using behavioral intelligence
US9332028B2 (en) * 2013-01-25 2016-05-03 REMTCS Inc. System, method, and apparatus for providing network security
US9525700B1 (en) 2013-01-25 2016-12-20 REMTCS Inc. System and method for detecting malicious activity and harmful hardware/software modifications to a vehicle
US9165142B1 (en) * 2013-01-30 2015-10-20 Palo Alto Networks, Inc. Malware family identification using profile signatures
US8875295B2 (en) * 2013-02-22 2014-10-28 Bitdefender IPR Management Ltd. Memory introspection engine for integrity protection of virtual machines
KR101394424B1 (en) * 2013-04-22 2014-05-13 한국인터넷진흥원 Hypervisor-based intrusion prevention platform and virtual network intrusion prevention system
WO2014179805A1 (en) * 2013-05-03 2014-11-06 Webroot Inc. Method and apparatus for providing forensic visibility into systems and networks
US9571511B2 (en) 2013-06-14 2017-02-14 Damballa, Inc. Systems and methods for traffic classification
US8943594B1 (en) 2013-06-24 2015-01-27 Haystack Security LLC Cyber attack disruption through multiple detonations of received payloads
US9852290B1 (en) 2013-07-12 2017-12-26 The Boeing Company Systems and methods of analyzing a software component
US9336025B2 (en) 2013-07-12 2016-05-10 The Boeing Company Systems and methods of analyzing a software component
US9280369B1 (en) 2013-07-12 2016-03-08 The Boeing Company Systems and methods of analyzing a software component
US9396082B2 (en) 2013-07-12 2016-07-19 The Boeing Company Systems and methods of analyzing a software component
US9479521B2 (en) 2013-09-30 2016-10-25 The Boeing Company Software network behavior analysis and identification system
US9246935B2 (en) 2013-10-14 2016-01-26 Intuit Inc. Method and system for dynamic and comprehensive vulnerability management
US10075460B2 (en) 2013-10-16 2018-09-11 REMTCS Inc. Power grid universal detection and countermeasure overlay intelligence ultra-low latency hypervisor
US9619346B2 (en) 2013-10-31 2017-04-11 Assured Information Security, Inc. Virtual machine introspection facilities
US9313281B1 (en) 2013-11-13 2016-04-12 Intuit Inc. Method and system for creating and dynamically deploying resource specific discovery agents for determining the state of a cloud computing environment
US9501345B1 (en) 2013-12-23 2016-11-22 Intuit Inc. Method and system for creating enriched log data
US9323926B2 (en) * 2013-12-30 2016-04-26 Intuit Inc. Method and system for intrusion and extrusion detection
US20150205962A1 (en) * 2014-01-23 2015-07-23 Cylent Systems, Inc. Behavioral analytics driven host-based malicious behavior and data exfiltration disruption
US9325726B2 (en) 2014-02-03 2016-04-26 Intuit Inc. Method and system for virtual asset assisted extrusion and intrusion detection in a cloud computing environment
US10225280B2 (en) 2014-02-24 2019-03-05 Cyphort Inc. System and method for verifying and detecting malware
US9245117B2 (en) 2014-03-31 2016-01-26 Intuit Inc. Method and system for comparing different versions of a cloud based application in a production environment using segregated backend systems
US9276945B2 (en) 2014-04-07 2016-03-01 Intuit Inc. Method and system for providing security aware applications
US20150304343A1 (en) 2014-04-18 2015-10-22 Intuit Inc. Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
US9374389B2 (en) 2014-04-25 2016-06-21 Intuit Inc. Method and system for ensuring an application conforms with security and regulatory controls prior to deployment
US9319415B2 (en) 2014-04-30 2016-04-19 Intuit Inc. Method and system for providing reference architecture pattern-based permissions management
US9900322B2 (en) 2014-04-30 2018-02-20 Intuit Inc. Method and system for providing permissions management
WO2015176029A1 (en) 2014-05-15 2015-11-19 Lynx Software Technologies, Inc. Systems and methods involving features of hardware virtualization such as hypervisor, pages of interest, and/or other features
CA2969422A1 (en) 2014-05-15 2015-11-19 Lynx Software Technologies Inc. Systems and methods involving features of hardware virtualization, hypervisor, apis of interest, and/or other features
WO2015176048A1 (en) 2014-05-15 2015-11-19 Lynx Software Technologies, Inc. Aspects of hardware virtualization, hypervisors, code detection
US9330263B2 (en) 2014-05-27 2016-05-03 Intuit Inc. Method and apparatus for automating the building of threat models for the public cloud
US9866581B2 (en) 2014-06-30 2018-01-09 Intuit Inc. Method and system for secure delivery of information to computing environments
US9851998B2 (en) * 2014-07-30 2017-12-26 Microsoft Technology Licensing, Llc Hypervisor-hosted virtual machine forensics
US10102082B2 (en) 2014-07-31 2018-10-16 Intuit Inc. Method and system for providing automated self-healing virtual assets
US9473481B2 (en) 2014-07-31 2016-10-18 Intuit Inc. Method and system for providing a virtual asset perimeter
US9832216B2 (en) 2014-11-21 2017-11-28 Bluvector, Inc. System and method for network data characterization
US9930065B2 (en) 2015-03-25 2018-03-27 University Of Georgia Research Foundation, Inc. Measuring, categorizing, and/or mitigating malware distribution paths
US10075461B2 (en) 2015-05-31 2018-09-11 Palo Alto Networks (Israel Analytics) Ltd. Detection of anomalous administrative actions
US9553885B2 (en) 2015-06-08 2017-01-24 Illusive Networks Ltd. System and method for creation, deployment and management of augmented attacker map
US9996374B2 (en) 2015-06-16 2018-06-12 Assured Information Security, Inc. Deployment and installation of updates in a virtual environment
US10270807B2 (en) * 2015-07-21 2019-04-23 Cymmetria, Inc. Decoy and deceptive data object technology
AU2016313409A1 (en) * 2015-08-25 2018-03-15 Volexity, Inc. Systems methods and devices for memory analysis and visualization
US9742804B2 (en) * 2015-10-28 2017-08-22 National Technology & Engineering Solutions Of Sandia, Llc Computer network defense system
US10142365B2 (en) * 2016-01-22 2018-11-27 The Boeing Company System and methods for responding to cybersecurity threats
CN105721446A (en) * 2016-01-26 2016-06-29 浪潮电子信息产业股份有限公司 Remote desktop anti-brute force attack intercepting method based on WINDOWS operating system
US10284598B2 (en) 2016-01-29 2019-05-07 Sophos Limited Honeypot network services
US10257226B2 (en) * 2016-03-24 2019-04-09 802 Secure, Inc. Identifying and trapping wireless based attacks on networks using deceptive network emulation
WO2017216735A1 (en) * 2016-06-14 2017-12-21 Cymmetria, Inc. Employing code signing as a tool in cyber-security deception
US20180324214A1 (en) * 2017-05-08 2018-11-08 Micron Technology, Inc. Crypto-Ransomware Compromise Detection
US10333951B1 (en) * 2017-07-31 2019-06-25 EMC IP Holding Company LLC Method and system for implementing golden container storage
US10333976B1 (en) 2018-07-23 2019-06-25 Illusive Networks Ltd. Open source intelligence deceptions
US10333977B1 (en) 2018-08-23 2019-06-25 Illusive Networks Ltd. Deceiving an attacker who is harvesting credentials

Family Cites Families (75)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5297282A (en) * 1991-05-29 1994-03-22 Toshiba America Information Systems, Inc. Resume processing function for the OS/2 operating system
US5664159A (en) * 1994-03-08 1997-09-02 Exponential Technology, Inc. Method for emulating multiple debug breakpoints by page partitioning using a single breakpoint register
US5740413A (en) * 1995-06-19 1998-04-14 Intel Corporation Method and apparatus for providing address breakpoints, branch breakpoints, and single stepping
US5621886A (en) * 1995-06-19 1997-04-15 Intel Corporation Method and apparatus for providing efficient software debugging
US6009274A (en) * 1996-12-13 1999-12-28 3Com Corporation Method and apparatus for automatically updating software components on end systems over a network
US6279113B1 (en) 1998-03-16 2001-08-21 Internet Tools, Inc. Dynamic signature inspection-based network intrusion detection
US6343280B2 (en) * 1998-12-15 2002-01-29 Jonathan Clark Distributed execution software license server
US6519645B2 (en) * 1999-02-19 2003-02-11 International Business Machine Corporation Method and apparatus for providing configuration information using a queued direct input-output device
US6360327B1 (en) * 1999-03-12 2002-03-19 Compaq Information Technologies Group, L.P. System with control registers for managing computer legacy peripheral devices using an advanced configuration power interface software power management system
US6446062B1 (en) * 1999-12-23 2002-09-03 Bull Hn Information Systems Inc. Method and apparatus for improving the performance of a generated code cache search operation through the use of static key values
WO2002008870A2 (en) * 2000-07-26 2002-01-31 David Dickenson Distributive access controller
WO2002071227A1 (en) * 2001-03-01 2002-09-12 Cyber Operations, Llc System and method for anti-network terrorism
US6792514B2 (en) * 2001-06-14 2004-09-14 International Business Machines Corporation Method, system and computer program product to stress and test logical partition isolation features
GB0118294D0 (en) * 2001-07-27 2001-09-19 Ibm Method and system for deadlock detection and avoidance
US7398389B2 (en) * 2001-12-20 2008-07-08 Coretrace Corporation Kernel-based network security infrastructure
US7222366B2 (en) * 2002-01-28 2007-05-22 International Business Machines Corporation Intrusion event filtering
US20080177994A1 (en) * 2003-01-12 2008-07-24 Yaron Mayer System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows
US20030229794A1 (en) * 2002-06-07 2003-12-11 Sutton James A. System and method for protection against untrusted system management code by redirecting a system management interrupt and creating a virtual machine container
JP3794491B2 (en) * 2002-08-20 2006-07-05 日本電気株式会社 Attack defense system and Allegations
RU2005115083A (en) * 2002-11-18 2006-01-20 Арм Лимитед (Gb) Switching the processor between protected and unprotected modes
GB2396930B (en) * 2002-11-18 2005-09-07 Advanced Risc Mach Ltd Apparatus and method for managing access to a memory
CN1761939A (en) * 2003-03-17 2006-04-19 精工爱普生株式会社 Method and system for preventing virus infection
US20040225877A1 (en) * 2003-05-09 2004-11-11 Zezhen Huang Method and system for protecting computer system from malicious software operation
US7392543B2 (en) * 2003-06-30 2008-06-24 Symantec Corporation Signature extraction system and method
BR0318459A (en) 2003-08-11 2006-09-12 Telecom Italia Spa intrusion detection system and method for detecting unauthorized use of a communications network
US8776050B2 (en) 2003-08-20 2014-07-08 Oracle International Corporation Distributed virtual machine monitor for managing multiple virtual resources across multiple physical nodes
US20050229250A1 (en) * 2004-02-26 2005-10-13 Ring Sandra E Methodology, system, computer readable medium, and product providing a security software suite for handling operating system exploitations
US8584239B2 (en) * 2004-04-01 2013-11-12 Fireeye, Inc. Virtual machine with dynamic data flow analysis
US8171553B2 (en) * 2004-04-01 2012-05-01 Fireeye, Inc. Heuristic based capture with replay to virtual machine
US8375444B2 (en) * 2006-04-20 2013-02-12 Fireeye, Inc. Dynamic signature creation and enforcement
US8539582B1 (en) * 2004-04-01 2013-09-17 Fireeye, Inc. Malware containment and security analysis on connection
JP2005316779A (en) * 2004-04-28 2005-11-10 Intelligent Cosmos Research Institute Unauthorized access detector, detection rule generation device, detection rule generation method, and detection rule generation program
US7748040B2 (en) * 2004-07-12 2010-06-29 Architecture Technology Corporation Attack correlation using marked information
US7627898B2 (en) 2004-07-23 2009-12-01 Microsoft Corporation Method and system for detecting infection of an operating system
US20060101516A1 (en) * 2004-10-12 2006-05-11 Sushanthan Sudaharan Honeynet farms as an early warning system for production networks
US7409719B2 (en) * 2004-12-21 2008-08-05 Microsoft Corporation Computer security management, such as in a virtual machine or hardened operating system
JP2006243878A (en) * 2005-03-01 2006-09-14 Matsushita Electric Ind Co Ltd Unauthorized access detection system
CA2604896C (en) * 2005-04-18 2012-04-03 Research In Motion Limited System and method of data source detection
AU2006236283A1 (en) 2005-04-18 2006-10-26 The Trustees Of Columbia University In The City Of New York Systems and methods for detecting and inhibiting attacks using honeypots
US7571482B2 (en) * 2005-06-28 2009-08-04 Microsoft Corporation Automated rootkit detector
JP4955943B2 (en) * 2005-06-28 2012-06-20 クラリオン株式会社 Information terminal and computer resource management method
US8327353B2 (en) * 2005-08-30 2012-12-04 Microsoft Corporation Hierarchical virtualization with a multi-level virtualization mechanism
JP2007079815A (en) * 2005-09-13 2007-03-29 Canon Inc Autoimmune protection system
US7743418B2 (en) * 2005-10-31 2010-06-22 Microsoft Corporation Identifying malware that employs stealth techniques
US8544058B2 (en) 2005-12-29 2013-09-24 Nextlabs, Inc. Techniques of transforming policies to enforce control in an information management system
US20070174429A1 (en) * 2006-01-24 2007-07-26 Citrix Systems, Inc. Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment
US7596654B1 (en) * 2006-01-26 2009-09-29 Symantec Operating Corporation Virtual machine spanning multiple computers
US7757290B2 (en) * 2006-01-30 2010-07-13 Microsoft Corporation Bypassing software services to detect malware
WO2007117585A2 (en) * 2006-04-06 2007-10-18 Smobile Systems Inc. System and method for managing malware protection on mobile devices
US20080016571A1 (en) * 2006-07-11 2008-01-17 Larry Chung Yao Chang Rootkit detection system and method
US8949826B2 (en) 2006-10-17 2015-02-03 Managelq, Inc. Control and management of virtual systems
US20080127114A1 (en) * 2006-11-28 2008-05-29 Amit Vasudevan Framework for stealth dynamic coarse and fine-grained malware analysis
US7996836B1 (en) * 2006-12-29 2011-08-09 Symantec Corporation Using a hypervisor to provide computer security
US20080222729A1 (en) 2007-03-05 2008-09-11 Songqing Chen Containment of Unknown and Polymorphic Fast Spreading Worms
US8631147B2 (en) 2007-03-12 2014-01-14 Citrix Systems, Inc. Systems and methods for configuring policy bank invocations
US20080320594A1 (en) * 2007-03-19 2008-12-25 Xuxian Jiang Malware Detector
US8560634B2 (en) * 2007-10-17 2013-10-15 Dispersive Networks, Inc. Apparatus, systems and methods utilizing dispersive networking
US9154386B2 (en) * 2008-06-06 2015-10-06 Tdi Technologies, Inc. Using metadata analysis for monitoring, alerting, and remediation
US8260751B2 (en) * 2008-08-12 2012-09-04 Tdi Technologies, Inc. Log file time sequence stamping
US20100095281A1 (en) * 2008-10-14 2010-04-15 Riverside Research Institute Internal Function Debugger
US20100153693A1 (en) 2008-12-17 2010-06-17 Microsoft Corporation Code execution with automated domain switching
US8505103B2 (en) * 2009-09-09 2013-08-06 Fujitsu Limited Hardware trust anchor
US20110126197A1 (en) * 2009-11-25 2011-05-26 Novell, Inc. System and method for controlling cloud and virtualized data centers in an intelligent workload management system
US8572613B1 (en) * 2009-12-28 2013-10-29 Amazon Technologies, Inc. Comparison of virtual computing states by performing identified repeatable computations in a changing virtual computing environment
US20110239291A1 (en) * 2010-03-26 2011-09-29 Barracuda Networks, Inc. Detecting and Thwarting Browser-Based Network Intrusion Attacks For Intellectual Property Misappropriation System and Method
CN102447723B (en) 2010-10-12 2015-09-09 运软网络科技(上海)有限公司 Client virtualization architecture
US8959492B2 (en) 2010-12-14 2015-02-17 Ngmoco, Llc Communication protocol between a high-level language and a native language
US20120179904A1 (en) * 2011-01-11 2012-07-12 Safenet, Inc. Remote Pre-Boot Authentication
US9027024B2 (en) * 2012-05-09 2015-05-05 Rackspace Us, Inc. Market-based virtual machine allocation
US8813227B2 (en) 2011-03-29 2014-08-19 Mcafee, Inc. System and method for below-operating system regulation and control of self-modifying code
US9262246B2 (en) 2011-03-31 2016-02-16 Mcafee, Inc. System and method for securing memory and storage of an electronic device with a below-operating system security agent
US8683548B1 (en) * 2011-09-30 2014-03-25 Emc Corporation Computing with policy engine for multiple virtual machines
US20130238785A1 (en) * 2012-03-06 2013-09-12 Rackspace Us, Inc. System and Method for Metadata Discovery and Metadata-Aware Scheduling
US9141408B2 (en) * 2012-07-20 2015-09-22 Sonatype, Inc. Method and system for correcting portion of software application
US9003408B2 (en) 2012-09-28 2015-04-07 Adventium Enterprises Providing virtual machine services by isolated virtual machines

Also Published As

Publication number Publication date
EP2953049A1 (en) 2015-12-09
JP5351883B2 (en) 2013-11-27
US20080016570A1 (en) 2008-01-17
AU2008242296B2 (en) 2012-06-14
JP5579907B2 (en) 2014-08-27
US20150074811A1 (en) 2015-03-12
AU2008242296A1 (en) 2008-10-30
EP2149087A1 (en) 2010-02-03
JP2010525459A (en) 2010-07-22
WO2008130923A1 (en) 2008-10-30
CA2689126A1 (en) 2008-10-30
CA2689126C (en) 2018-09-11
CA3013171A1 (en) 2008-10-30
EP2953049B1 (en) 2016-09-14
EP2149087A4 (en) 2014-07-09
EP2149087B1 (en) 2015-08-05
JP2013240114A (en) 2013-11-28
US9866584B2 (en) 2018-01-09

Similar Documents

Publication Publication Date Title
Modi et al. A survey of intrusion detection techniques in cloud
Jiang et al. Collapsar: A VM-Based Architecture for Network Attack Detention Center.
US8135657B2 (en) Systems and methods for processing data flows
US9525696B2 (en) Systems and methods for processing data flows
US7870612B2 (en) Antivirus protection system and method for computers
Baecher et al. The nepenthes platform: An efficient approach to collect malware
US9792430B2 (en) Systems and methods for virtualized malware detection
US7979368B2 (en) Systems and methods for processing data flows
US9971891B2 (en) Methods, systems, and media for detecting covert malware
US9916440B1 (en) Detection efficacy of virtual machine-based analysis with application specific events
US8819825B2 (en) Systems, methods, and media for generating bait information for trap-based defenses
Stinson et al. Characterizing bots’ remote control behavior
US7788723B2 (en) Method and apparatus for identifying computer vulnerabilities using exploit probes and remote scanning
US9594881B2 (en) System and method for passive threat detection using virtual memory inspection
US9338174B2 (en) Systems and methods for inhibiting attacks on applications
US8006305B2 (en) Computer worm defense system and method
US20110320816A1 (en) Systems and method for malware detection
WO2011105659A1 (en) System, method, program, and recording medium for real-time detection and blocking of harmful programs through behavioral analysis of a process
Castaneda et al. WORM vs. WORM: preliminary study of an active counter-attack mechanism
US20080229415A1 (en) Systems and methods for processing data flows
US9838411B1 (en) Subscriber based protection system
JP6441957B2 (en) Automatically demonstrated exploits in a suspected object, emphasizing the display information associated with the proven exploits system, apparatus, and method
US8832829B2 (en) Network-based binary file extraction and analysis for malware detection
US9251343B1 (en) Detecting bootkits resident on compromised computers
US8984638B1 (en) System and method for analyzing suspicious network data

Legal Events

Date Code Title Description
AS Assignment

Owner name: NEURALIQ, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CAPALIK, ALEN;REEL/FRAME:023322/0784

Effective date: 20091002

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: COUNTERTACK INC., CALIFORNIA

Free format text: CHANGE OF NAME;ASSIGNOR:NEURALIQ, INC.;REEL/FRAME:036074/0499

Effective date: 20120105