Trusted Key Service for OS Secret Persistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing technologies face challenges in maintaining operating system secrets and private data accessibility during device resets, reformatting, and operating system reinstallation, leading to potential data inaccessibility and security issues.
Innovation Solution
A method and system that utilize a master key and a trusted key service to encrypt and decrypt boot configuration-specific keys, ensuring that only the appropriate operating system can access its private data, even across device resets and operating system changes, by using a reset-resistant store and a trusted key service with an encrypted key vault and decrypted key store.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If operating system is reinstalled or replaced, then system can be updated or fixed, but data becomes inaccessible or is lost
Solution Approach 1:
The patent introduces a key service and encrypted key vault as intermediaries between the operating system and private data. The key service manages decryption keys securely, allowing the OS to access encrypted data without directly storing sensitive keys. This mediator architecture enables OS reinstallation while preserving data accessibility through the persistent key vault storage.
Solution Approach 2:
The system performs preliminary encryption of private data and secure storage of decryption keys in the key vault before OS reinstallation occurs. By pre-encrypting data and securing keys in a persistent storage mechanism, the system ensures that data remains accessible after OS replacement without requiring the original OS to be present.
2Reliability
If encryption is used to protect private data, then security is improved, but data access complexity increases
Solution Approach 1:
The key service implements self-service mechanisms by automatically managing the decryption key lifecycle. When the OS needs to access encrypted data, the key service autonomously retrieves the appropriate decryption key from the key vault and provides it to the OS, eliminating the need for manual key management by the OS or user.
Solution Approach 2:
The key service acts as an intermediary that simplifies key management complexity. Instead of the OS directly managing complex encryption keys and security protocols, the key service handles all key-related operations, presenting a simplified interface to the OS while maintaining strong security through the encrypted key vault.
3Reliability
If decryption keys are stored securely, then unauthorized access is prevented, but legitimate access may be blocked
Solution Approach 1:
The key service implements feedback mechanisms to verify OS authenticity before providing decryption keys. The system continuously monitors OS integrity and boot configuration, automatically providing key access when the OS is verified as legitimate while blocking access when anomalies are detected, thus balancing security with ease of operation.
Solution Approach 2:
The key service performs self-verification of OS legitimacy and automatically manages key distribution. The system autonomously determines whether to grant key access based on OS verification, eliminating the need for manual authentication while maintaining strong access control through automated security checks.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A device includes a reset resistant store and a trusted key service. The reset resistant store maintains data across various different device reset or data invalidation operations. The trusted key service maintains, for each of one or more operating systems that run on the device from a boot configuration, an encrypted key associated with the boot configuration. The device also has a master key that is specific to the device. Each of the keys associated with a boot configuration is encrypted using the master key. When booting the device, the boot configuration being run on the device is identified, and the key associated with that boot configuration is obtained (e.g., from the reset resistant store or the encrypted key vault). The master key is used to decrypt the obtained key, and the obtained key is used to decrypt secrets associated with the operating system run from the boot configuration.