# US 2019/0317924 A1 · Constructing a Multiple Entity Root of Trust

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

- Number: US 2019/0317924 A1
- Document ID: US20190317924A1
- Status: Published application
- Kind: A1
- Application number: 16/380,548
- Filed: 2019-04-10
- Published: 2019-10-17
- Earliest claimed: 2018-04-12
- Assignees: ISARA Corporation
- Applicants: ISARA Corporation
- Inventors: Parnian Alimi; Jiayuan Sui; Atsushi Yamada; Robert Williams; Alessandro Faieta
- Web page: https://patentgrep.com/patent/US20190317924A1

## CPC

- G06F 16/1824: {implemented using Network-attached Storage [NAS] architecture (distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097)}
- H04L 9/3255: {using group based signatures, e.g. ring or threshold signatures}
- G06F 16/1834: {implemented based on peer-to-peer networks, e.g. gnutella (p2p communication protocols H04L67/104)}
- 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 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/805: Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
- 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

In a general aspect, a multiple-entity root of trust is constructed and maintained for use in a cryptography system. In some aspects, a genesis data block includes genesis block data entries representing respective member entities of a root of trust consortium. A genesis block is generated by digitally signing the genesis data block. The genesis block is provided for use by end entities as a root of trust in a cryptography system. In some aspects, a hash of an existing block of a chain is obtained, and a data block comprising a data entry is generated. The data entry identifies an action by one or more member entities of the root of trust consortium. A new block of the chain is generated by digitally signing a combination of the data block and the hash of the existing block. The new block is provided for use by end entities as the root of trust in the cryptography system.

## Claims

### Claim 1

A method comprising:
generating a genesis data block comprising genesis block data entries representing respective member entities of a root of trust consortium, each genesis block data entry comprising:
an identifier of the member entity represented by the genesis block data entry;
a public key of the member entity represented by the genesis block data entry; and
a digital signature of a member entity other than the member entity represented by the genesis block data entry; and
generating a genesis block for the root of trust consortium based on the genesis data block, wherein generating the genesis block comprises digitally signing the genesis data block; and
providing the genesis block for use, by one or more end entities, as a root of trust in a cryptography system.

### Claim 2 (depends on 1)

The method of claim 1, wherein digitally signing the genesis data block comprises:
generating a digital signature of a manager of the root of trust consortium; and
appending the digital signature of the manager to the genesis data block.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
sending the genesis data block to a subset of the member entities;
receiving digital signatures from the subset of the member entities, wherein each of the digital signatures is generated by a respective one of the member entities based on the genesis data block; and
wherein generating the genesis block comprises combining the received digital signatures, the digital signature of the manager and the genesis data block.

### Claim 4 (depends on 1)

The method of claim 1, comprising obtaining the genesis block data entries from the member entities.

### Claim 5 (depends on 4)

The method of claim 4, wherein obtaining the genesis block data entries comprises initiating a ring signing process, and each genesis block data entry comprises a digital signature of a distinct entity.

### Claim 6 (depends on 1)

The method of claim 1, further comprising validating the genesis block data entries before providing the genesis block for use as a root of trust.

### Claim 7 (depends on 1)

The method of claim 1, wherein a chain comprising the genesis block is provided as the root of trust, and the method comprises:
obtaining a hash of an existing block of the chain;
generating a new data block comprising a new data entry, the new data entry identifying an action by one or more member entities of the root of trust consortium;
generating a new block of the chain for the root of trust consortium, wherein generating the new block comprises digitally signing a combination of the new data block and the hash of the existing block; and
providing the new block for use, by one or more end entities, as the root of trust in the cryptography system.

### Claim 8

A computer system comprising:
one or more processors; and
memory storing instructions that are operable when executed by the one or more processors to perform operations comprising:
generating a genesis data block comprising genesis block data entries representing respective member entities of a root of trust consortium, each genesis block data entry comprising:
an identifier of the member entity represented by the genesis block data entry;
a public key of the member entity represented by the genesis block data entry; and
a digital signature of a member entity other than the member entity represented by the genesis block data entry; and
generating a genesis block for the root of trust consortium based on the genesis data block, wherein generating the genesis block comprises digitally signing the genesis data block; and
providing the genesis block for use, by one or more end entities, as a root of trust in a cryptography system.

### Claim 9 (depends on 8)

The computer system of claim 8, wherein digitally signing the genesis data block comprises:
generating a digital signature of a manager of the root of trust consortium; and
appending the digital signature of the manager to the genesis data block.

### Claim 10 (depends on 9)

The computer system of claim 9, the operations further comprising:
sending the genesis data block to a subset of the member entities;
receiving digital signatures from the subset of the member entities, wherein each of the digital signatures is generated by a respective one of the member entities based on the genesis data block; and
wherein generating the genesis block comprises combining the received digital signatures, the digital signature of the manager and the genesis data block.

### Claim 11 (depends on 8)

The computer system of claim 8, the operations comprising obtaining the genesis block data entries from the member entities.

