Code injection technique for remediation at an endpoint of a network

Abstract

A technique injects code into a suspicious process containing malware executing on a node to enable remediation at the node. Illustratively, the technique may inject code into the suspicious process during instrumentation of the malware in a micro-virtual machine (VM) to monitor malicious behavior and to enable remediation of that behavior at a node embodied as an endpoint. According to the technique, code may be injected into the suspicious process during instrumentation in the micro-VM of the endpoint to restore states of kernel resources (e.g., memory) that may be infected (i.e., altered) by behavior (actions) of the malware.

Description

BACKGROUND

Technical Field

The present disclosure relates to malware detection systems and, more specifically, to code injection for remediation at an endpoint of a network.

Background Information

Data communication in a network involves the exchange of data between two or more entities interconnected by communication links and sub-networks (segments). The entities are typically software processes executing in operating systems of computers, such as end nodes and intermediate nodes. The intermediate nodes interconnect the communication links and segments to enable transmission of data between the end nodes. A local area network (LAN) is an example of segment that provides relatively short distance communication among the interconnected nodes, whereas a wide area network (WAN) enables long distance communication over links provided by telecommunications facilities. The Internet is an example of a WAN that connects disparate computer networks throughout the world, providing global communication between nodes on various networks.

Malicious software (malware) has become a pervasive problem for nodes coupled to networks, such as the Internet. Malware is often embedded within downloadable content intended to adversely influence or attack normal operations of a node. Whereas operating system vulnerabilities have traditionally been common targets of such malware content, attackers have broaden their attack to exploit vulnerabilities in processes or applications, such as web browsers. For example, malware content may be embedded within objects associated with a web page hosted by a malicious web site.

Various types of security enhanced nodes are often deployed at different segments of the networks. These nodes often employ virtualization systems to provide the enhanced security needed to uncover the presence of malware embedded within ingress content propagating over the different segments. The enhanced security may include anti-virus scanning software that scans the ingress content for viruses and other forms of malware, as well as virtual machines that replay the content to monitor its behavior during execution to detect anomalies that may indicate the presence of malware. However, increasingly sophisticated malware may be able to infect the nodes by, e.g., altering states of resources of the nodes. Moreover, strict specifications for some nodes (e.g., endpoints) may require execution of software, despite known vulnerabilities and potential of infection by malware. Thus, a technique to remediate malware infection in running software is needed.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and further advantages of the embodiments herein may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate identically or functionally similar elements, of which:

FIG. 1 is a block diagram of a network environment that may be advantageously used with one or more embodiments described herein;

FIG. 2 is a block diagram of a node that may be advantageously used with one or more embodiments described herein;

FIG. 3 is a block diagram of the threat-aware microvisor that may be advantageously used with one or more embodiments described herein;

FIG. 4 is a block diagram of a malware detection endpoint architecture that may be advantageously used with one or more embodiments described herein;

FIG. 5 is a block diagram of a malware detection appliance architecture that may be advantageously used with one or more embodiments described herein; and

FIG. 6 is a block diagram of endpoint remediation using code injection that may be advantageously used with one or more embodiments described herein.

OVERVIEW

The embodiments described herein provide a technique for injecting code into a suspicious process containing malware executing on a node to enable remediation of the malware at the node. Illustratively, the technique may inject code into the suspicious process during instrumentation of the malware in a micro-virtual machine (micro-VM) to monitor malicious behavior and to enable remediation of that behavior at a node embodied as an endpoint. According to the technique, code may be injected into the suspicious process during instrumentation in the micro-VM of the endpoint to restore states of kernel resources (e.g., memory) that may be infected (i.e., altered) by behavior (actions) of the malware. In one embodiment, execution of the suspicious process and malware on the endpoint may eventually be terminated after monitoring of the malware behavior, while in another embodiment, an operating system image (binary) containing the suspicious process may not be changed. In either embodiment, the code is illustratively injected to provide dynamic, in-process vulnerability patching that enables remediation of the malware behavior at the endpoint.

DESCRIPTION

FIG. 1 is a block diagram of a network environment 100 that may be advantageously used with one or more embodiments described herein. The network environment 100 illustratively includes a plurality of networks organized as a public network 120, such as the Internet, and a private network 130, such an organization or enterprise (e.g., customer) network. The networks 120, 130 illustratively include a plurality of network links and segments connected to a plurality of nodes 200. The network links and segments may include local area networks (LANs) 110 and wide area networks (WANs) 150, including wireless networks, interconnected by intermediate nodes 200_I to form an internetwork of nodes, wherein the intermediate nodes 200_I may include network switches, routers and/or one or more malware detection system (MDS) appliances (intermediate nodes 200_M) described further herein. As used herein, an appliance may be embodied as any type of general-purpose or special-purpose computer, including a dedicated electronic computing device, adapted to implement a variety of software architectures relating to exploit and malware detection functionality. The term “appliance” should therefore be taken broadly to include such arrangements, in addition to any systems or subsystems configured to perform a management function for exploit and malware detection, and associated with other equipment or systems, such as a network computing device interconnecting the WANs and LANs. The LANs 110 may, in turn, interconnect end nodes 200_E which, in the case of private network 130, may be illustratively embodied as endpoints.

In an embodiment, the endpoints may illustratively include, e.g., client/server desktop computers, laptop/notebook computers, process controllers, medical devices, data acquisition devices, mobile devices, such as smartphones and tablet computers, and/or any other intelligent, general-purpose or special-purpose electronic device having network connectivity and, particularly for some embodiments, that may be configured to implement a virtualization system. The nodes 200 illustratively communicate by exchanging packets or messages (i.e., communication traffic) according to a predefined set of protocols, such as the Transmission Control Protocol/Internet Protocol (TCP/IP); however, it should be noted that other protocols, such as the HyperText Transfer Protocol Secure (HTTPS), may be advantageously used with the embodiments herein. In the case of private network 130, the intermediate node 200_I may include a firewall or other network device configured to limit or block certain communication (network) traffic in an attempt to protect the endpoints from unauthorized users. Unfortunately, such conventional attempts often fail to protect the endpoints, which may be compromised.

FIG. 2 is a block diagram of a node 200, e.g., endpoint 200_E or MDS appliance 200_M, that may be advantageously used with one or more embodiments described herein. The node 200 illustratively includes one or more central processing unit (CPUs) 212, a memory 220, one or more network interfaces 214 and one or more devices 216 connected by a system interconnect 218, such as a bus. The devices 216 may include various input/output (I/O) or peripheral devices, such as storage devices, e.g., disks. The disks may be solid state drives (SSDs) embodied as flash storage devices or other non-volatile, solid-state electronic devices (e.g., drives based on storage class memory components), although, in an embodiment, the disks may also be hard disk drives (HDDs). Each network interface 214 may include one or more network ports containing the mechanical, electrical and/or signaling circuitry needed to connect the node to the network 130 to thereby facilitate communication over the network. To that end, the network interface 214 may be configured to transmit and/or receive messages using a variety of communication protocols including, inter alia, TCP/IP and HTTPS.

