Distributed trusted virtualization platform

• US 20090204964A1
• Filed: 10/14/2008
• Published: 08/13/2009
• Est. Priority Date: 10/12/2007
• Status: Abandoned Application

• Current Assignee: Zitovault, Inc.
• Original Assignee: Zitovault, Inc.
• Inventors: Foley, Peter F., Gupta, Rajesh, Haines, Brent, Bethur, Jithendra, Cherukuri, Rao
• Application Number:
  US12/287,833
• Publication Number:
  US 20090204964A1
• Time in Patent Office: Days
• US Class Current: 718/1
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 21/554 involving event detection and direct action
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 9/45537 Provision of facilities of other operating environments, e.g. WINE I/O emulation G06F13/105
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 2209/127 Trusted platform modules [TPM]
• CPC Class Codes: H04L 2209/42 Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/603 Digital right managament [DRM]
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations network architectures or network communication protocols using hop-by-hop encryption H04L63/0464
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 9/3271 using challenge-response

Abstract

A platform architecture shifts the networked computing paradigm from PC+Network to a system using trusted mobile internet end-point (MIEP) devices and cooperative agents hosted on a trusted server. The MIEP device can participate in data flows, arbitrate authentication, and/or participate in implementing security mechanisms, all within the context of assured end-to-end security. The MIEP architecture improves platform-level capabilities by suitably (and even dynamically) partitioning what is done at the MIEP nodes, the network, and the server based infrastructure for delivering services.

Claims

1. A trusted virtualization system comprising a trustworthy mobile endpoint device, the mobile endpoint device comprising:

a communications module that provides a communications link between the mobile endpoint device and a networked infrastructure;

a host processor and memory;

a hardware based tamper-resistant module (hereafter, the hardware root of trust or HROT), the HROT comprising;

secure non-volatile memory for storing integrity measurement data and data related to keys,

a computational module;

a key pair generation module, and

a random number generator;

a trusted boot process executed by the host processor to boot the mobile endpoint device into a known state, the trusted boot process utilizing the HROT to provide cryptographic resources and secure non-volatile memory to verify the integrity of the mobile endpoint device;

an attestation process executed by the host processor to attest to the integrity of the mobile endpoint device in response to an attestation challenge, the attestation process utilizing the HROT to provide integrity measurements of the mobile endpoint device, said integrity measurements verifying an integrity of a state of the mobile endpoint device;

a Type-1 trusted virtual machine monitor (hereafter, the Type-1 TMM) that executes on the host processor, the trusted boot process including booting of the Type-1 TVMM and utilizing the HROT to verify the integrity of the Type-1 TVMM, the Type-1 TVMM capable of hosting a plurality of virtual machines and virtualizing the HROT independently for each such hosted virtual machine.

2. The virtualization system of claim 1 wherein the attestation process can attest to a specific virtual machine independent of other virtual machines hosted by the mobile endpoint device, the attestation process utilizing the HROT to provide integrity measurements of layers in the hardware and software stack that are required for correct operation of the specific virtual machine.

3. The virtualization system of claim 2 wherein the virtual machines can host operating systems and the attestation process can attest to a specific operating system independent of other operating systems hosted by the mobile endpoint device, the attestation process utilizing the HROT to provide integrity measurements of layers in the hardware and software stack that are required for correct operation of the specific operating system.

4. The virtualization system of claim 3 wherein the virtual machines can host operating systems, the operating systems can host applications, and the attestation process can attest to a specific application independent of other applications hosted on the mobile endpoint device, the attestation process utilizing the HROT to provide integrity measurements of layers in the hardware and software stack that are required for correct operation of the specific application.

5. The virtualization system of claim 1 wherein the networked infrastructure comprises an agent server communicating with the mobile endpoint device over a communications channel that includes the communications link, the agent server comprising:

a virtual machine monitor hosted by the agent server, the virtual machine monitor capable of hosting virtual machines on behalf of the mobile endpoint device.

6. The virtualization system of claim 5 wherein the agent server further comprises:

a host processor and memory, the virtual machine monitor executing on the host processor;

an HROT comprising;

secure non-volatile memory for storing integrity measurement data and data related to keys,

a computational module,

a key pair generation module, and

a random number generator;

a trusted boot process executed by the host processor to boot the server into a known state, the trusted boot process utilizing the HROT to provide cryptographic resources and secure non-volatile memory to verify the integrity of the mobile endpoint device;

an attestation process executed by the host processor to attest to an integrity of the server in response to an attestation challenge received from the mobile endpoint device, the attestation process utilizing the HROT to provide integrity measurements of the server, said integrity measurements verifying an integrity of a state of the server; and

the virtual machine monitor capable of hosting a plurality of virtual machines (including virtual machines hosted on behalf of the mobile endpoint device) and virtualizing the HROT independently for each such hosted virtual machine.

7. The virtualization system of claim 6 wherein, on the agent server, the attestation process can attest to a specific virtual machine hosted on behalf of the mobile endpoint device independent of other virtual machines hosted by the agent server, the attestation process utilizing the HROT to provide integrity measurements of layers in the hardware and software stack that are required for correct operation of the specific virtual machine.

