Computer-implemented method and system for anonymization of inspection data

By using smart contracts in distributed database systems, the process of verification data anonymization is solved, and the problem of lack of data anonymization verification and audit in the existing technology is realized, and the automated and audited verification of data anonymization is realized.

CN117546166BActive Publication Date: 2024-11-22SIEMENS AG
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202280044817.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-06-25
Filing Date
2022-05-30
Publication Date
2024-11-22
Estimated Expiration
2042-05-30

AI Technical Summary

Technical Problem

The prior art lacks automation mechanisms to verify whether data is correctly anonymous, and lacks an audit mechanism for the anonymization process.

Method used

By using smart contracts in a distributed database system, reading data privacy rules, generating test data, comparing anonymous data with test data, outputting inspection results, and generating metadata based on the results for verification and storage, ensuring the automation of data anonymization and auditing.

Benefits of technology

It realizes automated verification of data anonymization, reduces individual negligence, provides proof of data anonymization and future audit mechanisms, and ensures data privacy protection.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117546166B_ABST
    Figure CN117546166B_ABST
Patent Text Reader

Abstract

The present invention relates to a computer-implemented method and system for checking the anonymization of data. Anonymized data (D2) is analyzed by a smart contract process based on data privacy rules (PR), so that flags are automatically generated in the event of anomalies. Smart contracts can be managed in a decentralized manner, wherein the anodes of a distributed database (DB) can verify the rules specified in the smart contract and / or evaluate anomalies. To this end, test data (D3) is generated at the data source by applying the data privacy rules (PR) to the original data (D1). The test data (D3) is checked against the anonymized data (D2) and metadata (MD) is generated based on the results of the check. The metadata (MD) is provided to the nodes of the distributed database for further verification.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a computer-implemented method and system and a computer program product for anonymization of inspection data. Background Art

[0002] Data collection is one of the most important aspects to support data analysis, process mining, machine learning and / or artificial intelligence. However, this data collection also raises concerns about data privacy and identification of users based on the data. With increasing importance and regulations being applied to protecting user data privacy, data anonymization techniques can be used to ensure the protection of user identities. Data anonymization basically removes identifiable parts of the data before or during collection and before sending the data to the data collector. There are various technical ways to achieve data anonymization, but regardless of the technology used, the end result should comply with data privacy regulations. However, an automated review mechanism is needed to determine whether the data has been anonymized correctly. Furthermore, there is usually no proof that the anonymization was performed correctly, for example, to be used for later audits.

[0003] US 2020 / 41 0135 A1 discloses a method for providing access to information, comprising method steps for anonymizing data. Summary of the invention

[0004] It is therefore an object of the present invention to provide verification of data anonymization.

[0005] This object is solved by the features of the independent claim. The dependent claims contain further developments of the invention.

[0006] According to a first aspect, the present invention provides a computer-implemented method for checking anonymization of data, the method comprising the following steps:

[0007] - read in the data privacy rules,

[0008] -Store the original data of the first node of the distributed database,

[0009] - reading in anonymized data, wherein the anonymized data is generated by means of an anonymization method and as a function of the original data when the original data is retrieved by the second node of the distributed database,

[0010] - Generate test data by applying data privacy rules to original data,

[0011] - checking at least part of the anonymized data against at least part of the test data and outputting a result of the checking,

[0012] - Generate metadata based on the inspection results,

[0013] as well as

[0014] - Send metadata to a distributed database.

[0015] According to a second aspect, the present invention provides a system for checking data anonymization, the system comprising:

[0016] - a first interface, which is configured to read in data privacy rules,

[0017] - a storage module configured to store raw data of a first node of a distributed database,

[0018] a second interface configured to read in anonymized data, wherein the anonymized data are generated by means of an anonymization method and as a function of the original data when the original data are retrieved by the second node of the distributed database,

[0019] - a test data generator configured to generate test data by applying data privacy rules to original data,

[0020] a checking module configured to check at least part of the test data against at least part of the anonymized data and to output a checking result,

[0021] - a metadata generator, configured to generate metadata based on the inspection results,

[0022] as well as

[0023] - An output module configured to send the metadata into a distributed database.