In one or more embodiments where the MDS appliance 200_M is communicatively coupled with the network 130, the network interface 214 may operate as a data capturing device (sometimes referred to as a “tap” or “network tap”) that is configured to receive incoming network (data) traffic propagating from public network 120 and into private network 130, and provide at least some of this data traffic or a duplicated copy of the traffic for malware detection. In one embodiment, the MDS appliance may be positioned (deployed) behind the firewall at an ingress point into the private network 130, and at least partially in-line with network devices (e.g., endpoints) so as to subject the incoming traffic to analysis (e.g., through static analysis) and potentially block that traffic which is classified as malware from reaching its destination (e.g., the endpoints). In another embodiment, the static analysis may be at least partially performed by the firewall or other intermediate device, or performed by the network interface 214 (e.g., by CPU 212 and/or a digital signal processor on a network interface card).

The memory 220 may include a plurality of locations that are addressable by the CPU(s) 212 and the network interface(s) 214 for storing software program code (including application programs) and data structures associated with the embodiments described herein. The CPU 212 may include processing elements or logic adapted to execute the software program code, such as threat-aware microvisor 300 as well as modules of malware detection architectures described herein, and manipulate the data structures. Exemplary CPUs may include families of instruction set architectures based on the x86 CPU from Intel Corporation of Santa Clara, Calif. and the x64 CPU from Advanced Micro Devices of Sunnyvale, Calif.

An operating system kernel 230, portions of which are typically resident in memory 220 and executed by the CPU, functionally organizes the node by, inter alia, invoking operations in support of the software program code and application programs executing on the node. A suitable operating system kernel 230 may include the Windows® series of operating systems from Microsoft Corp of Redmond, Wash., the MAC OS® and IOS® series of operating systems from Apple Inc. of Cupertino, Calif., the Linux operating system and versions of the Android™ operating system from Google, Inc. of Mountain View, Calif., among others. Suitable application programs may include Adobe Reader® from Adobe Systems Inc. of San Jose, Calif. and Microsoft Word from Microsoft Corp of Redmond, Wash. Illustratively, the software program code may be implemented as operating system processes of the kernel 230. As used herein, a process (e.g., a user mode process) is an instance of software program code (e.g., an application program) executing in the operating system that may be separated (decomposed) into one or more threads, wherein each thread is a sequence of execution within the process.

It will be apparent to those skilled in the art that other types of processing elements and memory, including various computer-readable media, may be used to store and execute program instructions pertaining to the embodiments described herein. Also, while the embodiments herein are described in terms of software program code, processes, and computer, e.g., application, programs stored in memory, alternative embodiments also include the code, processes and programs being embodied as engines and/or modules consisting of hardware, software, firmware, or combinations thereof.

Threat-Aware Microvisor

FIG. 3 is a block diagram of the threat-aware microvisor 300 that may be advantageously used with one or more embodiments described herein. The threat-aware microvisor (hereinafter “microvisor”) may be configured to facilitate run-time security analysis, including exploit and malware detection and threat intelligence, of operating system processes executing on the node 200. To that end, the microvisor may be embodied as a light-weight module disposed or layered beneath (underlying, i.e., directly on native hardware) the operating system kernel 230 of the node to thereby virtualize the hardware and control privileges (i.e., access control permissions) to kernel (e.g., hardware) resources of the node 200 that are typically controlled by the operating system kernel. Illustratively, the kernel resources may include (physical) CPU(s) 212, memory 220, network interface(s) 214, and devices 216. The microvisor 300 may be configured to control access to one or more of the resources in response to a request by an operating system process to access the resource.

As a light-weight module, the microvisor 300 may provide a virtualization layer having less functionality than a typical hypervisor. Therefore, as used herein, the microvisor 300 is a module (component) that underlies the operating system kernel 230 and includes the functionality of a micro-kernel (e.g., protection domains, execution contexts, capabilities and scheduling), as well as a subset of the functionality of a hypervisor (e.g., hyper-calls to implement a virtual machine monitor). The microvisor may cooperate with a unique virtual machine monitor (VMM), i.e., a type 0 VMM, to provide additional virtualization functionality in an operationally and resource efficient manner. Unlike a type 1 or type 2 VMM (hypervisor), the type 0 VMM (VMM 0) does not fully virtualize the kernel (hardware) resources of the node and supports execution of only one entire operating system/instance inside one virtual machine, i.e., VM 0. VMM 0 may thus instantiate VM 0 as a container for the operating system kernel 230 and its kernel resources. In an embodiment, VMM 0 may instantiate VM 0 as a module having instrumentation logic 360 directed to determination of an exploit or malware in any suspicious operating system process (kernel or user mode). Illustratively, VMM 0 is a pass-through module configured to expose the kernel resources of the node (as controlled by microvisor 300) to the operating system kernel 230. VMM 0 may also expose resources such as virtual CPUs (threads), wherein there is one-to-one mapping between the number of physical CPUs and the number of virtual CPUs that VMM 0 exposes to the operating system kernel 230. To that end, VMM 0 may enable communication between the operating system kernel (i.e., VM 0) and the microvisor over privileged interfaces 315 and 310.

The VMM 0 may include software program code (e.g., executable machine code) in the form of instrumentation logic 350 (including decision logic) configured to analyze one or more interception points originated by one or more operating system processes to invoke the services, e.g., accesses to the kernel resources, of the operating system kernel 230. As used herein, an interception point is a point in an instruction stream where control passes to (e.g., is intercepted by) either the microvisor, VMM 0 or another virtual machine. Illustratively, VMM 0 may contain computer executable instructions executed by the CPU 212 to perform operations that initialize and implement the instrumentation logic 350, as well as operations that spawn, configure, and control/implement VM 0 and its instrumentation logic 360.

In an embodiment, the microvisor 300 may be organized to include a protection domain illustratively bound to VM 0. As used herein, a protection domain is a container for various data structures, such as execution contexts, scheduling contexts, and capabilities associated with the kernel resources accessible by an operating system process. Illustratively, the protection domain may function at a granularity of an operating system process (e.g., a user mode process) and, thus, is a representation of the process. Accordingly, the microvisor may provide a protection domain for the process and its run-time threads executing in the operating system. A main protection domain (PD 0) of the microvisor controls all of the kernel resources available to the operating system kernel 230 (and, hence, the user mode process) of VM 0 via VMM 0 and, to that end, may be associated with the services provided to the user mode process by the kernel 230.

An execution context 320 is illustratively a representation of a thread (associated with an operating system process) and, to that end, defines a state of the thread for execution on CPU 212. In an embodiment, the execution context may include inter alia (i) contents of CPU registers, (ii) pointers/values on a stack, (iii) a program counter, and/or (iv) allocation of memory via, e.g., memory pages. The execution context 320 is thus a static view of the state of thread and, therefore, its associated process. Accordingly, the thread executes within the protection domain associated with the operating system process of which the thread is a part. For the thread to execute on a CPU 212 (e.g., as a virtual CPU), its execution context 320 is tightly linked to a scheduling context 330, which may be configured to provide information for scheduling the execution context 320 for execution on the CPU 212. Illustratively, the scheduling context information may include a priority and a quantum time for execution of its linked execution context on CPU 212.

