Unique Data Element Identifiers for Privacy Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing cryptography methods for privacy control in applications like Apple's Wallet, where sensitive data elements are stored in manifest files with hash codes, allow for potential privacy breaches as the same hash code can be associated with different users, enabling reverse engineering to expose unintended sensitive information.
Innovation Solution
Creating unique identifiers for each data element, hashing them with the identifier using a cryptographic hash function, and storing these identifiers and signatures within or outside the manifest file to ensure only the requested information is accessible, thereby enhancing privacy security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hash codes are used to verify data element integrity, then verification capability is improved, but privacy security deteriorates because the same hash code can be associated with different users enabling reverse engineering
Solution Approach 1:
The patent segments the verification process by creating unique identifiers for each data element within a group, rather than using a single hash code for the entire manifest. This allows the challenger to verify specific data elements without accessing other sensitive information in the manifest file.
Solution Approach 2:
The patent extracts only the necessary information for verification by creating signatures for specific data elements requested by the challenger, rather than providing the entire manifest file. This extracts and provides only the minimal required data for verification while maintaining privacy security.
2Reliability
If the entire manifest file is provided for verification, then verification completeness is improved, but information exposure increases revealing unintended sensitive data
Solution Approach 1:
The challenger extracts and receives only the specific data elements that are requested for verification, along with their corresponding unique identifiers and signatures. This prevents exposure of other sensitive information in the manifest file that is not required for verification.
Solution Approach 2:
Instead of providing the complete manifest file (excessive action), the system provides only the partial information necessary for verification - specifically the requested data elements, their unique identifiers, and signatures. This achieves verification completeness without unnecessary information exposure.
3Object-affected harmful factors
If unique identifiers are created for each data element, then privacy security is improved, but device complexity increases due to additional hashing and signature creation
Solution Approach 1:
The unique identifiers and signatures are created in advance during the setup phase, before any verification occurs. This preliminary action allows the manifest file to be pre-processed with all necessary cryptographic elements, reducing the complexity during the actual verification process when the challenger only needs to perform matching operations.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
This approach ensures that only the intended sensitive information is exposed to the challenger, preserving the security of other privacy information by using unique identifiers that correspond to random numbers, thus preventing unauthorized access to sensitive data.
Implementation Method 1
hashing the combined data element and identifier using a cryptographic hash function to create a hash code
Implementation Method 2
the signature is created by applying a private key to the hash code
Data Source
AI summary
A method, system and computer program product for privacy control. A unique identifier for each data element of a group of data elements (e.g., driver's license contains a group of data elements, such as name, driver's license number) is created. These identifiers may be stored along with documentation (e.g., label) of the associated data elements in a manifest file. Alternatively, the identifiers may be stored in a file outside of the manifest file. In this manner, by utilizing a data element identifier which corresponds to a random number, security of privacy information is improved as one would only be able to obtain such sensitive information by obtaining such an identifier. Furthermore, the user only needs to send the requested data elements, as opposed to all the data elements of the group of data elements, to the challenger. In this manner, the user is preserving the security of other privacy information.