[0024] Unless otherwise indicated in the following description, the terms "execution", "computation", "computer-aided", "calculation", "discovery", "generation", "configuration", "reconstruction" and the like preferably relate to actions and / or processes and / or processing steps which change and / or generate data and / or transform data into other data, said data being presentable or available as physical variables, in particular, for example, as electrical impulses. In particular, the expression "computer" should be interpreted as broadly as possible, in order to cover in particular all electronic devices having data processing properties.

[0025] Therefore, the computer can be, for example, a personal computer, a server, a programmable logic controller (PLC), a handheld computer system, a palmtop PC device, a mobile radio and other communication devices capable of processing data in a computer-aided manner, a processor for data processing and other electronic devices. The processor can be, in particular, a central processing unit (CPU), a microprocessor or a microcontroller, such as a dedicated integrated circuit or a digital signal processor that may be combined with a memory unit for storing program instructions, etc. As an example, the processor can also be an IC (integrated circuit), in particular an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit), or a DSP (digital signal processor) or a graphics processor GPU (graphics processing unit). The processor can also be understood to mean a virtualized processor, a virtual machine or a soft CPU. As an example, it can also be a programmable processor, which is equipped with a configuration step for performing a method according to an embodiment of the present invention, or it is configured by a configuration step so that the programmable processor implements the features of the method, component, module or other aspects and / or sub-aspects of the embodiments of the present invention.

[0026] In the context of an embodiment of the present invention, "module" can be understood to mean, for example, a processor and / or a memory unit for storing program instructions. As an example, a processor is specifically configured to execute program instructions so that the processor performs functions to realize or execute the method according to an embodiment of the present invention or the steps of the method according to an embodiment of the present invention. As an example, a module can also be a node of a distributed database system, which, for example, performs / implements a specific function / feature of an applicable module. As an example, each module can also be in the form of a separate or independent module. For this reason, for example, an applicable module can include other elements. These elements are, for example, one or more interfaces (for example, a database interface, a communication interface--for example, a network interface, a WLAN interface) and / or an evaluation unit (for example, a processor) and / or a memory unit. An interface can be used for example to exchange (for example, receive, transmit, send or provide) data. An evaluation unit can be used for example to compare, check, process, distribute or calculate data in a computer-assisted and / or automated manner. A memory unit can be used for example to store, retrieve or provide data in a computer-assisted and / or automated manner.

[0027] In the context of embodiments of the present invention, "providing", in particular with respect to data and / or information, may be understood to mean, for example, computer-assisted provision. The provisioning is implemented, for example, via an interface (e.g., a database interface, a network interface, an interface to a memory unit). The interface may be used, for example, to transmit and / or send and / or retrieve and / or receive applicable data and / or information during provisioning.

[0028] Within the context of embodiments of the present invention, "supply" may also be understood to mean, for example, a transaction that loads or stores, for example, a transaction that contains applicable data. As an example, this may be implemented on or by a memory module. "Supply" may also be understood to mean, for example, transmitting (or sending or transferring) applicable data from one node of a blockchain or distributed database system (or its infrastructure) to another node.

[0029] Within the context of embodiments of the present invention, a “smart contract process” may be understood to mean, in particular, a distributed database system or its infrastructure executing program code (eg, control instructions) in a process.

[0030] In the context of embodiments of the present invention, "inserted into a distributed database system" or the like may be understood to mean, for example, that in particular, one or more transactions or data blocks with their transactions are transmitted to one or more nodes of the distributed database system. If these transactions are, for example, successfully verified (e.g., by one or more nodes), these transactions are in particular concatenated with at least one existing data block of the distributed database system as a new data block. For this purpose, applicable transactions are stored, for example, in the new data block. In particular, such verification and / or concatenation may be performed by a trusted node (e.g., a mining node, a blockchain oracle, or a blockchain platform).

[0031] Within the context of embodiments of the present invention, a "transaction" or "transactions" may be understood to mean, for example, a smart contract, a data structure or a transaction data record, in particular, each including one or more transactions. Within the context of embodiments of the present invention, a "transaction" or "transactions" may also be understood to mean data of a transaction, such as a data block of a blockchain. For example, a transaction may in particular include program code that provides a smart contract. As an example, within the context of embodiments of the present invention, a transaction may also be understood to mean a control transaction and / or a confirmation transaction. Alternatively, as an example, a transaction may be a data structure that stores data (e.g., control instructions). For example, a transaction may in particular include program code that provides a smart contract.

