Dynamic Encryption Validation via Parallel Decryption Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data encryption and storage systems lack an effective mechanism to ensure data integrity, leading to potential storage of corrupted data that may not be retrievable even with the proper decryption key, especially in encryption techniques like cipher-block chaining or cipher feedback, where errors can go undetected until data is read back.

Innovation Solution

A method that decrypts a sequential data element in parallel with encrypting another, generating and comparing encryption validation metadata to determine if the encryption was valid, allowing for the detection of errors and suspension of further encryption operations or marking data for re-encryption if necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data encryption is performed without integrity validation, then encryption speed and storage efficiency are improved, but data integrity cannot be ensured and corrupted data may be stored

Engineering Contradiction:
Improveencryption speedVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback by decrypting the previously encrypted data block and validating its integrity against the current encryption operation. This feedback mechanism allows the system to detect encryption errors and ensure data integrity without significantly impacting encryption speed, as the validation occurs during the encryption process rather than requiring separate post-processing steps.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary decryption and validation of the previous data block before completing the current encryption operation. This preliminary action ensures that any errors in the encryption process are detected early, preventing corrupted data from being stored while maintaining efficient encryption throughput.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If encryption validation metadata is generated and compared for each data element, then data integrity is ensured, but processing time and computational resources increase

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

Solution Approach 1:

The system merges the validation operation with the encryption process by performing decryption and integrity validation of the previous block concurrently with the encryption of the current block. This merging of operations allows integrity checking to occur without adding significant time overhead, as the validation and encryption operations overlap in time.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system maintains continuous useful action by overlapping the decryption/validation of previous data with the encryption of current data. This continuous operation ensures that integrity validation is performed without creating idle time or significant delays, maintaining steady processing throughput while ensuring data integrity.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If read-back validation is performed for each encrypted block, then data integrity is verified, but latency and storage device manipulation complexity increase

Engineering Contradiction:
Improvedata integrityVSAvoidstorage device manipulation
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs the validation action preliminarily during the encryption process rather than requiring a separate read-back operation after storage. By completing the validation before the data is fully written to storage, the system eliminates the need for complex post-storage read-back operations and reduces storage device manipulation complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The encryption system performs self-validation by internally decrypting and validating the previous encryption block during the current encryption operation. This self-service mechanism eliminates the need for external read-back validation operations, reducing storage device manipulation complexity while ensuring data integrity.

Inventive Principle:
Principle #25Self-service

4Productivity

If encryption errors are not detected, then processing speed is maintained, but corrupted data may be stored and become irretrievable

Engineering Contradiction:
Improveprocessing speedVSAvoidcorrupted data
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The system implements feedback by validating the integrity of the previously encrypted data block during the current encryption operation. This feedback mechanism detects encryption errors in real-time, preventing corrupted data from being stored while maintaining processing speed, as the validation occurs concurrently with encryption rather than requiring separate error-checking steps.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary validation of the previous encryption block before completing the current encryption operation. This preliminary action ensures that errors are detected early in the process, preventing corrupted data from being stored while maintaining efficient processing speed through overlapping operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8135958B2Method, system, and apparatus for dynamically validating a data encryption operation
Publication Date: 2012.03.13 TAASERA LICENSING LLC
  • US8135958B2 patent drawing
  • US8135958B2 patent drawing
  • US8135958B2 patent drawing

AI summary

A method, system, and apparatus for dynamically validating a data encryption operation are disclosed. In one embodiment, a method is provided which comprises decrypting a first sequential data element of a plurality of data elements substantially in parallel with the encryption of a second sequential data element of the plurality, where the first element comprises first data and first encryption validation metadata. In response to the decryption, second encryption validation metadata is generated utilizing the first data. Thereafter, a determination is made whether the first element has been validly encrypted based upon a comparison of the first and second metadata. In other embodiments, an encryption validation indicator may be generated (e.g., to notify a user of a detected encryption error and/or to mark a portion of data for re-encryption), further encryption operations may be suspended, and/or the storage of the first data element may be controlled following such a determination.