Distributed Key Fragment Management for Cloud Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cryptographic key management systems face challenges such as single points of failure, high resource usage, and vulnerability to unauthorized access, particularly in cloud-based environments where master keys are stored in plaintext, making them susceptible to exposure by cloud providers.
Innovation Solution
A distributed Key Fragment Management (KFM) system is implemented, where each KFM instance retains a root key fragment, and data-specific keys are generated by combining fragments from multiple instances without assembling the root key, ensuring it never exists in one place, using non-deterministic and deterministic encryption methods, and employing a refreshable key system to constantly update ephemeral key fragments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If master keys are stored in plaintext in cloud-based environments, then key management is simplified, but security is compromised as cloud providers can access the keys
Solution Approach 1:
The master key is divided into multiple key fragments that are distributed across different KFM instances. Each fragment alone is insufficient to reconstruct the master key, providing security while maintaining operational simplicity through automated key management processes
Solution Approach 2:
KFM instances act as intermediaries that manage key fragments and generate data-specific key fragments on demand. This intermediary layer prevents direct access to master key material while enabling simplified key management operations for users
2Productivity
If a centralized key management system is used, then key generation and distribution is efficient, but single points of failure and security vulnerabilities arise
Solution Approach 1:
The centralized key management system is segmented into multiple distributed KFM instances, each holding a portion of the master key. This segmentation eliminates single points of failure while maintaining efficient key generation through parallel operations across instances
Solution Approach 2:
Multiple KFM instances work together to generate data-specific key fragments that are combined by the user's device to form complete data-specific keys. This merging of distributed fragments achieves centralized efficiency without centralized vulnerability
3Ease of operation
If root key fragments are aggregated to form the root key, then key management operations are simplified, but security is compromised as the root key becomes accessible
Solution Approach 1:
The root key remains segmented into fragments stored in different KFM instances. Data-specific key fragments are derived from these root fragments through cryptographic operations without requiring aggregation, maintaining security while enabling simplified operations through automated derivation processes
Solution Approach 2:
Only the necessary data-specific key fragments are extracted and provided to users, not the complete root key. This extraction approach maintains operational simplicity for data operations while preventing root key exposure by never assembling the complete root key
Data Source
AI summary
A system, a method and a computer program product and a system, for Key Fragment Management (KFM). The KFM system comprises a plurality of KFM instances and a client device. At least two KFM instances are executed on execution platforms of two different service providers. Each KFM instance retains a root key fragment. The client device is configured to perform a cryptographic process relating to a data item using a data-specific key. Each KFM instance is configured to generate a data-specific key fragment based on a data identifier of the data item and based on the root key fragment in response to the client device requesting to generate the data-specific key for the data item. The data-specific key is generated based on a plurality of data-specific key fragments generated by the each KFM instances.