Reversible Tokenization with Embedded Role-Based Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data tokenization methods fail to effectively embed role-based access control and ensure data privacy, as they lack mechanisms to securely update tokenization processor secrets and maintain data integrity without revealing sensitive information.
Innovation Solution
The method employs Tokenization Processors that use reversible tokens and cryptographic techniques to embed scope-specific indicia, ensuring that only authorized requestors can access data, and updates tokenization processor secrets without compromising data security, utilizing multiparty computation and threshold signature schemes to maintain security even if some processors are compromised.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional tokenization methods are used, then data can be tokenized, but role-based access control cannot be effectively embedded and data privacy cannot be ensured
Solution Approach 1:
The patent segments the tokenization system into multiple independent tokenization processors, each holding a portion of the tokenization secret. This segmentation enables both data privacy (through distributed secrets) and role-based access control (through scope-specific indicia embedded in tokens). The token itself is segmented to include multiple components: the actual token value and scope-specific indicia that encode access control information.
Solution Approach 2:
The patent embeds scope-specific indicia within the token structure, creating a nested information hierarchy. The token contains embedded access control metadata that is concealed within the token itself, allowing role-based access control to be integrated without compromising the token's primary function. This nesting enables versatile access control while maintaining data privacy.
2Reliability
If tokenization processor secrets are updated, then security can be maintained, but previously tokenized data must be retokenized
Solution Approach 1:
The patent performs preliminary action by embedding scope-specific indicia and access control metadata into the token at the time of tokenization. This preliminary embedding of access control information allows the system to maintain security through secret updates without requiring retokenization, as the access control structure is already established and can be independently managed.
Solution Approach 2:
The patent creates a universal token structure that serves multiple functions: it acts as both the data identifier and the access control mechanism. The scope-specific indicia embedded in the token enable role-based access control while the token itself maintains data reference functionality. This multi-functionality allows security updates without affecting the core tokenization.
3Ease of operation
If requestors can access data, then usability is improved, but sensitive information may be revealed
Solution Approach 1:
The patent applies local quality by providing different levels of data access to different requestors based on their roles and permissions. The scope-specific indicia in the token enable fine-grained access control where authorized requestors can access data while unauthorized requestors cannot. This localized access control ensures ease of operation for authorized users while preventing information exposure to unauthorized users.
Solution Approach 2:
The patent introduces the token with embedded scope-specific indicia as an intermediary between the requestor and the sensitive data. This intermediary mechanism allows authorized access control without direct exposure of sensitive information. The token acts as a mediator that verifies permissions and controls data access, enabling ease of operation while preventing data exposure.
Data Source
AI summary
Participants as requestors using a requesting network element request one or more tokenization processors to generate tokens that represent a sanitized version of data such that the resultant tokens are amenable to comparison across participants. As circumstances warrant, one or more such tokens can be submitted to the tokenization processor(s) to privately retrieve the original data. Role-based access control scope parameters and tokenization processor-specific tokenization processor secrets can be embedded into reversible tokens that remain invariant under updating of the tokenization processor secrets across tokenization processors. By another approach, role-based access control scope parameters and tokenization processor-specific tokenization processor secrets are embedded into tokens and corresponding key tokens such that upon authorized presentation of a token by a requestor, the corresponding key token is recovered so that the keying material that was used to generate ciphertext is retrievable in order to recover the corresponding plaintext.