[0032] Within the context of embodiments of the present invention, "program code" (e.g., smart contracts) may be understood to mean, for example, a program instruction or a plurality of program instructions, in particular stored in one or more transactions. The program code is in particular executable and, for example, executed by a distributed database system. This may be achieved by means of an execution environment (e.g., a virtual machine), for example, the execution environment or the program code is preferably Turing complete. The program code is preferably executed by the infrastructure of the distributed database system. This involves, for example, a virtual machine implemented by the infrastructure of the distributed database system.

[0033] In the context of embodiments of the present invention, a "smart contract" may be understood to mean, for example, executable program code (see in particular the definition of "program code"). A smart contract is preferably stored in a transaction of a distributed database system (e.g., a blockchain), for example in a data block of the distributed database system. As an example, a smart contract may be executed in the same manner as explained in the definition of "program code", in particular in the context of embodiments of the present invention.

[0034] Within the context of embodiments of the present invention, as an example, a “distributed database”, which may also be referred to as a distributed database system, may be understood to mean, for example, a local distributed database, a blockchain, a distributed ledger, a distributed memory system, a distributed ledger technology (DLT)-based system (DLTS), an anti-revision database system, a cloud, a cloud service, a blockchain in the cloud, or a peer-to-peer database.

[0035] A "distributed database system" may also be understood to mean, for example, a distributed database system having at least some of its nodes and / or devices and / or infrastructure implemented by a cloud. As an example, applicable components are implemented as nodes / devices in the cloud (e.g., virtual nodes in a virtual machine).

[0036] For example, the distributed database system may be a public distributed database system (e.g., a public blockchain) or a closed (or private) distributed database system (e.g., a private blockchain).

[0037] For example, a distributed database system may also be a distributed communication system or a peer-to-peer communication system or a peer-to-peer application for data exchange. For example, this may be a network or a peer-to-peer network. For example, a distributed database system may also be a local distributed database system and / or a local distributed communication system.

[0038] Within the context of embodiments of the present invention, "blockchain node", "node", "node of a distributed database system", etc. may be understood to mean, for example, a device (e.g., a field device), a computer, a smart phone, a client, or a subscriber that performs operations for (utilizing) a distributed database system (e.g., a blockchain). As an example, such a node may execute a transaction of the distributed database system or a data block thereof, or insert or concatenate a new data block with a new transaction into the distributed database system by means of a new data block.

[0039] Within the context of embodiments of the present invention, "data privacy rules", also referred to as privacy rules or (privacy) provisions, may be understood to include definitions, constraints and / or provisions regarding data privacy. Data privacy rules may, for example, be based on data classifications, where data classifications define which data are classified as private. For example, data privacy rules may define which part of a data set is restricted when collecting or storing the data set. Applying a data privacy rule to a data set may, for example, mean deleting or modifying at least a part of the data set to satisfy the data privacy rule.

[0040] In the context of embodiments of the present invention, "anonymization" may be understood as the anonymization of data using known anonymization methods / techniques. Anonymization methods may include, for example, suppression, in which information is removed from the data; generalization, in which information is generalized / coarsened; perturbation, in which information is modified, for example by adding noise to the data; and permutation, in which information is exchanged.

[0041] One advantage of the present invention is to automate the verification of data anonymization, where the automation can be managed by a smart contract executed on a distributed database system. Since such a smart contract is run by a group of nodes of the distributed database system, the chance of individual negligence can be minimized.

[0042] For example, the check can be performed by comparing the content of the data structure of the anonymized data with the content of the data structure of the test data. The check result can then be provided as metadata. The metadata is thus linked to the corresponding original data. Since only the metadata is provided, data privacy is maintained while providing proof about the data anonymization performed. Thus, future auditing of the data anonymization can also be achieved.

[0043] According to an embodiment of the method, in case of a negative check result, the metadata may include information about the deviation of the anonymized data from the test data.

[0044] Thus, the metadata can be further analyzed and / or verified. Deviations of the anonymized data from the test data may be, for example, data fields and / or specific information contained in the anonymized data that are not present in the test data. In case of a positive check result, the metadata preferably only includes information about a correctly performed anonymization.

[0045] According to a further embodiment of the method, the anonymization method may be defined by the second node.

[0046] Preferably, the data collector, ie the second node, can predefine / provide anonymization methods. When collecting / retrieving data from the first node, the anonymization technique should ensure that data privacy rules are met.

[0047] According to a further embodiment of the method, the metadata may include information about the anonymization method.

