IP Library Granted Patent US 10,157,276
Granted Patent B2
US 10,157,276 · App. 15/169,203 · Granted Dec 18, 2018

Extracting malicious instructions on a virtual machine in a network environment

Inventors: Jeffery Ray Schilling (Murphy, TX); Chase Cooper Cunningham (Frisco, TX); Tawfiq Mohan Shah (Argyle, TX); Srujan Das Kotikela (Dallas, TX)
Assignee: Armor Defense Inc.
G06F21/53G06F9/45545G06F9/45558G06F12/1009G06F17/30424G06F17/30598G06F21/54G06F21/56G06F21/561G06F21/565G06F21/566H04L63/0227H04L63/1408H04L63/1416H04L63/1425G06F21/567G06F2009/45579G06F2009/45583G06F2009/45587G06F2009/45591G06F2009/45595G06F2212/1052G06F2212/152G06F2212/154G06F2221/034G06F2221/2149
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,157,276
App. No.
15/169,203
Granted
Dec 18, 2018
Kind
B2
Abstract

A system including a guest virtual machine with one or more virtual machine measurement points configured to collect virtual machine operating characteristics metadata and a hypervisor control point configured to receive virtual machine operating characteristics metadata from the virtual machine measurement points. The hypervisor control point is further configured to send the virtual machine operating characteristics metadata to a hypervisor associated with the guest virtual machine. The system further includes the hypervisor configured to receive the virtual machine operating characteristics metadata and to forward the virtual machine operating characteristics metadata to a hypervisor device driver in a virtual vault machine. The system further includes the virtual vault machine configured to determine a classification for the guest virtual machine based on the virtual machine operating characteristics metadata and to send the determined classification to a vault management console.

Claims (71)

1. A system comprising:

a guest virtual machine comprising:

one or more virtual machine measurement points implemented by one or more processors to operate in a kernel space of the guest virtual machine, and configured to collect virtual machine operating characteristics metadata from at least one of the kernel space of the guest virtual machine and a user space of the guest virtual machine; and

a hypervisor control point implemented by the one or more processors to operate in the kernel space of the guest virtual machine, and configured to:

receive virtual machine operating characteristics metadata from the virtual machine measurement points; and

send the virtual machine operating characteristics metadata to a hypervisor associated with the guest virtual machine using a hypervisor connecting interface;

the hypervisor connecting interface configured to provide a secure virtual connection between the guest virtual machine and the hypervisor;

the hypervisor configured to:

receive the virtual machine operating characteristics metadata; and

forward the virtual machine operating characteristics metadata to a hypervisor device driver of a virtual vault machine using a secure virtual network connection;

the secure virtual network connection configured to provide a secure virtual connection between the hypervisor and the virtual vault machine, wherein the secure virtual network connection is configured to employ policy rules that only accepts data from the hypervisor and rejects data from unknown sources; and

the virtual vault machine configured to:

implement the hypervisor device driver in a kernel space of the virtual vault machine, wherein the hypervisor device driver is configured to send the virtual machine operating characteristics metadata to an analysis tool in a user space of the virtual vault machine; and

determine a classification for the guest virtual machine based on the virtual machine operating characteristics metadata using the analysis tool, wherein the classification is one of a healthy state and a compromised state; and

send the determined classification to a vault management console.

2. The system of claim 1 , wherein the secure virtual network connection comprises a tunnel connection with one or more virtual switches.

3. The system of claim 1 , wherein the processor implementing the virtual machine measurement points and the hypervisor control point is isolated from one or more other processors available to the guest virtual machine.

4. The system of claim 1 , wherein:

sending the virtual machine operating characteristics metadata to the hypervisor comprises sending the virtual machine operating characteristics metadata as a payload in an encrypted packet via the hypervisor connecting interface;

the encrypted packet does not comprise a destination address; and

forwarding the virtual machine operating characteristics metadata to the hypervisor device driver comprises sending the encrypted packet to the hypervisor device driver via the secure virtual network connection.

5. A system comprising:

a guest virtual machine comprising:

one or more virtual machine measurement points implemented by a processor, and configured to collect virtual machine operating characteristics metadata; and

a hypervisor control point implemented by the processor, and configured to:

receive virtual machine operating characteristics metadata from the one or more virtual machine measurement points; and

send the virtual machine operating characteristics metadata to a hypervisor associated with the guest virtual machine using a hypervisor connecting interface;

the hypervisor connecting interface configured to provide a secure virtual connection between the guest virtual machine and the hypervisor;

the hypervisor in data communication with the guest virtual machine, and configured to:

receive the virtual machine operating characteristics metadata; and

forward the virtual machine operating characteristics metadata to a hypervisor device driver in a virtual vault machine using a secure virtual network connection;

the secure virtual network connection configured to provide a secure virtual connection between the hypervisor and the virtual vault machine, wherein the secure virtual network connection is configured to employ policy rules that only accepts data from the hypervisor and rejects data from unknown sources; and

the virtual vault machine in data communication with the hypervisor, and configured to:

determine a classification for the guest virtual machine based on the virtual machine operating characteristics metadata, wherein the classification is one of a healthy state and a compromised state; and

send the determined classification to a vault management console.

