# US 2013/0254558 A1 · Systems and methods for secure third-party data storage

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254558 A1
- Document ID: US20130254558A1
- Status: Published application
- Kind: A1
- Application number: 13/787,757
- Filed: 2013-03-06
- Published: 2013-09-26
- Earliest claimed: 2012-03-26
- Assignees: Symantec Corporation
- Applicants: Symantec Corporation
- Inventors: Walter Bogorad
- Web page: https://patentgrep.com/patent/US20130254558A1

## CPC

- H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- G06F 21/6209: {to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- H04L 9/0822: {using key encryption key}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 63/0478: {applying multiple layers of encryption, e.g. nested tunnels or encrypting the content with a first key and then with at least a second key (cryptographic mechanisms or cryptographic arrangements using a plurality of keys or algorithms H04L9/14)}
- G06F 2221/2107: File encryption
- H04L 2463/062: applying encryption of the keys
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A computer-implemented method for secure third-party data storage may include 1) identifying, at a server-side computing device, a request from a client system to access an encrypted file stored under a user account, 2) identifying, in response to the request, an asymmetric key pair designated for the user account that includes an encryption key and a decryption key that has been encrypted with a client-side key, 3) receiving, from the client system, the client-side key, 4) decrypting the decryption key with the client-side key, and 5) using the decryption key to access an unencrypted version of the encrypted file. Various other methods, systems, and computer-readable media are also disclosed.

## Claims

### Claim 1

A computer-implemented method for secure third-party data storage, at least a portion of the method being performed by a server-side computing device comprising at least one processor, the method comprising:
identifying, at the server-side computing device, a request from a client system to access an encrypted file stored under a user account, wherein the requested access requires decryption of the encrypted file;
identifying, in response to the request, an asymmetric key pair designated for the user account that comprises an encryption key and a decryption key, wherein the decryption key has been encrypted with a client-side key that is not stored on the server-side computing device;
receiving, at the server-side computing device from the client system, the client-side key;
temporarily storing the client-side key on the server-side computing device;
decrypting, at the server-side computing device, the decryption key with the client-side key;
using the decryption key to access an unencrypted version of the encrypted file;
upon accessing the unencrypted version of the encrypted file, removing the client-side key from the server-side computing device.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein using the decryption key to access the unencrypted version of the encrypted file comprises:
identifying a file key used to encrypt the encrypted file, wherein the file key is encrypted with the encryption key;
decrypting the file key with the decryption key;
decrypting the encrypted file with the file key.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein:
accessing the encrypted file comprises providing access to the unencrypted version of the encrypted file to an additional user account;
an additional asymmetric key pair is designated for the additional user account, the additional asymmetric key pair comprising an additional encryption key and an additional decryption key that has been encrypted with an additional client-side key.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3, wherein providing access to the unencrypted version of the encrypted file to the additional user account comprises:
identifying a file key used to encrypt the encrypted file, wherein the file key is encrypted with the encryption key;
decrypting the file key with the decryption key;
encrypting a copy of the file key with the additional encryption key.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein accessing the encrypted file comprises transmitting the unencrypted version of the encrypted file to the client system.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein using the decryption key to access the unencrypted version of the encrypted file comprises generating metadata describing the unencrypted version of the encrypted file.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein generating the metadata describing the unencrypted version of the encrypted file comprises at least one of:
performing a security scan on the unencrypted version of the encrypted file;
indexing the unencrypted version of the encrypted file based on content within the unencrypted version of the encrypted file;
generating a preview of the unencrypted version of the encrypted file based on content within the unencrypted version of the encrypted file.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, further comprising:
receiving the unencrypted version of the encrypted file from the client system;
generating the encrypted file by:
generating a file key based on at least one characteristic of the unencrypted version of the encrypted file;
encrypting the unencrypted version of the encrypted file with the file key;
encrypting the file key with the encryption key.

### Claim 9 (depends on 8)

The computer-implemented method of claim 8, further comprising deduplicating the encrypted file with an additional encrypted file that is encrypted with the file key.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein temporarily storing the client-side key on the server-side computing device comprises storing the client-side key in volatile memory on the server-side computing device without storing the client-side key in non-volatile memory on the server-side computing device.

### Claim 11 (depends on 1)

