Transient Dataset Management System with Blockchain TTL
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies fail to effectively manage the lifecycle of data, particularly in ensuring that personal data is erased when no longer needed, as mandated by regulations like the EU's Right to be Forgotten.
Innovation Solution
Implementing a system that uses encryption and a Transient Dataset Management System (TDMS) header with timestamps, stored in a distributed ledger like Blockchain, to control access to data based on a specified Time To Live (TTL) or Time To Birth (TTB), ensuring data is accessible only within a defined timeframe.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored indefinitely for future access, then data availability is improved, but compliance with data protection regulations deteriorates
Solution Approach 1:
The system performs preliminary actions by embedding expiration timestamps and access control parameters into data headers before storage. The distributed ledger预先 records TTL (time-to-live) values and TTB (time-to-birth) timestamps, enabling automatic access denial and data deletion when time limits are reached, thus ensuring regulatory compliance while maintaining availability during the valid period.
Solution Approach 2:
The system implements feedback mechanisms where the distributed ledger continuously monitors current time against stored TTL and TTB parameters. When the current time exceeds the TTL or precedes the TTB, the system automatically updates access permissions and triggers deletion protocols, creating a closed-loop control system that maintains both availability and compliance.
2Adaptability or versatility
If manual data deletion processes are used, then flexibility in data management is improved, but automation level deteriorates
Solution Approach 1:
The system enables self-service automation where data automatically undergoes access denial and deletion based on pre-configured TTL and TTB parameters stored in the distributed ledger. The smart contracts autonomously execute deletion operations when time conditions are met, eliminating the need for manual intervention while maintaining flexible parameter configuration for different data types and regulatory requirements.
Solution Approach 2:
The system introduces dynamic time-based parameters (TTL and TTB) that automatically adjust access permissions and trigger deletion actions. These dynamic parameters allow flexible configuration for different data lifecycle requirements while automating the actual deletion process, combining adaptability with automation through programmable time-based rules.
3Reliability
If encryption keys are permanently stored, then data access security is improved, but key management complexity deteriorates
Solution Approach 1:
The system changes the temporal parameters of encryption key validity by associating each key with TTL and TTB timestamps stored in the distributed ledger. Keys are automatically invalidated when their time parameters expire, eliminating the need for permanent key storage and reducing key management complexity through automatic key rotation and deletion based on time-based parameters.
Solution Approach 2:
The distributed ledger acts as an intermediary between data storage and key management systems. Instead of permanently storing keys alongside data, the system stores time-based access parameters in the ledger, which mediates key validation and automatic revocation. This intermediary approach simplifies key management by replacing complex permanent key storage with automated time-based access control.
Data Source
AI summary
Examples described herein relate to a manner of provide a time of life of data. In some examples, data and control parameters are received from a data source. The data can be encrypted and stored. In addition, at least a portion of the control parameters can be stored into a distributed ledger. In some examples, the portion of the control parameters include an indicator of expiration time of the data. In some examples, a data header for the data is generated, where the data header includes an indication that the data is subject to a limited life span and a data identifier. The data header can be accessed with a request to access the encrypted data. In some examples, a request to determine if the data is valid and accessible is provided to a node of the distributed ledger and an indication of whether the data is valid and accessible is received from a node in the distributed ledger.