De-identification System Using Master Salt and Encryption Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data analytics systems face challenges in protecting sensitive information during data transfer and aggregation from multiple sources, as de-identification processes are prone to dictionary attacks and unauthorized linking, with a risk of single point failures and redundant computations.
Innovation Solution
A method and system that unify de-identified customer data by generating a global identifier using a master salt and encryption keys, ensuring secure transfer and linking while preventing unauthorized access, using a combination of masking, hashing, and encryption to maintain uniqueness and security across multiple sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If de-identification process is performed using hash keys at customer end, then sensitive information is protected during data transfer, but de-identified data becomes prone to dictionary attacks and unauthorized linking
Solution Approach 1:
The patent introduces a trusted third-party service (de-identification service) as an intermediary between data sources and target environments. This service performs de-identification using a master salt that is never exposed to customers or stored in any single location, thereby preventing dictionary attacks while maintaining the ability to link de-identified data across sources through deterministic hashing.
Solution Approach 2:
The patent segments the de-identification process into separate components: customer environments retain control of their data, the trusted service holds the master salt, and target environments receive de-identified data. This segmentation ensures that no single entity has both the data and the salt, eliminating the single point of failure while enabling secure data sharing.
2Productivity
If data from multiple sources is de-identified and merged at target environment, then analytics on larger dataset is enabled, but it becomes difficult to identify and link data with same identifiers
Solution Approach 1:
The patent transforms identifiers through deterministic hashing using a master salt, converting original identifiers into de-identified tokens that preserve equality relationships. This parameter transformation allows data from multiple sources to be linked by comparing hashed values rather than original identifiers, maintaining linkage capability while protecting sensitive information.
3Ease of manufacture
If salt or encryption keys are leaked, then entire de-identified data becomes vulnerable, creating a single point of failure
Solution Approach 1:
The patent implements protective measures in advance by never storing the master salt in any single location and never exposing it to customers. The salt is generated and held exclusively by the trusted de-identification service, providing beforehand cushioning against key leakage attacks while enabling secure de-identification across distributed systems.
4Reliability
If de-identification is performed at each customer end independently, then customer data privacy is maintained, but redundant computations occur and efficiency is reduced
Solution Approach 1:
The patent creates a universal de-identification service that performs the hashing function for all customers using a common master salt. This multi-functional service eliminates redundant computations by centralizing the de-identification process while maintaining customer data protection, as the same salt is used consistently across all data sources.
Data Source
AI summary
A method and a system are disclosed for generating a global identifier for linking or unifying a plurality of de-identified customer data received from multiple source environments. The plurality of customer data is de-identified based on a master salt and a master token is generated. The master token is encrypted using a source-encryption key to generate a source token. The source token is also encrypted using a target-encryption key to generate a transfer token. At a central environment or a central storage unit, the transfer token is decrypted and the source token is obtained. Thereafter, source token is decrypted to obtain the master token. At the central storage unit, the master token is hashed with a target salt to generate the global identifier which is subsequently used to unify the plurality of de-identified customer data.