# US 2017/0257214 A1 · Encryption key lifecycle management

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

- Number: US 2017/0257214 A1
- Document ID: US20170257214A1
- Status: Published application
- Kind: A1
- Application number: 15/059,430
- Filed: 2016-03-03
- Published: 2017-09-07
- Earliest claimed: 2016-03-03
- Assignees: Dell Products L.P.
- Applicants: Dell Products, L.P.
- Inventors: Kenneth Wade Stufflebeam
- Web page: https://patentgrep.com/patent/US20170257214A1

## CPC

- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 63/068: {using time-dependent keys, e.g. periodically changing keys (cryptographic mechanisms or cryptographic arrangements for controlling usage of secret information H04L9/088)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In some embodiments, a method may include: enforcing a key rotation policy associated with a current encryption key being used to encrypt and decrypt data stored in an IHS; monitoring a cryptoperiod associated with the current encryption key; in response to a determination that the current encryption key has reached the end of the cryptoperiod, automatically transmitting a request to a key provider for a new encryption key; and in response to the request, automatically: receiving the new encryption key, marking the current encryption key as old, un-encrypting the data using the old encryption key, re-encrypting the data using the new encryption key, and, in response to a determination that all of the data has been re-encrypted with the new encryption key, transmitting a request to the key provider that the old encryption key be discarded, and deleting a local copy of the old encryption key.

## Claims

### Claim 1

A method, comprising:
enforcing a key rotation policy associated with a current encryption key being used to encrypt and decrypt data stored in an Information Handling System (IHS);
monitoring a cryptoperiod associated with the current encryption key;
in response to a determination that the current encryption key has reached the end of the cryptoperiod, automatically transmitting a request to a key provider for a new encryption key; and
in response to the request, automatically: receiving the new encryption key, marking the current encryption key as old, un-encrypting the data using the old encryption key, re-encrypting the data using the new encryption key, and, in response to a determination that all of the data has been re-encrypted with the new encryption key, transmitting a request to the key provider that the old encryption key be discarded, and deleting a local copy of the old encryption key.

### Claim 2 (depends on 1)

The method of claim 1, wherein the receiving, marking, un-encrypting, re-encrypting operations are performed as background tasks.

### Claim 3 (depends on 1)

The method of claim 1, wherein the un-encrypting and re-encrypting operations are performed concurrently.

### Claim 4 (depends on 1)

The method of claim 1, further comprising requesting that the old encryption key be moved from a backup state to an archived state upon receipt of the new encryption key.

### Claim 5 (depends on 3)

The method of claim 3, further comprising, upon receiving the new encryption key, storing the new encryption key in an backup state.

### Claim 6 (depends on 1)

The method of claim 1, further comprising marking the new encryption key as active by setting an activation date attribute associated with the new encryption key.

### Claim 7 (depends on 1)

The method of claim 1, further comprising setting a rotation attribute associated with the new key to true.

### Claim 8 (depends on 1)

The method of claim 1, wherein the request for the new key starts running a new cryptoperiod for the new key.

### Claim 9 (depends on 1)

The method of claim 1, further comprising decrypting existing data with the old encryption key and encrypting newly created data with the new encryption key.

### Claim 10 (depends on 1)

The method of claim 1, further comprising marking the new encryption key as active by setting an activation date attribute associated with the new encryption key.

### Claim 11

A memory device having program instructions stored thereon that, upon execution by a processor of an Information Handling System (IHS), cause the IHS to:
monitor a cryptoperiod associated with a current encryption key being used to encrypt and decrypt data stored in the IHS;
in response to a determination that the current encryption key has reached the end of the cryptoperiod, transmit a request to a key provider for a new encryption key; and
in response to the request: receive the new encryption key, mark the current encryption key as old, un-encrypt the data using the old encryption key, re-encrypt the data using the new encryption key, and, in response to a determination that all of the data has been re-encrypted with the new encryption key, transmit a request to the key provider that the old encryption key be discarded.

### Claim 12 (depends on 11)

The memory device of claim 11, wherein the receiving, marking, un-encrypting, re-encrypting operations are performed as background tasks.

### Claim 13 (depends on 11)

The memory device of claim 11, wherein the un-encrypting and re-encrypting operations are performed concurrently.

### Claim 14 (depends on 11)

The memory device of claim 11, wherein the program instructions are further configured to cause the IHS to request that the old encryption key be moved from a backup state to an archived state upon receipt of the new encryption key.

### Claim 15 (depends on 14)

The memory device of claim 14, wherein the program instructions are further configured to cause the IHS to, upon receipt of the new encryption key, store the new encryption key in an backup state.

### Claim 16 (depends on 11)

The memory device of claim 11, wherein the program instructions are further configured to cause the IHS to mark the new encryption key as active by setting an activation date attribute associated with the new encryption key.

### Claim 17 (depends on 11)

The memory device of claim 11, wherein the program instructions are further configured to cause the IHS to set a rotation attribute associated with the new key to true.

### Claim 18

An Information Handling System (IHS), comprising:
a processor; and
a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to:
monitor a cryptoperiod associated with a current encryption key being used to encrypt and decrypt data stored in the IHS;
in response to a determination that the current encryption key has reached the end of the cryptoperiod, transmit a request to a key provider for a new encryption key; and
in response to the request: receive the new encryption key, mark the current encryption key as old, un-encrypt the data using the old encryption key, re-encrypt the data using the new encryption key, and, in response to a determination that all of the data has been re-encrypted with the new encryption key, transmit a request to the key provider that the old encryption key be discarded.

### Claim 19 (depends on 18)

The IHS of claim 18, wherein the program instructions are further configured to cause the IHS to request that the old encryption key be moved from a backup state to an archived state upon receipt of the new encryption key.

### Claim 20 (depends on 18)

The IHS of claim 18, wherein the program instructions are further configured to cause the IHS to set a rotation attribute associated with the new key to true.
