Per-Data Encryption Key Management Without Local Key Retention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud storage providers face security risks due to the management of cryptographic keys locally, which traditional encryption management mechanisms fail to address by not ensuring unique keys per data element, leading to potential decryption vulnerabilities.
Innovation Solution
Implementing a Derived Unique Key Per Raindrop (DUKPR) mechanism where each data unit, referred to as a 'raindrop', is encrypted with a unique key derived by a key management server using ephemeral keys, ensuring that only encrypted data is stored on the cloud provider and all decryption keys are destroyed after use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If cloud providers manage cryptographic keys locally, then key access is simplified, but security risks increase due to potential key retention and decryption vulnerabilities
Solution Approach 1:
The patent extracts the cryptographic key management function from the cloud provider's local system and places it in a separate key management server. The cloud provider can request decryption capabilities without retaining keys locally, thus maintaining ease of operation while improving security by eliminating local key storage risks.
Solution Approach 2:
The patent introduces a key management server as an intermediary between the cloud provider and the encrypted data. This mediator handles all key operations securely, allowing the cloud provider to access encrypted data without directly managing keys, thus resolving the contradiction between operational simplicity and security.
2Device complexity
If traditional encryption management is used, then system complexity is reduced, but security standards are not met due to lack of unique keys per data element
Solution Approach 1:
The patent segments the encryption key management by creating unique cryptographic keys for each individual data element (raindrop) rather than using a single key for all data. The key management server maintains a mapping between data elements and their unique keys, enabling fine-grained security control while keeping the overall system manageable through automated key generation and destruction protocols.
3Reliability
If unique keys per data element are implemented, then security is enhanced, but key management complexity increases
Solution Approach 1:
The patent implements self-service key management where the key management server automatically generates unique keys for each data element, manages the key-data mappings, and destroys keys when no longer needed. This automation eliminates the need for manual key management procedures, thus enhancing security through unique per-element keys while preventing management complexity from becoming unmanageable.
Data Source
AI summary
A method for a key management server to manage encryption for data stored by a cloud provider server includes receiving, by the key management server from the cloud provider server, a request for a drop key. The request includes a hash drop identifier that uniquely identifies a cipher drop, and the cipher drop comprises a unit of data stored by the cloud provider server. The method further includes generating the drop key based on at least the hash drop and the drop identifier and encrypting the drop key. A response comprising the encrypted drop key is sent to the cloud provider server.