Encrypted Disk Image Instantiation in Virtualized Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Whole disk encryption (WDE) in virtualized computer systems faces challenges as the bootstrap or bootloader portion of the disk must remain unencrypted, making it vulnerable to attacks like 'bootkit' infections, as encrypting it would prevent bootstrapping.
Innovation Solution
A method and system for instantiating an encrypted disk image in a virtualized computer system, where a software component executes in a first virtual machine, invoking a second hypervisor and providing a BIOS to decrypt and load the encrypted disk image, allowing for live migration to provide a wholly encrypted disk image, thereby addressing the vulnerability of unencrypted portions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the bootstrap or bootloader portion of the disk is kept unencrypted to enable system bootstrapping, then the system can boot properly, but the unencrypted portion becomes vulnerable to attacks like bootkit infections
Solution Approach 1:
The system is divided into two separate virtual machines: a first VM containing the unencrypted bootloader for system startup, and a second VM containing the encrypted disk image. This segmentation allows the bootloader to remain accessible while the data remains protected, resolving the contradiction between bootability and security.
Solution Approach 2:
A virtualization layer acts as an intermediary between the bootloader and the disk image. The first VM's bootloader can access and load the second VM's encrypted disk image without directly decrypting it, enabling secure bootstrapping while maintaining encryption integrity.
2Object-affected harmful factors
If the entire disk is encrypted including the bootloader, then security is improved, but the system cannot bootstrap or bootload the operating system
Solution Approach 1:
The disk is segmented into two separate virtual machine instances: the first VM holds the unencrypted bootloader necessary for system startup, while the second VM contains the fully encrypted disk image. This segmentation enables both full encryption security and successful bootstrapping.
Solution Approach 2:
The solution moves from a single-dimension approach (encrypting the entire physical disk) to a multi-dimensional virtualized approach where the bootloader and encrypted data reside in separate virtual machine contexts, allowing both encryption and bootability to coexist.
3Adaptability or versatility
If a dedicated partition is created for encryption software, then encryption functionality is provided, but storage space is consumed and an unencrypted vulnerability zone is created
Solution Approach 1:
The first virtual machine serves multiple functions: it contains the bootloader, provides the runtime environment for decryption operations, and manages the encrypted disk image from the second VM. This multi-functionality eliminates the need for separate dedicated encryption partitions, maximizing storage utilization while maintaining encryption capabilities.
Data Source
AI summary
A computer implemented method of instantiating an encrypted disk image for a virtualized computer system includes providing a software component executing in a first virtual machine for instantiation in a first hypervisor, the software component invoking a second hypervisor within the first virtual machine; and providing a basic input output system (BIOS) for the second hypervisor, the BIOS being configured to decrypt and load the encrypted disk image to instantiate the virtualized computer system as a second virtual machine in the second hypervisor, and wherein the software component is further configured to migrate the second virtual machine at a runtime of the second virtual machine to the first hypervisor so as to provide a wholly encrypted disk image for the second virtual machine executing in the first hypervisor.