Secure and zero knowledge data sharing for cloud applications
Disclosed is a zero-knowledge distributed application configured to securely share information among groups of users having various roles, such as doctors and patients. Confidential information may be encrypted client-side, with private keys that reside solely client side. Encrypted collections of data may be uploaded to, and hosted by, a server that does not have access to keys suitable to decrypt the data. Other users may retrieve encrypted data from the server and decrypt some or all of the data with keys suitable to gain access to at least part of the encrypted data. The system includes a key hierarchy with multiple entry points to a top layer by which access is selectively granted to various users and keys may be recovered.
1. A system for communicating patient data, the system comprising:
a first computing device associated with a patient, said first computing device configured to obtain patient data and encrypt the patient data with a first key, wherein the first computing device is further configured to transmit the encrypted patient data without providing the first key; and
a second computing device associated with a care provider, said second computing device configured to request the obtained patient data over a network from a third computing system, said third computing system does not have a decryption key to decrypt the encrypted patient data, wherein the second computing device is further configured to decrypt the encrypted data with a second key that is different than the first key and wherein the second key is a private key obtained by decrypting an encrypted private key (EPK) that was stored as part of a key hierarchy structure (KHS).
2. The system of claim 1 , wherein the first key is a public key.
3. The system of claim 1 , wherein the first and the second keys are generated at a time of registration of the patient as a new user.
4. The system of claim 1 , wherein another KHS is created based on a request to generate shared data.
5. The system of claim 1 , wherein names of entries of the KHS are obfuscated.
6. A system for communicating patient data, the system comprising a computing system configured to:
receive, over a network, encrypted patient data associated with a patient, said patient data encrypted with a first key, wherein the encrypted patient data is received without the first key;
store the encrypted patient data without access to any decryption keys to decrypt the encrypted patient data; and
transmit the encrypted patient data based on a request for stored patient data, wherein the encrypted patient data is decrypted with a second key that is different than the first key and wherein the second key is a private key obtained by decrypting an encrypted private key (EPK) that was stored as part of a key hierarchy structure (KHS).
7. The system of claim 6 , wherein the first key is a public key.
8. The system of claim 6 , wherein the first and the second keys are generated at a time of registration of the patient as a new user.
9. The system of claim 6 , wherein another KHS is created based on a request to generate shared data.
10. The system of claim 6 , wherein names of entries of the KHS are obfuscated.
11. A method for communicating patient data, the method comprising:
receiving, over a network, encrypted patient data associated with a patient, said patient data encrypted with a first key, wherein the encrypted patient data is received without the first key;
storing the encrypted patient data without access to any decryption keys to decrypt the encrypted patient data; and
transmitting the encrypted patient data based on a request for stored patient data, wherein the encrypted patient data is decrypted with a second key that is different than the first key and wherein the second key is a private key obtained by decrypting an encrypted private key (EPK) that was stored as part of a key hierarchy structure (KHS).
12. The method of claim 11 , wherein the first key is a public key.
13. The method of claim 11 , wherein the first and the second keys are generated at a time of registration of the patient as a new user.
14. The method of claim 11 , wherein another KHS is created based on a request to generate shared data.
15. The method of claim 11 , wherein names of entries of the KHS are obfuscated.