Detecting lateral movement using a hypervisor
AssigneeNicira, Inc.
InventorPRASAD DABAK
Life of this patent
Estimating the term…
Abstract
The subject matter described herein provides protection against zero-day attacks by detecting, via a hypervisor maintaining an extended page table, an attempt to execute arbitrary code associated with malware in a guest operation system (OS) running within a virtual machine (VM). Further, the subject matter provides detection of lateral movement of the malware. The hypervisor uses hidden breakpoints to detect a request for thread creation, and then determines whether the request is to download and execute arbitrary code.
Claims20
A system for hypervisor detection of attempted arbitrary code execution in zero-day exploits, said system comprising:
- at least one physical processor;
- and
- at least one memory comprising computer program code, the at least one memory and the computer program code configured to, with the at least one physical processor, cause the physical processor to at least:
- detect, by a hypervisor via a hidden breakpoint, a request from a current process in a guest operating system (OS) to create a thread, the request including a process identifier (ID) for the thread;
- in response to detecting the request, determine whether a process ID for the current process is different from the process ID for the thread and different from a process ID for a parent process of the thread;
- and
- upon determining that the process ID for the current process is different from the process ID for the thread and different from the process ID for the parent process of the thread:
- obtain a thread context for the thread and a process context for the current process, the thread context identifying an entry point for the thread, the process context identifying a set of modules associated with the current process;
- and
- upon the entry point being outside an address space of the identified set of modules or associated with a function that loads other code, classify the request as attempted lateral movement associated with malware.
A method for hypervisor detection of attempted arbitrary code execution in zero-day exploits, said method comprising:
- detecting, by a hypervisor via a hidden breakpoint, a request from a current process in a guest operating system (OS) to create a thread, the request including a process identifier (ID) for the thread;
- in response to detecting the request, determining whether a process ID for the current process is different from the process ID for the thread and different from a process ID for a parent process of the thread;
- and
- upon determining that the process ID for the current process is different from the process ID for the thread and different from the process ID for the parent process of the thread:
- obtaining a thread context for the thread and a process context for the current process, the thread context identifying an entry point for the thread, the process context identifying a set of modules associated with the current process;
- and
- upon the entry point being outside an address space of the identified set of modules or associated with a function that loads other code, classifying the request as attempted lateral movement associated with malware.
One or more non-transitory computer storage media having computer-executable instructions that, upon execution by a processor, cause the processor to at least perform operations comprising:
- detecting, by a hypervisor via a hidden breakpoint, a request from a current process in a guest operating system (OS) to create a thread, the request including a process identifier (ID) for the thread;
- in response to detecting the request, determining whether a process ID for the current process is different from the process ID for the thread and different from a process ID for a parent process of the thread;
- and
- upon determining that the process ID for the current process is different from the process ID for the thread and different from the process ID for the parent process of the thread:
- obtaining a thread context for the thread and a process context for the current process, the thread context identifying an entry point for the thread, the process context identifying a set of modules associated with the current process;
- and
- upon the entry point being outside an address space of the identified set of modules or associated with a function that loads other code, classifying the request as attempted lateral movement associated with malware.
Dependencies are inferred from the claim text.