8. The virtualization system of claim 6 wherein, on the agent server, the virtual machines can host operating systems and the attestation process can attest to an operating system hosted on the virtual machine hosted on behalf of the mobile endpoint device independent of other operating systems hosted by the agent server, the attestation process utilizing the HROT to provide integrity measurements of layers in the hardware and software stack that are required for correct operation of said operating system.

9. The virtualization system of claim 6 wherein, on the agent server, the virtual machines can host operating systems, the operating systems can host applications, and the attestation process can attest to a specific application hosted on the virtual machine on behalf of the mobile endpoint device independent of other applications hosted on the agent server, the attestation process utilizing the HROT to provide integrity measurements of layers in the hardware and software stack that are required for correct operation of the specific application.

10. The virtualization system of claim 5 wherein the mobile endpoint device can spawn virtual machines hosted by the agent server.

11. The virtualization system of claim 10 wherein the agent server can spawn virtual machines hosted by the mobile endpoint device.

12. The virtualization system of claim 11 wherein the agent server can stipulate a set of policies through the virtual machines spawned by the agent server on the mobile endpoint device.

13. The virtualization system of claim 10 wherein the mobile endpoint device can spawn agent applications hosted by virtual machines hosted by the agent server.

14. The virtualization system of claim 13 wherein the agent application is an anti-malware application that scans data prior to said data being transferred to the mobile endpoint device.

15. The virtualization system of claim 13 wherein the agent application is a behavioral monitoring agent that receives signatures from the mobile endpoint device of the execution behavior of the mobile endpoint device and uses said signatures to determine a health state of the mobile endpoint device.

16. The virtualization system of claim 13 wherein the agent application is a web browsing anonymization agent that assists the mobile endpoint device to retain anonymity while the mobile endpoint device browses the web.

17. The virtualization system of claim 13 wherein the agent application is a P2P proxy for a P2P client application, where the P2P client functionality is partitioned between the mobile endpoint device and the P2P proxy, the P2P proxy supporting upstream forwarding bandwidth requirements of a P2P network, said P2P proxy forwarding P2P downstream data to the mobile endpoint device and forwarding P2P upstream data to requesting peers in a P2P swarm.

18. The virtualization system of claim 13 wherein the agent application is a web filtering content agent that removes unwanted web page content before the web page is transmitted to the mobile endpoint device.

19. The virtualization system of claim 13 wherein the agent application is a data compression agent that compresses data before transmission to the mobile endpoint device.

20. The virtualization system of claim 13 wherein the agent application is a data storage agent that manages web based data storage for the mobile endpoint device.

21. The virtualization system of claim 13 wherein the agent application is a transaction proxy that is authorized to act on behalf of the mobile endpoint device to manage transactions.

22. The virtualization system of claim 13 wherein the agent application is a communications channel virtualization agent that coordinates a virtualization of multiple communications channels between the mobile endpoint device and the agent server into a single virtual communications channel.

23. The virtualization system of claim 13 wherein the agent application is a single sign-on agent that serves as a web identity broker to manage various user web identities and authentication information to create a personal secure virtual web SSO (Single Sign On) service.

24. The virtualization system of claim 13 wherein the agent application adjusts its functionality based on contextual awareness of the state of the mobile endpoint device.

25. The virtualization system of claim 13 wherein the agent application adjusts its functionality based on a bandwidth of the communications channel between the mobile endpoint device and the agent server.

26. The virtualization system of claim 13 wherein the agent application adjusts its functionality based on a latency of the communications channel between the mobile endpoint device and the agent server.

27. The virtualization system of claim 13 wherein the agent application adjusts its functionality based on a usage cost of the communications channel between the mobile endpoint device and the agent server.

28. The virtualization system of claim 13 wherein the agent application adjusts its functionality based on an energy status of the mobile endpoint device and/or energy use cost of the agent application.

29. The virtualization system of claim 13 wherein the agent application adjusts its functionality based on memory availability on the mobile endpoint device.

30. The virtualization system of claim 13 wherein the agent application adjusts its functionality based on a past location and/or time of past location of the mobile endpoint device and also based on current location and current state of the mobile endpoint device.

31. The virtualization system of claim 10 wherein the mobile endpoint device can stipulate a set of policies through the virtual machines spawned by the mobile endpoint device on the agent server.

32. The virtualization system of claim 31 wherein the set of policies includes a policy on permissible I/O modalities.

33. The virtualization system of claim 31 wherein the set of policies includes a policy on which URLs or web sites may be accessed by the mobile endpoint device.

34. The virtualization system of claim 31 wherein the set of policies includes a policy on permissible applications.

35. The virtualization system of claim 31 wherein the set of policies includes a policy on when and/or where certain applications may be executed.