In an embodiment, the capabilities 340 may be organized as a set of access control permissions to the kernel resources to which the thread may request access. Each time the execution context 320 of a thread requests access to a kernel resource, the capabilities 340 are examined. There is illustratively one set of capabilities 340 for each protection domain, such that access to kernel resources by each execution context 320 (i.e., each thread of an execution context) of a protection domain may be defined by the set of capabilities 340. For example, physical addresses of pages of memory 220 (resulting from mappings of virtual addresses to physical addresses) may have associated access permissions (e.g., read, write, read-write) within the protection domain. To enable an execution context 320 to access a kernel resource, such as a memory page, the physical address of the page may have a capability 340 that defines how the execution context 320 may reference that page. Illustratively, the capabilities may be examined by hardware (e.g., a hardware page fault upon a memory access violation) or by program code. A violation of a capability in a protection domain may be an interception point, which returns control to the VM (e.g., VM 0) bound to the protection domain.

Malware Detection Endpoint Architecture

In an embodiment, the threat-aware microvisor 300 may be deployed in a micro-virtualization architecture as a module of a virtualization system executing on the endpoint 200_E to provide exploit and malware detection within the network environment 100. FIG. 4 is a block diagram of a malware detection endpoint architecture 400 that may be advantageously used with one or more embodiments described herein. Illustratively, the architecture 400 may organize the memory 220 of the endpoint 200_E as a user space 402 and a kernel space 404. In an embodiment, the microvisor may underlie the operating system kernel 230 and execute in the kernel space 404 of the architecture 400 to control access to the kernel resources of the endpoint 200_E for any operating system process (kernel or user mode). Notably, the microvisor 300 executes at the highest privilege level of the hardware (CPU) to thereby virtualize access to the kernel resources of the endpoint in a light-weight manner that does not share those resources among user mode processes 410 when requesting the services of the operating system kernel 230. That is, there is one-to-one mapping between the resources and the operating system kernel, such that the resources are not shared.

A system call illustratively provides an interception point at which a change in privilege levels occurs in the operating system, i.e., from a privilege level of the user mode process to a privilege level of the operating system kernel. VMM 0 may intercept the system call and examine a state of the process issuing (sending) the call. The instrumentation logic 350 of VMM 0 may analyze the system call to determine whether the call is suspicious and, if so, instantiate (spawn) one or more “micro” virtual machines (VMs) equipped with monitoring functions that cooperate with the microvisor to detect anomalous behavior which may be used in determining an exploit or malware.

As used herein, an exploit may be construed as information (e.g., executable code, data, one or more commands provided by a user or attacker) that attempts to take advantage of a computer program or system vulnerability, often employing malware. Typically, a vulnerability may be a coding error or artifact of a computer program that allows an attacker to alter legitimate control flow during processing of the computer program by an electronic device (such as a node) and, thus, causes the electronic device to experience undesirable or unexpected behaviors. The undesired or unexpected behaviors may include a communication-based or execution-based anomaly which, for example, could (1) alter the functionality of the electronic device executing application software in a malicious manner; (2) alter the functionality of the electronic device executing the application software without any malicious intent; and/or (3) provide unwanted functionality which may be generally acceptable in another context. To illustrate, a computer program may be considered a state machine where all valid states (and transitions between states) are managed and defined by the program, in which case an exploit may be viewed as seeking to alter one or more of the states (or transitions) from those defined by the program. Malware may be construed as computer code that is executed by an exploit to harm or co-opt operation of an electronic device or misappropriate, modify or delete data. Conventionally, malware may often be designed with malicious intent, and may be used to facilitate an exploit. For convenience, the term “malware” may be used herein to describe a malicious attack, and encompass both malicious code and exploits detectable in accordance with the disclosure herein.

As used herein, the term “micro” VM denotes a virtual machine serving as a container that is restricted to a process (as opposed to VM 0 which is spawned as a container for the entire operating system.) Such spawning of a micro-VM may result in creation of an instance of another module (i.e., micro-VM N) that is substantially similar to VM 0, but with different (e.g., additional) instrumentation logic 360N illustratively directed to determination of malware in the suspicious process by, e.g., monitoring its behavior. In an embodiment, the spawned micro-VM illustratively encapsulates an operating system process, such as a user mode process 410. In terms of execution, operation of the process is controlled and synchronized by the operating system kernel 230; however, in terms of access to kernel resources, operation of the encapsulated process is controlled by VMM 0. Notably, the resources appear to be isolated within each spawned micro-VM such that each respective encapsulated process appears to have exclusive control of the resources. In other words, access to kernel resources is synchronized among the micro-VMs and VM 0 by VMM 0 rather than virtually shared. Similar to VM 0, each micro-VM may be configured to communicate with the microvisor (via VMM 0) over privileged interfaces (e.g., 315n and 310n).

In an embodiment, the privileged interfaces 310 and 315 may be embodied as a set of defined hyper-calls, which are illustratively inter process communication (IPC) messages exposed (available) to VMM 0 and VM 0 (including any spawned micro-VMs). The hyper-calls are generally originated by VMM 0 and directed to the microvisor 300 over privileged interface 310, although VM0 and the micro-VMs may also originate one or more hyper-calls (IPC messages) directed to the microvisor over privileged interface 315. However, the hyper-calls originated by VM 0 and the micro-VMs may be more restricted than those originated by VMM 0.

In an embodiment, the microvisor 300 may be organized to include a plurality of protection domains (e.g., PD 0-N) illustratively bound to VM 0 and one or more micro-VMs, respectively. For example, the spawned micro-VM (e.g., micro-VM N) is illustratively associated with (bound to) a copy of PD 0 (e.g., PD N) which, in turn, may be bound to the process, wherein such binding may occur through memory context switching. In response to a decision to spawn the micro-VM N, VMM 0 may issue a hyper-call over interface 310 to the microvisor requesting creation of the protection domain PD N. Upon receiving the hyper-call, the microvisor 300 may copy (i.e., “clone”) the data structures (e.g., execution contexts, scheduling contexts and capabilities) of PD 0 to create PD N for the micro-VM N, wherein PD N has essentially the same structure as PD 0 except for the capabilities associated with the kernel resources. The capabilities for PD N may limit or restrict access to one or more of the kernel resources as instructed through one or more hyper-calls from, e.g., VMM 0 and/or micro-VM N over interface 310n to the microvisor. Accordingly, the microvisor 300 may contain computer executable instructions executed by the CPU 212 to perform operations that initialize, clone and configure the protection domains.

Advantageously, the microvisor 300 may be organized as separate protection domain containers for the operating system kernel 230 (PD 0) and one or more operating system processes (PD N) to facilitate further monitoring and/or understanding of behaviors of a process and its threads. Such organization of the microvisor also enforces separation between the protection domains to control the activity of the monitored process. Moreover, the microvisor 300 may enforce access to the kernel resources through the use of variously configured capabilities of the separate protection domains. Unlike previous virtualization systems, separation of the protection domains to control access to kernel resources at a process granularity enables detection of anomalous behavior of malware. That is, in addition to enforcing access to kernel resources, the microvisor enables analysis of the operation of a process within a spawned micro-VM to detect exploits or other malicious code threats that may constitute malware.