[0048] Preferably, metadata is automatically generated when the raw data is read / collected by the second node. The metadata may include information about the data anonymization method / technique performed. Preferably, the metadata does not include sensitive information, but only includes information required to verify the data anonymization process.

[0049] According to a further embodiment of the method, the data privacy rules may define which part of the original data needs to be removed.

[0050] To this end, data privacy rules define which part of the data set should not be made public. For example, a data privacy rule may define that the data provider / data owner's name, age, gender, etc. should not be collected by the data collector.

[0051] According to a further embodiment of the method, in the case of a negative check result, the applied anonymization method and / or the second node can be marked.

[0052] For example, auditors can further examine the anonymized data based on this flag.

[0053] According to a further embodiment of the method, the metadata and / or the inspection results may be stored in a distributed database.

[0054] For example, the metadata can be inserted into a distributed database. Thus, information about the data anonymization process can be stored immutably and can be used, for example, for future audits.

[0055] According to a further embodiment of the method, data privacy rules may be defined by selected nodes of the distributed database.

[0056] Preferably, data privacy rules may be managed by a selected subset of the nodes of the distributed database system.

[0057] According to a further embodiment of the method, the metadata may be verified against data privacy rules by at least one selected node of the distributed database and / or an external entity.

[0058] According to a further embodiment of the method, the metadata may be verified by a plurality of selected nodes of the distributed database, and the verification is based on a consensus method performed by the selected nodes.

[0059] This has the advantage, for example, that the anonymization process is checked by several entities, thereby ensuring that the anonymization is performed correctly.

[0060] According to a further embodiment of the method, the method steps may be implemented by means of a smart contract executed by a node of the distributed database.

[0061] Thus, anonymized verification can be automated. Since smart contracts can be run by a group of nodes, the chances of individual oversight are minimized. Furthermore, smart contracts can be updated based on rules / regulations to maintain ongoing compliance.

[0062] According to a further embodiment of the method, the distributed database may be a blockchain or a distributed ledger.

[0063] Furthermore, protection is claimed for a computer program product (a non-transitory computer-readable storage medium having instructions which, when executed by a processor, perform actions), the computer program product having program instructions for performing the aforementioned method according to an embodiment of the invention, wherein one of the methods according to an embodiment of the invention, all the methods according to an embodiment of the invention, or a combination of the methods according to an embodiment of the invention can be performed each time by the computer program product. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] The present invention will be explained in more detail with reference to the accompanying drawings.

[0065] Figure 1 is a first exemplary embodiment of the present invention;

[0066] Figure 2 is a second exemplary embodiment of the present invention; and

[0067] Figure 3 is the third exemplary embodiment of the present invention.

[0068] Identical parts in different figures are marked with the same reference numerals. DETAILED DESCRIPTION

[0069] In addition, in particular, a person skilled in the art (relevant) with knowledge of one or more method claims is of course aware of all conventional options for realizing the product or for implementing in conventional technology, and therefore does not need to be specifically disclosed independently in the description. In particular, these conventional implementation variants known to those skilled in the art can be implemented exclusively by hardware (components) or exclusively by software (components). Alternatively and / or additionally, those skilled in the art can, within the scope of their professional competence, select any combination of hardware (components) and software (components) according to an embodiment of the present invention to the greatest extent possible, so as to implement implementation variants according to an embodiment of the present invention.

[0070] A combination of hardware (components) and software (components) according to embodiments of the present invention may occur, in particular if part of the effects according to embodiments of the present invention are preferably brought about exclusively by dedicated hardware (e.g. a processor in the form of an ASIC or FPGA) and / or another part by software (assisted by a processor and / or memory).

[0071] In particular, in view of the large number of different implementation options, it is impossible, unhelpful or necessary to name all of these implementation options for understanding the embodiments of the present invention. In this regard, in particular, all of the following exemplary embodiments are intended to show only by way of example some ways in which, in particular, such implementations according to the teachings of the embodiments of the present invention can be embodied.

[0072] Therefore, in particular, the features of the individual exemplary embodiments are not limited to the respective exemplary embodiments, but in particular generally relate to embodiments of the present invention. Therefore, features of one exemplary embodiment can also preferably be used as features of another exemplary embodiment, in particular when this does not have to be explicitly stated in the respective exemplary embodiments.

