Delta Encryption for Database Schema Field Reshaping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database encryption techniques are resource-intensive and inefficient, particularly in multi-tenant environments, where identifying and encrypting newly marked fields across application builds is challenging, leading to computational overhead and potential security breaches.
Innovation Solution
A delta encryption system that automates the identification of newly encryptable fields by comparing meta information between current and new database schemas, adjusting field sizes, and performing bulk encryption only on these fields, thereby reshaping and restructuring the database to accommodate changes efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional database encryption techniques are used to encrypt all fields, then data security is improved, but computational resources and time are excessively consumed
Solution Approach 1:
The patent segments the database fields into encryptable and non-encryptable categories based on sensitivity levels. Only fields marked as encryptable are subjected to encryption operations, while other fields remain unencrypted. This selective approach maintains data security for sensitive information while avoiding the computational overhead of encrypting entire databases.
Solution Approach 2:
The patent applies different quality attributes to different parts of the database by implementing field-level encryption rather than database-wide encryption. Each field can have its own encryption status based on its sensitivity requirements, allowing high-security measures for critical fields and standard protection for less sensitive data, thereby optimizing resource allocation.
2Reliability
If traditional database encryption techniques are used to encrypt all fields, then data security is improved, but encryption time is excessively long
Solution Approach 1:
The patent divides the encryption process into segments by identifying only the subset of fields that require encryption. The system compares the current database schema with the new schema to determine which fields are newly marked as encryptable, then applies encryption only to those specific fields rather than re-encrypting the entire database, significantly reducing encryption time.
Solution Approach 2:
The patent performs preliminary identification of encryptable fields by comparing schema metadata before executing the encryption process. The delta encryption system pre-processes the schema comparison to generate a list of fields requiring encryption, allowing the actual encryption operation to focus only on necessary fields and avoid unnecessary computational delays.
3Measurement precision
If manual identification of newly encryptable fields is performed, then encryption accuracy is improved, but operational complexity increases
Solution Approach 1:
The patent implements a self-service mechanism where the delta encryption system automatically identifies newly encryptable fields by comparing schema metadata without requiring manual intervention. The system autonomously performs schema comparison, identifies changes, and determines which fields are newly marked as encryptable, eliminating manual operational complexity while maintaining high accuracy through automated metadata analysis.
Solution Approach 2:
The patent employs feedback mechanisms by continuously comparing the current database schema with the new schema and using the comparison results to automatically update the encryption configuration. The system receives feedback from the schema comparison process and uses this information to precisely identify which fields require encryption, ensuring accuracy while automating the entire process.
4Reliability
If bulk encryption of all fields is performed, then comprehensive data protection is improved, but resource consumption increases
Solution Approach 1:
The patent segments the encryption operation to apply only to newly identified encryptable fields rather than performing bulk encryption on all fields. By dividing the database into encryptable and non-encryptable portions based on schema metadata comparison, the system provides comprehensive protection for sensitive data while minimizing resource consumption by excluding unnecessary encryption operations.
Solution Approach 2:
The patent applies partial action by encrypting only the specific subset of fields that are newly marked as encryptable, rather than performing excessive bulk encryption on the entire database. This approach ensures adequate protection for sensitive information while avoiding the wasteful consumption of computational resources on fields that do not require encryption.
Data Source
AI summary
In one aspect, systems and techniques for modifying a storage structure with newly encryptable fields is described. A delta encryption system loads a current database schema and an object model for a new database schema to a memory. The current database schema includes meta information identifying multiple fields and field information for a current application build. The object model includes meta information identifying multiple fields and field information for a new application build. The fields identified by the object model meta information include one or more encryptable fields. The delta encryption system calculates a field size information for the encryptable fields and compares the meta information from the current database schema with the meta information from the object model. In response to the comparison, the delta encryption system identifies which of the encryptable fields are newly encryptable fields and modifies a database based on the calculated field size information.