The user mode processes 410 and operating system kernel 230 may execute in the user space 402 of the endpoint architecture 400, although it will be understood to those skilled in the art that the user mode processes may execute in another address space defined by the operating system kernel. Illustratively, the operating system kernel 230 may execute under control of the microvisor at a privilege level (i.e., a logical privilege level) lower than a highest privilege level of the microvisor, but at a higher CPU privilege level than that of the user mode processes 410. In addition, VMM 0 and its spawned VMs (e.g., VM 0 and micro-VM N) may execute in user space 402 of the architecture 400. As a type 0 virtual machine monitor, VMM 0 (and its spawned VM 0 and micro-VMs) may execute at the highest (logical) privilege level of the microvisor. That is, VMM 0 (and its spawned VM 0 and micro-VMs) may operate under control of the microvisor at the highest microvisor privilege level, but may not directly operate at the highest CPU (hardware) privilege level.

Illustratively, the instrumentation logic of VMM 0 (and its spawned micro-VMs) may include monitoring logic configured to monitor and collect capability violations (e.g., generated by CPU 212) in response to one or more interception points to thereby infer malware. Inference of malware may also be realized through sequences of interception points wherein, for example, a system call followed by another system call having certain parameters may lead to an inference that the process sending the calls is malware. The interception point thus provides an opportunity for VMM 0 to perform “light-weight” (i.e., limited so as to maintain user experience at the endpoint with little performance degradation) analysis to evaluate a state of the process in order to detect possible malware without requiring any policy enforcement. VMM 0 may then decide to spawn a micro-VM and configure the capabilities of its protection domain to enable deeper monitoring and analysis (e.g., through interception points and capability violations) in order to determine whether the process includes malware. Notably, the analysis may also classify the process as a type of malware (e.g., a stack overflow) and may even identify the same. As a result, the invocation of instrumentation and monitoring logic of VMM 0 and its spawned VMs in response to interception points originated by operating system processes and capability violations generated by the microvisor advantageously enhance the virtualization system described herein to provide an exploit and malware detection system configured for run-time security analysis of the operating system processes executing on the endpoint.

VMM 0 may also log the state of the monitored process within system logger 470. In an embodiment, the state of the process may be realized through the contents of the execution context 320 (e.g., CPU registers, stack, program counter, and/or allocation of memory) executing at the time of each capability violation. In addition, the state of the process may be realized through correlation of various activities or behavior of the monitored process. The logged state of the process may thereafter be exported from the system logger 470 to the MDS 200_M of the network environment 100 by, e.g., forwarding the state as one or more IPC messages through VMM 0 (VM 0) and onto a network protocol stack (not shown) of the operating system kernel. The network protocol stack may then format the messages as one or more packets according to, e.g., a syslog protocol such as RFC 5434 available from IETF, for transmission over the network to the MDS appliance 200_M.

Malware Detection

Exploit and malware detection on the endpoint may be performed in accordance with one or more processes embodied as software modules or engines containing computer executable instructions executed by the CPU to detect suspicious and/or malicious behaviors of an operating system process (including an application program) when, e.g., executing contents of an object, and to correlate and classify the detected behaviors as indicative of malware (i.e., a matter of probability). Notably, the endpoint may perform (implement) exploit and malware detection as background processing (i.e., minor use of endpoint resources) with data processing being implemented as its primary processing (e.g., in the foreground having majority use of endpoint resources), whereas the MDS appliance implements such detection as its primary processing (i.e., majority use of appliance resources). Detection of a suspicious and/or malicious object may be performed at the endpoint by static and dynamic analysis of the object. As used herein, an object may include a logical entity such as, for example, a web page, email, email attachment, file or universal resource locator (URL). Static analysis may perform light-weight (quick) examination of the object to determine whether it is suspicious, while dynamic analysis may instrument the behavior of the object as the operating system process executes (runs) via capability violations of, e.g., operating system events. A correlation engine 410 and a classifier 420 may thereafter cooperate to perform correlation and classification of the detected behaviors as malicious or not. That is, the correlation engine 410 and classifier 420 may cooperate to analyze and classify observed behaviors of the object (based on the events) as indicative of malware.

In an embodiment, the static analysis may perform light-weight examination of the object (including a network packet) to determine whether it is suspicious and/or malicious. To that end, the static analysis may include a static inspection engine 430 and a heuristics engine 440 executing as user mode processes of the operating system kernel 230. The static inspection engine 430 and heuristics engine 440 may employ statistical analysis techniques, including the use of vulnerability/exploit signatures and heuristics, to perform non-behavioral analysis in order to detect anomalous characteristics (i.e., suspiciousness and/or malware) without execution (i.e., monitoring run-time behavior) of the object. For example, the static inspection engine 430 may employ signatures (referred to as vulnerability or exploit “indicators”) to match content (e.g., bit patterns) of the object with patterns of the indicators in order to gather information that may be indicative of suspiciousness and/or malware. The heuristics engine 440 may apply rules and/or policies to detect anomalous characteristics of the object in order to identify whether the object is suspect and deserving of further analysis or whether it is non-suspect (i.e., benign) and not in need of further analysis. The statistical analysis techniques may produce static analysis results that include, e.g., identification of communication protocol anomalies and/or suspect source addresses of known malicious servers.

The dynamic analysis may include exploit detection performed by, e.g., the microvisor 300 and micro-VM N to observe behaviors of the object. In an embodiment, exploit detection at the endpoint does not generally wait for results from the static analysis. The behaviors of the object may be observed by instrumenting the object (using, e.g., instrumentation logic 360N) as the operating system process runs at micro-VM N, wherein the observed run-time behaviors may be captured by the microvisor 300 and VMM 0, and provided to the correlation engine 410 as dynamic analysis results.

Illustratively, monitors may be employed during the dynamic analysis to monitor the run-time behaviors of the object and capture any resulting activity. The monitors may be embodied as capability violations configured to trace particular operating system events. During instrumenting of the object at the micro-VM, the system events may trigger capability violations (e.g., exceptions or traps) generated by the microvisor 300 to enable monitoring of the object's behaviors during run-time.

The static analysis results and dynamic analysis results may be stored in memory 220 (e.g., in system logger 470) and provided to the correlation engine 410, which may provide correlation information to the classifier 420. Alternatively, the results or events may be provided or reported to the MDS appliance 200_M for correlation. The correlation engine 410 may be configured to operate on correlation rules that define, among other things, sequences of known malicious events (if-then statements with respect to, e.g., attempts by a process to change memory in a certain way that is known to be malicious). The events may collectively correlate to malicious behavior. As noted, a micro-VM may be spawned to instrument a suspect process (object) and cooperate with the microvisor 300 and VMM 0 to generate capability violations in response to interception points, which capability violations are provided as dynamic analysis result inputs to the correlation engine 410. The rules of the correlation engine 410 may then be correlated against those dynamic analysis results, as well as static analysis results, to generate correlation information pertaining to, e.g., a level of risk or a numerical score used to arrive at a decision of (deduce) maliciousness. The classifier 420 may be embodied as a classification engine executing as a user mode process of the operating system kernel 230 and configured to use the correlation information provided by correlation engine 410 to render a decision as to whether the object is malicious. Illustratively, the classifier 420 may be configured to classify the correlation information, including monitored behaviors (expected and unexpected/anomalous) and capability violations, of the object relative to those of known malware and benign content.

Malware Detection Appliance Architecture