[0073] Figure 1 A first exemplary embodiment of the present invention is shown. It shows a flow chart illustrating method steps of a computer-implemented method for checking anonymization of data.

[0074] The data may be, for example, personal, sensitive, and / or secure data owned by a data source / data owner. For example, data is provided by a data source (e.g., an individual or device). Data may be collected / retrieved from a data source, for example, by a data collector. For example, data may be provided by an individual or group of IoT devices and sensors owned by an entity, and may be collected by another entity that may provide analysis and intelligence based on the data. For example, data may be provided by a group of individuals based on activities (e.g., parking patterns or traffic information), and may be collected by an autonomous driving company for intelligence.

[0075] The method can be implemented by a smart contract process running on a node of a distributed database system. For example, both the data source and the data collector can be nodes of the distributed database system. The method enables automatic verification of data anonymization, for example, by a smart contract process. In addition, information about the performed data anonymization can be inserted into the distributed database.

[0076] The method involves, in a first step S1, reading in data privacy rules. The data privacy rules may, for example, be defined by at least some of the nodes of the distributed database.

[0077] In the next step S2, the original data of the first node of the distributed database is provided. For example, the original data may include sensitive, confidential or personal data parts. For example, when collecting the original data, which data parts need to be removed or modified may be defined by data privacy rules.

[0078] The original data may be retrieved / collected, for example, by a second node of the distributed database system. The second node defines an anonymization method, which is applied to the original data when retrieving the original data, thereby generating anonymized data. In other words, when collecting / retrieving the original data, the original data is modified by means of the anonymization method, so that the data collector retrieves only the anonymized data.

[0079] In a next step S3, the anonymized data is provided. Preferably, the anonymized data is read when it is created and before it is collected by the data collector.

[0080] In the next step S4, test data is generated by applying the data privacy rules to the original data. To this end, the original data is modified to comply with the data privacy rules. Therefore, the test data preferably only includes approved / authorized data portions that comply with the data privacy rules.

[0081] In a next step S5, at least part of the anonymized data is checked against at least part of the test data and the result of the check is output. For example, the anonymized data may be compared with the test data and the result of the comparison returned. It is also possible to randomly select parts of the test data and compare corresponding parts of the anonymized data.

[0082] In the case where the anonymized data does not correspond to the test data, the check result may be negative. In this case, the check result may include information about the deviation of the anonymized data from the test data.

[0083] In the case where the anonymized data matches the test data, the check result may be positive. In this case, the check result may include a record of the status of the anonymized data.

[0084] In the next step S6, metadata is generated according to the inspection result. Preferably, the metadata includes the inspection result.

[0085] In the next step S7, the metadata may be sent and / or inserted into the distributed database. The metadata may, for example, be part of a transaction, which may be verified by at least part of the nodes of the distributed database. Thus, the metadata may be immutably stored in the distributed database.

[0086] The metadata may then be checked, for example, by an auditor (e.g., a node of the distributed database and / or an external auditor). Additionally or alternatively, if the check is negative, the metadata may be verified against data privacy rules. The verification may, for example, be performed by a node of the distributed database and / or an external auditor. Preferably, the verification may be performed by a subset of the nodes of the distributed database and may be based on a consensus method.

[0087] Figure 2 A schematic diagram of an embodiment of a system for anonymizing inspection data is shown.

[0088] The system 100 includes a first interface 101 , a storage module 102 , a second interface 103 , a test data generator 104 , a checking module 105 , a metadata generator 106 , and an output module 107 .

[0089] Preferably, the system can be implemented at least in part by nodes N, N1, N2 of a distributed database DB. The checking of the data anonymization process can be implemented, for example, by executing a smart contract by the nodes of the distributed database. The distributed database DB can be, for example, a blockchain or a distributed ledger.

[0090] The system 100 enables data collection DC of data D1 from a first node N1 by a second node N2, wherein the data is anonymized using a given anonymization method, and automatically checks the result of the anonymization process.

[0091] The first node N1 may be, for example, a device owned by a user. The data stored on the device may include, for example, sensitive, confidential or personal data.

[0092] The first interface 101 is configured to read in data privacy rules PR. The data privacy rules PR are, for example, defined by at least part of the nodes N, N1, N2 of the distributed database DB. Preferably, the data privacy rules PR may be defined in a smart contract.

