# US 2021/0067334 A1 · System and Method for Cryptographic Key Fragments Management

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

- Number: US 2021/0067334 A1
- Document ID: US20210067334A1
- Status: Published application
- Kind: A1
- Application number: 16/508,410
- Filed: 2019-07-11
- Published: 2021-03-04
- Earliest claimed: 2018-07-11
- Assignees: Akeyless Security Ltd.
- Applicants: Akeyless Security LTD.
- Inventors: Refael ANGEL
- Web page: https://patentgrep.com/patent/US20210067334A1

## CPC

- H04L 9/0869: {involving random numbers or seeds}
- 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)}
- G06F 21/602: {Providing cryptographic facilities or services}
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system, a method and a computer program product and a system, for Key Fragment Management (KFM). The KFM system comprises a plurality of KFM instances and a client device. At least two KFM instances are executed on execution platforms of two different service providers. Each KFM instance retains a root key fragment. The client device is configured to perform a cryptographic process relating to a data item using a data-specific key. Each KFM instance is configured to generate a data-specific key fragment based on a data identifier of the data item and based on the root key fragment in response to the client device requesting to generate the data-specific key for the data item. The data-specific key is generated based on a plurality of data-specific key fragments generated by the each KFM instances.

## Claims

### Claim 1

A method comprising:
obtaining a data identifier of a data item;
transmitting the data identifier to a plurality of Key Fragment Management (KFM) instances, wherein each KFM instance retains a root key fragment, wherein each KFM instance is configured to generate a data-specific key fragment based on the data identifier and based on the root key fragment;
obtaining from the plurality of KFM instances, a plurality of data-specific key fragments;
generating a data-specific key based on the plurality of data-specific key fragments; and
performing a cryptographic process relating to the data item using the data-specific key.

### Claim 2 (depends on 1)

The method of claim 1, wherein the cryptographic process is an encryption of the data item using the data-specific key to provide an encrypted data item.

### Claim 3 (depends on 2)

The method of claim 2 further comprises storing the encrypted data item and storing the data identifier in a manner allowing retrieval thereof for the encrypted data item.

### Claim 4 (depends on 1)

The method of claim 1, wherein the cryptographic process is a decryption of an encrypted data item using the data-specific key to obtain the data item.

### Claim 5 (depends on 1)

The method of claim 1, wherein said obtaining the data identifier comprises generating a non-deterministic data identifier.

### Claim 6 (depends on 1)

The method of claim 1, wherein at least two KFM instance are provided by two different service providers.

### Claim 7 (depends on 1)

The method of claim 1 further comprises:
obtaining, in a local environment, a user key fragment,
wherein said generating the data-specific key is performed in the local environment and based on the plurality of data-specific key fragments and based on the user key fragment.

### Claim 8 (depends on 1)

The method of claim 1, wherein said obtaining the data identifier comprises applying a hash function on the data item.

### Claim 9 (depends on 8)

The method of claim 8, wherein each KFM instance is configured to generate the data-specific key fragment by:
deriving, using the data identifier and the root key fragment, a pseudo-identifier, whereby obtaining a plurality of pseudo-identifiers from the plurality of KFM instances; and
deriving, using the pseudo-identifier and the root key fragment, the data-specific key fragment.

### Claim 10 (depends on 9)

The method of claim 9,
wherein the cryptographic process is an encryption of the data item using the data-specific key to provide an encrypted data item; and
wherein the method further comprises storing the encrypted data item and storing the plurality of pseudo-identifiers in a manner allowing retrieval thereof for the encrypted data item.

### Claim 11 (depends on 9)

The method of claim 9,
wherein the cryptographic process is a decryption of an encrypted data item using the data-specific key to obtain the data item; and
wherein said obtaining the data identifier comprises retrieving the plurality of pseudo-identifiers for the encrypted data item;
wherein said transmitting comprises transmitting the plurality of pseudo-identifiers to the plurality of KFM instances, wherein each KFM instance is configured to generate the data-specific key fragment based on the pseudo-identifier and based on the root key fragment using a single derivation process.

### Claim 12 (depends on 1)

The method of claim 1, wherein each KFM instance is configured to generate at least a portion of a respective root key fragment independently.

### Claim 13 (depends on 1)

The method of claim 1, wherein each KFM instance is configured to generate a respective root key fragment using a random function.

### Claim 14 (depends on 1)

The method of claim 1, wherein a root key that is an aggregation of the root key fragments is never assembled.

### Claim 15 (depends on 1)

The method of claim 1,
wherein each root key fragment comprises a static key fragment and an ephemeral key fragment, wherein a root key is an aggregation of the static key fragments and ephemeral key fragments;
wherein the method further comprises updating at least a portion of the ephemeral key fragments of the KFM instances without modifying the root key.

### Claim 16

A Key Fragment Management (KFM) system comprising:
a plurality of KFM instances, wherein at least two KFM instances are executed on execution platforms of two different service providers, wherein each KFM instance retains a root key fragment;
a client device, wherein said client device is configured to perform a cryptographic process relating to a data item using a data-specific key; and
wherein each KFM instance is configured to generate a data-specific key fragment based on a data identifier of the data item and based on the root key fragment in response to said client device requesting to generate the data-specific key for the data item, wherein the data-specific key is generated based on a plurality of data-specific key fragments generated by the each KFM instances.

### Claim 17 (depends on 16)

The KFM system of claim 16, wherein the data identifier is a non-deterministic data identifier.

### Claim 18 (depends on 16)

The KFM system of claim 16, wherein the data-specific key is generated in a local environment of the client device, wherein the local environment is not accessible from the KFM instances, wherein the data specific key is generated based on the plurality of data-specific key fragments and based on a user key fragment obtained by said client device.

### Claim 19 (depends on 16)

The KFM system of claim 16, wherein the data identifier is a deterministic data identifier.

### Claim 20 (depends on 16)

The KFM system of claim 16, wherein each KFM instance is configured to generate at least a portion of a respective root key fragment independently.

### Claim 21 (depends on 16)

The KFM system of claim 16, wherein a root key that is an aggregation of the root key fragments is never assembled within any portion of the KFM system.

### Claim 22 (depends on 16)

The KFM system of claim 16, wherein a root key of the KFM system is an aggregation of the root key fragments, wherein the KFM system is configured to refresh the root key fragments in at least a portion of the KFM instances without modifying the root key.

### Claim 23

A computer program product comprising a non-transitory computer readable storage medium retaining program instructions, which program instructions when read by a processor, cause the processor to perform a method comprising:
obtaining a data identifier of a data item;
transmitting the data identifier to a plurality of Key Fragment Management (KFM) instances, wherein each KFM instance retains a root key fragment, wherein each KFM instance is configured to generate a data-specific key fragment based on the data identifier and based on the root key fragment;
obtaining from the plurality of KFM instances, a plurality of data-specific key fragments;
generating a data-specific key based on the plurality of data-specific key fragments; and
performing a cryptographic process relating to the data item using the data-specific key.