In one or more embodiments, the MDS appliance 200_M may be embodied as an intermediate node configured to analyze communication traffic associated with one or more endpoints 200_E coupled to a network segment, such as segment 110, of a network, such as private network 130. The MDS appliance 200_M may be illustratively positioned (e.g., as an ingress/egress point) within the private network 130 or segment 110 to intercept (i.e., capture) the traffic. In one or more embodiments, the MDS appliance may manage each endpoint by, e.g., requesting replay and instrumentation of the traffic by the endpoint 200_E. The intercepted traffic may also be replayed and instrumented (i.e., monitored) at the appliance. Thereafter, the instrumented traffic may be correlated at the MDS appliance 200_M, and the appliance may be configured to communicate with and instruct the endpoint to, e.g., perform an action and receive notification of that action being performed.

Illustratively, the MDS appliance 200_M may include functionality directed to replaying of communication traffic and correlating instrumentation of that traffic with actions resulting from that traffic at the endpoint. For every network packet received, the appliance may run a heuristic to compute a flow, as appropriate, for the packet, and then create (spawn) a virtual machine (VM) to emulate the endpoint using an image of an operating system (guest operating system and one or more applications) configured to replicate a software processing environment of the endpoint, e.g., based on a payload (object) of the packet to be replayed and instrumented. As noted, an object may include a logical entity such as, for example, a web page, an email or email attachment, an executable (i.e., binary or script), a file (which may contain an executable), or URL. Information as to an appropriate processing environment may be provided by the packet itself, e.g., the packet header may identify the packet type, for example, a document such as a Portable Document Format (PDF) document and, thus, the processing environment may include a document reader, such as a PDF reader from Adobe Systems Inc. Additionally, or in alternative embodiments, information may also be provided by the endpoint (such as the destination endpoint as specified in the packet) to the MDS appliance indicating a type of application software (process) executing within the operating system on the endpoint. The appliance may then launch a copy of the application along with appropriate instrumentation to process each object. For example, assume the MDS appliance 200_M replays HTTPS traffic received at the endpoint which executes, inter alia, an application (i.e., a web browser). The appliance may capture the communication (HTTPS) traffic destined to the endpoint, spawn the VM and launch a copy of the web browser along with instrumentation to monitor the traffic.

In an embodiment, the threat-aware microvisor 300 may be deployed in a virtualization architecture as a module of a virtualization system executing on the MDS appliance 200_M to provide exploit and malware detection within the network environment 100. FIG. 5 is a block diagram of a malware detection appliance architecture 500 that may be advantageously used with one or more embodiments described herein. Illustratively, the architecture 500 may organize the memory 220 of the MDS appliance 200_M as a user space 502 and a kernel space 504. The microvisor may underlie the operating system kernel 230 and execute at the highest privilege level of the CPU within the kernel space 504 of the architecture 500 to control access to the kernel resources of the appliance 200_M for any operating system process (kernel or user mode). User mode processes 510 and operating system kernel 230 may execute in the user space 502 of the appliance architecture 500. Illustratively, the operating system kernel 230 may execute under control of the microvisor at a privilege level (i.e., a logical privilege level) lower than a highest privilege level of the microvisor, but at a higher CPU privilege level than that of the user mode processes 510. In addition, VMM 0 and VM 0 may execute in user space 502 under control of the microvisor at the highest microvisor privilege level, but may not directly operate at the highest CPU (hardware) privilege level.

One or more hypervisors, e.g., type 1 VMM, may be disposed as one or more modules over the microvisor 300 and operate in user space 502 of the architecture 500 under control of the microvisor at the highest microvisor privilege level to provide additional layers of virtualization for the MDS appliance 200_M. Illustratively, each hypervisor provides full virtualization of kernel (hardware) resources and supports execution of one or more entire operating system instances (i.e., guest operating system) inside one or more full virtual machines. In one or more embodiments, the full virtual machine (VM) may simulate a computer (machine) based on specifications of a hypothetical (abstract) computer or based on an architecture and functions of an actual (real) computer. To that end, a hypervisor (e.g., VMM 1) may instantiate a full VM (e.g., VM 1) as a module provisioned with a software profile that includes a guest operating system (e.g., guest operating system 515) and any associated application programs (e.g., application 525), as well as instrumentation logic (e.g., instrumentation logic 360A) directed to determination of malware in any suspicious object or application executing on the guest operating system. Illustratively, the hypervisor may instantiate the full VM from a pool of VMs configured to closely simulate various target operating environments (e.g., software profiles) in which the malware is to be analyzed. The software profile (e.g., guest operating system and/or application program) provisioned and configured in the VM may be different (e.g., in vendor, type and/or version) from the software profile provisioned and configured in other instantiated VMs (e.g., VM N).

The instantiated VM (e.g., VM 1) is illustratively associated with (bound to) a copy of PD 0 (e.g., PD 1), wherein such binding may occur through memory context switching. In response to a decision to instantiate (spawn) the VM 1, VMM 1 may issue a hyper-call over interface 310b to the microvisor requesting creation of the protection domain PD 1. Upon receiving the hyper-call, the microvisor 300 may copy (i.e., “clone”) the data structures (e.g., execution contexts, scheduling contexts and capabilities) of PD 0 to create PD 1 for the VM 1, wherein PD 1 has essentially the same structure as PD 0 except for the capabilities associated with the kernel resources. The capabilities for PD 1 may limit or restrict access to one or more of the kernel resources as instructed through one or more hyper-calls from, e.g., VMM 1 and/or VM 1 over interface 310b to the microvisor.

Illustratively, each hypervisor (e.g., VMM 1-N) may contain computer executable instructions executed by the CPU 212 to perform operations that initialize and configure the instrumentation logic (e.g., instrumentation logic 350A-N), as well as operations that spawn, configure, and control/implement the VM (e.g., VM 1-N) and their instrumentation logic (e.g., 360A). In an embodiment, there is illustratively one hypervisor (e.g., VMM 1-N) for each VM (e.g., VMs 1-N), wherein each VM may be used to emulate an endpoint. The MDS appliance 200_M may not emulate every endpoint on, e.g., a segment of the network 130, but when a suspicious object (such as, e.g., a file of a network packet) is identified, the VMM 1 of the appliance may create (spawn) a full VM 1 to analyze that object. The virtualization layers of the MDS appliance 200_M may cooperate to implement an abstraction of virtual devices exposed as, e.g., virtual network interfaces to the VMs, as opposed to the real network interfaces exposed to the micro-VMs of the endpoint.

The user mode processes 510 executing on the MDS appliance 200_M may include a heuristic engine 530 that, in response to receiving communication traffic, is configured to run one or more heuristics to determine whether the traffic (e.g., an object of a packet) is suspicious. Illustratively, the heuristic engine may use pre-defined anomalous behaviors (monitored activity) of verified exploits and malware to, e.g., identify communication protocol anomalies and/or suspect source addresses of known malicious servers. For example, the heuristic engine may examine metadata or attributes of the object and/or a code image (e.g., a binary image of an executable) of the object to determine whether a portion of the object matches a predetermined pattern or signature associated with a known type of malware. The heuristic engine 530 may provide the packet of the suspicious traffic to one or more processes 510 embodied as analysis engine 540. In an embodiment, the analysis engine 540 may be configured to perform static analysis of the object of the packet to, e.g., identify software profile information associated with an operating system instance for execution in a full VM (virtualizing all kernel resources).

