Hypervisor driven embedded endpoint security monitoring
Aspects of the present disclosure are directed to methods and systems of hypervisor driven embedded endpoint security monitoring. A computer implemented method may include providing one or more computer processors configured to operate a bare-metal hypervisor; launching a user OS virtual machine operatively connected to the hypervisor; launching a security virtual machine operatively connected to the hypervisor and receiving data from the security virtual machine via the hypervisor; and receiving data representative of security information from the computer processor processed by the security virtual machine. The hypervisor may include using a virtual switch for providing communications between the user OS virtual machine and the security virtual machine. The method may include using the security virtual machine to monitor malware on the user OS virtual machine.
1. An apparatus, comprising:
a computing device having:
at least one processor; and
at least one memory storing computer executable instructions that, when executed, cause the apparatus at least to:
booting up a bare-metal hypervisor on the computing device; in response to booting up the bare-metal hypervisor, concurrently launching a user OS virtual machine and a security virtual machine (security VM) transparent to a user on the computing device, the security VM isolating malicious software occurring in the user OS virtual machine;
abstracting an application programming interface (API) of the computing device into a virtual switch, the security virtual machine having full access to the virtual switch; mirroring data traffic to and from the user OS virtual machine;
directing data from the user OS virtual machine to a network cloud, the mirrored data traffic being directed through the virtual switch of the hypervisor;
routing the mirrored data traffic to the security VM; and monitoring the data traffic by the security VM by: observing all data traffic to and from the user OS virtual machine via the virtual switch; and
sending data representative of security information to a network control center (NCC) server; and
the NCC server configured to:
receive said data representative of security information;
subsequently analyze the security information; and
in response to analysis of the security information, deploy components to the bare-metal hypervisor.
2. The apparatus of claim 1 , wherein the executable instructions, when executed, further cause the apparatus to use the security virtual machine to monitor intrusive executable instructions on the user OS virtual machine.
3. The apparatus of claim 1 , wherein the executable instructions, when executed, further cause the apparatus to receive data representative of log activity associated with the computing device.
4. The apparatus of claim 1 , wherein the executable instructions, when executed, further cause the apparatus to receive data representative of a shared memory associated with the computing device.
5. The apparatus of claim 1 , wherein the executable instructions, when executed, further cause the apparatus to check authenticity of the computing device as a node endpoint by the security virtual machine.
6. A computer implemented method, comprising:
providing one or more computer processors configured to boot up a bare-metal hypervisor;
in response to booting up the bare-metal hypervisor, concurrently launching a user OS virtual machine and a security virtual machine (VM) transparent to a user, the security VM isolating malicious software occurring in the user OS virtual machine;
abstracting an application programming interface (API) into a virtual switch, the security virtual machine having full access to the virtual switch; mirroring data traffic to and from the user OS virtual machine;
directing data from the user OS virtual machine to a network cloud, the mirrored data traffic being directed through the virtual switch of the hypervisor;
routing the mirrored data traffic to the security VM;
monitoring the data traffic by the security VM by:
observing all data traffic to and from the user OS virtual machine via the virtual switch; and
sending security information to a network control center (NCC) server;
receiving, by the NCC server, said data representative of the security information;
subsequently analyzing the security information; and
in response to analysis of the security information, deploying components to the bare-metal hypervisor.
7. The computer implemented method of claim 6 , further comprising a step of using the security virtual machine to monitor intrusive executable instructions on the user OS virtual machine.
8. The computer implemented method of claim 6 , further comprising a step of receiving data representative of log activity associated with the one or more computer processors via the security virtual machine.
9. The computer implemented method of claim 6 , further comprising a step of receiving data representative of a shared memory associated with the one or more computer processors.
10. The computer implemented method of claim 6 , further comprising a step of checking authenticity of the one or more computer processors as a node endpoint by the security virtual machine.
11. One or more non-transitory computer readable media storing computer executable instructions that, when executed by at least one processor, cause the at least one processor to perform a method comprising:
booting up a bare-metal hypervisor;
in response to booting up the bare-metal hypervisor, concurrently launching a user OS virtual machine and a security virtual machine (VM) transparent to a user, the security VM isolating malicious software occurring in the user OS virtual machine;
abstracting an application programming interface (API) into a virtual switch, the security virtual machine having full access to the virtual switch; mirroring data traffic to and from the user OS virtual machine;
directing data from the user OS virtual machine to a network cloud, the mirrored data traffic being directed through the virtual switch of the hypervisor;
routing the mirrored data traffic to the security VM;
monitoring the data traffic by the security VM by:
observing all data traffic to and from the user OS virtual machine via the virtual switch; and
sending security information to a network control center (NCC) server;
receiving, by the NCC server, said data representative of the security information;
subsequently analyzing the security information; and
in response to the analysis of the security information, deploying components to the bare-metal hypervisor.
12. The one or more non-transitory computer readable media of claim 11 , further comprising a step of using the security virtual machine to monitor intrusive executable instructions on the user OS virtual machine.
13. The one or more non-transitory computer readable media of claim 11 , further comprising a step of receiving data representative of log activity associated with the one or more computer processors via the security virtual machine.
14. The one or more non-transitory computer readable media of claim 11 , further comprising a step of receiving data representative of a shared memory associated with the least one processor.
15. The one or more non-transitory computer readable media of claim 11 , further comprising a step of checking authenticity of the at least one processor as a node endpoint by the security virtual machine.