# US 2015/0149772 A1 · Secure access for encrypted data

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

- Number: US 2015/0149772 A1
- Document ID: US20150149772A1
- Status: Published application
- Kind: A1
- Application number: 14/087,045
- Filed: 2013-11-22
- Published: 2015-05-28
- Earliest claimed: 2013-11-22
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Nicholas Read Leavy; Venkata Krishna Sashank Dara
- Web page: https://patentgrep.com/patent/US20150149772A1

## CPC

- H04L 9/0822: {using key encryption key}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- 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)}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 2209/24: Key scheduling, i.e. generating round keys or sub-keys for block 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)

## Abstract

Embodiments generally provide techniques for managing data security. One embodiment includes providing, at a client system, an encrypted private key that can be decrypted using a locker key. Encrypted data is received from a remote system, and embodiment determine that the received encrypted data can be decrypted using a private key recovered by decrypting the encrypted private key. A request is transmitted to the remote system for the locker key corresponding to the encrypted private key, and the requested locker key is received from the remote system. Embodiments decrypt the encrypted private key using the received locker key to recover the private key, and decrypt the encrypted data, using the private key.

## Claims

### Claim 1

A method, comprising:
providing, at a client system, an encrypted private key that can be decrypted using a locker key;
receiving encrypted data from a remote system;
determining that the received encrypted data can be decrypted using a private key recovered by decrypting the encrypted private key;
transmitting a request to the remote system for the locker key corresponding to the encrypted private key;
receiving, from the remote system, the requested locker key;
decrypting the encrypted private key using the received locker key to recover the private key; and
decrypting the encrypted data, using the private key.

### Claim 2

The method of claim, wherein the private key is stored as a value in a key-value pair in a web browser on the client system.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
receiving a web page containing a JavaScript program that, when executed, performs the operations of transmitting, receiving, decrypting the encrypted private key and decrypting the encrypted data.

### Claim 4 (depends on 1)

The method of claim 1, wherein the remote system is configured to authenticate and authorize the client system, responsive to receiving the request and before transmitting the requested locker key to the client system.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
upon decrypting the encrypted data, purging the private key.

### Claim 6 (depends on 1)

The method of claim 1, wherein the remote system comprises a cloud node of a cloud computing environment, configured to store the encrypted data on a storage device within the cloud computing environment.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving the private key over a secure network session;
encrypting the private key, using a second key; and
storing the encrypted private key.

### Claim 8 (depends on 1)

The method of claim 1, wherein the transmitted request includes a second key used to decrypt the locker key at the remote system.

### Claim 9

A method, comprising:
providing an encrypted locker key, wherein a locker key can be recovered by decrypting the encrypted locker key using a first key;
transmitting encrypted data to a client system, wherein the encrypted data can be decrypted using a private key;
receiving a request for the encrypted locker key, the request specifying the first key;
decrypting the encrypted locker key using the first key to recover the locker key; and
transmitting the locker key to the client system, wherein the client system is configured to use the locker key to decrypt a private key and further configured to use the private key to decrypt the encrypted data.

### Claim 10 (depends on 9)

The method of claim 9, wherein the client system is configured store the encrypted private key as a value in a key-value pair in a web browser on the client system.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
transmitting a web page to the client system, wherein the web page includes a JavaScript program that, when executed, performs an operation of transmitting the request, receiving the decrypted locker key, decrypting the encrypted private key using the received locker key to recover a private key, and decrypting the encrypted data using the private key.

### Claim 12 (depends on 9)

The method of claim 9, further comprising:
performing an operation for authenticating and authorizing the client system, responsive to receiving the request and before transmitting the locker key to the client system.

### Claim 13 (depends on 9)

The method of claim 9, wherein the client system is further configured to purge the private key, upon decrypting the encrypted data.

### Claim 14 (depends on 9)

The method of claim 9, further comprising:
establishing a secure network session with the client system; and
transmitting the private key over the secure network session,
wherein the client system is configured to encrypt the private key, using a second key, and to store the encrypted private key.

### Claim 15

A method, comprising:
receiving, within a browser application of a client system, web content from a remote system;
receiving, within the browser application of the client system, encrypted data from the remote system; and
executing program code within the received web content to perform an operation, comprising:
determining that the encrypted data can only be decrypting using both first key data stored on the client system and second key data stored on the remote system;
retrieving the second key data from the remote system; and
decrypting the encrypted data, using both the first key data and the second key data.

### Claim 16 (depends on 15)

The method of claim 15, wherein the first key data comprises an encrypted private key stored as a value in a key-value pair in the web browser on the client system.

### Claim 17 (depends on 16)

The method of claim 16, wherein decrypting the encrypted data, using both the first key data and the second key data, further comprises:
decrypting the encrypted private key on the client system using the retrieved second key data to recover a private key; and
decrypting the encrypted data using the private key.

### Claim 18 (depends on 17)

The method of claim 17, the operation further comprising:
upon decrypting the encrypted data, purging the private key.

### Claim 19 (depends on 15)

The method of claim 15, wherein the remote system is configured to authenticate and authorize the client system, responsive to receiving request for the second key data, and prior to transmitting the second key data to the client system.

### Claim 20 (depends on 15)

The method of claim 15, wherein the remote system comprises a cloud node of a cloud computing environment, configured to store the second key data on a storage device within the cloud computing environment.