### Claim 12 (depends on 11)

The computer system of claim 11, wherein obtaining the genesis block data entries comprises initiating a ring signing process, and each genesis block data entry comprises a digital signature of a distinct entity.

### Claim 13 (depends on 8)

The computer system of claim 8, the operations further comprising validating the genesis block data entries before providing the genesis block for use as a root of trust.

### Claim 14 (depends on 8)

The computer system of claim 8, wherein a chain comprising the genesis block is provided as the root of trust, and the operations comprise:
obtaining a hash of an existing block of the chain;
generating a new data block comprising a new data entry, the new data entry identifying an action by one or more member entities of the root of trust consortium;
generating a new block of the chain for the root of trust consortium, wherein generating the new block comprises digitally signing a combination of the new data block and the hash of the existing block; and
providing the new block for use, by one or more end entities, as a root of trust in a cryptography system.

### Claim 15

A method comprising:
obtaining a hash of an existing block of a chain provided by a root of trust consortium;
generating a data block comprising a data entry, the data entry identifying an action by one or more member entities of the root of trust consortium;
generating a new block of the chain for the root of trust consortium, wherein generating the new block comprises digitally signing a combination of the data block and the hash of the existing block; and
providing the new block for use, by one or more end entities, as a root of trust in a cryptography system.

### Claim 16 (depends on 15)

The method of claim 15, wherein the data entry comprises an identifier of an action type, an identity of a member entity, a public key of the member entity, and a digital signature.

### Claim 17 (depends on 16)

The method of claim 16, further comprising validating the digital signature in each data entry before providing the new block for use as a root of trust.

### Claim 18 (depends on 15)

The method of claim 15, wherein the data block comprises multiple data entries identifying multiple actions by one or more of the member entities.

### Claim 19 (depends on 15)

The method of claim 15, wherein the action comprises at least one of:
adding a new member to the root of trust consortium;
removing a member from the root of trust consortium;
updating a public key of a member of the root of trust consortium;
revoking a public key of a member of the root of trust consortium;
replacing a public key of a member of the root of trust consortium;
adding an additional public key of a member of the root of trust consortium;
canceling a public key of a member of the root of trust consortium;
timestamping a valid state of the chain;
recording a summary of all currently valid identity information;
freezing the block; or
unfreezing the block.

### Claim 20 (depends on 15)

The method of claim 15, wherein digitally signing the combination of the data block and the hash of the existing block comprises:
a generating a digital signature of a manager of the root of trust consortium; and
appending the digital signature of the manager to the data block.

### Claim 21 (depends on 20)

The method of claim 20, further comprising:
sending the data block to a subset of the member entities;
receiving digital signatures from the subset of the member entities, wherein each of the digital signatures is generated by a respective one of the member entities based on the data block; and
wherein generating the new block comprises combining the received digital signatures, the digital signature of the manager and the data block.

### Claim 22

A computer system comprising:
one or more processors; and
memory storing instructions that are operable when executed by the one or more processors to perform operations comprising:
obtaining a hash of an existing block of a chain provided by a root of trust consortium;
generating a data block comprising a data entry, the data entry identifying an action by one or more member entities of the root of trust consortium;
generating a new block of the chain for the root of trust consortium, wherein generating the new block comprises digitally signing a combination of the data block and the hash of the existing block; and
providing the new block for use, by one or more end entities, as a root of trust in a cryptography system.

### Claim 23 (depends on 22)

The computer system of claim 22, wherein the data entry comprises an identifier of an action type, an identity of a member entity, a public key of the member entity, and a digital signature.

### Claim 24 (depends on 23)

The computer system of claim 23, the operations further comprising validating the digital signature in each data entry before providing the new block for use as a root of trust.

### Claim 25 (depends on 22)

The computer system of claim 22, wherein the data block comprises multiple data entries identifying multiple actions by one or more of the member entities.

### Claim 26 (depends on 22)

The computer system of claim 22, wherein the action comprises at least one of:
adding a new member to the root of trust consortium;
removing a member from the root of trust consortium;
updating a public key of a member of the root of trust consortium;
revoking a public key of a member of the root of trust consortium;
replacing a public key of a member of the root of trust consortium;
adding an additional public key of a member of the root of trust consortium;
canceling a public key of a member of the root of trust consortium;
timestamping a valid state of the chain;
recording a summary of all currently valid identity information;
freezing the block; or
unfreezing the block.

### Claim 27 (depends on 22)

The computer system of claim 22, wherein digitally signing the combination of the data block and the hash of the existing block comprises:
a generating a digital signature of a manager of the root of trust consortium; and
appending the digital signature of the manager to the data block.

### Claim 28 (depends on 27)

The computer system of claim 27, the operations further comprising:
sending the data block to a subset of the member entities;
receiving digital signatures from the subset of the member entities, wherein each of the digital signatures is generated by a respective one of the member entities based on the data block; and
wherein generating the new block comprises combining the received digital signatures, the digital signature of the manager and the data block.
