Trusted Execution Enclave for Secure Cloud Data Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud-based computing environments, ensuring data confidentiality and integrity is challenging due to the hierarchical privilege structure, which can lead to software vulnerabilities being inherited by programs, making them susceptible to malicious attacks and compromising the security of sensitive data.

Innovation Solution

Implementing a secure computation provider with secure hardware components and a primitive programming model that isolates trusted code from untrusted code components, using signed data to verify and authenticate message data, and establishing secure communication channels to protect data integrity and confidentiality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If code partitioning schemes are used to separate trusted code from untrusted code, then data security is improved, but the complexity of the system increases and manual tasks become error-prone and slow

Engineering Contradiction:
Improvedata securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a trusted execution environment (TEE) as an intermediary layer between untrusted cloud infrastructure and sensitive data/code. The TEE creates an isolated enclave that mediates all access requests, allowing secure code execution without requiring complex manual partitioning of trusted code across multiple locations. This single intermediary structure simplifies the overall system architecture while maintaining strong security boundaries.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the security-critical code and data into a separate trusted execution environment, removing them from the untrusted cloud infrastructure. This extraction eliminates the need for complex partitioning schemes throughout the system, as all security-sensitive operations are consolidated in the isolated TEE enclave, reducing system complexity while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If cloud-based services are used instead of on-premises hardware, then scalability and affordability are improved, but security vulnerabilities increase due to hierarchical privilege structure

Engineering Contradiction:
ImprovescalabilityVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the cloud computing system into distinct trust zones: an untrusted external cloud infrastructure and a trusted internal execution environment (TEE). This segmentation allows the system to leverage cloud scalability while maintaining security by isolating sensitive operations in the TEE enclave, preventing privilege escalation attacks from the untrusted external layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary security measures by establishing the TEE enclave before any sensitive code execution or data processing occurs. The enclave pre-configures secure boundaries and authentication mechanisms, proactively preventing potential security exploits from the cloud infrastructure's hierarchical privilege structure before they can compromise the system.

Inventive Principle:
Principle #9Preliminary anti-action

3Loss of information

If manual code partitioning is performed to enhance security, then data confidentiality is improved, but the process becomes error-prone and slow

Engineering Contradiction:
Improvedata confidentialityVSAvoiddeployment speed
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent enables automated enclave creation and configuration within the TEE, allowing the system to self-secure sensitive code and data without manual intervention. The automated processes handle code injection, enclave configuration, and security boundary establishment, eliminating error-prone manual partitioning tasks while maintaining strong confidentiality protections.

Inventive Principle:
Principle #25Self-service

4Reliability

If trusted code is distributed across multiple locations for security, then security is improved, but the ability to examine correctness is reduced

Engineering Contradiction:
ImprovesecurityVSAvoidcorrectness verification
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent merges all security verification and attestation functions into the centralized TEE enclave. This consolidation allows comprehensive examination and verification of trusted code correctness within a single controlled environment, while the enclave itself provides the security boundaries. The merging eliminates the difficulty of verifying distributed code across multiple locations, as all verification occurs in one auditable location.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3657377B1Techniques to secure computation data in a computing environment
Publication Date: 2024.09.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3657377B1 patent drawingFigure 1
  • EP3657377B1 patent drawingFigure 2
  • EP3657377B1 patent drawingFigure 3

AI summary

Techniques to secure computation data in a computing environment from untrusted code. These techniques involve an isolated environment within the computing environment and an application programming interface (API) component to execute a key exchange protocol that ensures data integrity and data confidentiality for data communicated out of the isolated environment. The isolated environment includes an isolated memory region to store a code package. The key exchange protocol further involves a verification process for the code package stored in the isolated environment to determine whether the one or more exchanged encryption keys have been compromised. If the signature successfully authenticates the one or more keys, a secure communication channel is established to the isolated environment and access to the code package's functionality is enabled. Other embodiments are described and claimed.