Format-Preserving Tokenization for Secure Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data security methods face challenges in securely managing and accessing sensitive data like credit card numbers and health information, as encryption increases data size, requiring schema changes and posing risks, while distributing encryption keys across systems makes them vulnerable to hacking.
Innovation Solution
A format-preserving tokenization system that replaces sensitive data with tokenized strings, allowing secure access and utilization by generating a token body portion independent of the data values, stored in a secure database with encryption keys, and allowing retrieval upon proper authorization, accommodating various tokenization strategies and data types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If encryption is used to secure sensitive data, then data security is improved, but data size increases requiring schema changes
Solution Approach 1:
The patent creates a tokenized copy of the sensitive data that preserves the original format and size. Instead of storing encrypted data that is larger than the original, the system generates a tokenized representation that is identical in size to the original data field, eliminating the need for schema changes while maintaining security through tokenization rather than traditional encryption.
Solution Approach 2:
The system changes the parameter of data representation from encrypted form to tokenized form. This parameter change allows the data to maintain its original size characteristics while achieving security through a different mechanism that does not increase data volume, thereby resolving the contradiction between security and data size.
2Adaptability or versatility
If encryption keys are distributed to multiple systems, then data accessibility is improved, but security vulnerability increases
Solution Approach 1:
The patent extracts the security mechanism from traditional encryption key distribution and replaces it with tokenization. The sensitive data is tokenized at the source, and only tokens are distributed to various systems. This extraction removes the vulnerability associated with key distribution while maintaining the ability for multiple systems to access and process the data securely through token-based operations.
Solution Approach 2:
The token acts as an intermediary between the sensitive data and the multiple systems that need to access it. Instead of distributing encryption keys directly to systems, the token serves as a secure mediator that allows systems to process data without having access to the original sensitive information or requiring encryption keys, thereby reducing security vulnerabilities while maintaining accessibility.
3Reliability
If data format is changed for security, then security is improved, but system compatibility deteriorates
Solution Approach 1:
The patent applies local quality by preserving the original data format characteristics at the token level. The tokenized data maintains the same format, length, and structure as the original sensitive data in local contexts, ensuring compatibility with existing systems. This allows each system to continue processing data in its expected format while the underlying security mechanism remains robust through tokenization.
Data Source
AI summary
Systems and methods for secure access and utilization of sensitive data such as credit card numbers, Social Security Numbers, personal identifying information, etc. A tokenizing strategy component provides for creating, managing, and storing tokenization strategies on behalf of a plurality of users. A data tokenizing component is operative to (a) receive an input data string of sensitive data from a user, (b) apply a selected tokenization strategy to the input data string to generate a tokenized data string, and (c) provide the tokenized data string for storage in association with the input data string. A secure server including a secure database stores the tokenized data string and the input data string in a corresponding mapped relationship. A security component controls access to and retrieval of the tokenized data string and to the input data string in accordance with predetermined security requirements of the users.