Tenant-Specific Container Encryption in Multi-Tenant Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud-based, multi-tenant applications, efficiently and reliably enabling tenant-specific encryption of containers using group-level encryption in an in-memory database with persistency is challenging, especially when assigning encryption groups to pre-existing containers without requiring application redesign.
Innovation Solution
A method involving the assignment of an encryption group identifier to containers, creation of a special container entry, initialization of a job for encryption, and flushing the container using the encryption key, followed by deletion of the special container entry upon completion, ensures tenant-specific encryption without re-implementation of multi-tenant applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If physical access protection is implemented at the data volume level, then security against physical access is improved, but multi-tenant data privacy control is worsened
Solution Approach 1:
The patent divides the encryption scope from the entire data volume level down to the container level, creating separate encryption contexts for different tenants. Each container can be assigned to a specific encryption group, allowing individual tenant data isolation while maintaining the overall data volume security structure.
Solution Approach 2:
The patent implements differential encryption at the container level within the data volume, where different containers can have different encryption keys and algorithms based on their tenant affiliation. This allows local customization of security properties while maintaining global data volume protection.
2Adaptability or versatility
If group-level encryption is implemented for multi-tenant applications, then tenant-specific data privacy is improved, but complexity of managing pre-existing containers is worsened
Solution Approach 1:
The patent creates a special container entry in advance that tracks the encryption group assignment status and manages the transition state. This preliminary structure is prepared before actual encryption operations, simplifying the management of pre-existing containers by providing a standardized entry point for encryption group assignments.
Solution Approach 2:
The patent introduces a special container entry as an intermediary data structure that mediates between the container and the encryption group assignment. This intermediary tracks assignment status, manages state transitions, and coordinates the encryption process, thereby reducing the direct complexity of managing encryption groups for pre-existing containers.
3Adaptability or versatility
If encryption is applied to pre-existing containers in multi-tenant applications, then data privacy for existing containers is improved, but application redesign requirements increase
Solution Approach 1:
The patent enables pre-existing containers to self-register with encryption groups through automatic detection and assignment mechanisms. The system automatically identifies unassigned containers, creates appropriate encryption group assignments, and manages the encryption process without requiring manual application redesign or intervention, allowing existing containers to service their own encryption needs.
Data Source
AI summary
Computer-readable media, methods, and systems are disclosed for tenant-specific encryption of container in connection with a database employing group-level encryption. An encryption group identifier may be assigned to container. The encryption group identifier may define how the container is encrypted. A container entry corresponding to the container may be created. A commit operation may be received for committing the assignment of the encryption group identifier to the container. A job may be initialized for encryption the container according to the encryption group identifier. The container may be flagged as modified. A flush operation may be initiated whereby the container is re-encrypted according to the encryption group identifier. Once flushing is complete, the container entry may be deleted.