Allow-List Token Obfuscation for Re-Identification Risk Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data obfuscation techniques fail to adequately protect sensitive information by allowing identifiable data to remain in shared environments, as they rely on deny lists that do not account for evolving definitions of sensitivity and unexpected data formats, exposing clients' information to risks and failing to ensure compliance with data protection standards.
Innovation Solution
A device and method that utilize an allow list to standardize and selectively mask incoming tokens, appending allowed tokens with delineators and masking others, with the option of replacement patterns, ensuring sufficient coverage and utility for downstream use while maintaining security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If deny list techniques are used to scrub sensitive data, then obvious identifiers matching preset patterns are removed, but data that does not match preset patterns remains and may be re-identifiable
Solution Approach 1:
The patent inverts the conventional deny list approach by using an allow list methodology. Instead of starting with all data and removing what should be protected, the system starts with all data and retains only what is explicitly permitted. This inversion ensures that any data not matching the allow list is automatically masked, preventing re-identification risks while maintaining useful information for downstream partners.
Solution Approach 2:
The system dynamically adjusts the obfuscation parameters based on the allow list definitions. By standardizing tokens against the allow list and applying consistent masking rules, the system adapts to evolving definitions of sensitive data while maintaining reliable protection effectiveness across different data formats and contexts.
2Device complexity
If conventional obfuscation techniques are applied, then processing is simpler, but sensitive information may be exposed to unnecessary risks
Solution Approach 1:
The system performs preliminary actions by pre-defining the allow list with standardized tokens and masking rules before processing the actual data. This preparation enables the obfuscation process to automatically and reliably protect sensitive information without requiring complex real-time analysis, reducing both complexity and exposure risk.
3Reliability
If allow list techniques are used to standardize and mask tokens, then only allowed tokens are shared with adequate contextual information, but the processing complexity increases
Solution Approach 1:
The allow list serves multiple functions: it defines permitted tokens, establishes standardization rules, and provides masking guidelines. This multi-functionality reduces processing complexity by consolidating what would otherwise require separate systems, while maintaining reliable data protection compliance through consistent application of all rules from a single source.
Data Source
AI summary
A device, method, and non-transitory computer readable medium for obfuscating text data by selectively masking incoming tokens within the text data based on allowed tokens within an allow list, and storing a result thereof within a memory.


