Encrypted Cloud OS Secure Boot via Key Access Protocol

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing operating systems designed for local execution face challenges in providing secure boot mechanisms in cloud environments, as they require manual authentication and are not compatible with cloud infrastructure, leading to security vulnerabilities and inefficiencies.

Innovation Solution

A method is introduced where a first execution environment within the cloud initiates a key access protocol to access and store a cipher key, allowing the decryption and execution of an encrypted operating system, with authentication protocols ensuring secure and automated or user-supported boot processes, utilizing a key server for secure token management and authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a secure operating system is executed in the cloud without cloud-specific design, then security is compromised, but cloud compatibility is achieved

Engineering Contradiction:
ImprovesecurityVSAvoidcloud compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system separates the secure operating system execution into distinct components: a cloud-compatible execution environment and a security enforcement layer. The OS is divided into encrypted segments that are decrypted and executed within controlled boundaries, allowing secure operations to be segmented from unsecure cloud infrastructure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary execution environment is introduced between the cloud infrastructure and the secure operating system. This intermediary layer provides the necessary security controls and authentication mechanisms while maintaining cloud compatibility, acting as a mediator that enables both cloud execution and security requirements to coexist.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual authentication is required for each VM boot, then security is maintained, but operational efficiency deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidoperational efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Authentication credentials and security configurations are pre-configured and stored securely before VM boot operations. The system performs preliminary authentication setup where trust relationships are established in advance, allowing automated authentication during boot without requiring manual intervention for each startup while maintaining security standards.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The virtual machine system performs self-authentication using pre-configured credentials and automated authentication protocols. The VM automatically retrieves and uses stored authentication information to prove its identity and security compliance during boot, eliminating the need for manual authentication while maintaining security requirements.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If broadcast or multicast is used for authentication in cloud environment, then authentication capability is improved, but cloud infrastructure compatibility deteriorates

Engineering Contradiction:
Improveauthentication capabilityVSAvoidcloud infrastructure compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system replaces broadcast/multicast mechanical network communication with individualized unicast authentication channels. Instead of relying on broadcast mechanisms that require specific network infrastructure support, the authentication process uses direct point-to-point communication channels that are compatible with standard cloud network architectures, substituting the mechanical broadcast system with a more versatile unicast approach.

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

4Reliability

If operating system is encrypted for security, then security is improved, but execution speed deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidexecution speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The operating system is pre-decrypted into memory or a secure execution environment before execution begins. Encryption is applied to stored OS images, but the active execution copy is maintained in decrypted form in secure memory, allowing fast execution without real-time decryption overhead. The preliminary decryption action separates the security protection (storage encryption) from the execution performance requirements.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10154023B1Method and system for secure instantiation of an operation system within the cloud
Publication Date: 2018.12.11 EMC IP HLDG CO LLC
  • US10154023B1 patent drawing
  • US10154023B1 patent drawing
  • US10154023B1 patent drawing

AI summary

A method is disclosed for executing a secure virtual machine stored in encrypted form in IaaS cloud such as Microsoft Azure or Amazon Web Services. A first execution environment comprising a key access protocol for accessing a cipher key is initiated. The first execution environment executes the secure virtual machine by accessing a secret for use in deciphering the encrypted form of the secure virtual machine and providing same to allow the secure virtual machine to be executed.