Hierarchical Key Management for Database Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database management systems face challenges in internal key management, security, granularity of encryption, and the need for separate permission systems, particularly in preventing data leakage and ensuring secure access to sensitive data.
Innovation Solution
A granular encryption database management system with hierarchical internal key management using asymmetric encryption, where keys are stored within the database server, and access is granted through a hierarchical structure using hash functions and public/private key pairs, eliminating the need for external key management and separate permission systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If internal key management is used to store keys in the database server, then operational costs are reduced and system simplicity is improved, but security is worsened because database administrators can access the entire key table
Solution Approach 1:
The patent segments the key table into multiple encrypted partitions, each protected by a different encryption key. Instead of storing all keys in a single accessible location, the key table is divided so that each segment can be independently encrypted and protected, preventing administrators from accessing the entire key table with a single credential set.
Solution Approach 2:
Different regions or partitions of the key table are assigned different security properties through asymmetric encryption. Each user or administrator group is granted access to specific encrypted segments based on their role, rather than providing uniform access to the entire key table. This creates localized security zones within the key management system.
2Device complexity
If a single master key is used to encrypt the key table, then key management simplicity is improved, but security is worsened because the entire system becomes vulnerable if the master key is compromised
Solution Approach 1:
The patent replaces the single master key approach with multiple encryption keys, each protecting different portions of the key table. This segmentation ensures that compromise of one key does not expose the entire system, as each key segment independently protects its designated area.
Solution Approach 2:
The system employs asymmetric encryption where different keys serve different purposes - some keys are used for encryption while others are used for decryption. This asymmetric key structure creates a more robust security model compared to symmetric single-master-key systems, as it enables fine-grained access control and key rotation without compromising the entire system.
3Reliability
If granular encryption of specific fields is implemented, then security is improved by limiting key compromise impact, but key management complexity increases requiring dedicated key management systems
Solution Approach 1:
The patent implements granular encryption by segmenting the database into different fields and records, each encrypted with specific keys stored in the key table. This allows selective encryption of sensitive fields while maintaining simplicity in key management through the integrated key table structure.
Solution Approach 2:
The patent merges granular field-level encryption capabilities with integrated key management in a single system. Rather than requiring separate dedicated key management systems, the solution combines fine-grained encryption control with centralized key storage and management in the database server itself.
4Reliability
If external key management servers are used to prevent administrator access to keys, then security is improved, but operational costs increase and reliability concerns arise from third-party dependencies
Solution Approach 1:
The patent extracts the security vulnerability of administrator access by implementing encrypted key table partitions that are mathematically inaccessible to administrators through asymmetric encryption. Instead of physically removing key management from the database server, the solution extracts the security risk through cryptographic mechanisms.
Solution Approach 2:
The system provides self-service key management where the database server itself manages key encryption and decryption without requiring external key management servers. The integrated approach uses the database server's existing security infrastructure combined with asymmetric encryption to provide secure key management independently.
Data Source
AI summary
A granular encryption database management system characterized by hierarchical internal key management using asymmetric encryption of the user's keys, which are stored within a (local) encryption key table. Data is encrypted, decrypted, stored, and accessed from rows within the database (hereinafter ‘instances’). Instances are ordered in categories called Types. Instances are encrypted with Instance keys. All instances of the same type have their Instance keys generated by means of a hash function of their common Type's key, while Type keys are generated from the key of the higher category which is often the Master key of the whole system.