Automated Backup Data Purging with Expiring Encryption Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems lack sufficient support for automatically enforcing complex and evolving data privacy regulations, leading to increased risks of non-compliance and threats to customer data privacy due to manual ad-hoc solutions.
Innovation Solution
An automated data governance system that integrates with existing databases, using encryption keys to enforce data retention and purging policies, ensuring compliance by encrypting data elements and deleting encryption keys based on policy expiration dates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual ad-hoc solutions are used for data retention and purging, then organizations can attempt to comply with data privacy regulations, but the risk of non-compliance increases and customer data privacy is threatened
Solution Approach 1:
The system enables self-service automation where the database management system automatically identifies data subject to purging policies, encrypts it using expiration keys, and deletes the keys after the retention period without requiring manual intervention. This self-automating process eliminates reliance on manual ad-hoc solutions while ensuring consistent compliance with data privacy regulations.
Solution Approach 2:
The system performs preliminary encryption of data before the purging date using expiration keys that are predetermined based on retention policies. This preliminary action ensures that when the purging time arrives, the system can automatically delete the encryption keys to irreversibly secure the data, rather than relying on manual processes at the last moment.
2Reliability
If data is retained in backups for extended periods to meet compliance requirements, then data privacy protection is maintained, but the security risk of stored data increases
Solution Approach 1:
The system changes the security parameter of stored backup data over time by initially storing data in encrypted form with expiration keys, then after the retention period expires, deleting the encryption keys. This parameter change transforms the data from decryptable to irreversibly secured, maintaining privacy protection while eliminating ongoing security risks of long-term storage.
Solution Approach 2:
The system converts the potential harm of long-term data storage (increased security risk) into a benefit by using the retained backup data for compliance purposes while simultaneously eliminating the security risk through key deletion. The encrypted data serves its compliance function without posing ongoing security threats.
3Manufacturing precision
If automated data governance systems are implemented to enforce retention and purging policies, then compliance accuracy is improved, but system complexity increases
Solution Approach 1:
The system segments the compliance enforcement process into distinct automated components: policy definition, data identification, encryption key management, and key deletion. This segmentation allows each function to be handled by specific system modules, improving compliance accuracy through dedicated functionality while managing complexity through modular design.
Solution Approach 2:
The system implements a universal automated governance framework that can enforce multiple retention and purging policies across different data types and compliance requirements through a single integrated platform. This multi-functional approach improves compliance accuracy for various regulations while reducing overall system complexity by avoiding separate manual processes for each policy.
4Ease of operation
If encryption keys are retained indefinitely to allow data recovery, then data accessibility is maintained, but the ability to securely purge data is compromised
Solution Approach 1:
The system dynamically manages encryption key availability based on retention policy timelines. Keys are made available during the retention period for data accessibility, then automatically deleted after expiration to enable secure purging. This dynamic key management resolves the contradiction by adapting key persistence to the specific operational phase.
Solution Approach 2:
The system implements periodic review and deletion of encryption keys based on predetermined retention periods. During each retention period, keys remain accessible for data recovery operations. After the periodic retention interval expires, keys are automatically deleted to enable secure purging, creating a rhythm of accessibility followed by secure deletion that satisfies both requirements.
Data Source
AI summary
The various implementations described herein include methods and systems of data governance. In one aspect, a method of purging backup data includes obtaining a database table having a corresponding data policy and generating an encrypted version of the database table by applying an encryption key, including encrypting at least a portion of the database table. The method further includes identifying an expiration date for the encryption key based on the data policy, and storing the encryption key, the expiration date, and an encryption identifier for the encryption key in an encryption table. The method also includes receiving a command to back up the database table and, in response to the command, generating a backup of the encrypted version of the database table. The method further includes storing the backup and, when a current date is at least the expiration date for the encryption key, deleting the encryption key.