Uni-directional Token Correlation for Secure Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current tokenization mechanisms are vulnerable to security breaches, as a compromised first database system can potentially reveal tokens to adversaries, allowing fraudulent access to sensitive information stored in a second database system.
Innovation Solution
Implementing a uni-directional data correlation token system using one-way cryptographic hash functions to generate and manage tokens, where a tokenization server generates and stores tokens in separate databases, ensuring that even if one token is compromised, the other cannot be used for unauthorized access due to different hash functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single tokenization system stores tokens in a database, then data access is simplified, but security is compromised because a breach reveals all tokens
Solution Approach 1:
The patent divides the token storage system into multiple independent database instances (first database instance, second database instance, etc.), each storing different tokens. This segmentation ensures that a security breach in one database does not compromise tokens stored in other databases, thus improving security while maintaining operational simplicity through standardized access procedures.
2Reliability
If tokens are stored in multiple separate databases, then security is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal token retrieval process that can access tokens from multiple different database instances using the same procedure. The system uses a common identifier format and similar retrieval logic across all database instances, making the multi-database system function as a unified whole and reducing the operational complexity despite the increased security architecture.
3Productivity
If all tokens are stored in one database, then retrieval efficiency is high, but the impact of a security breach is maximized
Solution Approach 1:
The patent segments token storage across multiple database instances so that each database contains only a subset of tokens. This segmentation limits the impact of security breaches to only the tokens stored in the compromised database, while retrieval efficiency is maintained through optimized query mechanisms that efficiently search across segmented storage.
4Reliability
If different database systems are used for different tokens, then security isolation is achieved, but data management complexity increases
Solution Approach 1:
The patent creates a universal data management interface that handles multiple different database instances through a single standardized procedure. The system manages diverse database systems using consistent identifier formats and retrieval logic, providing security isolation through physical separation while maintaining simple unified data management through the universal interface.
Data Source
AI summary
A method is disclosed. The method includes receiving by a tokenization server, a request to process an interaction from a user device, where the request includes a user identifier associated with a user. The tokenization server generates a first token using a first one-way cryptographic hash function based on the user identifier, and a second token using a second one-way cryptographic hash function based on the first token. The tokenization server retrieves first information stored in a first data storage associated with the tokenization server based on the second token, and transmits the first token and the first information to a processing computer. The processing computer is programmed to retrieve, from a second data storage associated with the processing computer, second information based on the first token, and execute the interaction based on the first information and the second information.