# US 2015/0039886 A1 · Secure application access system

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

- Number: US 2015/0039886 A1
- Document ID: US20150039886A1
- Status: Published application
- Kind: A1
- Application number: 14/101,326
- Filed: 2013-12-09
- Published: 2015-02-05
- Earliest claimed: 2013-08-01
- Assignees: Bitglass, Inc.
- Applicants: Bitglass, Inc.
- Inventors: Anurag Kahol; Anoop Kumar Bhattacharjya; Balas Natarajan Kausik
- Web page: https://patentgrep.com/patent/US20150039886A1

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/10: Protecting distributed programs or content, e.g. vending or licensing of copyrighted material (protection in video systems or pay television H04N7/16) {; Digital rights management [DRM]}
- G06F 21/6227: {where protection concerns the structure of data, e.g. records, types, queries}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 63/0471: {applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding}
- H04L 63/0272: {Virtual private networks}
- H04L 2209/76: Proxy, i.e. using intermediary entity to perform cryptographic operations
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A proxy server creates an index of keywords, receives at least a portion of a file, and, when a keyword in the index is encountered in the at least a portion of the file as the at least a portion of the file is being encrypted, associates in the index an encrypted record location identifier with the encountered keyword. The proxy server receives a search query and uses the keyword index to retrieve encrypted records from the server. The encrypted records are decrypted and sent as search results in response to the search query.

## Claims

### Claim 1

A method, comprising:
receiving, over a network, by a proxy server, a file to be encrypted;
creating, by the proxy server, an index of keywords;
encrypting, by the proxy server, the file, when a keyword in the index is encountered in the file as the file is being encrypted, associating in the index a substring of encrypted data extracted from the encrypted file in which the keyword was encountered with the encountered keyword.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein the encryption step encrypts the file as encrypted data records, and wherein the sub string of encrypted data is associated with an encrypted data record.

### Claim 3 (depends on 1)

The method as recited in claim 1, further comprising:
inserting a unique identifier string in the encrypted file corresponding to a location where the keyword was encountered.

### Claim 4 (depends on 1)

The method as recited in claim 1, further comprising:
sending the encrypted file to a second device for storage.

### Claim 5 (depends on 4)

The method as recited in claim 4, wherein the second device is a server.

### Claim 6

(canceled)

### Claim 7 (depends on 1)

The method as recited in claim 1, wherein the index is created for a particular cloud application program.

### Claim 8 (depends on 1)

The method as recited in claim 1, wherein the index is created for a particular user.

### Claim 9 (depends on 1)

The method as recited in claim 1, further comprising:
receiving, by the proxy server, a search query, the search query comprising one or more keywords;
matching the one or more keywords with one or more keywords in the index;
in response to a match of a keyword in the index, issuing a search query to a second device, the search query including a substring of encrypted data associated with the matched keyword.

### Claim 10 (depends on 9)

The method as recited in claim 9, further comprising:
receiving, by the proxy server, a search result set from the second device, the search result set including at least one encrypted record;
decrypting the at least one encrypted record;
including the decrypted at least one encrypted record in a second search result set;
sending the second search result set to a third device.

### Claim 11

An apparatus, comprising:
a subsystem at a proxy server, implemented at least partially in hardware, that receives, over a network, a file to be encrypted;
a subsystem at the proxy server, implemented at least partially in hardware, that creates an index of keywords;
an encryption subsystem at the proxy server, implemented at least partially in hardware, that encrypts the file, when a keyword in the index is encountered in the file as the file is being encrypted, associates in the index a substring of encrypted data extracted from the encrypted file in which the keyword was encountered with the encountered keyword.

### Claim 12 (depends on 11)

The apparatus as recited in claim 11, wherein the encryption subsystem encrypts the file as encrypted data records, and wherein the substring of encrypted data is associated with an encrypted data record.

### Claim 13 (depends on 11)

The apparatus as recited in claim 11, further comprising:
a subsystem at the proxy server, implemented at least partially in hardware, that inserts a unique identifier string in the encrypted file corresponding to a location where the keyword was encountered.

### Claim 14 (depends on 11)

The apparatus as recited in claim 11, further comprising:
a subsystem at the proxy server, implemented at least partially in hardware, that sends the encrypted file to a second device for storage.

### Claim 15 (depends on 14)

The apparatus as recited in claim 14, wherein the second device is a server.

### Claim 16

(canceled)

### Claim 17 (depends on 11)

The apparatus as recited in claim 11, wherein the index is created for a particular cloud application program.

### Claim 18 (depends on 11)

The apparatus as recited in claim 11, wherein the index is created for a particular user.

### Claim 19 (depends on 11)

The apparatus as recited in claim 11, further comprising:
a subsystem at the proxy server, implemented at least partially in hardware, that receives a search query, the search query comprising one or more keywords;
a subsystem at the proxy server, implemented at least partially in hardware, that matches the one or more keywords with one or more keywords in the index;
a subsystem at the proxy server, implemented at least partially in hardware, that in response to a match of a keyword in the index, issues a search query to a second device, the search query including a substring of encrypted data associated with the matched keyword.

### Claim 20 (depends on 19)

The apparatus as recited in claim 19, further comprising:
a subsystem at the proxy server, implemented at least partially in hardware, that receives a search result set from the second device, the search result set including at least one encrypted record;
a subsystem at the proxy server, implemented at least partially in hardware, that decrypts the at least one encrypted record;
a subsystem at the proxy server, implemented at least partially in hardware, that includes the decrypted at least one encrypted record in a second search result set;
a subsystem at the proxy server, implemented at least partially in hardware, that sends the second search result set to a third device.

### Claim 21

A non-transitory computer readable medium, storing software instructions, which when executed by one or more processors cause performance of:
receiving, over a network, by a proxy server, a file to be encrypted;
creating, by the proxy server, an index of keywords;
encrypting, by the proxy server, the file, when a keyword in the index is encountered in the file as the file is being encrypted, associating in the index a substring of encrypted data extracted from the encrypted file in which the keyword was encountered with the encountered keyword.

### Claim 22 (depends on 21)

The non-transitory computer readable medium as recited in claim 21, wherein the encryption step encrypts the file as encrypted data records, and wherein the substring of encrypted data is associated with an encrypted data record.

### Claim 23 (depends on 21)

The non-transitory computer readable medium as recited in claim 21, further comprising:
inserting a unique identifier string in the encrypted file corresponding to a location where the keyword was encountered.

### Claim 24 (depends on 21)

The non-transitory computer readable medium as recited in claim 21, further comprising:
sending the encrypted file to a second device for storage.

### Claim 25 (depends on 24)

The non-transitory computer readable medium as recited in claim 24, wherein the second device is a server.

### Claim 26

(canceled)

### Claim 27 (depends on 21)

The non-transitory computer readable medium as recited in claim 21, wherein the index is created for a particular cloud application program.

### Claim 28 (depends on 21)

The non-transitory computer readable medium as recited in claim 21, wherein the index is created for a particular user.

### Claim 29 (depends on 21)

The non-transitory computer readable medium as recited in claim 21, further comprising:
receiving, by the proxy server, a search query, the search query comprising one or more keywords;
matching the one or more keywords with one or more keywords in the index;
in response to a match of a keyword in the index, issuing a search query to a second device, the search query including a substring of encrypted data associated with the matched keyword.

### Claim 30 (depends on 29)

The non-transitory computer readable medium as recited in claim 29, further comprising:
receiving, by the proxy server, a search result set from the second device, the search result set including at least one encrypted record;
decrypting the at least one encrypted record;
including the decrypted at least one encrypted record in a second search result set;
sending the second search result set to a third device.