[0093] The storage module 102 is configured to store the original data D1 of the first node N1. It is also possible that the storage module 102 only references the original data, for example through a link.

[0094] The second interface 103 is configured to read in the anonymized data D2 , wherein the anonymized data D2 is generated from the original data D1 by means of an anonymization method AM when the DC original data D1 is retrieved by the second node N2 .

[0095] The test data generator 104 is configured to generate test data D3 by applying the data privacy rule PR to the original data D1 .

[0096] The checking module 105 is configured to check at least part of the test data D3 against at least part of the anonymized data D2 and output a checking result CR.

[0097] The metadata generator 106 is configured to generate metadata MD, wherein the metadata includes a check result CR. In case of a negative check result CR, i.e. if the anonymized data does not match the test data, the applied anonymization method AM and / or the second node N2 may be marked. The mark may be stored, for example, in a distributed database DB.

[0098] The output module 107 is configured to insert the metadata MD and / or the check result CR into the distributed database. The metadata MD can then be verified, for example, by at least one selected node N of the distributed database DB and / or an external entity against the data privacy rules PR. Alternatively, the metadata MD can be verified by a plurality of selected nodes of the distributed database, and the verification is based on a consensus method performed by the selected nodes.

[0099] Figure 3 Another embodiment of a method for checking anonymization of data is shown. It shows a flow chart illustrating method steps of a computer-implemented method for checking anonymization of data.

[0100] When the data is collected by the data collector, the data is anonymized using anonymization techniques. Smart contracts can be used to analyze the anonymized data based on predefined data privacy rules / regulations and automatically generate flags in case of anomalies or discrepancies. Smart contracts are preferably executed by nodes of a distributed database (such as a blockchain) and can therefore be managed in a decentralized manner. Preferably, the nodes can verify the rules specified in the smart contract and evaluate the anomalies of the data anonymization. The nodes can approve transactions containing information about the anonymization of the data. Therefore, this provides a permanent auditable record about the anonymization of the data, which can be used in the event of future disputes or discrepancies.

[0101] The system performing the following method steps may include the following components: nodes forming a distributed network, smart contracts, data classification for different data types collected, data sources (e.g., individuals or devices from which data is generated), and a management federation, which is a subset of nodes that can verify and maintain a distributed database of anonymization proofs.

[0102] Data classification labels, for example, which data is considered private and needs to be anonymized, and which data can be collected by the data collector. For example, a data classification may define that a name or social security number is private and therefore should not be collected, while other data, for example, can be collected. Essentially, data classification can provide the basis for determining data privacy rules that justify anonymization.

[0103] The federation may include, for example, nodes from the enterprise collecting the data, an auditing entity, and / or nodes from individuals or groups of individuals whose data is being collected.

[0104] According to data privacy regulations, the data to be collected can be defined and classified. This classification divides the data into two categories: first, the actual data collected after anonymization, and second, the metadata associated with the data. This metadata is automatically generated at the source when the data is anonymized.

[0105] Data collection and anonymization proof are performed as follows.

[0106] A smart contract is established for data privacy rules, see step S1. The rules in the smart contract are configured to analyze the metadata from each data read to verify whether the anonymization result complies with the data privacy rules.

[0107] The data may be provided by a data source, see step S2. The reader or collector of the data is free to choose any data anonymization mechanism or technique. When reading / collecting the data, anonymized data is generated with the aid of the anonymization mechanism. The anonymized data may then be provided for verification of the data anonymization process, see step S3.

[0108] Smart contracts can provide definitions of metadata based on data privacy rules, as well as scripts that create metadata when reading data. For example, the script / smart contract can compare the original data from the data source and the anonymized data generated to copy the data. Based on the comparison, metadata can be generated.

[0109] The metadata may be generated, for example, as follows: A small number of random data sets are selected from a data source. A corresponding anonymized data set is obtained based on an anonymization technique. Based on data classification and / or data privacy rules indicating fields that need to be removed for user privacy, the selected original random data set is changed by a script, and a corresponding new data set is output, see step S4. Then, this new data set based on the data privacy rules is compared with the anonymized data set, see step S5. The metadata may then include information about the comparison results.

[0110] This comparison can lead to two different situations of generating metadata, see step S6: If the anonymized data set has correctly omitted the specified data, i.e. a positive check result, the metadata can only record that the state of anonymization is good. If there is a violation of data anonymization, i.e. a negative check result, the metadata can include information about the various data fields stored by the anonymized data set and how it differs from the specified data privacy rules.