6. The system of claim 5 , wherein the processor implementing the virtual machine measurement points and the hypervisor control points is isolated from one or more other processors available to the guest virtual machine.

7. The system of claim 5 , wherein the secure virtual network connection comprises a tunnel connection with one or more virtual switches.

8. The system of claim 5 , wherein:

the secure virtual network connection comprises a first tunnel connection; and

the hypervisor connecting interface comprises a second tunnel connection.

9. The system of claim 5 , wherein:

sending the virtual machine operating characteristics metadata to the hypervisor comprises sending the virtual machine operating characteristics metadata as a payload in an encrypted packet via the hypervisor connecting interface;

the encrypted packet does not comprise a destination address; and

forwarding the virtual machine operating characteristics metadata to the hypervisor device driver comprises sending the encrypted packet to the hypervisor device driver via the secure virtual network connection.

10. The system of claim 5 , wherein:

the hypervisor device driver is in a kernel space of the virtual vault machine; and

the hypervisor device driver is configured to communicate the virtual machine operating characteristics metadata to an analysis tool in a user space of the virtual vault machine to determine the classification.

11. The system of claim 5 , wherein:

the hypervisor control point and the one or more virtual machine measurement points are in a kernel space of the guest virtual machine; and

the one or more virtual machine measurement points are configured to collect the virtual machine operating characteristics metadata from at least one of the kernel space of the guest machine and a user space of the guest virtual machine.

12. A virtual machine intrusion detection method comprising:

collecting, using virtual machine measurement points operably coupled to a hypervisor control point, virtual machine operating characteristics metadata from a guest virtual machine, wherein the virtual machine measurement points and the hypervisor control point are implemented by a processor;

generating, by the hypervisor control point, a packet that comprises the virtual machine operating characteristics metadata;

sending, by the hypervisor control point, the packet to a hypervisor associated with the guest virtual machine via a hypervisor connecting interface, wherein the hypervisor connecting interface is configured to provide a secure virtual connection between the guest virtual machine and the hypervisor;

forwarding, by the hypervisor, the packet to a hypervisor device driver in a virtual vault machine via a secure virtual network connection, wherein the secure virtual network connection is configured to provide a secure virtual connection between the hypervisor and the virtual vault machine, wherein the secure virtual network connection is configured to employ policy rules that only accepts data from the hypervisor and rejects data from unknown sources;

determining, by the virtual vault machine, a classification for the guest virtual machine based on the virtual machine operating characteristics metadata; and

sending, by the virtual vault machine, the determined classification to a vault management console.

13. The method of claim 12 , wherein the processor implementing the virtual machine measurement points and the hypervisor control point is isolated from one or more other processors available to the guest virtual machine.

14. The method of claim 12 , wherein the secure virtual network connection comprises a tunnel connection with one or more virtual switches.

15. The method of claim 12 , wherein:

the secure virtual network connection comprises a first tunnel connection; and

the hypervisor connecting interface comprises a second tunnel connection.

16. The method of claim 12 , wherein:

generating the packet comprises encrypting the virtual machine operating characteristics metadata as a payload; and

the packet does not comprise a destination address.

17. The method of claim 12 , wherein:

the hypervisor device driver is in a kernel space of the virtual vault machine; and

the hypervisor device driver is configured to communicate the virtual machine operating characteristics metadata to an analysis tool in a user space of the virtual vault machine to determine the classification.

18. The method of claim 12 , wherein:

the hypervisor control point and the virtual machine measurement points are in a kernel space of the guest virtual machine; and

collecting the virtual machine operating characteristics metadata comprises collecting the virtual machine operating characteristics metadata from at least one of the kernel space of the guest virtual machine and a user space of the guest virtual machine.

Assignments (6)
RELEASE OF SECURITY INTEREST Recorded Apr 6, 2026
From: ESCALATE CAPITAL IV, LP
To: ARMOR DEFENSE INC.; ARMOR DEFENSE LIMITED
Reel/Frame 074284/0469 →
RELEASE OF SECURITY INTEREST Recorded Apr 6, 2026
From: SILICON VALLEY BANK
To: ARMOR DEFENSE LIMITED; ARMOR DEFENSE INC.
Reel/Frame 074284/0476 →
SECURITY INTEREST Recorded Oct 1, 2024
From: ARMOR DEFENSE INC.
To: SUNFLOWER BANK , N.A.
Reel/Frame 068758/0972 →
SECURITY INTEREST Recorded Dec 23, 2020
From: ARMOR DEFENSE INC.; ARMOR DEFENSE LIMITED
To: ESCALATE CAPITAL IV, LP
Reel/Frame 054741/0749 →
SECURITY INTEREST Recorded Oct 16, 2019
From: ARMOR DEFENSE, INC.
To: SILICON VALLEY BANK
Reel/Frame 050730/0113 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 31, 2016
From: SCHILLING, JEFFERY RAY; CUNNINGHAM, CHASE COOPER; SHAH, TAWFIQ MOHAN; KOTIKELA, SRUJAN DAS
To: ARMOR DEFENSE INC.
Reel/Frame 038753/0469 →
Continuity (2)
Provisional Application 62258730 · Nov 23, 2015
Related Publication 20180004938A1 · Jan 4, 2018
Cited By (4)
US 12,248,581 US 12,361,140 US 12,547,733 US 12,683,989