Hierarchical Encryption Key Distribution Across Tablet Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing encryption keys in large-scale cloud environments is cumbersome due to the complexity of key management and distribution across numerous servers, especially when customers generate their own keys.
Innovation Solution
A key management system that splits data into tablets, generates unique resource and data encryption keys, encrypts them with a user key, and distributes control to independent tablet servers, using access control lists to ensure secure and efficient access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If encryption keys are managed in large-scale cloud environments with numerous servers, then data security is improved, but key management complexity increases
Solution Approach 1:
The patent segments the key management system by introducing resource keys at the table level and data encryption keys at the tablet level. Each tablet has its own DEK encrypted with the table's RK, which is encrypted with the user's UK. This hierarchical segmentation allows independent management of keys at different levels, reducing overall management complexity while maintaining security across numerous servers.
Solution Approach 2:
The resource key acts as an intermediary between the user key and the data encryption keys. Instead of directly managing individual DEKs for each tablet, the system uses RK as a mediator that can decrypt multiple DEKs. This intermediary layer simplifies key management by allowing centralized control through the UK while enabling distributed access through the RK-DEK hierarchy.
2Reliability
If unique data encryption keys are generated for each tablet, then data protection is improved, but key distribution complexity increases
Solution Approach 1:
The patent segments key distribution into two stages: first distributing the resource key (encrypted with user key) to authorized servers, then having servers decrypt the DEKs using the resource key. This segmentation separates the distribution of master keys from the distribution of data keys, simplifying the overall process while maintaining unique protection for each tablet.
Solution Approach 2:
The system performs preliminary encryption of the resource key with the user key before distribution to servers. This preliminary action ensures that only authorized servers can access the DEKs, as they must first decrypt the RK using the UK. This advance preparation simplifies subsequent key distribution by establishing security before data access is needed.
3Adaptability or versatility
If control is distributed to independent tablet servers, then system scalability is improved, but access control complexity increases
Solution Approach 1:
The patent segments access control by introducing access control lists (ACLs) that associate resource keys with specific tablet servers. Each server maintains its own DEKs and can independently manage tablets, but ACLs provide centralized control over which servers can access which resource keys. This segmentation enables scalability while managing access control through hierarchical authorization.
Solution Approach 2:
The resource key serves multiple functions: it encrypts multiple data encryption keys, it is controlled by access control lists, and it enables multiple servers to access data in the same table. This multi-functionality reduces the need for separate control mechanisms for each server, simplifying access control while maintaining scalability.
4Productivity
If the number of decryption requests is reduced, then system efficiency is improved, but access control strictness may worsen
Solution Approach 1:
The system performs preliminary encryption of the resource key with the user key before distribution. Servers must first decrypt the RK using the UK to access any DEKs. This preliminary decryption step ensures strict access control is maintained before any data access occurs, preventing unauthorized servers from requesting or accessing data while reducing the number of subsequent decryption requests needed for authorized access.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method receiving a table (158) including a plurality of data blocks (154) and splitting the table into a plurality of tablets (159) including a corresponding portion of data blocks. The method also includes generating a resource key (172) uniquely associated with the table, and for each tablet, generating a unique data encryption key (182) for the corresponding tablet to encrypt with the unique data encryption key. The method also includes encrypting each data encryption key with the resource key and distributing control of each encrypted tablet and each corresponding encrypted data encryption key to a plurality of tablet servers (150), each controlling one or more of the encrypted tablets. The resource key transmits to a remote entity (190) causing the remote entity to encrypt the resource key with a user key (192) and transmit the encrypted resource key.