The computer-implemented method of claim 1, further comprising:
identifying an additional user account designated to access the unencrypted version of the encrypted file, wherein an additional asymmetric key pair is designated for the additional user account, the additional asymmetric key pair comprising an additional encryption key and an additional decryption key that has been encrypted with an additional client-side key;
encrypting the decryption key with the additional encryption key.

### Claim 12 (depends on 11)

The computer-implemented method of claim 11, further comprising:
identifying an additional request from an additional client system to further access the encrypted file via the additional user account, wherein the additional requested access requires decryption of the encrypted file;
decrypting the decryption key with the additional decryption key;
using the decryption key to access the unencrypted version of the encrypted file via the additional user account.

### Claim 13 (depends on 1)

The computer-implemented method of claim 1, wherein using the decryption key to access the unencrypted version of the encrypted file comprises:
identifying an additional asymmetric key pair designated for a plurality of user accounts comprising the user account, the additional asymmetric key pair comprising an additional encryption key and an additional decryption key that has been encrypted with the encryption key;
decrypting the additional decryption key with the decryption key;
identifying a file key used to encrypt the encrypted file, wherein the file key is encrypted with the additional encryption key;
decrypting the file key with the additional decryption key;
decrypting the encrypted file with the file key.

### Claim 14

A system for secure third-party data storage, the system comprising:
an identification module programmed to identify, at a server-side computing device, a request from a client system to access an encrypted file stored under a user account, wherein the requested access requires decryption of the encrypted file;
a key module programmed to identify, in response to the request, an asymmetric key pair designated for the user account that comprises an encryption key and a decryption key, wherein the decryption key has been encrypted with a client-side key that is not stored on the server-side computing device;
a receiving module programmed to:
receive, at the server-side computing device from the client system, the client-side key;
temporarily store the client-side key on the server-side computing device;
a decryption module programmed to decrypt, at the server-side computing device, the decryption key with the client-side key;
an access module programmed to:
use the decryption key to access an unencrypted version of the encrypted file;
upon accessing the unencrypted version of the encrypted file, remove the client-side key from the server-side computing device;
at least one processor configured to execute the identification module, the key module, the receiving module, the decryption module, and the access module.

### Claim 15 (depends on 14)

The system of claim 14, wherein the access module is programmed to use the decryption key to access the unencrypted version of the encrypted file by:
identifying a file key used to encrypt the encrypted file, wherein the file key is encrypted with the encryption key;
decrypting the file key with the decryption key;
decrypting the encrypted file with the file key.

### Claim 16 (depends on 14)

The system of claim 14, wherein:
the access module is programmed to access the encrypted file by providing access to the unencrypted version of the encrypted file to an additional user account;
an additional asymmetric key pair is designated for the additional user account, the additional asymmetric key pair comprising an additional encryption key and an additional decryption key that has been encrypted with an additional client-side key.

### Claim 17 (depends on 16)

The system of claim 16, wherein the access module is programmed to provide access to the unencrypted version of the encrypted file to the additional user account by:
identifying a file key used to encrypt the encrypted file, wherein the file key is encrypted with the encryption key;
decrypting the file key with the decryption key;
encrypting a copy of the file key with the additional encryption key.

### Claim 18 (depends on 14)

The system of claim 14, wherein the access module is programmed to access the encrypted file by transmitting the unencrypted version of the encrypted file to the client system.

### Claim 19 (depends on 14)

The system of claim 14, wherein the access module is programmed to use the decryption key to access the unencrypted version of the encrypted file by generating metadata describing the unencrypted version of the encrypted file.

### Claim 20

A non-transitory computer-readable-storage medium comprising one or more computer-executable instructions that, when executed by at least one processor of a server-side computing device, cause the server-side computing device to:
identify, at the server-side computing device, a request from a client system to access an encrypted file stored under a user account, wherein the requested access requires decryption of the encrypted file;
identify, in response to the request, an asymmetric key pair designated for the user account that comprises an encryption key and a decryption key, wherein the decryption key has been encrypted with a client-side key that is not stored on the server-side computing device;
receive, at the server-side computing device from the client system, the client-side key;
temporarily store the client-side key on the server-side computing device;
decrypt, at the server-side computing device, the decryption key with the client-side key;
use the decryption key to access an unencrypted version of the encrypted file;
upon accessing the unencrypted version of the encrypted file, remove the client-side key from the server-side computing device.
