Tamper-Proof Digital Data Retention via Cryptographic Checksums
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital data retention management systems in cloud computing are vulnerable to tampering and premature deletion due to the ability to manipulate retention dates and system clocks, leading to potential legal and business consequences.
Innovation Solution
Implementing a cryptographic checksum for metadata associated with data objects, including retention dates, and using a trusted component to verify metadata validity and retention expiration before authorizing deletion, ensuring secure and tamper-proof retention management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If retention dates are stored in a database without cryptographic protection, then the system is simple and easy to operate, but the retention dates can be tampered with or corrupted
Solution Approach 1:
A trusted component is introduced as an intermediary between the storage system and the deletion process. This component verifies the cryptographic checksum of metadata before allowing deletion, preventing tampering without requiring complex cryptographic implementations throughout the entire system. The trusted component acts as a mediator that ensures integrity while maintaining system simplicity.
Solution Approach 2:
The cryptographic checksum is calculated and stored alongside the metadata at the time of data ingestion or update. This preliminary action ensures that any future tampering with the retention date can be detected, as the stored checksum serves as a pre-computed reference that must match any subsequent metadata verification.
2Reliability
If the system clock can be freely adjusted by administrators, then system operation is flexible and easy to manage, but records can be prematurely destroyed by fast-forwarding time
Solution Approach 1:
The system applies preliminary anti-action by using cryptographic checksums to prevent future tampering with retention dates. The checksum is computed over the metadata including the retention date, and any modification to the retention date would result in a checksum mismatch, thereby preventing premature deletion even if the system clock is adjusted.
Solution Approach 2:
The patent replaces the mechanical/system-level time adjustment mechanism with a cryptographic verification mechanism. Instead of relying on system clock management to prevent premature deletion, the system uses cryptographic checksums to verify retention dates, substituting a more secure but less flexible time management approach with a data-integrity-based approach.
3Reliability
If cloud providers manage retention without strong protection, then the system is simple and scalable, but records are vulnerable to tampering and premature deletion
Solution Approach 1:
The trusted component serves as an intermediary that cloud providers can integrate into their retention management systems. This mediator handles the cryptographic verification operations, allowing cloud providers to implement strong protection without managing complex cryptographic systems themselves. The trusted component abstracts the complexity while providing robust record protection.
Solution Approach 2:
The system creates a cryptographic copy of the metadata checksum that can be verified independently of the original metadata storage. This copy serves as a tamper-evident reference that can be validated by the trusted component, providing protection against cloud provider tampering while maintaining system scalability.
Data Source
AI summary
Embodiments relate to digital data retention management. An aspect includes calculating a retention date associated with a data object in a storage system. Another aspect includes generating a cryptographic checksum for metadata relating to said data object, the metadata comprising the retention date. Another aspect includes storing said metadata and said cryptographic checksum. Another aspect includes, based on receiving a request to perform a deletion transaction on said data object for deleting said data object from the storage system: verifying metadata validity by checking the cryptographic checksum for the metadata associated with said data object to detect possible tampering of the metadata; verifying retention expiration by determining that a current date is past the retention date comprised in said metadata; and based on successful verification of metadata validity and retention expiration, authorizing deletion of said data object by the storage system.