Distributed logging for securing non-repudiable multi-party transactions
Disclosed herein are methods, systems, and processes for distributed logging for securing non-repudiable transactions. Credentials, request information, response information, and action items generated and received by a requesting computing system and a responding computing system, and transmitted between the requesting computing system and the responding computing system are separately recorded and stored in a requestor log maintained by the requesting computing system and in a responder log maintained by the responding computing system.
1. A computer-implemented method comprising:
receiving a request message from a requesting computing system, wherein the request message comprises one or more action items,
the one or more action items are associated with a transaction between the requesting computing system and a responding computing system, and
the one or more action items are added to a requestor log by the requesting computing system, wherein the requestor log is non-repudiable, and wherein the one or more action items are added to the requestor log on a transaction-by-transaction basis without requiring consensus from a network majority or a block of transactions to be formed;
storing the one or more action items in a responder log, wherein the responder log is non-repudiable, and wherein the one or more action items are added to the responder log on a transaction-by-transaction basis without requiring consensus from the network majority or the block of transactions to be formed; and
transmitting data responsive to the one or more action items to the requesting computing system.
2. The computer-implemented method of claim 1 , further comprising:
accessing a tamper-evident log upon receiving the request message; and
determining that the one or more action items in the request message is stored in the tamper-evident log.
3. The computer-implemented method of claim 2 , further comprising:
updating the tamper-evident log to indicate transmission of the data responsive to the one or more action items prior to transmitting the data to the requesting computing system.
4. The computer-implemented method of claim 1 , wherein
the requestor log is maintained by the requesting computing system, and
the responder log is maintained by the responding computing system.
5. The computer-implemented method of claim 2 , wherein a copy of the tamper-evident log is maintained by the requesting computing system, the responding computing system, and an external computing system.
6. The computer-implemented method of claim 2 , further comprising:
accessing the tamper-evident log; and
performing an audit transaction to verify the transaction between the requesting computing system and the responding computing system.
7. The computer-implemented method of claim 2 , wherein
the tamper-evident log is a distributed ledger.
8. The method of claim 1 , wherein:
the one or more action items are also logged by an audit computing system in an audit log that is non-repudiable.
9. The method of claim 1 , wherein:
the responder log and the requestor log are business-specific and confidential.
10. The method of claim 1 , wherein:
the method is performed with means for an authenticate-request-response-action with separate logging systems.
11. The method of claim 1 , comprising:
steps for auditing by request and response actors.
12. The method of claim 1 , wherein:
the responder log is updated with means for implementing a distributed ledger.
13. The method of claim 1 , comprising:
steps for recording requests including the request.
14. The method of claim 1 , comprising:
steps for recording requests, responses, and results by the requesting computing system.
15. The method of claim 1 , comprising:
steps for recording requests, responses, and results by the responding computing system.
16. The method of claim 1 , comprising:
steps for requestor-side auditing.
17. The method of claim 1 , comprising:
steps for responder-side auditing.
18. The method of claim 1 , the responding computing system comprises:
the responder log;
a transaction engine;
a verification engine; and
an audit engine, wherein:
the responder log is rendered non-repudiable by a directed graph of cryptographic hash pointers.
19. A tangible, non-transitory, machine-readable medium storing instructions that when executed cause operations comprising:
receiving a request message from a requesting computing system, wherein the request message comprises one or more action items,
the one or more action items are associated with a transaction between the requesting computing system and a responding computing system, and
the one or more action items are added to a requestor log by the requesting computing system, wherein the requestor log is non-repudiable, and wherein the one or more action items are added to the requestor log on a transaction-by-transaction basis without requiring consensus from a network majority or a block of transactions to be formed;
storing the one or more action items in a responder log, wherein the responder log is non-repudiable, and wherein the one or more action items are added to the responder log on a transaction-by-transaction basis without requiring consensus from the network majority or the block of transactions to be formed; and
transmitting data responsive to the one or more action items to the requesting computing system.