The analysis engine 540 may also be configured to analyze other content of the packet (e.g., destination address of a network header) to determine its destination (i.e., the endpoint). To that end, the analysis engine 540 may be configured to cooperate with a module, e.g., endpoint (EP) logic 560, to communicate with the endpoint 200_E, e.g., to identify and/or acquire information (including the software profile) associated with execution of the malware on the endpoint. Illustratively, communication with the endpoint may be effected by, e.g., forwarding one or more IPC messages to a network protocol stack (not shown) of the operating system kernel 230. The network protocol stack may then format the messages as one or more packets for transmission over the network to the endpoint. The analysis engine 540 may then provide the software profile information to another process embodied as scheduler 550, which may coordinate with the hypervisor, e.g., VMM 1, to spawn a VM, e.g., VM 1, to replay the traffic.

When replaying the traffic, the analysis engine 540 may employ the EP logic 560 to invoke appropriate instrumentation logic 360A of VM 1 to enable communication with the endpoint to perform dynamic analysis and/or correlation of the suspicious object. In an embodiment, correlation (as described herein) may be performed by one or more user mode processes embodied as a correlation engine 570. The instrumentation logic 360A may be configured to monitor different types of objects, such as payloads of network (web) and email packets, although alternatively, there could be separate web-based and email-based MDS appliances, each of which may be deployed the same way and configured to perform that same work. The MDS appliance 200_M may include a module that communicates with a similar module on the endpoint to perform the requested instrumentation. For example in the case of email objects, the application may be an email reader that analyzes email traffic captured by the appliance (and endpoint).

During instrumentation (monitoring) in VM 1, the object may manifest behaviors that are captured by the microvisor and VMM 1. That is, the object may execute within the software profile of VM 1 and its monitored operation (behaviors) observed. The microvisor 300 and VMM 1 may record any resulting activity as, e.g., an event within a database of another user mode process embodied as an event logger 590. In addition, the activity of the object (including the event) may be provided to the correlation engine 570 and to yet another user mode process embodied as a classifier 580 for classification and/or validation of the object as, e.g., malware. Illustratively, correlation engine 570 may be configured to correlate observed behaviors (e.g., results of dynamic analysis) with known malware and/or benign objects (embodied as defined rules) and generate an output (e.g., a level of risk or a numerical score associated with an object) that is provided to the classifier. The classifier 580 may be configured to classify the observed behaviors (expected and unexpected/anomalous) and capability violations of the object relative to those of known malware and benign content to render a decision of malware, i.e., validate the monitored operation of the object as malicious activity, based on the risk level or score exceeding a probability threshold.

Operationally, the MDS appliance may intercept (i.e., receive) and store communication traffic flowing over the network that is destined to the endpoints. The appliance may analyze the traffic and communicate with the endpoints over the network using a messaging protocol that encapsulates an object of interest (e.g., a file of a network packet). Illustratively, the MDS appliance may deploy the network protocol stack, e.g., of the operating system kernel 230 configured to employ a protocol to communicate with the endpoints. For example, the EP logic 560 may notify an endpoint to replay the object using a network message having a MAC address (layer 2 connectivity) and/or IP address of the endpoint (layer 3 connectivity).

Code Injection for Remediation

The embodiments described herein provide a technique for injecting code into a suspicious process containing malware executing on a node to enable remediation at the node. Illustratively, the technique may inject code into the suspicious process (i.e., inject instructions into memory within an address space of process) during instrumentation of the malware in a micro-VM to monitor malicious behavior and to enable remediation of that behavior at a node embodied as an endpoint. According to the technique, code may be injected into the suspicious process during instrumentation in the micro-VM of the endpoint to restore states of kernel resources (e.g., memory) that may be infected and altered by behavior (actions) of the malware. Notably, restoration of kernel resource states may occur by (1) an act of injecting the code itself (e.g., overwriting malware in memory) and (2) execution of the injected code (e.g., repairing damage done by malware). In one embodiment, execution of the suspicious process and malware on the endpoint may be terminated after monitoring of the malware behavior, while in another embodiment, an operating system image (binary) containing the suspicious process may not be changed. In either embodiment, the code is illustratively injected to provide dynamic, in-process vulnerability patching that enables remediation of the malware behavior at the endpoint.

FIG. 6 is a block diagram of endpoint remediation using code injection that may be advantageously used with one or more embodiments described herein. Assume there has been an infection that manifests as changes to a kernel resource 630 (e.g., memory) by an exploit (i.e., vulnerability) to enable malware 610a to execute in process 620a in micro-VM A. Code may be injected (i.e., injected code 640a) to restore the memory (i.e., resource 630) to its state prior to the infection. Assume further that original code 625 of, e.g., process 620b stored at certain pages of memory is altered by malware 610b. During instrumentation of the process 620b in micro-VM B, the behavior of the malware 610b may be monitored as it attempts to change the original code stored in the memory pages. In response, the technique described herein may inject code 640b to reverse the changes made to the original code 625 by the malware 610b and to restore the state of that code. That is, the malicious changes to the memory pages may be overwritten (or alternatively removed and replaced) with the original code (i.e., the injected code 640b) to provide non-fixed (i.e., dynamic) patching of the process vulnerability. Thus, the process 620b altered by the malware need not be terminated; rather, the process 620b may be dynamically repaired at run-time. As such, the original code persistent on storage devices 216 need not be patched, despite the known exploit and/or malicious content (i.e., detected vulnerability) so as to, e.g., meet any requirements to run a specific version of the original code (e.g., embodied as application 525). Notably, restoration of the original code 625 may be accomplished by executing the injected code 640b at run-time to repair (rather than simply overwrite) the memory pages that store that original code.

In an embodiment, a file 660 containing the specific version of software (e.g., version of the application 525) may be executed at the endpoint; yet it may be undesirable (e.g., to meet a compliance requirement) to permanently change the file such that the software's instruction sequence or “logic” is altered. That is, the file may be an executable binary of an operating system that is deemed not subjectable to fixed (i.e., static) patching on the storage device 216. The executed binary (e.g., process 620b) may be instrumented at micro-VM B of the endpoint to uncover the malicious content and, further, to monitor its malicious behavior. According to the technique, the microvisor and VMM 0 do not stop (“kill”) the malicious process 620b, but rather allow it to run in the micro-VM B while reversing any changes to the memory pages having the original code 625 or other kernel resource that the malware 610b may attempt. Essentially, the technique provides a dynamic patch while the process (malware) is running, e.g., in memory, without rendering any fixed or static changes to the executable file (binary) on the storage device. Notably, the patch may include code injected along-side the existing software instructions of the process (e.g., within an address space of the process) that is executed to repair damage by the malware. Illustratively, the dynamic patch may operate in a manner such that every time the malware attempts to alter (i.e., modify) the content of the kernel resource, such as a memory location, the microvisor and VMM 0 may remove (i.e., reverse) the modification and restore the state of that location, e.g., to its (prior) unaltered state. The microvisor and VMM 0 may direct operation of the dynamic patch either by directly restoring the altered kernel resource or executing the injected code (to effect restoration of the kernel resource), or combinations thereof.

