Encrypted Data Expiration via Secure Key Deletion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database systems face challenges in managing encryption keys, as removing old keys can result in loss of vital information, while storing them indefinitely leads to storage and security concerns, making it difficult to expire encrypted data effectively.
Innovation Solution
A system that expires encrypted data by receiving an expiry-request with object-identifying information, identifying and deleting the associated keys in a secure key repository, ensuring that only valid keys are maintained, thereby preventing decryption of expired data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If old keys are removed before encrypted data expires, then storage space is freed and security is improved, but vital information is lost
Solution Approach 1:
The system performs preliminary actions by establishing expiration policies and monitoring key lifecycles before keys become stale. The database system proactively identifies keys associated with expired data and schedules their deletion, ensuring that keys are removed only after their associated data has truly expired, thus preventing both security vulnerabilities and information loss.
2Reliability
If keys are stored indefinitely, then data can always be decrypted, but storage costs increase and security risks accumulate
Solution Approach 1:
The system changes the parameter of key validity by introducing expiration timestamps and lifecycle states. Keys are no longer stored indefinitely but have defined validity periods. The system transitions keys through states (active, expired, deleted) based on time and data expiration conditions, optimizing storage by removing unnecessary keys while maintaining accessibility for valid data.
3Reliability
If keys are stored indefinitely, then data can always be decrypted, but security concerns increase due to stale keys
Solution Approach 1:
The system implements self-service mechanisms where the database system automatically monitors, evaluates, and manages key lifecycles without manual intervention. The system autonomously identifies expired data, determines associated keys, and deletes them according to defined policies, eliminating the need for manual key management and ensuring consistent security practices are applied throughout the system.
4Adaptability or versatility
If manual key management is used, then flexibility is high, but operational complexity and errors increase
Solution Approach 1:
The system implements self-service mechanisms where the database system automatically monitors, evaluates, and manages key lifecycles without manual intervention. The system autonomously identifies expired data, determines associated keys, and deletes them according to defined policies, eliminating the need for manual key management and ensuring consistent security practices are applied throughout the system.
Data Source
AI summary
One embodiment of the present invention provides a system that can expire encrypted-data. During operation, the system receives an expiry-request that includes object-identifying information, which can be used to identify a set of database objects that contain the encrypted-data, wherein a database object can be a table, a partition, a row, or a column in a row. Furthermore, a database object can have an expiration time, and it can be stored in an archive, which is typically used to store large amounts of data for long periods using a slower, but cheaper storage medium than the storage medium used by the database. The system then identifies a set of keys for the encrypted-data using the object-identifying information. Next, the system deletes the set of keys, thereby expiring the encrypted-data. Note that, deleting the set of keys ensures that the secure key repository does not contain any stale keys associated with expired encrypted-data.