Hierarchical Key Management for Encrypted Distributed Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database encryption methods require downtime for key rotation, which compromises availability and security, especially in high-performance distributed database systems with replica sets.
Innovation Solution
A system and method for rotating master and internal database keys while maintaining availability, using a key management server interface to obtain and store temporary master keys, and performing key rotation on each node in a replica set sequentially without disrupting read/write operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional database encryption methods are used with local key storage, then security is improved, but availability deteriorates due to required downtime for key rotation
Solution Approach 1:
The patent introduces a key management server as an intermediary between database nodes and master keys. The server stores encrypted master keys and provides them to nodes as needed, enabling key rotation without taking database nodes offline. This mediator allows secure key management while maintaining continuous database availability.
Solution Approach 2:
The patent segments the key management function from the database storage function. Master keys are stored and managed separately on a dedicated key management server, while database nodes focus on data storage and processing. This separation allows independent key rotation operations without impacting database availability.
2Ease of operation
If master keys are stored locally in encrypted keyfiles, then ease of operation is improved, but security deteriorates due to increased attack surface
Solution Approach 1:
The key management server acts as a secure intermediary that stores master keys in a protected environment. Instead of storing keys locally on multiple database nodes, the centralized server provides keys as needed, reducing the overall attack surface while maintaining operational simplicity through automated key distribution.
Solution Approach 2:
The patent uses temporary copies of master keys that are transmitted from the key management server to database nodes only when needed for operations. These copies are ephemeral and automatically discarded, reducing the window of vulnerability while maintaining ease of key access for legitimate operations.
3Reliability
If key rotation is performed on all nodes simultaneously, then security is improved, but productivity deteriorates due to complete system downtime
Solution Approach 1:
The patent divides the key rotation process into independent segments that can be executed on individual nodes or subsets of nodes. The key management server can provide different key versions to different nodes at different times, allowing incremental rotation without requiring simultaneous system-wide rotation that would cause complete downtime.
Solution Approach 2:
The key management server prepares and stores multiple versions of master keys in advance. When rotation is needed, nodes can transition from old key versions to new key versions without interruption, as the new keys are already prepared and available from the server. This preliminary preparation eliminates the need for coordinated simultaneous rotation.
4Reliability
If internal database keys are stored in encrypted format, then security is improved, but device complexity increases due to additional encryption layers
Solution Approach 1:
The patent implements automated key management where the key management server automatically handles key generation, encryption, distribution, and rotation. Database nodes automatically request and use keys from the server without manual intervention. This self-service automation reduces the operational complexity despite the multiple encryption layers, as the system manages itself without requiring complex manual key management procedures.
Data Source
AI summary
According to one aspect, methods and systems are provided for modifying an encryption scheme in a database system. The methods and systems can include at least one internal database key; at least one database configured to be encrypted and decrypted using the at least one internal database key; a memory configured to store a master key; a key management server interface configured to communicate with a key management server; and a database application configured to receive, into the memory, the master key from the key management server via the key management server interface, and encrypt and decrypt the at least one internal database key using the master key.