In an embodiment, the technique may restore the malicious alterations (i.e., modifications) to an original resource state 632a by, e.g., capturing the state of the kernel resource execution context of the process (thread) before the process (thread) executes (i.e., original resource 632a) on the CPU and then reverting that context to the original captured state after being changed to an altered resource state 632b once execution of the thread begins. As a result, the microvisor and the VMM 0 may need to be aware of the occurrence of the malware in the process 620c so that the state of the kernel resource may be captured prior to the occurrence. Accordingly, once the malicious behavior of the malware is detected and the unaltered (i.e., original) state of the kernel resource 632a of the process is captured, dynamic (i.e., run-time) reversion to that unaltered state may be made by the microvisor and VMM 0 to thereby thwart the attempted malicious modification to the resource. Notably, the captured original state may require maintenance to enable reversion to that state after the occurrence.

Illustratively, knowledge of the exploit (and the malware) based on its malicious behavior may be known a priori (i.e., the exploit vulnerability and the resource altering behavior of the malware may be detected and recorded previously) so as to anticipate when the exploit occurs (and when the malware makes its illicit modifications). Notably, the a priori knowledge (i.e., identification of the malware and corresponding remediation) may be from another source, such as a cloud service 680 (i.e., an internet-based distribution service) or a database of the endpoint. That is, identification of the malware and the associated remediation (e.g., code injection to restore state of the affected process) may be obtained illustratively as a dynamic patch available from cloud service 680, the endpoint database, or a local server on the private network 130, wherein the patch may be available from an author (i.e., vendor) of the binary (i.e., application 525). As a result, the process need not be constantly instrumented (monitored) to uncover the occurrence. The technique (i.e., dynamic patching of the kernel resource) may be applied on subsequent executions of the binary file (i.e., invocations of the process 620b having the software instructions from the file 660) without instrumenting those subsequent executions. Accordingly, application of the dynamic patch need not have knowledge of the patch and specific kernel resources that may be remediated by applying that patch. The technique may merely inject the dynamic patch which performs appropriate remediation. In an embodiment, dynamic patches using injected code 640d to the instructions (original code 625) of the process 620d may be made as a preventative measure to avoid the exploit from occurring entirely, such that the malware 610d cannot execute. Illustratively, the dynamic patch may be in the form of a dynamic link library (DLL) injected into the process by 1) loading the DLL into the memory 220; 2) mapping one or more memory pages (e.g., code pages) having the dynamic patch into the address space of the process; and 3) executing the instructions of the dynamic patch to affect remediation.

In another embodiment, the original logic of the software instructions (i.e., flow of execution) of the process may be maintained, even though the malicious code (malware) remains in the process. That is, the malicious code (instructions) of the process may not be altered (e.g., overwritten); rather the original (i.e., non-malicious) flow of execution of the code (i.e., original process logic) may be maintained by dynamically altering the kernel resource so as to bypass execution of the malicious code. For example, assume the kernel resource is a process (call) stack and an exploit of the process executes (e.g., in a micro-VM) to cause a buffer overflow of the stack. Illustratively, the exploit may change a return address (for a function call) with an address of the malicious code (malware). As noted, the microvisor assumes control over the execution point of the process while it is running in the micro-VM. When the process is scheduled to execute on the CPU (by the scheduler), the microvisor and VMM 0 may divert execution to, e.g., the injected code without breaking the process logic. By injecting a correct return address on the stack, execution of the malware may be obviated by providing a dynamic patch that restores the stack to its correct state (i.e., the original non-malicious flow of execution) without breaking the logic (life cycle) of the process and without stopping or restarting the process (i.e., so as to allow the process to continue running).

In an embodiment, the restore state utilized by the microvisor and VMM 0 may be provided by the MDS appliance, which may have the a priori knowledge of the exploit vulnerability and the resource altering behavior of the malware. Although exploit and malware detection may be performed on a process at a micro-VM of the endpoint to render a determination that the process may contain an exploit/malware, the endpoint may report the determination to the MDS appliance for validation and/or more extensive analysis. As noted, the instrumentation of the micro-VM is light-weight in order to, inter alia, preserve (i.e., maintain) the user experience at the endpoint. Accordingly, the instrumentation performed by the micro-VM is limited such that there is no extensive CPU processing, i.e., efficient instrumentation that limits CPU processing to preserve the user experience. Instead, any extensive CPU processing is performed at the MDS appliance using, e.g., a run-time environment (software profile) of the endpoint. As a result of such extensive processing associated with the analysis, the MDS appliance may specify actions that VMM 0 and the microvisor should perform in order to address the occurrence of the detected exploit or malware at the endpoint. That is, the MDS appliance may detect the exploit and, based on the vulnerability, gather (i.e., record) the resource altering behavior of the malware. As such, the MDS appliance may illustratively instruct (e.g., via message 670 having injected code 640) the microvisor and VMM 0 as to when (e.g., relative to beginning execution of the process) and how to restore the state of the altered kernel resource with the original kernel resource (e.g., code content and/or a referenced address of the run-time environment) so as to avoid the exploit or repair damage from the malware according to the technique described herein.

While there have been shown and described illustrative embodiments for injecting code into a suspicious process containing malware executing on a node to enable remediation of that malware at the node, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the embodiments herein. For example, embodiments have been shown and described herein with relation the endpoint injecting code for remediation by the microvisor and VMM 0. However, the embodiments in their broader sense are not so limited, and may, in fact, provide a warning that may be displayed to an end user of the endpoint indicating detection of malware and/or remediation. The warning may instruct the end user to be aware (and be patient) while remediation is applied.

In addition, although the embodiments have been shown and described herein with relation to the microvisor and VMM 0 cooperating (at the endpoint) to inject code for remediation of malware, the embodiments may alternatively include a micro-kernel without protection domains (e.g., in lieu of the microvisor) operating at the highest CPU (hardware) privilege level and providing one or more interception points that pass control from the suspicious object executed in the VM N to the micro-kernel and/or hypervisor. In another alternative embodiment, the micro-kernel (without protection domains), VMM 0 and/or one or more hypervisors may be combined into a virtualization layer operating at the highest CPU privilege level that provide the one or more interception points. That is, the virtualization layer may underlie the operating system kernel (and/or guest operating system) such that the virtualization layer is configured to inject the code for remediation of malware at the endpoint.

The foregoing description has been directed to specific embodiments. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. For instance, it is expressly contemplated that the components and/or elements described herein can be implemented as software encoded on a tangible (non-transitory) computer-readable medium (e.g., disks, electronic memory, and/or CDs) having program instructions executing on a computer, hardware, firmware, or a combination thereof. Moreover, the embodiments or aspects thereof can be implemented in hardware, firmware, software, or a combination thereof. In the foregoing description, for example, in certain situations, terms such as “engine,” “component” and “logic” are representative of hardware, firmware and/or software that is configured to perform one or more functions. As hardware, engine (or component/logic) may include circuitry having data processing or storage functionality. Examples of such circuitry may include, but is not limited or restricted to a microprocessor, one or more processor cores, a programmable gate array, a microcontroller, an application specific integrated circuit, semiconductor memory, or combinatorial logic. Accordingly this description is to be taken only by way of example and not to otherwise limit the scope of the embodiments herein. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the embodiments herein.

