Cloud key escrow system

• US 9,900,288 B2
• Filed: 11/18/2014
• Issued: 02/20/2018
• Est. Priority Date: 06/17/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: D'Souza, Roy Peter, Pandey, Omkant
• Primary Examiner(s): SCOTT, RANDY A
• Application Number:
  US14/546,341
• Publication Number:
  US 20150074402A1
• Time in Patent Office: 1,190 Days
• Field of Search: 713168, 713172, 713185, 713193, 726 2, 726 5, 726 17
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 2221/2107 File encryption
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 9/0825 using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
• CPC Class Codes: H04L 9/085 Secret sharing or secret splitting, e.g. threshold schemes
• CPC Class Codes: H04L 9/0894 Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage

Abstract

Embodiments are directed to allowing a user to store encrypted, third-party-accessible data in a data store and to providing third party data access to a user'"'"'s encrypted data according to a predefined policy. A data storage system receives encrypted data from a user at a data storage system. The data is encrypted using the user'"'"'s private key. The data storage system stores the received encrypted data according to a predefined policy. The encryption prevents the storage system from gaining access to the encrypted data, while the policy allows the encrypted data to be released upon receiving a threshold number of requests from verified third parties. The data storage system implements a verifiable secret sharing scheme to verify that the encrypted data can be reconstituted without the data storage system accessing the encrypted data. The data storage system synchronously acknowledges that the received encrypted data has been verified and successfully stored.

Claims

1. At a computer system including at least one processor and a memory, in a computer networking environment including a plurality of computing systems, a computer-implemented method for allowing a user to store encrypted, third-party-accessible data in a data store, the method comprising:

receiving at a data storage system encrypted data from a user, wherein the encrypted data was encrypted prior to having been received and the encryption having been completed prior to being received by the data storage system, wherein the received encrypted data is an encrypted key which is stored as a plurality of shares, the shares being mathematical transformations of the user'"'"'s private key, and wherein each share is provided to one of the verified third parties;

storing the received encrypted data in the data storage system according to a predefined policy, the encryption preventing the storage system from decrypting the encrypted data, the policy allowing the encrypted data to be released upon receiving at least a threshold number of requests from verified third parties; and

the data storage system implementing a verifiable secret sharing scheme to verify that the encrypted data can be decrypted without the data storage system having the ability to decrypt the encrypted data.

2. The method of claim 1, wherein each verified third party publishes their own public keys and encrypts their share of the encrypted key using their published public key.

3. The method of claim 2, wherein the verified third party shares encrypted according to the third parties'"'"' public keys are stored in the data storage system, the encrypted shares preventing the data storage system from accessing the user'"'"'s data.

4. The method of claim 3, wherein the shares are generated in such a way that a threshold gate is used to recreate the original key from those shares.

5. The method of claim 4, wherein the predefined policy indicates that the threshold gate is a specified number or percentage of the total number of shares, such that when that specified number of verified third party share holders has requested release of the encrypted data, the data storage system provides the encrypted data.

6. The method of claim 5, wherein the predefined policy indicates a set of rules comprising Boolean logic indicating which specific verified third parties are to request release of the encrypted data before the data storage system will release the encrypted data.

7. The method of claim 1, wherein the verifiable secret sharing scheme performs the verification without opening or looking at the encrypted data.

8. A computer system comprising the following:

one or more processors;

system memory;

one or more computer-readable storage devices having stored thereon computer- executable instructions that, when executed by the one or more processors, causes the computing system to perform a method for allowing a user to store encrypted, third-party-accessible data in a data store, the method comprising the following;

receiving at a data storage system encrypted data from a user, wherein the encrypted data was encrypted prior to having been received and the encryption having been completed prior to being received by the data storage system;

storing the received encrypted data in the data storage system according to a predefined policy, the encryption preventing the storage system from decrypting the encrypted data, the policy allowing the encrypted data to be released upon receiving at least a threshold number of requests from verified third parties, wherein a received encrypted key is stored as a plurality of shares, the shares being mathematical transformations of the user'"'"'s private key, and wherein each share is provided to one of the verified third parties;

the data storage system implementing a verifiable secret sharing scheme to verify that the encrypted data can be decrypted without the data storage system having the ability to decrypt the encrypted data;

receiving a request from the user requesting the user'"'"'s encrypted data; and

the data storage system providing the user'"'"'s stored encrypted data based at least in part on the user'"'"'s request.

9. The system of claim 8, wherein each verified third party publishes their own public keys and encrypts their share of the encrypted key using their published public key, such that the verified third party shares encrypted according to third parties'"'"' public keys are stored in the data storage system.

10. The system of claim 8, wherein one or more of the trusted third parties are themselves users of the system of claim 8, and wherein the trusted third party system users'"'"' own public keys are escrowed to other trusted third parties in the system.