Tokenization Table for Quantum-Resistant Hash Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Advanced computing, such as quantum computing, increases the likelihood of finding hash collisions, compromising existing hashing techniques and potentially leading to security vulnerabilities in data validation processes.

Innovation Solution

The implementation of a tokenization table that stores hash tokens corresponding to record hashes, allowing for secure validation by comparing received hash tokens to stored hashes, thereby obfuscating the original hash and resisting quantum computing attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional hashing techniques are used for data validation, then the system is simple and easy to implement, but the security is compromised due to vulnerability to hash collisions from advanced computing

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a tokenization table as an intermediary component between the original data and its hash. The tokenization table stores mappings between tokens and hashed values, acting as a mediator that enhances security without requiring changes to the fundamental hashing mechanism. This intermediary layer protects against hash collision attacks by advanced computing while maintaining the simplicity of hash-based validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the hash validation process into two distinct parts: (1) the original hashing function that generates hash values from data, and (2) the tokenization table that provides an additional security layer. This segmentation allows the system to maintain the simplicity of traditional hashing while adding security through the separate tokenization component, resolving the contradiction between security and complexity.

Inventive Principle:
Principle #1Segmentation

2Reliability

If hash tokens are stored in a tokenization table for secure validation, then the system resists quantum computing attacks, but the device complexity increases

Engineering Contradiction:
Improvesecurity against quantum computingVSAvoidtokenization table structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a copy of the hash validation functionality through the tokenization table. Instead of modifying the original hashing algorithm to be quantum-resistant, the system creates a parallel validation mechanism using tokenized hashes. This copying approach provides quantum-resistant security while keeping the original simple hashing system intact, thus managing complexity through replication rather than redesign.

Inventive Principle:
Principle #26Copying

3Reliability

If tokenization is implemented to obfuscate original hashes, then data integrity is protected, but the ease of operation decreases due to additional validation steps

Engineering Contradiction:
Improvedata integrityVSAvoidvalidation process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The tokenization process is performed in advance during data ingestion or initial storage. The tokenization table is pre-populated with token-hash mappings before validation is needed. This preliminary action ensures that when validation occurs, the tokenization infrastructure is already in place, reducing the operational burden during actual validation tasks while maintaining data integrity protections.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240333537A1Audit Chain for Hashes Using Tokenization
Publication Date: 2024.10.03 MICRO FOCUS LLC
  • US20240333537A1 patent drawing
  • US20240333537A1 patent drawing
  • US20240333537A1 patent drawing

AI summary

A first hash of a record is retrieved. The first hash is tokenized by storing the first hash in a tokenization table that has a corresponding hash token. A request is received to validate the record. The request to validate the record comprises a second hash of the record and a second hash token. In response to receiving the request to validate the record, the record is validated by looking up the first hash in the tokenization table using the second hash token and comparing the looked up first hash to the second hash. In response to the looked up first hash being the same as the second hash, the record is validated. In response to the looked up first hash not being the same as the second hash, the record is not validated.