Native Multi-Tenant Row Table Encryption with Tenant-Specific Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-tenant database systems lack efficient tenant-level encryption, leading to potential data leakage and increased liability due to shared database instances, and require separate database instances for each tenant, which is costly and inefficient.
Innovation Solution
Implement tenant-specific encryption keys for data pages and logs, using identifiers in headers to determine encryption and decryption keys, allowing data to be encrypted before persistent storage and decrypted upon loading into volatile memory, while maintaining a single database instance for multiple tenants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If a single database instance is used to manage data of multiple tenants, then cost efficiency is improved by sharing computing resources, but data security deteriorates due to potential data leakage and increased liability
Solution Approach 1:
The patent segments encryption at the tenant level by assigning unique encryption keys to each tenant. Data pages are encrypted with tenant-specific keys, creating logical separation of data within a shared database instance. This allows multiple tenants to share computing resources while maintaining data security through cryptographic isolation.
Solution Approach 2:
The patent applies local quality by implementing tenant-specific encryption keys for each tenant's data. Each tenant's data pages are encrypted with their own unique key, providing localized security measures tailored to each tenant's data while maintaining a shared database infrastructure.
2Reliability
If separate database instances are provisioned for each tenant, then data security is improved through physical separation, but cost efficiency deteriorates due to increased computing resource consumption
Solution Approach 1:
The patent merges multiple tenants' data into a single database instance while maintaining security through encryption. Instead of provisioning separate database instances for each tenant, the system combines all tenant data in one instance and applies tenant-specific encryption keys, achieving both cost efficiency and data security.
Solution Approach 2:
The patent introduces encryption keys as an intermediary mechanism between the shared database instance and tenant data. These keys act as a mediator that enables secure access control and logical separation without requiring physical isolation through separate database instances.
3Device complexity
If data is encrypted using a database system key, then implementation simplicity is improved, but tenant-level data security deteriorates due to inability to isolate specific tenant data
Solution Approach 1:
The patent implements dynamic encryption key selection based on tenant identification. The system automatically determines which encryption key to use based on the tenant associated with each data page, enabling flexible and adaptive security without manual configuration. This dynamic approach maintains simplicity while achieving tenant-level security.
Solution Approach 2:
The patent changes the encryption parameter from a single database-level key to multiple tenant-specific keys. By modifying the encryption key parameter based on tenant identification stored in data page headers, the system achieves tenant-level security isolation while maintaining automated key management.
Data Source
AI summary
Systems and methods include determination of a first encryption key associated with a data page of a row store database table stored in a volatile memory, based on a header of the data page, encryption of a body of the data page using the first encryption key, and storage of an encrypted data page comprising the header and the encrypted body in a persistent storage system.