# US 2011/0258438 A1 · System and Method for Providing Different Levels of Key Security for Controlling Access to Secured Items

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

- Number: US 2011/0258438 A1
- Document ID: US20110258438A1
- Status: Published application
- Kind: A1
- Application number: 13/079,583
- Filed: 2011-04-04
- Published: 2011-10-20
- Earliest claimed: 2002-02-12
- Assignees: Guardian Data Storage, LLC
- Inventors: Hal S. HILDEBRAND
- Web page: https://patentgrep.com/patent/US20110258438A1

## CPC

- H04L 63/04: {for providing a confidential data exchange among entities communicating through data packet networks}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

With files secured by encryption techniques, keys are often required to gain access to the secured files. Techniques for providing and using multiple levels of keystores for securing the keys are disclosed. The keystores store keys that are needed by users in order to access secured files. The different levels of keystores offer compromises between security and flexibility/ease of use.

## Claims

### Claim at position 1

-48. (canceled)

### Claim 49

A method comprising:
receiving a request to access a header of a secured file, wherein the header comprises a file key, at least the header of the secured file is configured to be decrypted by a user key, and a data portion of the secured file is configured to be decrypted by the file key;
obtaining the user key from a storage location corresponding to a level of security of the user key, wherein the level of security is defined in a policy based on a degree of access associated with the user key; and
decrypting the header using the user key to produce the file key.

### Claim 50 (depends on 49)

The method of claim 49, wherein obtaining the user key from the storage location comprises obtaining the user key from a central server keystore corresponding to a high level of security of the user key.

### Claim 51 (depends on 49)

The method of claim 49, wherein obtaining the user key from the storage location comprises obtaining the user key from a local server keystore corresponding to an intermediate level of security of the user key.

### Claim 52 (depends on 49)

The method of claim 49, wherein obtaining the user key from the storage location comprises obtaining the user key from a user keystore corresponding to a low level of security of the user key.

### Claim 53 (depends on 49)

The method of claim 49, wherein the policy based on the degree of access provided by the user key comprises a requirement that the user key be obtained from a particular storage location based on the level of security of the user key.

### Claim 54 (depends on 49)

The method of claim 49, wherein obtaining the user key from the storage location comprises obtaining the user key from the storage location corresponding to a user group associated with the user key.

### Claim 55 (depends on 49)

The method of claim 49, wherein obtaining the user key from the storage location comprises obtaining the user key from a persistent storage location that is mutually exclusive from one or more additional persistent storage locations.

### Claim 56 (depends on 55)

The method of claim 55, wherein the user key is further available at a non-persistent storage location.

### Claim 57 (depends on 49)

The method of claim 49, wherein obtaining the user key from the storage location comprises providing the header to a central server keystore configured to obtain the user key and decrypt the header using the user key.

### Claim 58 (depends on 57)

The method of claim 57, further comprising:
receiving the file key, decrypted from the header, from the central server keystore.

### Claim 59 (depends on 49)

The method of claim 49, further comprising:
caching the user key at a local cache.

### Claim 60 (depends on 59)

The method of claim 59, further comprising:
clearing the local cache after a predetermined duration.

### Claim 61

A computer-readable medium having instructions stored thereon, execution of which, by a computing device, causes the computing device to perform operations comprising:
receiving a request to access a header of a secured file, wherein the header comprises a file key, at least the header of the secured file is configured to be decrypted by a user key, and a data portion of the secured file is configured to be decrypted by the file key;
obtaining the user key from a storage location corresponding to a level of security of the user key, wherein the level of security is defined in a policy based on a degree of access associated with the user key; and
decrypting the header using the user key to produce the file key.

### Claim 62 (depends on 61)

The computer-readable medium of claim 61, wherein obtaining the user key from the storage location comprises obtaining the user key from a central server keystore corresponding to a high level of security of the user key.

### Claim 63 (depends on 61)

The computer-readable medium of claim 61, wherein obtaining the user key from the storage location comprises obtaining the user key from a local server keystore corresponding to an intermediate level of security of the user key.

