# US 2021/0334412 A1 · Secured file storage

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

- Number: US 2021/0334412 A1
- Document ID: US20210334412A1
- Status: Published application
- Kind: A1
- Application number: 16/858,115
- Filed: 2020-04-24
- Published: 2021-10-28
- Earliest claimed: 2020-04-24
- Assignees: Wells Fargo Bank, N.A.
- Applicants: Wells Fargo Bank, N.A.
- Inventors: Chris Theodore Kalaboukis; Joon Maeng; Ramanathan Ramanathan; Abhijit Rao; Abhijit Shetti
- Web page: https://patentgrep.com/patent/US20210334412A1

## CPC

- G06F 21/572: {Secure firmware programming, e.g. of basic input output system [BIOS]}
- G06F 21/78: to assure secure storage of data (address-based protection against unauthorised use of memory G06F12/14; record carriers for use with machines and with at least a part designed to carry digital markings G06K19/00)
- G06F 16/182: Distributed file systems
- G06F 2221/2107: File encryption
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods may generally be used to securely store an executable file or to compile a securely stored executable file. An example method may include receiving an executable file for long-term storage, segmenting the executable file into a plurality of file segments, encrypting a file segment of the plurality of file segments, storing the plurality of file segments, and retrieving the file segment based on a segment identity for the file segment. The file segment may be output, for example to a requesting device.

## Claims

### Claim 1

A method of securely storing data comprising:
receiving an executable file for long-term storage;
segmenting the executable file into a plurality of file segments;
encrypting a file segment of the plurality of file segments;
separately storing the plurality of file segments in respectively different memory devices; and
storing a mapping of segment identities of the plurality of file segments to storage locations.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
identifying that an encryption technique used to perform the encrypting has been broken;
decrypting the file segment; and
re-encrypting the file segment using a different encryption technique.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
identifying that a stronger encryption technique is available for encrypting the at least one of the plurality of file segments;
decrypting the file segment; and
re-encrypting the file segment using the stronger encryption technique.

### Claim 4 (depends on 1)

The method of claim 1, further comprising identifying a change in storage location of the file segment to a new storage location and, in response, updating the mapping of the respective segment identity of the file segment to the new storage location.

### Claim 5 (depends on 1)

The method of claim 1, further comprising identifying that a storage location of the file segment is compromised, and, in response, changing a storage location of the file segment.

### Claim 6 (depends on 1)

The method of claim 1, further comprising encrypting a second file segment of the plurality of file segments with a second encryption technique that differs from a first encryption technique used to encrypt the file segment.

### Claim 7 (depends on 1)

The method of claim 1, wherein the executable file is configured to be unexecutable without being compiled from all file segments of the plurality of file segments.

### Claim 8 (depends on 1)

The method of claim 1, wherein encrypting the file segment includes encrypting all file segments of the plurality of file segments using a homomorphic encryption technique.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
receiving a request, from a device, for the file segment of the plurality of file segments, the request including a respective segment identity of the file segment;
retrieving the file segment based on the mapping and the segment identity; and
sending the file segment to the device.

### Claim 10 (depends on 9)

The method of claim 9, wherein sending the file segment to the device includes sending current encryption information for the file segment.

### Claim 11

A system of securely storing data comprising:
processor circuitry; and
memory, including instructions, which when executed by the processing circuitry, causes the processing circuitry to perform operations to:
receive an executable file for long-term storage;
segment the executable file into a plurality of file segments;
encrypt a file segment of the plurality of file segments;
separately send for storage, in respectively different memory devices, the plurality of file segments; and
store, in the memory, a mapping of segment identities of the plurality of file segments to storage locations.

### Claim 12 (depends on 11)

The system of claim 11, wherein the instructions further cause the processor to:
identify that an encryption technique used to perform the encrypting has been broken;
decrypt the file segment; and
re-encrypt the file segment using a different encryption technique.

### Claim 13 (depends on 11)

The system of claim 11, wherein the instructions further cause the processor to:
identify that a stronger encryption technique is available for encrypting the at least one of the plurality of file segments;
decrypt the file segment; and
re-encrypt the file segment using the stronger encryption technique.

### Claim 14 (depends on 11)

The system of claim 11, wherein the instructions further cause the processor to identify a change in storage location of the file segment to a new storage location and, in response, update the mapping of the respective segment identity of the file segment to the new storage location.

### Claim 15 (depends on 11)

The system of claim 11, wherein the instructions further cause the processor to identify that a storage location of the file segment is compromised, and, in response, change a storage location of the file segment.

### Claim 16 (depends on 11)

The system of claim 11, wherein the instructions further cause the processor to encrypt a second file segment of the plurality of file segments with a second encryption technique that differs from a first encryption technique used to encrypt the file segment.

### Claim 17 (depends on 11)

The system of claim 11, wherein the executable file is configured to be unexecutable without being compiled from all file segments of the plurality of file segments.

### Claim 18 (depends on 11)

The system of claim 11, wherein to encrypt the file segment, the instructions further cause the processor to encrypt all file segments of the plurality of file segments using a homomorphic encryption technique.

### Claim 19 (depends on 11)

The system of claim 11, wherein the instructions further cause the processor to:
receive a request, from a device, for the file segment of the plurality of file segments, the request including a respective segment identity of the file segment;
retrieve the file segment based on the mapping and the segment identity; and
send the file segment to the device.

### Claim 20 (depends on 19)

The system of claim 19, wherein to send the file segment to the device, the instructions further cause the processor to send current encryption information for the file segment.
