Dynamic Root of Trust Measurement for Hypervisor Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The conventional boot process in computing platforms faces a trust gap between the vendor-controlled environment and the third-party operating system, which can lead to security breaches and compromise the root of trust, especially when loading a hypervisor.

Innovation Solution

The proposed solution involves hashing the core root of trust measurement code and system management code, storing the hash in a secure register, validating certificates, and establishing a dynamic root of trust measurement session to ensure the integrity of the boot process and secure execution of the hypervisor.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a third-party operating system is loaded after vendor boot software, then system compatibility and software freedom are improved, but a trust gap emerges that compromises the root of trust

Engineering Contradiction:
Improveoperating system compatibilityVSAvoidroot of trust credibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a measurement session manager and hash validation mechanism as an intermediary between the vendor boot software and third-party operating system. This intermediary verifies the integrity of the boot process by comparing stored hash values with computed hash values, ensuring that the root of trust is maintained even when third-party software is loaded. The intermediary component bridges the trust gap by providing cryptographic verification without preventing OS compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If hash validation and certificate verification are performed, then security and trust credibility are improved, but the boot process complexity increases

Engineering Contradiction:
Improvesecurity credibilityVSAvoidboot process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-computing and storing hash values of the core root of trust measurement code and system management code in secure registers during the manufacturing or initial setup phase. This preliminary preparation allows for rapid validation during the boot process without adding significant complexity, as the verification logic simply compares pre-prepared reference values with newly computed values, streamlining the security verification process.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If a dynamic root of trust measurement session is established, then hypervisor security is improved, but the boot time and processing overhead increase

Engineering Contradiction:
Improvehypervisor securityVSAvoidboot time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent maintains continuity of useful action by integrating the root of trust measurement and validation processes seamlessly into the existing boot sequence. Rather than adding separate, time-consuming security checks, the measurement session manager operates continuously throughout the boot process, measuring and validating code as it is loaded and executed. This continuous approach ensures hypervisor security without requiring additional boot time, as the security verification is performed concurrently with normal system initialization.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8341393B2Security to extend trust
Publication Date: 2012.12.25 LENOVO (SINGAPORE) PTE LTD
  • US8341393B2 patent drawing
  • US8341393B2 patent drawing
  • US8341393B2 patent drawing

AI summary

An exemplary apparatus includes one or more processors; memory; circuitry configured to hash a value associated with core root of trust measurement code and system management code; store the hash in a secure register; load an operating system; validate a certificate associated with the core root of trust measurement code and validate a certificate associated with the system management code; based on the validated certificates, provide an expected hash associated with the core root of trust measurement code and the system management code; decide if the expected hash matches the hash stored in the register; and, if the expected hash matches the hash stored in the register, commence a dynamic root of trust measurement session. Various other apparatuses, systems, methods, etc., are also disclosed.