# US 2022/0012042 A1 · Mechanism for secure and resilient configuration upgrades

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

- Number: US 2022/0012042 A1
- Document ID: US20220012042A1
- Status: Published application
- Kind: A1
- Application number: 17/484,455
- Filed: 2021-09-24
- Published: 2022-01-13
- Earliest claimed: 2021-09-24
- Assignees: Intel Corporation
- Inventors: Kshitij Arun Doshi; Ned M. Smith; Francesc Guim Bernat
- Web page: https://patentgrep.com/patent/US20220012042A1

## CPC

- H04L 41/082: the condition being updates or upgrades of network functionality
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- H04L 9/0819: {Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062)}
- H04L 9/3218: {using proof of knowledge, e.g. Fiat-Shamir, GQ, Schnorr, ornon-interactive zero-knowledge proofs}
- H04L 9/3247: {involving digital signatures}
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 43/50: Testing arrangements
- G06F 2221/033: Test or assess software
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 41/145: {involving simulating, designing, planning or modelling of a network}
- H04L 41/147: for predicting network behaviour
- H04L 41/149: for prediction of maintenance
- H04L 41/16: using machine learning or artificial intelligence
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
- 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

Various systems and methods for providing secure and resilient configuration upgrades are described herein. A system, includes a processor; and memory to store instructions, which when executed by the processor, cause the system to: receive at a resilient security island (RSI) partition of a first network node, an update from a source, the first network node hosting the RSI partition and a host partition, the RSI comprising reserved hardware resources of the first network node; verify, by the RSI, provenance of the update; apply, by the RSI, the update to modify a configuration of the RSI or the host partition; test, by the RSI, the modified configuration of the RSI or the host partition; and provide a cryptographic proof that the test was completed and an update status to an update coordinator.

## Claims

### Claim 1

A system, comprising:
a processor; and
memory to store instructions, which when executed by the processor, cause the system to:
receive at a resilient security island (RSI) partition of a first network node, an update from a source, the first network node hosting the RSI partition and a host partition, the RSI comprising reserved hardware resources of the first network node;
verify, by the RSI, provenance of the update;
apply, by the RSI, the update to modify a configuration of the RSI or the host partition;
test, by the RSI, the modified configuration of the RSI or the host partition; and
provide a cryptographic proof that the test was completed and an update status to an update coordinator.

### Claim 2 (depends on 1)

The system of claim 1, wherein the source is a local device.

### Claim 3 (depends on 2)

The system of claim 2, wherein the instructions cause the system to: after receiving the update from the source, verifying device credentials of the local device and chain of custody of the update.

### Claim 4 (depends on 1)

The system of claim 1, wherein the source is a peer RSI partition at a second network node.

### Claim 5 (depends on 4)

The system of claim 4, wherein the instructions to receive the update from the source comprise instructions to receive the update over a secure network that links the first network node with the second network node.

### Claim 6 (depends on 5)

The system of claim 5, wherein the secure network is a resilient network.

### Claim 7 (depends on 5)

The system of claim 5, wherein the secure network includes redundant paths.

### Claim 8 (depends on 4)

The system of claim 4, wherein the instructions cause the system to perform attestation on the peer RSI prior to receiving the update from the peer RSI partition.

### Claim 9 (depends on 1)

The system of claim 1, wherein the instructions to verify provenance of the update comprise instructions to:
obtain a cryptographic key from a chain-of-trust of the RSI partition; and
use the cryptographic key to verify provenance of the update.

### Claim 10 (depends on 1)

The system of claim 1, wherein the instructions to apply the update is performed in a plurality of stages, wherein during the completion of a stage of the plurality of stages, the instructions cause the system to:
verify application of the update; and
perform a function depending on whether the application was verified.

### Claim 11 (depends on 10)

The system of claim 10, wherein the instructions to perform the function comprise instructions to if the verification fails, rolling back to a previous safe point.

### Claim 12 (depends on 10)

The system of claim 10, wherein the instructions to perform the function comprise instructions to if the verification succeeds, committing the stage to a safe point.

### Claim 13 (depends on 1)

