Managing standard operating procedures using distributed ledger networks

Patent metadata

Field	Value
Publication number	US-12095925-B2
Application number	US-202217571660-A
Country	US
Kind code	B2
Filing date	Jan 10, 2022
Priority date	Jan 10, 2022
Publication date	Sep 17, 2024
Grant date	Sep 17, 2024

Abstract

Systems and methods of the disclosure include: receiving, by a node of a distributed ledger network, first transaction data, wherein the first transaction data comprises an alert derived from a state of a computer system; storing the first transaction data in a first block of the distributed ledger network; receiving, by the node, second transaction data, wherein the second transaction data comprises an identifier of a remedial action performed on the computer system in response to the alert and a result of performing the remedial action; and storing the second transaction data in a block of the distributed ledger network, wherein the block is provided by one of: the first block or a second block.

First claim

What is claimed is:

1. A method comprising:
receiving, by a node of a distributed ledger network, first transaction data, wherein the first transaction data comprises an alert derived from a state of a computer system;
storing, by the node, the first transaction data in a first block of the distributed ledger network;
receiving, by the node, second transaction data, wherein the second transaction data comprises an identifier of a remedial action performed on the computer system in response to the alert and a result of performing the remedial action;
storing the second transaction data in a block of the distributed ledger network, wherein the block is provided by one of: the first block or a second block;
receiving, by the node, third transaction data, wherein the third transaction data comprises one or more cryptographic signatures from one or more stakeholders of the computer system; and
storing, by a processing device of the node, the third transaction data in the first block, wherein at least one of the first transaction data, the second transaction data, or the third transaction data are accessed by a device as part of a recovery process for the computer system.

2. The method of claim 1 , further comprising:
receiving, by the node, fourth transaction data, wherein the fourth transaction data comprises a state of a production system in response to performing the remedial action.

3. The method of claim 1 , further comprising:
receiving, by the node, fourth transaction data, wherein the fourth transaction data comprises one or more cryptographic signatures from one or more parties; and
storing the fourth transaction data in a fourth block of the distributed ledger network.

4. The method of claim 3 , wherein each cryptographic signature in the one or more cryptographic signatures comprises a cryptographic hash value of a message transmitted to the one or more parties.

5. The method of claim 1 , wherein the first transaction data is received in response to a system failure of the computer system, and wherein the alert is indicative of the system failure.

6. The method of claim 1 , wherein the first transaction data is received in response to a user request for a configuration change of the computer system, and wherein the alert is to indicate the user request.

7. A system comprising:
a distributed ledger network client; and
a distributed ledger network comprising a node to:
receive, from the distributed ledger network client, first transaction data, wherein the first transaction data comprises an alert derived from a state of a computer system;
store the first transaction data in a first block of the distributed ledger network;
receive second transaction data, wherein the second transaction data comprises an identifier of a remedial action performed on the computer system in response to the alert and a result of performing the remedial action;
store the second transaction data in a block of the distributed ledger network, wherein the block is provided by one of: the first block or a second block;
receive, by the node, third transaction data, wherein the third transaction data comprises one or more cryptographic signatures from one or more stakeholders of the computer system; and
store, by a processing device, the third transaction data in the first block, wherein at least one of the first transaction data, the second transaction data, or the third transaction data are accessed by a device as part of a recovery process for the computer system.

8. The system of claim 7 , wherein the node is further to:
receive fourth transaction data, wherein the fourth transaction data comprises a state of a production system in response to performing the remedial action.

9. The system of claim 7 , wherein the node is further to:
receive fourth transaction data, wherein the fourth transaction data comprises one or more cryptographic signatures from one or more parties; and
store the fourth transaction data in a fourth block of the distributed ledger network.

10. The system of claim 9 , wherein each cryptographic signature in the one or more cryptographic signatures comprises a cryptographic hash value of a message transmitted to the one or more parties.

11. The system of claim 7 , wherein to receive the first transaction data, the node is to receive the first transaction data in response to a system failure of the computer system, and wherein the alert is indicative of the system failure.

12. The system of claim 7 , wherein to receive the first transaction data, the node is to receive the first transaction data in response to a user request for a configuration change of the computer system, and wherein the alert is to indicate the user request.

13. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processing device, cause the processing device to:
monitor, by a monitoring component of a computer system, a state of the computer system;
detect that the state of the computer system comprises a failed state;
send, to a node of a distributed ledger network, an alert indicating the state of the computer system;
determine that transaction data stored on a block of the distributed ledger network comprises one or more cryptographic signatures, wherein the one or more cryptographic signatures satisfy a prerequisite condition;
in response to the determination that the transaction data stored on the block of the distributed ledger network comprises the one or more cryptographic signatures, monitor one or more remedial actions executed on the computer system; and
send, by the processing device and to the node of the distributed ledger network, data comprising the one or more remedial actions executed on the computer system.

14. The non-transitory computer-readable storage medium of claim 13 , wherein the instructions, when executed by the processing device, cause the processing device further to:
generate a user interface, wherein the user interface is modified to perform a change to the computer system.

15. The non-transitory computer-readable storage medium of claim 13 , wherein the instructions, when executed by the processing device, cause the processing device further to:
send, to the node of the distributed ledger network, data comprising a result of the one or more remedial actions executed on the computer system.

16. The non-transitory computer-readable storage medium of claim 13 , wherein the instructions, when executed by the processing device, cause the processing device further to:
in response to the monitoring of the one or more remedial actions executed on the computer system, detect a current state of the computer system; and
send, to the node of the distributed ledger network, data comprising the current state of the computer system.

17. The non-transitory computer-readable storage medium of claim 13 , wherein each cryptographic signature in the one or more cryptographic signatures comprises a cryptographic hash value of a message transmitted to one or more parties.

Assignees

• Red Hat Inc

Inventors

• Gallagher Brian
• O'Connor Cathal

Classifications

• H04L9/50 Primary

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L9/3247

  involving digital signatures · CPC title

• H04L63/126

  the source of the received data · CPC title

• H04L63/123

  received data contents, e.g. message integrity · CPC title

• H04L9/3239 Primary

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title