UUID Anonymization via Controlled Masking and Format-Preserving Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to adequately anonymize user identities when using unique user identifiers (UUIDs) across multiple partner systems, leading to potential privacy breaches and compliance issues, particularly in large networks where a single UUID is used for various interactions, resulting in correlation of user data and compromised privacy.
Innovation Solution
The solution involves generating multiple modified versions of a UUID by selectively encrypting and masking its non-masked portions, with each version associated with different partner systems and rules, preventing correlation and enhancing anonymization without the need for separate UUIDs for each device or transaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single UUID is used across multiple partner systems, then system simplicity and ease of operation are improved, but user privacy and data security deteriorate due to correlation of user data
Solution Approach 1:
The UUID is segmented into multiple versions, each tailored for specific partner systems. Instead of using a single universal UUID, the system generates partitioned UUID variants that are distributed to different partners, preventing any single partner from obtaining the complete identifier and thus preventing user correlation across systems.
Solution Approach 2:
Each partner system receives a UUID version with quality characteristics optimized for its specific needs and security requirements. The UUID structure is customized locally for each partner, with different encryption levels and masking strategies applied based on the partner's specific privacy requirements and use case.
2Object-affected harmful factors
If multiple separate UUIDs are generated for different partner systems, then user privacy is improved, but device complexity and processing overhead increase
Solution Approach 1:
The system performs preliminary generation of all necessary UUID versions in advance, before they are needed by partner systems. This pre-generation process creates a comprehensive set of UUID variants that can be distributed and stored locally, eliminating the need for complex real-time generation logic at each partner system while ensuring privacy from the outset.
Solution Approach 2:
Instead of generating entirely separate UUIDs for each partner, the system creates copies of the base UUID with specific modifications (encryption, masking, transformation). These copied and adapted UUIDs maintain the essential identifying function while reducing complexity compared to generating completely independent identifier systems for each partner.
3Object-affected harmful factors
If UUIDs are encrypted and masked for different partners, then user anonymization is improved, but processing time and computational resources increase
Solution Approach 1:
Encryption and masking operations are performed in advance during the UUID generation phase, rather than being applied in real-time during each transaction. This preliminary cryptographic processing converts the UUIDs into their protected forms beforehand, allowing partner systems to use the pre-encrypted identifiers without incurring additional computational overhead during operations.
Solution Approach 2:
The system changes the cryptographic parameters and encryption strength based on the specific requirements of each partner and transaction type. By adjusting encryption parameters dynamically during the pre-processing phase, the system optimizes the balance between security and processing efficiency, applying stronger encryption only where absolutely necessary.
4Adaptability or versatility
If partner systems can correlate UUIDs across different systems, then system versatility and data utility are improved, but user privacy and compliance with regulations deteriorate
Solution Approach 1:
The universal identifier is segmented into partner-specific UUID versions that cannot be easily correlated. Each segment is designed to work independently within its designated partner system, breaking the correlation chain that would otherwise allow cross-system tracking while maintaining sufficient functionality for each partner's data utility needs.
Solution Approach 2:
The modified UUID structure acts as an intermediary that enables partner systems to process user data without direct correlation capability. The UUID serves as a mediator that preserves user anonymity while still allowing partners to perform their designated functions, thus maintaining compliance while preserving data utility through the intermediary identifier structure.
Data Source
AI summary
Systems are methods are used for facilitating identify anonymization by using controlled masking and encryption of user identifiers, such as UUIDs. A system that manages a UUID converts the UUID into a set of one or more different unique versions of the UUID for one or more corresponding different partner system(s) by removing and replacing masked portions of the UUID and by selectively encrypting the non-masked portions of the UUID. New masked portions added to the new version(s) of the UUID identify different corresponding partner(s) and/or rules to be applied by the different partner(s) when handling the different unique version(s) of the UUID(s). Partner systems that receive the new versions of the UUID identify and utilize the new masked portions to deterministically control decrypting and/or other processing of the new version of the UUID.