Zero-Trust Attestation in Cloud TEEs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Trusted Execution Environments (TEEs) in cloud service systems do not allow for remote attestation, forcing clients to trust their cloud service providers, which increases the risk of attacks and resource misuse.

Innovation Solution

Implementing a mutual remote attestation (MRA) system that executes a zero-trust attestation service (ZTAS) agent within a TEE using virtualization-based confidential computing technology, allowing clients to verify the launch measurements and behavior of cloud services independently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional TEE is used in cloud service systems, then the system operation is simple and clients must trust the provider, but the security risk increases and clients cannot independently verify service integrity

Engineering Contradiction:
Improveservice integrity verificationVSAvoidattestation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the attestation process into distinct components: a TEE agent running within the TEE that collects launch measurements and behavior data, and a remote attestation service that verifies these measurements. This segmentation allows independent verification while maintaining manageable system complexity through clear separation of concerns between the trusted environment and the verification infrastructure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a TEE agent as an intermediary component that bridges the TEE and the remote attestation service. This agent collects launch measurements, monitors TEE behavior, and provides attestation data to external verifiers, enabling clients to independently verify service integrity without requiring direct access to TEE internals or trusting the cloud provider directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If remote attestation is implemented, then clients can verify service integrity independently, but the system complexity and resource requirements increase

Engineering Contradiction:
Improvetrust verification capabilityVSAvoidcomputational resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary attestation by capturing launch measurements at TEE initialization and pre-registering them with the remote attestation service. This preliminary action establishes a baseline of expected TEE behavior before actual service execution, allowing efficient verification during runtime without requiring continuous heavy computational resources for analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces complex continuous monitoring mechanisms with a more efficient verification approach based on cryptographic proof. Instead of continuously analyzing TEE behavior with heavy computational resources, the system uses cryptographic signatures on launch measurements and attestation tokens that can be verified with minimal computational overhead, substituting mechanical monitoring with cryptographic verification.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Object-affected harmful factors

If mutual remote attestation is implemented, then security against attacks is improved, but the attestation procedure becomes more complex

Engineering Contradiction:
Improveattack resistanceVSAvoidattestation procedure complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent implements mutual attestation where both the client and the cloud service provider verify each other's integrity. Instead of only the client verifying the provider, the system inverts the traditional trust model by having the provider also verify the client's TEE state. This mutual verification approach strengthens security against attacks while distributing the complexity burden across both parties rather than concentrating it in a single verification system.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS12294578B2Zero-trust attestation in cloud computing
Publication Date: 2025.05.06 RED HAT LLC
  • US12294578B2 patent drawing
  • US12294578B2 patent drawing
  • US12294578B2 patent drawing

AI summary

A system and method of performing a mutual attestation procedure for a trusted execution environment (TEE) of a cloud service system. The method includes receiving, by the cloud service provider, a request to provide a trusted service to a client device. The method includes performing, by a processing device of the cloud service provider using a first TEE, a mutual attestation procedure with a second TEE to obtain a grant to execute a third TEE that is trusted by the second TEE. The method includes initiating, using the second TEE, an execution of the third TEE responsive to obtaining the grant. The method includes providing, using the third TEE, the trusted service to the client device, where the client device trusts the trusted service.