[0111] The metadata can then be written to the blockchain network, see step S7. The smart contract can, for example, verify the metadata against the data privacy rules to confirm whether the anonymization complies with the data privacy rules. In the case of a positive check result, the alliance node can verify and sign that the data anonymization complies with the data privacy rules. In the case of a negative check result, the smart contract generates a flag about the data anonymization technology. Based on the flag, an auditor from the alliance node or an external auditor can verify the anonymized data. After the inspection (e.g., manual inspection), the auditor can update the status of the reading entity and the data anonymization technology on the blockchain. The owner or original source of the data can always access the blockchain to access the audit trail of all data reads and the related anonymization report.

[0112] While the present invention has been described in detail with reference to preferred embodiments, it will be understood that the invention is not limited to the disclosed examples and that numerous additional modifications and variations may be made thereto by those skilled in the art without departing from the scope of the invention.

Claims

1. A computer-implemented method for anonymization of inspection data, the method comprising the following steps: - read in (S1) the data privacy rules (PR), - storing (S2) the original data (D1) of the first node (N1) of the distributed database (DB), - reading in (S3) anonymized data (D2), wherein the anonymized data (D2) is generated from the original data by means of an anonymization method (AM) when the original data is retrieved from the second node (N2) of the distributed database, - generating (S4) test data (D3) by applying data privacy rules (PR) to the original data (D1), - checking (S5) at least part of the anonymized data (D2) against at least part of the test data (D3) and outputting a checking result (CR), - generating (S6) metadata (MD) based on the check result (CR), and - sending (S7) the metadata (MD) to a distributed database (DB), wherein the method steps are implemented by smart contracts executed by nodes of the distributed database.

2. The computer-implemented method of claim 1 , wherein: In case of a negative check result (CR), the metadata includes information about the deviations of the anonymized data from the test data.

3. The computer-implemented method according to any one of the preceding claims, wherein: The anonymization method (AM) is defined by the second node (N2).

4. A computer-implemented method according to claim 1 or claim 2, wherein the metadata (MD) comprises information about an anonymization method (AM).

5. The computer-implemented method of claim 1 or claim 2, wherein: Data privacy rules (PR) define which parts of the original data need to be removed.

6. The computer-implemented method of claim 1 or claim 2, wherein: In the case of a negative check result (CR), the applied anonymization method (AM) and / or the second node (N2) is marked.

7. A computer-implemented method according to claim 1 or claim 2, wherein the metadata (MD) and / or the check results (CR) are stored in a distributed database (DB).

8. The computer-implemented method of claim 1 or claim 2, wherein: Data privacy rules (PR) are defined by selected nodes of a distributed database (DB).

9. The computer-implemented method of claim 1 or claim 2, wherein: The metadata (MD) is validated against the data privacy rules (PR) by at least one selected node of the distributed database and / or an external entity.

10. The computer-implemented method of claim 1 or claim 2, wherein: The metadata (MD) is verified by a plurality of selected nodes of the distributed database, and the verification is based on a consensus method performed by the selected nodes.

11. The computer-implemented method of claim 1 or claim 2, wherein: A distributed database (DB) is a blockchain or distributed ledger.

12. Computer program product directly loadable into the internal memory of a digital computer, comprising software code portions for performing the method steps of one of the preceding claims when said computer program product is run on a computer.

13. A system (100) for anonymization of inspection data, the system comprising: - a first interface (101) configured to read in data privacy rules (PR), - a storage module (102) configured to store the original data (D1) of the first node (N1) of the distributed database, a second interface (103) configured to read in anonymized data (D2), wherein the anonymized data are generated from the original data (D1) by means of an anonymization method (AM) when the original data are retrieved by a second node of the distributed database, - a test data generator (104) configured to generate test data (D3) by applying data privacy rules to original data, a checking module (105) configured to check at least part of the test data (D3) against at least part of the anonymized data (D2) and to output a checking result (CR), - a metadata generator (106) configured to generate metadata (MD) based on the check result (CR), and - An output module (107) configured to send the metadata (MD) to a distributed database.

Citation Information

Patent Citations

  • Data security

    US20200410135A1

  • Logistics privacy protection method and system based on block chain and readable storage medium

    CN110719176A

  • Method and system for providing anonymized data from a database

    US20150067881A1