MICRO FOCUS LLC (20240333537). Audit Chain for Hashes Using Tokenization simplified abstract
Contents
Audit Chain for Hashes Using Tokenization
Organization Name
Inventor(s)
Douglas Max Grover of RIGBY ID (US)
MICHAEL F. Angelo of HOUSTON TX (US)
Audit Chain for Hashes Using Tokenization - A simplified explanation of the abstract
This abstract first appeared for US patent application 20240333537 titled 'Audit Chain for Hashes Using Tokenization
- Simplified Explanation:**
A method for validating records using hash tokens is described in the patent application. The process involves tokenizing a first hash of a record and storing it in a tokenization table. When a request to validate the record is received, the record is validated by comparing the first hash with a second hash using corresponding hash tokens.
- Key Features and Innovation:**
- Retrieval and tokenization of a first hash of a record.
- Storing the first hash in a tokenization table with a corresponding hash token.
- Validation of records by comparing the first hash with a second hash using hash tokens.
- Potential Applications:**
This technology can be applied in data security systems, record validation processes, and authentication mechanisms.
- Problems Solved:**
- Ensures the integrity and authenticity of records.
- Provides a secure method for validating records using hash tokens.
- Benefits:**
- Enhanced data security.
- Efficient record validation process.
- Reliable authentication mechanism.
- Commercial Applications:**
The technology can be utilized in industries such as finance, healthcare, and legal sectors for secure record validation and data integrity maintenance.
- Questions about the Technology:**
1. How does this technology improve data security measures? 2. What are the potential implications of using hash tokens for record validation?
- Frequently Updated Research:**
Stay updated on advancements in hash tokenization technology and its applications in data security and record validation processes.
Original Abstract Submitted
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.
