Secure Component Work-Sharing for Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for secure data handling, particularly in unsecure applications or software components, face challenges such as performance degradation and user experience issues due to the overhead of cryptographic operations and the impending post-quantum threat.

Innovation Solution

A method for tamper-resistant work-sharing between a secure component and a software component, where the secure component produces a cryptogram using a trust cryptography function and the software component uses this cryptogram to cipher and decipher data, thereby offloading computational workload and ensuring data integrity and privacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cryptographic operations are performed within the secure component for data integrity and authenticity, then data security and trust are improved, but the secure component's workload increases and performance degrades

Engineering Contradiction:
Improvedata securityVSAvoidsecure component performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The cryptographic processing is segmented into two parts: the secure component performs hash computation on data references (not the entire data), while the actual data encryption/decryption is performed by the unsecure application using provided keys. This segmentation reduces the secure component's workload while maintaining security through the trusted hash verification mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention extracts the computationally intensive cryptographic operations from the secure component and relocates them to the unsecure application environment. The secure component only retains the essential function of verifying data integrity through hash comparison, while the application handles the heavy lifting of actual data encryption and decryption.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If oversized data is processed and ciphered by the secure component, then data integrity is ensured, but user experience deteriorates due to performance bottlenecks

Engineering Contradiction:
Improvedata integrityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The data processing is segmented into reference handling (secure component) and actual data processing (unsecure application). The secure component only processes small data references and their hashes, while the application handles the oversized data, thereby improving user experience without compromising data integrity verification.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If data is stored encrypted outside the hardware component and decrypted only when needed, then storage flexibility is improved, but the decryption task becomes a bottleneck to user experience quality

Engineering Contradiction:
Improvestorage flexibilityVSAvoiduser experience quality
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The decryption operation is extracted from the secure component and performed by the unsecure application. The secure component only provides the necessary cryptographic keys and verifies data integrity through hash comparison, while the application handles the time-consuming decryption process, eliminating it as a user experience bottleneck.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4554141A1Method of entrusting data using a secure component
Publication Date: 2025.05.14 THALES DIS FRANCE SA
  • EP4554141A1 patent drawingFigure 1
  • EP4554141A1 patent drawingFigure 2~3
  • EP4554141A1 patent drawingFigure 4~5

AI summary

The invention relates to a method to entrust requested data at a relying party, said requested data coming from an unsecure software component in a user equipment of a user, said user equipment having a secure component storing data hash of said data and having a pseudonym. The secure component produces a cryptogram being a concatenation of several ciphertexts successively obtained by chaining executions of a trust cryptography function using a secure component's secret key, said function being applied to successive plaintexts comprising at least the secure component's pseudonym and data hash of the data corresponding to data's references requested by the relying party which then receives and deciphers the requested data that has been enciphered by the software component using the last ciphertext concatenated in at least said cryptogram and an applicative cryptography algorithm. The cryptogram is sent to a trust service for de-concatenation and chaining executions of a trust cryptography function correlated to the trust cryptography function of the secure component to extract the secure component's pseudonym and the data hash of the data corresponding to the given data's reference in successive de-ciphered plaintexts. The method entrusts received deciphered data only if the extracted pseudonym corresponds to the received pseudonym, and if the data hash corresponding to the given data's reference extracted by the trust service corresponds to the data hash corresponding to the given data's reference calculated by the relying party.