Multi-factor data certification
The multi-factor data certification system addresses the reliance on single-source authentication by using a decentralized, non-repudiable register to ensure data integrity and robustness through multiple attestation points.
Patent Information
- Application Number
- FR2022001791
- Authority / Receiving Office
- FR · FR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-03-01
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2042-03-01
AI Technical Summary
Existing data certification systems rely solely on actor authentication, which is based on a single source of information and depends heavily on the training of all stakeholders, making them unreliable and difficult to implement in practice.
A multi-factor data certification system using a processing module that associates user identifiers with a non-repudiable register containing ordered lists of certificates, timestamps, and electronic signatures, implemented on a distributed ledger like a blockchain, to ensure data integrity and non-repudiation.
Enhances data integrity verification by allowing multiple attestation points, reducing reliance on individual training and improving system robustness through decentralized, non-repudiable record keeping.
Smart Images

Figure 00000011_0000 
Figure 00000011_0001 
Figure 00000012_0000
Abstract
Description
Title of the invention: Multi-factor data certification Technical field
[0001] The invention lies in the field of computer encryption and systems guaranteeing non-repudiation, for example blockchains. State of the prior art
[0002] The world of cyber security is focused on hunting down bad actors.
[0003] Existing data certification systems are based solely on Actor authentication. At best, existing systems such as PGP and S / MIME allow for encryption and signing. They are rarely used in practice and require extensive administration and technical knowledge from all the actors who use them.
[0004] A disadvantage of this data certification system is that it is based on a single source of information. The robustness of the system depends exclusively on the training of all stakeholders. Statement of the invention
[0005] One aim of the invention is in particular to remedy all or part of the aforementioned drawbacks.
[0006] According to a first aspect of the invention, a module is proposed for processing certifying instances of digital data, the module comprising an identifier of the user and of certifying systems, in which each of the certifying instances is associated with a storage address, with a user terminal, and with a non-repudiable register comprising an ordered list of elements, each of the elements comprising: • a certificate generated by one of the certification systems, the certificate comprising a type of certificate, a summary of a document, a timestamp by the certification system of the time of generation of said certificate, • an electronic signature of said certificate, • a timestamp by the processing module of the moment the element was added to the ordered list, • optionally a pointer to the electronic document (for example a memory address in a storage device on a network), in clear or encrypted by an asymmetric key held by the creator of the MFC.
[0007] According to a second aspect of the invention, a system is proposed comprising at least one client, at least one certifying system, and a processing module. of instance according to the first aspect of the invention, or one or more of its improvements.
[0008] According to another aspect of the invention, there is provided a method implemented in a system according to the second aspect of the invention, or one or more of its improvements.
[0009] The method may comprise a step of verifying the integrity of a file by a user terminal, said file being received from another user terminal.
[0010] The step of verifying the integrity of the file then includes the following steps, implemented at the user terminal: • calculate a digest of the received file, • receive from the other user terminal a storage address of a certifying instance, • generate a request to receive a certifying instance from said storage address and send it to the module, • receive from the module the certifying instance associated with said storage address, • browse the list of elements of the received certifying instance to determine the presence or absence of a condensate of an attestation which is the same as the calculated condensate.
[0011] If the presence of the calculated condensate is verified, the step of verifying the integrity of the file may include one or more steps of verifying the other attestations of the ordered list of elements of said certifying instance. Description of figures
[0012] Other advantages and particularities of the invention will appear on reading the detailed description of implementations and embodiments which are in no way limiting, with regard to the appended drawings in which: • [Fig.l] illustrates an example of an embodiment of a system according to the invention, • [Fig.2] illustrates a case of use of a system according to the invention, • [Fig.3] illustrates the different stages of certification by a system according to the invention, • [Fig.4] illustrates a sequence diagram of exchanges within the system according to the invention. Description of embodiments
[0013] The embodiments described below being in no way limiting, it will be possible in particular to consider variants of the invention comprising only a selection of characteristics described, subsequently isolated from the other characteristics described, if this selection of characteristics is sufficient to confer a technical advantage. or to differentiate the invention from the prior art. This selection includes at least one feature, preferably functional without structural details, or with only part of the structural details if only this part is sufficient to confer a technical advantage or to differentiate the invention from the prior art.
[0014] In the figures, an element appearing in several figures retains the same reference. Definitions
[0015] Digest: A digest is the result of a hash function that creates a fingerprint of documents, data, etc. A digest is used to validate the integrity of data.
[0016] Digital certification: a process using encryption and asymmetric cryptography to ensure the provenance of digital data.
[0017] [Fig-1] is a diagram of an embodiment of a system according to the invention.
[0018] The system according to the invention comprises: a module 1 for processing certifying instances (100) of digital data, said module comprising an identifier of the user (200) and of certifying systems (300).
[0019] Each of the certifying instances is associated with a storage address of said instance, with a user terminal that owns said instance, and with a non-repudiable ledger (ledgef). The ledger includes an ordered list of elements.
[0020] Each of the elements of the ordered list of elements: • a certificate generated by one of the certification systems, a certificate comprising a type of certificate, a summary of a document, • a timestamp by the certifying system of the time of generation of said certificate, • an electronic signature of said certificate, • a timestamp by the processing module of the moment the element was added to the ordered list, • possibly a pointer to the document.
[0021] The ledger can be implemented as a “smart contract” on a permissionless distributed ledger, such as a blockchain, or any other implementation that guarantees non-repudiation of transactions on the ledger.
[0022] A certifying instance is initialized by a step of registering an actor, identifiable by asymmetric keys, and creating a key for encrypting the data stored in the certifying instance.
[0023] Module 1 implements a function for adding an attestation to a certifying instance.
[0024] Module 1 implements a function for transferring a certifying instance to another user terminal.
[0025] Module 1 implements a function for verifying all the attestations of a certifying body upon receipt of a digest and the certifying body.
[0026] Module 1 can be configured to accept a request to share the certificates comprising a register of a certifying instance with authorization from the actor owning the MFC. The certificates
[0027] A certificate is generated by any certifying system that has data related to the type of certificate requested by a user terminal or other digital system.
[0028] A certificate includes a digest obtained from a file in the certifying system that allows the type of certificate to be validated. A type of certificate corresponds to an assertion by the user terminal. This may include: a file (for example, a photograph or an audio file), a location, a signature, an audit (for example, a human verification of the systems that generated the digest or an automated audit), proximity, the presence of a witness, a residence, a purchase, proof of ownership, a delegation. Delegation-type certificates. Delegation allows you to sign "on behalf" of a person or company. This type of certificate is important for changing the key of a certifying system, and for keeping track of the fact that the signature was recognized at a date prior to the key change.The certificate is electronically signed and time-stamped by the certifying system, a signature which can identify the company or the person responsible for the signature.
[0029] The certifying instance can be configured to encrypt the attestation in its storage and thus make it accessible only to the user terminal associated with the certifying instance, i.e. its owner. The public key of the owner actor will then be used by default to encrypt the attestation.
[0030] It is possible for a certifying system to certify the absence of data linked to a user terminal. In this case the digest will have the value “verified absence”, for example coded by the value -1, or “absence” coded by the value “-2”. “Verified absence” corresponds to a case where there is data which proves that the statement to be certified is false. For example, for the location of a mobile phone, the value “absence” means that the system has no data linked to the user terminal.
[0031] A previous certificate can be invalidated by adding a new certificate with the “error” digest. The invalidated transaction will be pointed to by its identifier in the registry.
[0032] Example of implementation of a system according to the invention
[0033] [Fig.2] illustrates an exemplary embodiment of a method implemented in a system according to the invention.
[0034] A user uses his mobile phone to generate a file, which includes a photograph, located by the GPS of his mobile phone, and metadata.
[0035] The user sends a request to create an instance to module 1, by sending it a digest of the generated file and an electronic signature of the digest, which is illustrated by steps 1 and 2 of [Fig.3].
[0036] Module 1 creates an MFC certifying instance associated with the user terminal.
[0037] A first element is added to the register of the MFC certifying instance. The first element includes: • a certificate generated by the user, the certificate comprising a file type certificate type, the digest of the generated file, a timestamp by the certifying system of the time of generation of said certificate, • an electronic signature of said certificate, • a timestamp by module 1 of the instant the element was added to the ordered list.
[0038] Subsequently, the user sends a certification request for this file to a certification system. To do this, the user terminal sends to the certification system a required type of certification, as well as an identifier of the user terminal with the certification service of this company.
[0039] In the example shown, the certification system is intended to certify the access of the user terminal to the company's Wi-Fi system, which is illustrated by step 3 of [Fig.3].
[0040] Upon receipt of the request, the certifying system collects data from an information system to generate a file relating to the type of certification required, to the identifier of the user terminal.
[0041] The certifying system subsequently calculates a digest and generates a certificate including a timestamp by the certifying system of the time the certificate was created. The certificate is sent, along with its electronic signature, to the user terminal.
[0042] Upon receipt of the certificate and the electronic signature by the user terminal, the latter sends its elements, as well as the address of the certifying authority to module 1.
[0043] Module 1 is then configured to add the certificate and its electronic signature as a new element to the ordered list of elements of the instance.
[0044] Subsequently, the user can send a new certification request for this file to another certification system.
[0045] In the example shown in [Fig.3], step 4, the method involves the addition of a certificate (or link) of proximity verification with an employee's phone.
[0046] In the example shown in [Fig.3], step 5, the method further comprises the addition a certificate (or link) of photo verification by an employee.
[0047] [Fig. 4] illustrates an example of a sequence of a method implemented in a system according to the invention. The references here are specifically linked to [Fig. 4].
[0048] A user 1 uses 1 a mobile application configured to communicate with the system according to the invention. Said mobile application creates on the one hand a photograph and on the other hand addresses 3 a request for creation of instance to the module by sending it a digest of the generated file and an electronic signature of the digest, which is illustrated by steps 1 and 2 of [Fig.3].
[0049] The module creates 4 an MFC certifying instance associated with the user terminal, comprising a register.
[0050] The module returns 5 an address of the certifying instance to the mobile application.
[0051] The mobile application receives 6 an aggregate of the photo.
[0052] The mobile application sends 7 a request to add certificates to the module in sending him the address of the certifying body, a digest of the generated file and an electronic signature of the digest
[0053] A first element is added 8 to the register of the MFC certifying instance. The first element includes: • a certificate generated by the application, the certificate comprising a file-type certificate type, the digest of the generated file, a timestamp by the certifying system of the time of generation of said certificate, • an electronic signature of said certificate, • a timestamp by module 1 of the instant the element was added to the ordered list,
[0054] As a result, the mobile application requires the addition of GPS location to the module.
[0055] A second element is added 10 to the register of the certifying instance. Subsequently, the user sends 11 to a certifying system a request for attestation for this file. To do this, the user terminal sends to the certifying system, a type of attestation required, as well as an identifier of the user terminal with the certifying service of this company.
[0056] In the example shown, the certification system is designed to certify the access of the user terminal to the company's Wi-Fi system.
[0057] Upon receipt of the request, the certifying system collects data from an information system to generate a file relating to the type of certification required, to the identifier of the user terminal.
[0058] The certifying system subsequently calculates a digest 12 and generates a certificate comprising a timestamp by the certifying system of the time of creation of the certificate. In the example illustrated, the certificate is sent 13, along with its electronic signature, to the module.
[0059] Module 1 is then configured to add 14 the attestation and its electronic signature as a new element to the ordered list of elements of the instance. Checking the integrity of a file
[0060] The method according to the invention may comprise a step of verifying the integrity of a file by a user terminal, the file being received from another user terminal.
[0061] To this end, the user terminal implements the following steps: • calculate a digest of the received file, • receive from the other user terminal a storage address of a certifying instance, • generate a request to receive a certifying instance from said storage address and send it to the module (1), • receive from module (1) the certifying instance associated with said storage address, • browse the ordered list of elements of the received certifying instance to determine the presence or absence of a condensate of an attestation which is the same as the calculated condensate
[0062] If the presence of the calculated condensate is verified, the step of verifying the integrity of the file may include one or more steps of verifying the other attestations of the ordered list of elements of said certifying instance.
[0063] For this purpose, the user terminal can send, for example iteratively, a verification request to each of the certifying systems, comprising the attestation.
[0064] Upon receipt of said verification request, the certifying system can verify the integrity of the attestation by recalculating the digest linked to the file used to generate the attestation, and comparing it with the digest contained in the received attestation. If the two digests are equal, the certifying system sends a positive response to the user terminal, otherwise it sends a negative response.
[0065] The user terminal can thus ensure the integrity of the file received from several certification systems, thus increasing its confidence in the integrity of the file received.
[0066] Of course, the invention is not limited to the examples which have just been described and numerous adjustments can be made to these examples without departing from the scope of the invention. In addition, the various characteristics, forms, variants and modes of embodiment of the invention may be combined with each other in various combinations provided that they are not incompatible or mutually exclusive.
Claims
Demands
1. Module (1) for processing certifying instances (100) of digital data, said module comprising an identifier of a user terminal (200) and of certifying systems (300), in which each of the certifying instances is associated with a storage address, a user terminal, and a non-repudiable ledger comprising an ordered list of elements, each of the elements comprising: an attestation generated by one of the certifying systems, the attestation comprising an attestation type, a document digest, a timestamp by the certifying system of the time of generation of said attestation, an electronic signature of said attestation, a timestamp by the processing module of the time of addition of the element to the ordered list, optionally a pointer to the document, said module being further configured to invalidate a previous attestation by adding a new attestation with the digest “error”,The invalidated certificate is identified by its identifier in the register.
2. Data certification system comprising at least one user terminal (200), at least one certification system, and an instance processing module according to the preceding claim.
3. A data certification method implemented in a data certification system according to the preceding claim, comprising a step of verifying the integrity of a file by a user terminal, said file being received from another user terminal, said step comprising the following steps, implemented at the user terminal: a. calculating a hash of the received file, b. receiving from the other user terminal a storage address of a certificate instance, c. generating a request to receive a certificate instance from said storage address and sending it to the module (D, d. receive from module (1) the certificate instance associated with said storage address, e. scan the ordered list of elements of the received certifying instance to determine the presence or absence of a digest of an attestation that is the same as the calculated digest.
