Encrypted Virtual Hard Disk Administrator Header Key Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for securing encrypted virtual hard disks face challenges such as the inability for enterprises to access data without user cooperation, password management issues leading to security risks, and the need for centralized key management to prevent single-point compromises.
Innovation Solution
A system where a virtual hard disk is created with a volume key placed in an administrator header, encrypted with a protection key generated from user and volume identifiers and cryptographic secrets, with these secrets stored separately to prevent transmission and ensure only local recreation of the protection key, thus maintaining security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If user passwords are stored in a central database for password recovery, then users can recover their passwords, but passwords may be intercepted during transmission over the network, compromising security
Solution Approach 1:
The encryption key is divided into multiple segments: a volume key for encrypting the virtual hard disk and a protection key for encrypting the administrator header. These segments are stored separately, and neither alone can decrypt the data, eliminating the need to transmit recovery passwords over the network.
Solution Approach 2:
A protection key acts as an intermediary between the volume key and the administrator header. The protection key is generated locally from cryptographic secrets and never transmitted over the network, serving as a secure mediator that enables administrator access without exposing sensitive credentials.
2Ease of operation
If a single encryption key is used for the virtual hard disk, then decryption is simplified, but a single point of compromise exists that could allow unauthorized access
Solution Approach 1:
The encryption system is segmented into multiple independent components: the volume key encrypts the data payload, while the protection key encrypts the administrator header containing the volume key. This segmentation ensures that compromising one key does not enable decryption of the entire system.
Solution Approach 2:
The encryption architecture uses a composite structure where multiple encryption layers (volume key encryption and protection key encryption) are combined. Each layer provides independent security, and the combination creates a robust multi-layered defense that resists single-point compromises.
3Extent of automation
If the protection key is transmitted over the network for key management, then centralized control is achieved, but the key may be intercepted, compromising security
Solution Approach 1:
The protection key serves as a local intermediary that enables centralized control functionality without requiring transmission. Administrators can manage keys centrally by controlling the cryptographic secrets, while the protection key itself remains local and never traverses the network.
Solution Approach 2:
The system enables self-service key management where the protection key is automatically generated locally from cryptographic secrets stored in secure enclaves. This eliminates the need for manual key transmission while maintaining centralized control over the secrets that generate the keys.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
Securing encrypted virtual hard disks may include a variety of processes. In one example, a virtual hard disk is created for a user and encrypted with a volume key, and the volume key placed in an administrator header. The administrator header may be encrypted with a protection key, the protection key created from a user identifier corresponding to the user, a volume identifier corresponding to the virtual hard disk, and two cryptographic secrets. The protection key may then destroyed after encrypting the administrator header and therefore, might never leave the encryption engine. The two cryptographic secrets may be stored in separate storage locations, one accessible to the user and the other accessible to administrators. Accordingly, the protection key might never transmitted or can be intercepted, and no single entity may be compromised to gain access to all of the information needed to recreate the protection key.