Claims

1. A method comprising: receiving an object at an endpoint on a network,determining, by a virtual machine monitor, at least whether the object is suspicious as including possible malware configured to attempt a modification of one or more kernel resources;instantiating, by the virtual machine monitor, a virtual machine as a container including an operating system process executing contents of the object, the operating system process to access one or more kernel resources;monitoring one or more operations of the operating system process included in the virtual machine as the operating system process accesses the one or more kernel resources of the endpoint; andinjecting code into a portion of memory associated with an address space of the operating system process during instrumentation of the virtual machine, the injected code being configured to remediate the modification of the one or more kernel resources accessed by the operating system process by restoring an original state of the one or more kernel resources without terminating the operating system process.

2. The method of claim 1 wherein the injected code executes in the portion of the memory associated with the address space of the operating system process to effect the remediation of the one or more kernel resources.

3. The method of claim 1 wherein the injecting of the code comprises: overwriting the object in the portion of the memory, and wherein the one or more kernel resources include locations in the portions of the memory storing the object.

4. The method of claim 1 further comprising: capturing the original state of the one or more kernel resources prior to the operating system process accessing the one or more kernel resources; andexecuting the injected code to restore the modification of the one or more kernel resources to the original state.

5. The method of claim 1 wherein a message having the injected code is received via the network at the endpoint, the message instructing the endpoint to restore the one or more kernel resources.

6. The method of claim 1 wherein the modification to the one or more kernel resources is prevented by the injected code, thereby thwarting the attempted modification of the one or more kernel resources by the object.

7. The method of claim 1 wherein the operating system process includes instructions for a version of an application having known malware in the object, the application stored in a file unpatched to prevent the modification of the one or more kernel resources.

8. The method of claim 1 wherein a virtual machine monitor injects the code into the operating system process in response to a capability violation of a protection domain associated with the operating system process.

9. The method of claim 1 wherein an original flow of execution of the operating system process is restored without altering the logic of the software instructions of the operating system process.

10. The method of claim 1 wherein the instantiating of the virtual machine as the container comprises creating an instance from another virtual machine that is substantially similar to the VM, but includes different instrumentation logic.

11. The method of claim 10 wherein the injecting of the code comprises: overwriting the object in the portion of memory, and wherein the one or more kernel resources include locations in the portions of the memory storing the object.

12. The method of claim 1, wherein the determining that the operating system process is suspicious includes conducting a static analysis on the object, the static analysis includes one or more non-behavioral analyses of the object in order to detect, without execution of the object, anomalous characteristics associated with the object.

13. A method to remediate malware, included as part of an object, that is infecting an endpoint, the method comprising: determining, by a virtual machine monitor, at least whether the object is suspicious as possibly including malware configured to attempt a modification of one or more kernel resources;instantiating, by the virtual machine monitor, a virtual machine to process an operating system process configured to execute contents of an object that include possible malware, the operating system process having instructions for a version of an application vulnerable to the malware;monitoring one or more operations of the operating system process included in the virtual machine as the operating system process accesses one or more kernel resources; andinjecting code into a portion of memory associated with an address space of the operating system process during instrumentation of the virtual machine, the injected code being configured to remediate the modification of at least one of the one or more kernel resources accessed by the operating system process by at least restoring an original state of the at least one of the one or more kernel resources without terminating the operating system process.

14. The method of claim 13 wherein the injected code executes in the portion of the memory associated with the address space of the operating system process to effect the remediation of the at least one of the one or more kernel resources.

15. The method of claim 13 further comprising: capturing the original state of the one or more kernel resources prior to the operating system process accessing the one or more kernel resources; andexecuting the injected code to restore the modification of the at least one of the one or more kernel resources to the original state.

16. The method of claim 13 wherein a message having the injected code is received via a network at the endpoint, the message instructing the endpoint to restore the modification of the at least one kernel resource of the one or more kernel resources.

17. The method of claim 13 wherein the modification to the at least one of the one or more kernel resources is prevented by the injected code, thereby thwarting the modification of the at least one of the one or more kernel resources by the object.

18. The method of claim 13 wherein the operating system process includes instructions for the version of the application vulnerable to the known malware, the application being stored in a file unpatched from preventing the attempted modification of the one or more kernel resources.

19. The method of claim 13 wherein the virtual machine monitor injects the code into the operating system process in response to a capability violation of a protection domain associated with the operating system process.

20. The method of claim 13 wherein an original flow of execution of the operating system process is restored without terminating the operating system process.

21. The method of claim 13, wherein the determining that the operating system process is suspicious includes conducting a static analysis on the object, the static analysis includes one or more non-behavioral analyses of the object in order to detect, without execution of the object, anomalous characteristics associated with the object.

22. A system comprising: a network interface connected to a network;a memory coupled to the network interface and configured to store an object, a module, a virtual machine monitor and a virtual machine; anda central processing unit (CPU) coupled to the memory and adapted to execute the module, virtual machine monitor and virtual machine, wherein the module and virtual machine monitor are configured to: determine, by the virtual machine monitor, at least whether the object is suspicious as including possible malware configured to attempt a modification of one or more kernel resources,instantiate, by the virtual machine monitor, the virtual machine as a container to include an operating system process executing contents of the object, the operating system process to access one or more kernel resources,monitor one or more operations of the operating system process included in the virtual machine as the operating system process accesses one or more kernel resources, andinject code into a portion of the memory associated with an address space of the operating system process during instrumentation of the virtual machine, the injected code being configured to remediate the modification of the one or more kernel resources accessed by the operating system process by restoring an original state of the one or more kernel resources without terminating the operating system process.

23. The system of claim 22 wherein the injected code executes in the portion of the memory associated with the address space of the operating system process to effect the remediation of the one or more kernel resources.

24. The system of claim 22 wherein the injected code overwrites the object in the portion of the memory, and wherein the one or more kernel resources include locations in the portion of the memory storing the object.

25. The system of claim 22 wherein the module and the virtual machine monitor are further configured to: capture the original state of the one or more kernel resources prior to the operating system process accessing the one or more kernel resources; andexecute the injected code to restore the modification of the one or more kernel resources to the original state.

26. The system of claim 22 wherein a message having the injected code is received via the network at the system from a cloud service, the message instructing the system to restore the one or more kernel resources.

27. The system of claim 22 wherein the modification to the one or more kernel resources is prevented by the injected code, thereby thwarting the modification of the one or more kernel resources by the object.

28. The system of claim 22 wherein the operating system process includes instructions for a version of an application having known malware in the object, the application stored in a file unpatched to prevent attempted modification of the one or more kernel resources by the malware.

29. The system of claim 22 wherein the virtual machine monitor injects the code into the operating system process in response to a capability violation of a protection domain associated with the operating system process.

30. The system of claim 22 wherein an original flow of execution of the operating system process is restored without altering the logic of the software instructions of the operating system process.

31. The system of claim 26 wherein the message includes instructions relative to a beginning of execution of the operating process to inject the code.

32. The system of claim 22, wherein the CPU determining that the operating system process is suspicious by at least conducting a static analysis on the object, the static analysis includes one or more non-behavioral analyses of the object in order to detect, without execution of the object, anomalous characteristics associated with the object.