The system of claim 1, wherein the instructions to apply the update comprise instructions to:
assume control over hardware assets of the host partition; and
apply the update to the hardware assets of the host partition.

### Claim 14 (depends on 1)

The system of claim 1, wherein the instructions to test the modified configuration comprise instructions to:
assume control over hardware assets of the host partition;
place software of the host partition in a sandbox; and
apply the update to the software of the host partition.

### Claim 15 (depends on 1)

The system of claim 1, wherein the instructions to test the modified configuration comprise instructions to:
obtain new measurements of components that were affected by the update;
generate a signature based on the new measurements; and
compare the signature against a pre-update signature that was generated based on the components before the update was applied.

### Claim 16 (depends on 1)

The system of claim 1, wherein the instructions to provide a cryptographic proof comprise instructions to cryptographically signing a certification of completion.

### Claim 17 (depends on 1)

The system of claim 1, wherein the update status indicates that the update was applied.

### Claim 18 (depends on 1)

The system of claim 1, wherein the update status indicates that the update was not applied.

### Claim 19 (depends on 1)

The system of claim 1, wherein the instructions cause the system to perform attestation on a host partition of the first network node.

### Claim 20 (depends on 1)

The system of claim 1, wherein the instructions cause the system to maintain, at the RSI partition, a cryptographically verifiable chain of trust of prior attested bootstrap events that resulted in a current operating state.

### Claim 21

A method, comprising:
receiving at a resilient security island (RSI) partition of a first network node, an update from a source, the first network node hosting the RSI partition and a host partition, the RSI comprising reserved hardware resources of the first network node;
verifying, by the RSI, provenance of the update;
applying, by the RSI, the update to modify a configuration of the RSI or the host partition;
testing, by the RSI, the modified configuration of the RSI or the host partition; and
providing a cryptographic proof that the test was completed and an update status to an update coordinator.

### Claim 22 (depends on 21)

The method of claim 21, wherein the source is a peer RSI partition at a second network node.

### Claim 23 (depends on 22)

The method of claim 22, wherein receiving the update from the source comprises receiving the update over a secure network that links the first network node with the second network node.

### Claim 24

At least one machine-readable medium including instructions, which when executed by a machine, cause the machine to perform operations comprising:
receiving at a resilient security island (RSI) partition of a first network node, an update from a source, the first network node hosting the RSI partition and a host partition, the RSI comprising reserved hardware resources of the first network node;
verifying, by the RSI, provenance of the update;
applying, by the RSI, the update to modify a configuration of the RSI or the host partition;
testing, by the RSI, the modified configuration of the RSI or the host partition; and
providing a cryptographic proof that the test was completed and an update status to an update coordinator.

### Claim 25 (depends on 24)

The at least one machine-readable medium of claim 24, wherein the source is a local device, and comprising instructions for after receiving the update from the source, verifying device credentials of the local device and chain of custody of the update.

### Claim 26 (depends on 24)

The at least one machine-readable medium of claim 24, wherein the source is a peer RSI partition at a second network node, and wherein the instructions for receiving the update from the source comprise instructions for receiving the update over a secure network that links the first network node with the second network node.

### Claim 27 (depends on 26)

The at least one machine-readable medium of claim 26, comprising instructions for performing attestation on the peer RSI prior to receiving the update from the peer RSI partition.

### Claim 28 (depends on 24)

The at least one machine-readable medium of claim 24, wherein the instructions for verifying provenance of the update comprise instructions for:
obtaining a cryptographic key from a chain-of-trust of the RSI partition; and
using the cryptographic key to verify provenance of the update.

### Claim 29 (depends on 24)

The at least one machine-readable medium of claim 24, wherein the instructions for applying the update comprise instructions for:
assuming control over hardware assets of the host partition; and
applying the update to the hardware assets of the host partition.

### Claim 30 (depends on 24)

The at least one machine-readable medium of claim 24, wherein the instructions for testing the modified configuration comprise instructions for:
obtaining new measurements of components that were affected by the update;
generating a signature based on the new measurements; and
comparing the signature against a pre-update signature that was generated based on the components before the update was applied.
