Network-based client side encryption

Patent metadata

Field	Value
Publication number	US-10298576-B2
Application number	US-201715727018-A
Country	US
Kind code	B2
Filing date	Oct 6, 2017
Priority date	Feb 12, 2015
Publication date	May 21, 2019
Grant date	May 21, 2019

Abstract

A device may provide an upload request to upload a file. The device may receive, based on the upload request, a unique identifier associated with the device. The device may obtain a file key for encrypting the file and a security key for encrypting the file key. The security key may be obtained based on the unique identifier. The device may encrypt the file, using the file key, to create an encrypted file. The device may encrypt the file key, using the security key, to create an encrypted file key. The device may provide the encrypted file and the encrypted file key for storage by a storage device.

First claim

What is claimed is:

1. A device, comprising:
a memory; and
one or more processors to:
encrypt, using a file key, a file to create an encrypted file;
receive, from a first other device, a unique identifier associated with the device;
encrypt, using a security key generated based on the unique identifier, the file key to create an encrypted file key;
provide, to the first other device, the encrypted file key for storage at the first other device;
delete the file key based on encrypting the file key;
provide, to a second other device, a download request to download the encrypted file key;
receive, from the first other device and based on the download request, the encrypted file key;
decrypt, using the security key, the encrypted file key to recover the file key; and
decrypt, based on recovering the file key, the encrypted file using the file key to recover the file.

2. The device of claim 1 , where the one or more processors are further to:
provide an upload request to upload the encrypted file; and
where the one or more processors, when receiving the unique identifier, are to:
receive the unique identifier based on providing the upload request.

3. The device of claim 1 , where the one or more processors, when receiving the unique identifier, are to:
receive the unique identifier via a secure session.

4. The device of claim 1 , where the one or more processors, when receiving the unique identifier, are to:
receive the unique identifier based on the device being authenticated.

5. The device of claim 1 , where the security key is generated based on a hashing algorithm being applied to the unique identifier to create a hash value,
the hash value being utilized as the security key.

6. The device of claim 1 , where the one or more processors are to:
store the security key locally on the device.

7. A method, comprising:
encrypting, by a device and using a file key, a file to create an encrypted file;
receiving, by the device and from a first other device, a unique identifier associated with the device;
encrypting, by the device and using a security key generated based on the unique identifier, the file key to create an encrypted file key;
providing, by the device and to the first other device, the encrypted file key for storage at the first other device;
deleting, by the device, the file key based on encrypting the file key;
providing, by the device and to a second other device, a download request to download the encrypted file key;
receiving, from the first other device and based on the download request, the encrypted file key;
decrypting, by the device and using the security key, the encrypted file key to recover the file key; and
decrypting, by the device and based on recovering the file key, the encrypted file using the file key to recover the file.

8. The method of claim 7 , further comprising:
deleting the security key based on encrypting the file key; and
re-generating the security key based on obtaining the encrypted file key.

9. The method of claim 7 , further comprising:
storing the security key locally.

10. The method of claim 7 , where the download request is provided by a different application than an application for providing an upload request to upload the encrypted file.

11. The method of claim 7 , where receiving, from the first other device and based on the download request, the encrypted file key comprises:
receiving, from the first other device, the encrypted file based on the download request being authenticated.

12. The method of claim 7 , where the security key is received from a third other device.

13. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to:
encrypt, using a file key, a file to create an encrypted file;
receive, from a first other device, a unique identifier;
encrypt, using a security key generated based on the unique identifier, the file key to create an encrypted file key;
provide, to the first other device, the encrypted file key for storage at the first other device;
delete the file key based on encrypting the file key;
provide, to a second other device, a download request to download the encrypted file key;
receive, from the first other device and based on the download request, the encrypted file key;
decrypt, using the security key, the encrypted file key to recover the file key; and
decrypt, based on recovering the file key, the encrypted file using the file key to recover the file.

14. The non-transitory computer-readable medium of claim 13 , where an authentication request for the first other device is generated based on the download request.

15. The non-transitory computer-readable medium of claim 13 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
provide an update request to a device that stores the encrypted file; and
obtain the encrypted file key based on providing the update request.

16. The non-transitory computer-readable medium of claim 13 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
provide an upload request to a network device,
the upload request being a request to upload the encrypted file, and
the upload request causing the network device to determine the unique identifier; and

where the one or more instructions, that cause the one or more processors to receive, from the first other device, the unique identifier, cause the one or more processors to:
receive, from the first other device, the unique identifier based on providing the upload request to the network device.

17. The non-transitory computer-readable medium of claim 16 , where the upload request causes the network device to provide an authentication request to the first other device to authenticate the device.

18. The device of claim 1 , where the unique identifier includes at least one of:
a mobile directory number (MDN),
an international mobile subscriber identity (IMSI),
an international mobile station equipment identity (IMEI), or
a mobile equipment identifier (MEID).

19. The method of claim 7 , where providing, to the first other device, the encrypted file key further comprises:
providing, to the first other device, the encrypted file.

20. The non-transitory computer-readable medium of claim 13 , where the one or more instructions, that cause the one or more processors to receive, from the first other device, the encrypted file key, further cause the one or more processors to:
receive, from the first other device, the encrypted file.

Assignees

• Verizon Patent & Licensing Inc

Inventors

• Bao Guanqun
• Sharma Manish
• Blong Devin
• Flores Kevin
• Chaudhary Tushar
• Gupta Gaurav

Classifications

• H04W12/06

  Authentication · CPC title

• H04L63/0876 Primary

  based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title

• G06F21/602 Primary

  Providing cryptographic facilities or services · CPC title

• H04W12/04

  Key management, e.g. using generic bootstrapping architecture [GBA] · CPC title

• H04W12/02

  Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title