Secure Guest Image Update via Trusted Execution Environment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In computing environments, secure guests require secure image updates and metadata management to ensure integrity and confidentiality, especially when hosted by untrustworthy hypervisors, necessitating a method to generate and manage updated secure guest images and metadata while maintaining security and flexibility.

Innovation Solution

A computer program product facilitates processing by enabling a secure guest to generate an updated image and metadata, using a trusted execution environment to obtain encryption keys, compute measurements, and store the updated image and metadata for secure boot, ensuring integrity and confidentiality through protected encryption and challenge-response mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a traditional hypervisor is used to host secure guests, then the hypervisor has full control and can inspect/modify guest memory, but the integrity and confidentiality of secure guest images cannot be guaranteed

Engineering Contradiction:

Improveintegrity and confidentiality of secure guest imageVSAvoidsystem architecture complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A trusted execution environment (TEE) is introduced as an intermediary between the hypervisor and secure guests. The TEE hosts a secure virtual machine manager (secure VMM) that manages secure guests, while the regular hypervisor manages non-secure guests. This mediator architecture ensures that secure guest images are loaded and executed in isolation within the TEE, preventing the regular hypervisor from inspecting or modifying them, thus guaranteeing integrity and confidentiality while maintaining manageable system complexity through clear separation of duties.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If secure guest images are protected when loaded, then integrity and confidentiality are maintained, but updates and modifications to secure guests become difficult

Engineering Contradiction:

Improveintegrity protection of secure guestVSAvoidflexibility to update secure guest

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic update capabilities for secure guests through multiple mechanisms: (1) Secure guests can request image updates by providing an updated image and measurements, which the secure VMM verifies and applies; (2) Configuration metadata can be updated independently of the image; (3) The system supports hot-plugging of secure guests and dynamic resource allocation. These dynamic features allow secure guests to be updated and adapted during runtime while maintaining integrity protection through cryptographic verification of updates.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions to enable future updates: (1) Secure guest images are signed and measured in advance, creating a baseline for verification; (2) The secure VMM maintains measurement registers and metadata that can be updated without reloading the entire image; (3) Update mechanisms are pre-configured and validated. These preliminary preparations allow efficient and secure updates to be performed later without compromising integrity.

Inventive Principle:

Principle #10Preliminary action

3Ease of operation

If the hypervisor can modify guest memory, then resource management is flexible, but secure guests cannot maintain confidentiality of their image and data

Engineering Contradiction:

Improveresource management flexibilityVSAvoidconfidentiality of secure guest data

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system segments the virtualization environment into distinct trusted and untrusted zones. The TEE creates an isolated execution environment for secure guests, separated from the regular hypervisor and non-secure guests. This segmentation is implemented through: (1) Separate virtual machine managers for secure and non-secure guests; (2

Inventive Principle:

Principle #1Segmentation

4Adaptability or versatility

If updated secure guest images are generated and stored, then security fixes and customizations can be applied, but the risk of introducing vulnerabilities or compromising integrity increases

Engineering Contradiction:

Improveability to apply security fixes and customizationsVSAvoidrisk of vulnerabilities and integrity compromise

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system implements comprehensive feedback mechanisms for update verification: (1) Measurements (hashes) of secure guest images and components are computed and stored in metadata; (2) Before applying updates, the system verifies measurements against expected values; (3) The secure VMM continuously monitors the integrity of loaded images by comparing measurements; (4) If verification fails, the update is rejected and the system can roll back to the previous known-good state. This feedback loop ensures that only verified, intact updates are applied, minimizing the risk of introducing vulnerabilities.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12130953B2Secure guest image and metadata update

Publication Date: 2024.10.29 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A secure guest generates an updated image for the secure guest, and computes one or more measurements for the updated image. The secure guest provides the one or more measurements to a trusted execution environment and obtains from the trusted execution environment metadata for the updated image. The metadata is generated based on metadata of the secure guest and obtaining the one or more measurements.