IP Library Granted Patent US 9,954,825
Granted Patent B2
US 9,954,825 · App. 15/072,092 · Granted Apr 24, 2018

Secure virtual machine

Inventors: Chad Prey (San Diego, CA); Alexander Ryzhak (San Diego, CA); Jeff Thompson (San Diego, CA); John Thompson (Chicago, IL); Bradley Rintoul (San Diego, CA); Adam Browning (Reston, VA); Michael E. Martinka (Vienna, VA); Darby Mullen (San Antonio, TX)
Assignee: NTREPID CORPORATION
H04L63/0272G06F9/45533H04L63/083
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 9,954,825
App. No.
15/072,092
Granted
Apr 24, 2018
Kind
B2
Abstract

Various embodiments pertain to computing devices and virtual machines. In particular, various embodiments relate to the start-up, operation, and communication of virtual machines. A method includes initiating operation of a virtual machine on a computing device, and sending a token from the computing device to a virtual machine, where the token is used to connect the computing device and the virtual machine. The method also includes establishing a virtual private network between the virtual machine and a network node using the token, and launching a user interface of the virtual machine on the computing device after the virtual private network has been established.

Claims (72)

1. A method, comprising:

initiating operation of a virtual machine on a computing device, wherein a user cannot access a user interface of the virtual machine until after a virtual private network is established;

sending a token from the computing device to the virtual machine, wherein the token is used to connect the computing device to the virtual machine;

establishing the virtual private network between the virtual machine and a network node using the token; and

launching the user interface of the virtual machine on the computing device after the virtual private network has been established.

2. The method according to claim 1 , wherein the token is configured for at least a short term or a single use.

3. The method according to claim 1 , wherein the token is random and does not include any user identifying information.

4. The method according to claim 1 , further comprising:

generating the token in another network node.

5. The method according to claim 4 , further comprising:

retrieving the token with a host-side application.

6. The method according to claim 5 , wherein the host-side application communicates with the virtual machine.

7. The method according to claim 6 , wherein the host-side application sends at least one uniform resource locator to the virtual machine.

8. The method according to claim 7 , wherein the uniform resource locator is sent to the virtual machine via the network node.

9. The method according to claim 1 , further comprising:

generating the token in the computing device with the use of an algorithm.

10. The method according to claim 1 , wherein establishing the virtual private network is automatic.

11. The method according to claim 1 , wherein the virtual private network is the only network data path into the virtual machine and out of the virtual machine.

12. The method according to claim 1 , further comprising:

locking down all communications between the virtual machine and all external devices and networks if the virtual private network is disrupted or dropped.

13. The method according to claim 1 , further comprising:

re-establishing the virtual private network automatically if the virtual private network drops.

14. The method according to claim 1 , wherein a user desktop on the computing device and the virtual machine are different instances on a virtual device interface server.

15. An apparatus comprising:

at least one memory comprising computer program code;

at least one processor;

wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

initiate operation of a virtual machine on a computing device, wherein a user cannot access a user interface of the virtual machine until after a virtual private network is established;

send a token from the computing device to the virtual machine, wherein the token is used to connect the computing device to the virtual machine;

establish the virtual private network between the virtual machine and a network node using the token; and

launch the user interface of the virtual machine on the computing device after the virtual private network has been established.

16. The apparatus according to claim 15 , wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

generate the token in another network node.

17. The apparatus according to claim 15 , wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

generate the token in the computing device with the use of an algorithm.

18. The apparatus according to claim 15 , wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

retrieve the token with a host-side application.

19. The apparatus according to claim 15 , wherein establishing the virtual private network is automatic.

20. The apparatus according to claim 15 , wherein the virtual private network is the only network data path into the virtual machine and out of the virtual machine.

21. The apparatus according to claim 15 , further comprising:

locking down all communications between the virtual machine and all external devices and networks, including the network node, if the virtual private network is disrupted or dropped.

22. The apparatus according to claim 15 , wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

re-establish the virtual private network automatically if the virtual private network drops.

23. The method according to claim 15 , wherein a user desktop on the computing device and the virtual machine are different instances on a virtual device interface server.

24. A method comprising:

receiving a token initiating operation of a virtual machine, wherein a user cannot access a user interface of the virtual machine until after a virtual private network is established;

establishing the virtual private network between the virtual machine and a network node using the token before displaying the user interface to the virtual machine on the computing device; and

communicating with the virtual machine.

25. The method according to claim 24 , wherein the token is retrieved from another network node by the computing device.

26. The method according to claim 24 , wherein a host-side application is used to generate the token.

27. The method according to claim 24 , wherein establishing the virtual private network is automatic.

28. The method according to claim 24 , wherein the virtual private network is the only network data path into the virtual machine and out of the virtual machine.

29. The method according to claim 24 , further comprising:

locking down all communications between the virtual machine and all external devices and networks, including the network node, if the virtual private network is disrupted or dropped.

30. The method according to claim 24 , further comprising:

re-establishing the virtual private network automatically if the virtual private network is disrupted.

31. An apparatus comprising:

at least one memory comprising computer program code;

at least one processor;

wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

receive a token initiating operation of a virtual machine, wherein a user cannot access a user interface of the virtual machine until after a virtual private network is established;

establish the virtual private network between the virtual machine and a network node using the token before displaying the user interface to the virtual machine on the computing device; and

communicate with the virtual machine.

32. The apparatus according to claim 31 , wherein the token is retrieved from another network node by the computing device.

33. The apparatus according to claim 31 , wherein a host-side application is used to generate the token.

34. The apparatus according to claim 31 , wherein the computing device uses an algorithm to generate the token.

35. The apparatus according to claim 31 , wherein establishing the virtual private network is automatic.

36. The apparatus according to claim 31 , wherein the virtual private network is the only network data path into the virtual machine and out of the virtual machine.

37. The apparatus according to claim 31 , wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

lock down all communications between the virtual machine and all external devices and networks, including the network node, if the virtual private network is disrupted or dropped.

38. The apparatus according to claim 31 , wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to:

re-establish the virtual private network automatically if the virtual private network is disrupted.

Assignments (3)
SECURITY INTEREST Recorded Jan 26, 2026
From: NTREPID, LLC
To: BOATHOUSE CAPITAL III LP
Reel/Frame 073583/0248 →
ENTITY CONVERSION Recorded Dec 3, 2018
From: NTREPID CORPORATION
To: NTREPID, LLC
Reel/Frame 050143/0499 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 16, 2016
From: PREY, CHAD; RYZHAK, ALEXANDER; THOMPSON, JEFF; THOMPSON, JOHN; RINTOUL, BRADLEY; BROWNING, ADAM; MARTINKA, MICHAEL E.; MULLEN, DARBY
To: NTREPID CORPORATION
Reel/Frame 038004/0895 →
Continuity (1)
Related Publication 20170272404A1 · Sep 21, 2017