Time-Based Encryption Key Management for Secure Data Deletion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data encryption methods require the entire encrypted data to be rewritten with 1s and 0s for deletion, which is inefficient and not practical for managing encrypted data effectively.

Innovation Solution

Implementing a time-based encryption key system where encrypted data is stored with metadata identifying the key, allowing for the deletion of encryption keys instead of the data itself, and storing the key in a location other than the storage medium, such as a cache or server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If encrypted data is deleted by rewriting with 1s and 0s, then data security is maintained, but data maintenance efficiency deteriorates

Engineering Contradiction:
Improvedata securityVSAvoiddata maintenance efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system divides the encryption key into multiple segments distributed across different storage locations. Deleting data becomes as simple as removing or corrupting these key segments, rather than repeatedly overwriting the entire data set. This segmentation transforms a complex deletion process into a simple key removal operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The encryption key is extracted from the data storage medium and stored separately in volatile memory or cache. This separation allows the key to be independently managed and deleted without affecting the stored data. The data remains on disk while the extracted key in memory controls access, enabling efficient deletion by simply clearing the key from memory.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of operation

If the encryption key is stored on the storage medium with the data, then data access is simplified, but data deletion efficiency deteriorates

Engineering Contradiction:
Improvedata access simplicityVSAvoiddata deletion efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The encryption key is extracted from persistent storage and placed in volatile memory or cache during system operation. This extraction enables fast data access while allowing independent key management. Deletion is achieved by clearing the key from memory rather than modifying stored data, resolving the contradiction between access simplicity and deletion efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Volatile memory acts as an intermediary between persistent data storage and the processing system. The key resides in this intermediary layer, providing fast access to data while enabling efficient deletion through key clearance. This intermediary layer decouples the access path from the deletion path, allowing optimized operations for each.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the entire encrypted data is rewritten for deletion, then data security is maintained, but time and resources are wasted

Engineering Contradiction:
Improvedata securityVSAvoiddeletion time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The encryption key is extracted from the storage medium and stored in volatile memory. Deletion is accomplished by simply clearing this extracted key from memory, which instantly renders the encrypted data inaccessible. This approach reduces deletion from a time-consuming multi-pass overwrite operation to a single memory clearance operation, dramatically reducing deletion time while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system uses volatile memory for key storage, which is inherently temporary and easily cleared. This disposable characteristic of volatile memory allows for rapid key deletion without permanent traces, providing secure and fast data deletion. The short-lived nature of volatile storage enables efficient key management compared to persistent storage methods.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS9152814B1Writing and reading encrypted data using time-based encryption keys
Publication Date: 2015.10.06 EMC INT
  • US9152814B1 patent drawing
  • US9152814B1 patent drawing
  • US9152814B1 patent drawing

AI summary

In one aspect, a method to manage encrypted data includes configuring a first portion of a storage medium to store encrypted data. The encrypted data is encrypted using a time-based encryption key. The method also includes configuring a second portion of the storage medium to include metadata identifying the time-based encryption key and storing the time-based encryption key in a location other than the storage medium.