Diffie Hellman Key Exchange for Secure Medical Dataset Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing key distribution mechanisms for secure data transfer, particularly in medical datasets, are inefficient and inconvenient for reversing pseudo-anonymization, especially when dealing with sensitive data like increased radiation dosage values that require analysis.
Innovation Solution
A method and system utilizing a Diffie Hellman key pair generation on both user and server sides, where a user-side Diffie Hellman key pair is generated on the user device, the public key is transferred to the server, and a server-side Diffie Hellman key is used to encrypt the dataset, which is then transferred to a cloud service, allowing secure decryption on the user device without the cloud service's ability to decrypt the data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional key distribution mechanisms are used for secure data transfer, then data security is maintained, but the process becomes complex and inconvenient for reversing pseudo-anonymization
Solution Approach 1:
The patent extracts the key generation process from the server and places it on the user device. The user device independently generates its own Diffie-Hellman key pair, eliminating the need for complex certificate management and key distribution from the server side. This extraction simplifies the overall system operation while maintaining security.
Solution Approach 2:
The user device performs self-service by autonomously generating its own cryptographic key pair and managing its own authentication credentials. This self-service approach eliminates dependency on complex server-side key distribution mechanisms and makes the reversing of pseudo-anonymization convenient for the user.
2Productivity
If symmetric encryption is used for efficient data transfer, then transfer speed is improved, but key distribution becomes insecure through cloud services
Solution Approach 1:
The patent employs asymmetric cryptography (Diffie-Hellman key exchange) where the user device generates a key pair with public and private components. The public key can be freely shared for efficient symmetric encryption of data transfer, while the private key remains securely stored on the user device, preventing insecure key distribution through cloud services.
Solution Approach 2:
The cryptographic system is segmented into public and private components. The public key is used for open key distribution and establishing secure channels, while the private key is kept segmented and isolated on the user device. This segmentation allows efficient symmetric encryption to be used for data transfer while maintaining security through separate key management.
3Reliability
If asymmetric encryption is used for secure key management, then security is improved, but processing time increases
Solution Approach 1:
The patent merges asymmetric and symmetric encryption methods in a hybrid approach. Asymmetric encryption (Diffie-Hellman) is used for secure key exchange and establishment, while symmetric encryption is used for the actual bulk data transfer. This combination leverages the security of asymmetric methods for key management while achieving the speed of symmetric methods for data processing.
Solution Approach 2:
The asymmetric key exchange is performed preliminarily to establish secure symmetric encryption keys before the actual data transfer begins. This preliminary action using computationally intensive asymmetric encryption is done once during key establishment, allowing subsequent fast symmetric encryption to handle the bulk data transfer without time loss.
4Ease of operation
If data is stored in cloud service, then accessibility is improved, but unauthorized decryption risk increases
Solution Approach 1:
The user device acts as an intermediary that holds the private key and controls decryption authority. Data can be stored and accessed through cloud services with improved accessibility, but the user device intermediary maintains security by being the sole entity capable of decrypting the data using its privately stored key, preventing unauthorized decryption even if cloud storage is compromised.
Data Source
AI summary
A method for transfer of a dataset includes provisioning or generating a user-side Diffie Hellman key pair, including a secret user key and a public user key; transferring the public user key to the server; provisioning or generating a server-side Diffie Hellman key pair, including secret server and public server keys; provisioning a dataset on the server; generating a server-side Diffie Hellman key using the secret server key and the public user key, and encrypting the dataset to generate an encrypted dataset, via a resulting server-side Diffie Hellman key generated on the server side; transferring the encrypted dataset to the cloud service; retrieving the public server key and the encrypted dataset from the cloud service; and generating a user-side Diffie Hellman key using the secret user key and the public server key retrieved, and decrypting the encrypted dataset on the user device using the user-side Diffie Hellman key.