### Claim 64 (depends on 61)

The computer-readable medium of claim 61, wherein obtaining the user key from the storage location comprises obtaining the user key from a user keystore corresponding to a low level of security of the user key.

### Claim 65 (depends on 61)

The computer-readable medium of claim 61, wherein the policy based on the degree of access provided by the user key comprises a requirement that the user key be obtained from a particular storage location based on the level of security of the user key.

### Claim 66 (depends on 61)

The computer-readable medium of claim 61, wherein obtaining the user key from the storage location comprises obtaining the user key from the storage location corresponding to a user group associated with the user key.

### Claim 67 (depends on 61)

The computer-readable medium of claim 61, wherein obtaining the user key from the storage location comprises obtaining the user key from a persistent storage location that is mutually exclusive from one or more additional persistent storage locations.

### Claim 68 (depends on 67)

The computer-readable medium of claim 67, wherein the user key is further available at a non-persistent storage location.

### Claim 69 (depends on 61)

The computer-readable medium of claim 61, wherein obtaining the user key from the storage location comprises providing the header to a central server keystore configured to obtain the user key and decrypt the header using the user key.

### Claim 70 (depends on 69)

The computer-readable medium of claim 69, the operations further comprising:
receiving the file key, decrypted from the header, from the central server keystore.

### Claim 71 (depends on 61)

The computer-readable medium of claim 61, the operations further comprising:
caching the user key at a local cache.

### Claim 72 (depends on 71)

The computer-readable medium of claim 71, the operations further comprising:
clearing the local cache after a predetermined duration.

### Claim 73

A system comprising:
a memory storing:
a receiving module configured to receive a request to access a header of a secured file, wherein the header comprises a file key, at least the header of the secured file is configured to be decrypted by a user key, and a data portion of the secured file is configured to be decrypted by the file key,
an obtaining module configured to obtain the user key from a storage location corresponding to a level of security of the user key, wherein the level of security is defined in a policy based on a degree of access associated with the user key, and
a decrypting module configured to decrypt the header using the user key to produce the file key; and
one or more processors configured to process the modules.

### Claim 74 (depends on 73)

The system of claim 73, wherein obtaining the user key from the storage location comprises obtaining the user key from a central server keystore corresponding to a high level of security of the user key.

### Claim 75 (depends on 73)

The system of claim 73, wherein obtaining the user key from the storage location comprises obtaining the user key from a local server keystore corresponding to an intermediate level of security of the user key.

### Claim 76 (depends on 73)

The system of claim 73, wherein obtaining the user key from the storage location comprises obtaining the user key from a user keystore corresponding to a low level of security of the user key.

### Claim 77 (depends on 73)

The system of claim 73, wherein the policy based on the degree of access provided by the user key comprises a requirement that the user key be obtained from a particular storage location based on the level of security of the user key.

### Claim 78 (depends on 73)

The system of claim 73, wherein obtaining the user key from the storage location comprises obtaining the user key from the storage location corresponding to a user group associated with the user key.

### Claim 79 (depends on 73)

The system of claim 73, wherein obtaining the user key from the storage location comprises obtaining the user key from a persistent storage location that is mutually exclusive from one or more additional persistent storage locations.

### Claim 80 (depends on 79)

The system of claim 79, wherein the user key is further available at a non-persistent storage location.

### Claim 81 (depends on 73)

The system of claim 73, wherein obtaining the user key from the storage location comprises providing the header to a central server keystore configured to obtain the user key and decrypt the header using the user key.

### Claim 82 (depends on 81)

The system of claim 81, further comprising:
a second receiving module configured to receive the file key, decrypted from the header, from the central server keystore.

### Claim 83 (depends on 73)

The system of claim 73, further comprising:
a caching module configured to cache the user key at a local cache.

### Claim 84 (depends on 83)

The system of claim 83, further comprising:
a clearing module configured to clear the local cache after a predetermined duration.
