# US 2013/0254460 A1 · Using different secure erase algorithms to erase chunks from a file associated with different security levels

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

- Number: US 2013/0254460 A1
- Document ID: US20130254460A1
- Status: Published application
- Kind: A1
- Application number: 13/477,991
- Filed: 2012-05-22
- Published: 2013-09-26
- Earliest claimed: 2012-03-26
- Assignees: International Business Machines Corporation
- Inventors: Shah Mohammad R. Islam; Sandeep R. Patil; Riyazahamad M. Shiraguppi; Divyank Shukla
- Web page: https://patentgrep.com/patent/US20130254460A1

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 2221/2113: Multi-level security, e.g. mandatory access control
- G06F 2221/2143: Clearing memory, e.g. to prevent the data from being stolen
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Provided are a computer program product, system, and method for using different secure erase algorithms to erase chunks from a file associated with different security levels. A request is received to secure erase a file having a plurality of chunks stored in at least one storage device. A determination is made of a first secure erase algorithm to apply to a first chunk in the file in response to the request and of a second secure erase algorithm to apply to a second chunk in the file in response to the request. The first secure erase algorithm is applied to erase the first chunk and the second secure erase algorithm is applied to erase the second chunk. The first and second secure erase algorithms use different processes to erase the chunks to which they are applied.

## Claims

### Claim at position 1

1-22. (canceled)

### Claim 23

A method for secure deleting a file, comprising:
receiving a request to secure erase a file having a plurality of chunks stored in at least one storage device;
determining a first secure erase algorithm to apply to a first chunk in the file in response to the request;
determining a second secure erase algorithm to apply to a second chunk in the file in response to the request;
applying the first secure erase algorithm to erase the first chunk; and
applying the second secure erase algorithm to erase the second chunk, wherein the first and second secure erase algorithms use different processes to erase the chunks to which they are applied.

### Claim 24 (depends on 23)

The method of claim 23, wherein a determination is made for each chunk in the file, including the first and second chunks, to apply at least one of the first erase algorithm and the second erase algorithm, and wherein the determined secure erase algorithm for the chunk is applied to erase the chunk.

### Claim 25 (depends on 23)

The method of claim 23, further comprising:
receiving chunk security level information associating one of a plurality of security levels with the chunks;
wherein the determining of the first secure erase algorithm comprises:
determining from the chunk security level information a first security level associated with the first chunk; and
determining from the first security level the first secure erase algorithm associated with the first security level.

### Claim 26 (depends on 25)

The method of claim 25, wherein the determining of the second secure erase algorithm comprises:
determining from the chunk security level information a second security level associated with the second chunk; and
determining from the second security level the second secure erase algorithm associated with the second security level.

### Claim 27 (depends on 26)

The method of claim 26, wherein further comprising:
maintaining security level algorithm information associating security levels with secure erase algorithms, including associating the first security level with the first secure erase algorithm and associating the second security level with the second secure erase algorithm,
wherein the determining from the first security level the first secure erase algorithm comprises determining from the security level algorithm information the first secure erase algorithm that is associated with the first security level provided for the first chunk,
wherein the determining from the second security level the second secure erase algorithm comprises determining from the security level algorithm information the second secure erase algorithm that is associated with the second security level provided for the first chunk.

### Claim 28 (depends on 25)

The method of claim 25, further comprising:
maintaining security level algorithm information associating security levels with secure erase algorithms, including associating the first security level with the first secure erase algorithm and associating the second security level with the second secure erase algorithm;
determining that the secure erase algorithm information does not provide one secure erase algorithm for the second security level associated with the second chunk;
using the second secure erase algorithm in response to determining that the secure erase algorithm information does not provide one secure erase algorithm for the second security level.

### Claim 29 (depends on 28)

The method of claim 28, wherein the second secure erase algorithm provides a maximum secure erase protection of the security algorithms indicated in the secure erase algorithm information.

### Claim 30 (depends on 25)

The method of claim 25, wherein the chunk security level information is provided in metadata separate from the file.

### Claim 31 (depends on 30)

The method of claim 30, further comprising:
using the chunk security level information to select storage locations on which to store the chunks, wherein different storage locations are associated with different security levels, and wherein storage locations are selected to store chunks that provide secure storage commensurate with the security levels assigned to the chunks in the chunk security level information.

### Claim 32 (depends on 25)

The method of claim 25, wherein the chunk security level information is included in a write request to write the file to storage, wherein chunks comprise contiguous blocks associated with a same security level, and wherein the chunk security level information is used to select storage devices associated with different security levels to store the chunks of the file for the write request.

### Claim 33 (depends on 23)

The method of claim 23, wherein the first and second secure erase algorithms are different in at least one of a pattern of data to write and a number of times the pattern of data is written.
