Client-Hosted Virtualization Full Volume Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current information handling systems lack effective solutions for securely supporting full volume encryption devices in client-hosted virtualization systems, which is crucial for protecting sensitive data and preventing malicious software attacks.

Innovation Solution

The implementation of a secure client-hosted virtualization (CHV) architecture with a CHV manager that resides in secure memory, supports I/O port assignment and security policies, provides pre-boot authentication, and enables full volume encryption mechanisms, ensuring secure storage and access to common storage devices for multiple virtual machines.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full volume encryption is implemented for virtual machines, then data security is improved, but system complexity increases

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

Solution Approach 1:

A virtualization layer is introduced as an intermediary between the physical storage devices and multiple virtual machines. This layer implements full volume encryption at the virtual disk level, managing cryptographic operations transparently. The intermediary handles key management, encryption/decryption processes, and presents encrypted storage to virtual machines without requiring modifications to the VMs themselves, thus improving security while managing complexity through abstraction.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional mechanical security approaches (physical security, access controls) with cryptographic mechanisms. Full volume encryption using cryptographic algorithms substitutes for physical security measures, providing data protection through mathematical principles rather than physical barriers. This substitution enables security to be enforced at the data level regardless of physical access, improving reliability while the cryptographic operations are managed automatically by the virtualization layer.

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

2Productivity

If multiple virtual machines share common storage devices, then resource utilization is improved, but security risks increase

Engineering Contradiction:
Improveresource utilizationVSAvoidsecurity risks
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The common storage device is segmented into multiple virtual disks, with each virtual disk assigned to a specific virtual machine. Full volume encryption is applied at the virtual disk level, creating isolated encrypted namespaces for each VM. This segmentation ensures that even though physical storage is shared, each VM can only access its own encrypted portion, preventing unauthorized access to other VMs' data and eliminating security risks while maintaining resource sharing benefits.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different security properties are applied to different portions of the storage system. Each virtual disk within the common storage device has its own encryption context, keys, and security policies tailored to the specific virtual machine it serves. This local quality approach allows each VM to have customized security requirements while sharing the same physical storage infrastructure, enabling resource utilization improvement without compromising security.

Inventive Principle:
Principle #3Local quality

3Reliability

If pre-boot authentication is implemented, then system security is improved, but boot time increases

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

Solution Approach 1:

Authentication credentials and cryptographic keys are prepared and validated in advance during system initialization and firmware setup. The pre-boot authentication mechanism verifies user credentials and loads necessary cryptographic materials before the operating system starts. By performing authentication preliminarily, the system ensures security requirements are met before full system operation begins, while minimizing the time impact during actual boot by having verification materials ready ahead of time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9235708B2System and method for supporting full volume encryption devices in a client hosted virtualization system
Publication Date: 2016.01.12 DELL PROD LP
  • US9235708B2 patent drawing
  • US9235708B2 patent drawing
  • US9235708B2 patent drawing

AI summary

A client hosted virtualization system includes a full volume encryption (FVE) storage device, a processor, and non-volatile memory with BIOS code and virtualization manager code. The virtualization manager initializes the client hosted virtualization system, authenticates a virtual machine image, launches the virtual machine based on the image, receives a transaction from the virtual machine targeted to the FVE storage device, sends the transaction to the FVE storage device, receives a response from the FVE storage device, and sends the first response to the first virtual machine. The client hosted virtualization system is configurable to execute the BIOS or the virtualization manager.