36. The virtualization system of claim 5 wherein the mobile endpoint device has a capability to clone a virtual machine hosted by the Type-1 TVMM and also operating system(s) and application(s) hosted on the virtual machine, and the mobile endpoint device further has a capability to transfer the clone to the agent server as an executable template for execution on behalf of the mobile endpoint device.

37. The virtualization system of claim 36 wherein the executable template further includes integrity measurements of the cloned virtual machine, operating system(s) and application(s).

38. The virtualization system of claim 5 wherein the mobile endpoint device has a capability to clone a virtual machine hosted by the Type-1 TVMM and also operating system(s) and application(s) hosted on the virtual machine, and the mobile endpoint device further has a capability to transfer the clone to the agent server as a honeypot clone to test software or content destined for the mobile endpoint device for malware or malicious behavior before said software or content is transferred to the mobile endpoint device.

39. The virtualization system of claim 1 wherein a past location history and/or times of past locations of the mobile endpoint device is used as a factor in a multi-factor user authentication process.

40. The virtualization system of claim 1 wherein the Type-1 TVMM collects aggregate meta-data that cannot be associated with any particular virtual machine, the meta-data characterizing a behavior and/or performance of virtualized resources used by the mobile endpoint device, the meta-data available to the virtual machines hosted by the Type-1 TVMM and to applications hosted by said virtual machines.

41. The virtualization system of claim 1 wherein the mobile endpoint device further comprises:

a display framebuffer, a portion of which is controlled by the Type-1 TVMM to indicate a trust level of the mobile endpoint device.

42. The virtualization system of claim 41 wherein the mobile endpoint device further comprises:

a multi-windowed environment, wherein the Type-1 TVMM can lock down a cursor and keyboard focus to a specific window.

43. The virtualization system of claim 41 wherein the portion of the display framebuffer controlled by the Type-1 TVMM further indicates a trust level of a virtual component executing on an agent server in the networked infrastructure on behalf of the mobile endpoint device.

44. The virtualization system of claim 1 wherein the communications link is a wireless communications link.

45. The virtualization system of claim 1 wherein the networked infrastructure includes the Internet.

46. A mobile trust module comprising:

a first standard connector for connecting the mobile trust module to a mobile endpoint device;

a hardware based tamper-resistant module (hereafter, the hardware root of trust or HROT), the HROT comprising;

secure non-volatile memory for storing integrity measurement data and data related to keys,

a computational module,

a key pair generation module,

a random number generator;

a trusted boot process that boots the mobile endpoint device into a known state, the trusted boot process utilizing the HROT to provide cryptographic resources and secure non-volatile memory to verify the integrity of the mobile endpoint device;

an attestation process to attest to an integrity of the mobile endpoint device in response to an attestation challenge received by the mobile endpoint device, the attestation process utilizing the HROT to provide integrity measurements of the mobile endpoint device, said integrity measurements verifying an integrity of a state of the mobile endpoint device;

a Type-1 trusted virtual machine monitor (hereafter, the Type-1 TVMM), the trusted boot process including booting of the Type-1 TVMM onto the mobile endpoint device and utilizing the HROT to verify an integrity of the Type-1 TVMM, the Type-1 TVMM capable of hosting a plurality of virtual machines and virtualizing the HROT independently for each such hosted virtual machine.

47. The mobile trust module of claim 46 wherein the first standard connector is a USB connector.

48. The mobile trust module of claim 46 wherein the first standard connector is a Secure Digital (SD) connector.

49. The mobile trust module of claim 46 wherein the first standard connector is an SDIO connector.

50. The mobile trust module of claim 46 wherein the first standard connector is a MiniSD connector.

51. The mobile trust module of claim 46 wherein the first standard connector is a MicroSD connector.

52. The mobile trust module of claim 46 further comprising:

a second standard connector of a same type but opposite polarity as the first standard connector, allowing pass through of signals from the second standard connector to the first standard connector.

53. The mobile trust module of claim 46 further comprising:

a physical user control, activation of which initiates the trusted boot process.

54. The mobile trust module of claim 46 further comprising:

a human perceptible indicator that indicates a trust level of the mobile endpoint device.

55. The mobile trust module of claim 54 wherein the human perceptible indicator indicates whether the trusted boot process and/or verification of integrity of the state of the mobile endpoint device has been successfully completed.

56. The mobile trust module of claim 54 wherein the human perceptible indicator indicates when the trusted boot process and/or verification of integrity of the state of the mobile endpoint device is in process.

57. The mobile trust module of claim 54 wherein the human perceptible indicator indicates whether the trusted boot process and/or verification of integrity of the state of the mobile endpoint device has failed or has not been initiated.

58. The mobile trust module of claim 46 wherein, prior to initiation of the trusted boot process from the mobile trust module onto the mobile endpoint device, a current state of the mobile endpoint device is stored for possible later restoration.

59. The mobile trust module of claim 46 further comprising:

anti-malware software that performs an anti-malware scan of the mobile endpoint device prior to initiation of the trusted boot process from the mobile trust module onto the mobile endpoint device.

60. The mobile trust module of claim 46 wherein the HROT further comprises a real-time clock.