Systems and methods for conducting remote attestation

Patent metadata

Field	Value
Publication number	US-12200141-B2
Application number	US-202117494716-A
Country	US
Kind code	B2
Filing date	Oct 5, 2021
Priority date	Oct 5, 2021
Publication date	Jan 14, 2025
Grant date	Jan 14, 2025

Abstract

Disclosed embodiments may include a system that may receive a document associated with an entity and may generate a first hash associated with the document. The system may prompt a first user to provide a first signature of the document and may generate a second hash associated with the first signature. The system may prompt the first user to provide authentication information and may determine whether received authentication information matches stored authentication information. In response to determining the authentication information matches the stored authentication information, the system may prompt a second user to provide a second signature of the document, may generate a third hash associated with the second signature, may generate a fourth hash associated with a verified record of the first, second, and third hashes, may generate a block comprising the first, second, third, and fourth hashes, and may publish the block to a blockchain.

First claim

What is claimed is:

1. A system for conducting remote attestation comprising:
one or more processors; and
a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to:
receive a first document associated with an entity;
generate a first hash associated with the first document;
prompt a first user to provide, via a first user device associated with the first user, a first signature of the first document;
receive the first signature of the first document from the first user device;
generate a second hash associated with the first signature of the first document;
prompt the first user, via the first user device, to provide authentication information of the first user comprising three or more required authentication factors, each required authentication factor comprises a personal identification number (PIN), a physical token, a facial recognition, a thumbprint image, a retina scan, or an encrypted quick response (QR) code;
receive, from the first user via the first user device, the authentication information of the first user comprising the three or more required authentication factors;
determine whether the authentication information of the first user matches stored authentication information of the first user;
in response to determining that the authentication information of the first user matches the stored authentication information of the first user, prompt a second user to provide, via a second user device associated with the second user, a second signature of the first document, wherein the first user is different than the second user;
receive the second signature of the first document from the second user device;
generate a third hash associated with the second signature of the first document;
determine whether a predetermined threshold has been satisfied;
responsive to determining that the predetermined threshold has been satisfied, generate a fourth hash associated with a verified record of the first hash, the second hash, and the third hash;
generate a first block comprising the first hash, the second hash, the third hash, and the fourth hash; and
publish the first block to a public blockchain.

2. The system of claim 1 , wherein the three or more required authentication factors are customizable by the first user and the second user.

3. The system of claim 1 , wherein the instructions are further configured to cause the system to:
prompt the first user, via a graphical user interface (GUI) of a third user device associated with the first user, to generate a first encrypted QR code; and
receive, from the first user via the first user device, the first encrypted QR code,
wherein at least one of the three or more required authentication factors comprises the first encrypted QR code.

4. The system of claim 3 , wherein the first user device is a computer and the third user device is a mobile phone.

5. The system of claim 1 , wherein the second user is a notary.

6. The system of claim 1 , wherein the system is integrated into a video capable software.

7. A system for conducting remote attestation comprising:
one or more processors; and
a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to:
receive a first document associated with an entity;
generate a first hash associated with the first document;
prompt a first user to provide, via a first user device associated with the first user, a first signature of the first document;
receive the first signature of the first document from the first user device;
generate a second hash associated with the first signature of the first document;
prompt the first user, via the first user device, to provide authentication information of the first user comprising a first encrypted quick response (QR) code and two or more required authentication factors, each required authentication factor comprises a personal identification number (PIN), a physical token, a facial recognition, a thumbprint image, or a retina scan;
receive, from the first user via the first user device, the authentication information of the first user comprising the first encrypted QR code and the two or more required authentication factors;
determine whether the authentication information of the first user matches stored authentication information of the first user;
in response to determining that the authentication information of the first user matches the stored authentication information of the first user, prompt a second user to provide, via a second user device associated with the second user, a second signature of the first document, wherein the first user is different than the second user;
receive the second signature of the first document from the second user device;
generate a third hash associated with the second signature of the first document;
determine whether a predetermined threshold has been satisfied;
responsive to determining that the predetermined threshold has been satisfied, generate a fourth hash associated with a verified record of the first hash, the second hash, and the third hash;
generate a first block comprising the first hash, the second hash, the third hash, and the fourth hash; and
publish the first block to a public blockchain.

8. The system of claim 7 , wherein prompting the first user to provide the authentication information of the first user comprises prompting the first user, via a graphical user interface (GUI) of a third user device associated with the first user, to generate the first encrypted QR code, and wherein receiving the authentication information of the first user comprises receiving, from the first user via the first user device, the first encrypted QR code.

9. The system of claim 8 , wherein the first user device is a computer and the third user device is a mobile phone.

10. The system of claim 7 , wherein the two or more required authentication factors are customizable by the first user and the second user.

11. The system of claim 7 , wherein the second user is a notary.

12. A system for conducting remote attestation comprising:
one or more processors; and
a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to:
receive a first document associated with an entity;
generate a first hash associated with the first document;
prompt a first user to provide, via a first user device associated with the first user, a first signature of the first document;
receive the first signature of the first document from the first user device;
generate a second hash associated with the first signature of the first document;
prompt the first user, via the first user device, to provide three or more required authentication factors associated with the first user;
receive, from the first user via the first user device, the three or more required authentication factors associated with the first user;
determine that the three or more required authentication factors associated with the first user match three or more stored authentication factors associated with the first user;
in response to determining that the three or more required authentication factors associated with the first user match three or more stored authentication factors associated with the first user, prompt a second user to provide, via a second user device associated with the second user, a second signature of the first document, wherein the first user is different than the second

Assignees

• Capital One Services Llc

Inventors

• Fletcher Abel

Classifications

• H04L9/50

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

• H04L9/3213

  using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807) · CPC title

• G06Q50/18 Primary

  Legal services · CPC title

• H04L9/3226

  using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083) · CPC title

• H04L9/3239

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