Enterprise credit data privacy protection method and device based on zero-knowledge proof technology

Abstract

The embodiment of the invention provides an enterprise credit data privacy protection method and device based on a zero-knowledge proof technology, and the method comprises the steps: obtaining enterprise credit data, and encrypting the data; adaptively selecting a zero-knowledge proof protocol according to service requirements; generating a pair of public key and private key, and selecting a zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and the enterprise credit data; transmitting the zero-knowledge proof and the public key thereof to a third party, so that the third party performs verification by using the received zero-knowledge proof and the public key; receiving a verification result fed back by the third party; through the zero-knowledge proof, the enterprise can prove the credit condition without disclosing specific credit data, so that sensitive information and commercial secrets are protected, the risk of data leakage is reduced, in addition, the enterprise does not need to share any sensitive data, does not need to decrypt and share the data, and can complete credit verification only by providing the zero-knowledge proof. And the potential risk caused by data sharing is greatly reduced.

Description

Technical Field

[0001] The present application relates to the technical field of credit data privacy protection, and specifically, to a method and device for protecting the privacy of enterprise credit data based on zero-knowledge proof technology. Background Art

[0002] Data encryption is the process of converting data into a form that can only be interpreted by people with the correct key, so as to protect the security of data during storage and transmission. The most common method for encrypting corporate credit data is the AES algorithm. AES (Advanced Encryption Standard) is a widely used symmetric key encryption standard. AES is designed to replace the previous DES algorithm, providing higher security and the ability to adapt to future computing power growth.

[0003] Although AES encryption can effectively protect corporate credit data, in some cases, attackers can still infer certain information by analyzing the patterns, metadata, or other side channel information of encrypted data. For example, frequent access patterns may reveal certain behaviors or trends. In addition, when encrypted data needs to be used for calculation or analysis, it is usually necessary to decrypt it first, which may also expose corporate credit data to potential risks. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a method and device for protecting the privacy of enterprise credit data based on zero-knowledge proof technology, so as to solve the problem that existing methods usually need to decrypt encrypted data before using it for calculation or analysis, which may expose the enterprise credit data to potential risks and cause data leakage.

[0005] In a first aspect, the embodiment of the present application provides a method for protecting the privacy of enterprise credit data based on zero-knowledge proof technology, including: Obtain enterprise credit data and encrypt the data; Adaptively select zero-knowledge proof protocols based on business needs; Generate a pair of public and private keys, and select the zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and corporate credit data; Transmitting the zero-knowledge proof and its public key to a third party, so that the third party can verify it using the received zero-knowledge proof and public key; Receive third-party feedback on validation results.

[0006] In the above implementation process, the embodiment of the present application obtains enterprise credit data and encrypts the data; adaptively selects a zero-knowledge proof protocol according to business needs; generates a pair of public keys and private keys, and selects a zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and the enterprise credit data; transmits the zero-knowledge proof and its public key to a third party, so that the third party uses the received zero-knowledge proof and public key for verification; receives the verification results fed back by the third party; through zero-knowledge proof, the enterprise can prove its credit status without disclosing specific credit data, so that sensitive information and business secrets can be protected, reducing the risk of data leakage. In addition, the enterprise does not need to share any sensitive data, does not need to decrypt and share the data, and only needs to provide zero-knowledge proof to complete credit verification, which greatly reduces the potential risks brought by data sharing.

[0007] Furthermore, the adaptive selection of the zero-knowledge proof protocol according to business requirements includes: Adaptively select the zero-knowledge proof protocol based on data type, security requirements, performance requirements, and application scenarios.

[0008] In the above implementation process, enterprises can adaptively select the zero-knowledge proof protocol that suits their credit data privacy protection needs to achieve efficient and secure data protection.

[0009] Furthermore, the method of selecting a zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and the enterprise credit data includes: Determine the zero-knowledge proof protocol and pre-process the enterprise credit data; Trusted setup for zero-knowledge proof protocols; Build a zero-knowledge proof system and input the enterprise credit data into the zero-knowledge proof system to generate a zero-knowledge proof; Perform preliminary verification on the generated zero-knowledge proof.

[0010] In the above implementation process, it is ensured that only the authenticity of the enterprise credit data is proved without revealing the specific data content.

[0011] Further, the third party uses the received zero-knowledge proof and public key to perform verification, including: Confirm the origin of public keys and zero-knowledge proofs; Understand the zero-knowledge proof protocol, obtain the corresponding verification algorithm and parameters, parse the public key and zero-knowledge proof, execute the verification algorithm, and check the verification results; Record validation results, take appropriate actions, and update validation regularly.

[0012] In the above implementation process, the third party uses the received public key and certificate to verify and confirm the authenticity of the enterprise credit data.

[0013] Furthermore, the adaptive selection of the zero-knowledge proof protocol according to the data type, security requirements, performance requirements and application scenarios includes: If the enterprise credit data is discrete numerical data, use a zero-knowledge proof protocol based on discrete logarithms; For cases involving continuous numerical data, a zero-knowledge proof protocol based on elliptic curve cryptography is used; If the data contains text information, encode the text into numerical data, and then select the zero-knowledge proof protocol based on the characteristics of the converted data; Analyze the type of attack faced and select the zero-knowledge proof protocol; To meet the needs of resisting quantum computing attacks, we choose a zero-knowledge proof protocol based on quantum-resistant cryptography; Determine the required security level based on the sensitivity of the enterprise credit data and select a protocol with strict security certification; Evaluate the enterprise's computing resources, including server performance and network bandwidth, consider the proof generation time and verification time of the protocol, and select a protocol that meets the enterprise's business needs; Consider the communication overhead of data transmission and the interactivity of the protocol, and select a protocol that meets your needs; Select the corresponding zero-knowledge proof protocol according to different enterprise credit data application scenarios.

[0014] Furthermore, the zero-knowledge proof protocol is determined to pre-process the enterprise credit data, including: Select a zero-knowledge proof protocol based on the characteristics, security requirements, performance requirements, and application scenarios of corporate credit data; Clean and organize corporate credit data to remove noise and outliers; Convert enterprise credit data into a format that matches the zero-knowledge proof protocol; The trusted setting of the zero-knowledge proof protocol includes: When performing a trusted setup, select a scenario and random number generator that meet the requirements and generate public parameters; The step of constructing a zero-knowledge proof system and inputting the enterprise credit data into the zero-knowledge proof system to generate a zero-knowledge proof includes: According to the selected zero-knowledge proof protocol, define the logical structure of the proof, select the encryption algorithm and hash function to build the corresponding zero-knowledge proof system; For the polynomial commitment-based protocol, a polynomial commitment scheme is constructed and the enterprise credit data is encoded into a polynomial; Input the enterprise credit data into the zero-knowledge proof system and generate zero-knowledge proof through encryption and hash operations; The preliminary verification of the generated zero-knowledge proof includes: Sending the generated zero-knowledge proof and the corresponding statement to the verifier to instruct the verifier to verify the received proof using the verification algorithm of the zero-knowledge proof protocol; wherein the verification process includes decryption, hash operation and logic verification of the proof; If the certificate is verified, the enterprise credit data and the corresponding certificate will be stored in a secure database.

[0015] Furthermore, the source of the confirmed public key and zero-knowledge proof includes: Verify the channel of the public key and zero-knowledge proof to confirm that the channel is relevant to the expected corporate credit data verification; Check the integrity of public keys and zero-knowledge proofs; The understanding of the zero-knowledge proof protocol, obtaining the corresponding verification algorithm and parameters, parsing the public key and the zero-knowledge proof, executing the verification algorithm, and checking the verification result include: Understand the principles and verification methods of the zero-knowledge proof protocol used; According to the zero-knowledge proof protocol, obtain the corresponding verification algorithm and parameters, wherein the parameters include protocol-specific mathematical constants and hash functions; Parse the public key and extract the key information contained therein, where the key information includes: encryption algorithm parameters and key length; Parse zero-knowledge proofs and understand their structure and content, where zero-knowledge proofs include encrypted data and logical assertions; Take the public key and zero-knowledge proof as input and run the verification algorithm, which includes a series of mathematical operations and logical judgments; Perform verification according to the steps specified in the protocol, which include performing encryption and decryption operations, calculating hash values, and checking logical relationships; After the verification algorithm is executed, a verification result is output; If the verification result is true, it means that the enterprise credit data statement is credible; if the verification result is false, it means that the zero-knowledge proof is invalid and an investigation is conducted; The recording of verification results, taking corresponding actions, and regularly updating the verification include: Record the verification time, the source of the public key and zero-knowledge proof, and the verification result; If the verification result is false, record the relevant error information and abnormal conditions; Take appropriate actions based on the verification results; If the verification result is true, continue to use the enterprise credit data for subsequent business processing; If the verification result is false, refuse to use the data; The verification process is updated regularly, and the validity of public keys and certificates is checked regularly.

[0016] In a second aspect, the embodiment of the present application provides an enterprise credit data privacy protection device based on zero-knowledge proof technology, including: A data acquisition module is used to acquire enterprise credit data and encrypt the data; The protocol selection module is used to adaptively select the zero-knowledge proof protocol according to business needs; The proof generation module is used to generate a pair of public and private keys, and select the zero-knowledge proof protocol to generate zero-knowledge proof based on the private key and corporate credit data; A proof verification module, used to transmit the zero-knowledge proof and its public key to a third party, so that the third party can use the received zero-knowledge proof and public key for verification; The verification feedback module is used to receive verification results from third-party feedback.

[0017] In a third aspect, an embodiment of the present application provides an electronic device, including: A processor, a memory and a bus, wherein the processor is connected to the memory via the bus, and the memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, they are used to implement the enterprise credit data privacy protection method based on zero-knowledge proof technology as described above.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a server, the enterprise credit data privacy protection method based on zero-knowledge proof technology as described above is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 A flowchart of a method for protecting the privacy of enterprise credit data based on zero-knowledge proof technology provided in an embodiment of the present application; Figure 2 It is a structural schematic diagram of an enterprise credit data privacy protection device based on zero-knowledge proof technology provided in an embodiment of the present application; Figure 3 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0022] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0023] Data encryption is the process of converting data into a form that can only be interpreted by people with the correct key, in order to protect the security of data during storage and transmission. The most common method for encrypting corporate credit data is the AES algorithm.

[0024] AES (Advanced Encryption Standard) is a widely used symmetric key encryption standard. AES is designed to replace the previous DES algorithm, providing higher security and the ability to adapt to future computing power growth. AES supports three key lengths: 128 bits, 192 bits, and 256 bits, of which 128 bits is the most commonly used version.

[0025] The AES algorithm uses a block encryption method with a fixed block size of 128 bits (16 bytes). Its core is a series of repeated permutation-permutation network (SPN) structures, called "rounds". The AES encryption process usually includes multiple rounds (the specific number of rounds depends on the key length: 10 rounds for 128-bit keys, 12 rounds for 192-bit keys, and 14 rounds for 256-bit keys), each of which contains the following four basic operations: Byte substitution (SubBytes): Use a fixed S-box (permutation box) to perform non-linear substitution on each byte; Row shift (ShiftRows): Circularly shift each row in the data block to the left by a specified number of bits; Column mixing (MixColumns): Each column of the data block is confused by matrix multiplication operations, except for the last round; Round key addition (AddRoundKey): XOR the round key with the data block. The round key is derived from the original key through the key scheduling algorithm.

[0026] The decryption process is the reverse operation of the encryption process, using the same key and inverse transformation to restore the original data. Although AES encryption can effectively protect corporate credit data, in some cases, attackers can still infer certain information by analyzing the patterns, metadata, or other side channel information of encrypted data. For example, frequent access patterns may reveal certain behaviors or trends. In addition, when encrypted data needs to be used for calculation or analysis, it is usually necessary to decrypt it first, which may also expose corporate credit data to potential risks.

[0027] Based on this, an embodiment of the present application proposes a method for protecting the privacy of enterprise credit data based on zero-knowledge proof technology to solve the above problems.

[0028] Please see Figure 1 , Figure 1 A flowchart of a method for protecting the privacy of enterprise credit data based on zero-knowledge proof technology provided in an embodiment of the present application. The method for protecting the privacy of enterprise credit data based on zero-knowledge proof technology includes: 100. Obtain enterprise credit data and encrypt the data.

[0029] Optionally, necessary corporate credit data is first collected, such as financial statements, credit scores, transaction records, etc. Wherein, the collected data is encrypted before storage to prevent unauthorized access.

[0030] 200. Adaptively select zero-knowledge proof protocols based on business needs.

[0031] Specifically, the zero-knowledge proof protocol is adaptively selected based on the data type, security requirements, performance requirements, and application scenarios.

[0032] Among them, the zero-knowledge proof protocol is adaptively selected according to the data type.

[0033] Optionally, if the enterprise credit data is discrete numerical data, a zero-knowledge proof protocol based on discrete logarithms is used; illustratively, if the enterprise credit data is mainly discrete numerical data, such as credit ratings, number of defaults, etc., a zero-knowledge proof protocol based on discrete logarithms can be used, such as the Schnorr protocol or its variants. Such protocols are relatively efficient in processing integer operations.

[0034] Optionally, for cases involving continuous numeric data, a zero-knowledge proof protocol based on elliptic curve cryptography is used; illustratively, for cases involving a large amount of continuous numeric data, such as amount data in financial statements, a zero-knowledge proof protocol based on elliptic curve cryptography can be used. Elliptic curve cryptography may have higher security and efficiency when processing continuous numerical values.

[0035] Optionally, if the data contains text information, encode the text into numerical data, and then select the zero-knowledge proof protocol based on the characteristics of the converted data.

[0036] Among them, the zero-knowledge proof protocol is adaptively selected according to the data scale.

[0037] Alternatively, for small-scale corporate credit data, you can choose a zero-knowledge proof protocol with relatively low computational complexity, such as the Groth16 protocol in succinct non-interactive zero-knowledge proofs (zk-SNARKs). This protocol has low computational overhead in the proof generation and verification stages and is suitable for processing small amounts of data.

[0038] Optionally, when the data scale is large, it is necessary to consider protocols with higher scalability. For example, the zk-STARKs protocol has better performance on large-scale data because it does not rely on a trusted setup and the verification time is logarithmic with the proof size.

[0039] Among them, the zero-knowledge proof protocol is adaptively selected considering security requirements.

[0040] Optionally, analyze the attack type faced and select a zero-knowledge proof protocol; illustratively, analyze the possible attack types faced, such as selected plaintext attack, selected ciphertext attack, etc. If there is a powerful attacker, it may be necessary to select a zero-knowledge proof protocol with higher security.

[0041] Optionally, to resist quantum computing attacks, a zero-knowledge proof protocol based on quantum-resistant cryptography is selected; for example, a protocol based on lattice cryptography.

[0042] Optionally, determine the required security level based on the sensitivity of the enterprise credit data and select a protocol with strict security proof, such as a zero-knowledge proof protocol that has been strictly mathematically proven. In addition, consider the security assumptions of the protocol, such as whether it is based on strong cryptographic assumptions, and the reliability of these assumptions in practical applications.

[0043] Optionally, evaluate the computing resources of the enterprise, where computing resources include server performance and network bandwidth. If computing resources are limited, a zero-knowledge proof protocol with low computing overhead can be selected to ensure the operating efficiency of the system. Optionally, consider the proof generation time and verification time of the protocol and select a protocol that meets the business needs of the enterprise; for example, in a real-time credit assessment scenario, a protocol with a shorter verification time needs to be selected.

[0044] Optionally, considering the communication overhead of data transmission and the interactivity of the protocol, a protocol that meets the requirements is selected; exemplarily, if the communication overhead of data transmission is an important consideration, a zero-knowledge proof protocol with a smaller proof size can be selected to reduce the amount of data transmitted over the network; exemplarily, considering the interactivity of the protocol, non-interactive zero-knowledge proof protocols usually have lower communication overhead and are suitable for use in poor network environments.

[0045] Optionally, a corresponding zero-knowledge proof protocol may be selected according to different enterprise credit data application scenarios. For example, different enterprise credit data application scenarios may have different requirements for zero-knowledge proof protocols. For example, in a credit loan approval scenario, it may be necessary to quickly verify the credit status of the enterprise. In this case, a protocol with a shorter verification time may be selected.

[0046] For example, in a supply chain finance scenario, multiple parties may need to jointly verify the corporate credit data. In this case, it is necessary to select a zero-knowledge proof protocol that supports multi-party verification.

[0047] For example, considering the requirements of local laws and regulations on data privacy protection, some regions may recognize or restrict specific types of zero-knowledge proof protocols, and enterprises need to choose appropriate protocols based on local laws.

[0048] In some embodiments, different zero-knowledge proof protocols are theoretically analyzed to compare their security, performance, and functional characteristics; illustratively, reference may be made to academic literature, evaluation reports of cryptography research institutions, etc.

[0049] In some embodiments, candidate zero-knowledge proof protocols are tested in a real environment to evaluate their actual effectiveness in protecting the privacy of corporate credit data; illustratively, simulated data or a subset of real data can be used for testing to compare the performance and security of different protocols.

[0050] In some embodiments, the maintainability of the protocol is considered, including the update frequency of the protocol, community support, etc.; illustratively, selecting a protocol with active community support can ensure that security vulnerabilities or performance issues can be fixed in a timely manner when they occur.

[0051] As described above, the embodiments of the present application enable enterprises to adaptively select a zero-knowledge proof protocol that suits their credit data privacy protection needs to achieve efficient and secure data protection.

[0052] 300. Generate a pair of public and private keys, and select a zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and corporate credit data.

[0053] 310. Determine the zero-knowledge proof protocol and pre-process the enterprise credit data.

[0054] 311. Select a zero-knowledge proof protocol based on the characteristics, security requirements, performance requirements, and application scenarios of corporate credit data.

[0055] 312. Clean and organize corporate credit data to remove noise and outliers.

[0056] Optionally, the corporate credit data is cleaned and organized to remove noise and outliers; if the data contains sensitive information, it needs to be encrypted or anonymized to ensure the privacy of the data.

[0057] 313. Convert enterprise credit data into a format that matches the zero-knowledge proof protocol; In addition, the data is converted into a format suitable for the zero-knowledge proof protocol. For example, for some protocols, it may be necessary to represent the data in the form of a polynomial or matrix.

[0058] 320. Perform trusted setup for zero-knowledge proof protocol.

[0059] When performing trusted settings, select scenarios and random number generators that meet the requirements and generate public parameters.

[0060] Specifically, for some zero-knowledge proof protocols, such as zk-SNARKs, a trusted setup is required, which usually involves generating a set of public parameters that are used to generate and verify the proof; at the same time, the trusted setup needs to be performed in a secure environment to ensure the security of the parameters.

[0061] In addition, during the trusted setup process, it is necessary to select a suitable random number generator and ensure that the generated parameters are sufficiently random and secure.

[0062] 330. Build a zero-knowledge proof system and input the enterprise credit data into the zero-knowledge proof system to generate a zero-knowledge proof.

[0063] 331. According to the selected zero-knowledge proof protocol, define the logical structure of the proof, select the encryption algorithm and hash function to build the corresponding zero-knowledge proof system.

[0064] 332. For the protocol based on polynomial commitment, a polynomial commitment scheme is constructed and the enterprise credit data is encoded into a polynomial.

[0065] 333. Input the enterprise credit data into the zero-knowledge proof system and generate zero-knowledge proof through encryption and hash operations.

[0066] Among them, in the process of generating the certificate, attention should be paid to protecting the randomness of the certificate to prevent attackers from inferring the content of the enterprise credit data by analyzing the randomness of the certificate.

[0067] 340. Perform preliminary verification on the generated zero-knowledge proof.

[0068] Specifically, the generated zero-knowledge proof and the corresponding statement are sent to the verifier to instruct the verifier to verify the received proof using the verification algorithm of the zero-knowledge proof protocol; wherein the verification process includes decryption, hash operation and logic verification of the proof.

[0069] Among them, Ming is usually an assertion about the company's credit data, such as "the company's credit rating is A."

[0070] Specifically, if the certificate is verified, the enterprise credit data and the corresponding certificate are stored in a secure database.

[0071] Optionally, if the proof passes verification, the verifier can accept the statement and consider that the enterprise credit data meets the corresponding conditions; if the proof fails verification, the verifier can reject the statement and request more evidence or regenerate the proof.

[0072] Among them, if the proof is verified, the enterprise credit data and the corresponding proof can be stored in a secure database for subsequent query and use; when storing data, attention should be paid to protecting the privacy and security of the data, such as using encrypted storage or access control mechanisms.

[0073] Among them, corporate credit data may change over time, so the zero-knowledge proof needs to be updated regularly; the process of updating the proof can be similar to the process of generating the proof, but it is necessary to consider the changes in the data and the validity of the proof.

[0074] The enterprise transmits the generated zero-knowledge proof and its public key to a third party that needs verification (such as a partner or regulator). The third party uses the received public key and proof to verify the authenticity of the enterprise's credit data. During the verification process, the third party cannot obtain any detailed information about the enterprise's specific credit data.

[0075] As described above, the embodiments of the present application ensure that only the authenticity of the enterprise credit data is proven without revealing the specific data content.

[0076] 400. Transmit the zero-knowledge proof and its public key to a third party, so that the third party uses the received zero-knowledge proof and public key for verification.

[0077] 410. Confirm the source of public keys and zero-knowledge proofs.

[0078] Verify the specific channels of public keys and zero-knowledge proofs, and confirm that the channels are related to the expected corporate credit data verification; check the integrity of public keys and zero-knowledge proofs. Thus, ensure that the public keys and proofs come from trusted channels and are related to the expected corporate credit data verification; check the integrity of public keys and proofs to confirm that they have not been tampered with during transmission.

[0079] 420. Understand the zero-knowledge proof protocol, obtain the corresponding verification algorithm and parameters, parse the public key and zero-knowledge proof, execute the verification algorithm, and check the verification results.

[0080] 421. Understand the principles and verification methods of the zero-knowledge proof protocol used.

[0081] Specifically, you should be familiar with the principles and verification methods of the zero-knowledge proof protocol used. Different protocols may have different verification processes and mathematical foundations. You should understand the security assumptions of the protocol and the reliability guarantees of the verification.

[0082] 422. According to the zero-knowledge proof protocol, obtain corresponding verification algorithms and parameters, wherein the parameters include protocol-specific mathematical constants and hash functions.

[0083] Thus, the correctness and completeness of the verification algorithm and parameters are ensured.

[0084] 423. Parse the public key and extract the key information contained therein, wherein the key information includes: parameters of the encryption algorithm and key length.

[0085] 424. Analyze zero-knowledge proof and understand its structure and content. Zero-knowledge proof includes encrypted data and logical assertions.

[0086] Thereby, the authenticity of the enterprise credit data is verified.

[0087] 425. Take the public key and zero-knowledge proof as input and run the verification algorithm, where the verification algorithm includes a series of mathematical operations and logical judgments.

[0088] Thus, the validity of the certificate is guaranteed.

[0089] 426. Verification is performed according to the steps specified in the protocol, which verification steps include performing encryption and decryption operations, calculating hash values, and checking logical relationships.

[0090] 427. After the verification algorithm is executed, a verification result is output.

[0091] The verification result is usually a Boolean value, indicating whether the proof is valid.

[0092] 428. If the verification result is true, it means that the declaration of the enterprise credit data is credible; if the verification result is false, it means that the zero-knowledge proof is invalid and an investigation is conducted.

[0093] 430. Record verification results, take appropriate actions, and update verification regularly.

[0094] 431. Record the verification time, the source of the public key and zero-knowledge proof, and the verification result.

[0095] 432. If the verification result is false, record the relevant error information and abnormal conditions.

[0096] Optionally, the verification results should be recorded for subsequent query and audit, and the record should include information such as the time of verification, the source of the public key and certificate, and the verification result. If the verification result is false, the relevant error information and abnormal conditions should be recorded for troubleshooting and problem solving.

[0097] 433. Take corresponding actions based on the verification results.

[0098] 434. If the verification result is true, continue to use the enterprise credit data for subsequent business processing.

[0099] 435. If the verification result is false, refuse to use the data.

[0100] For example, take corresponding actions based on the verification result; if the verification result is true, you can continue to use the enterprise credit data for subsequent business processing, such as loan approval, cooperation decision-making, etc.; if the verification result is false, you should refuse to use the data and notify the relevant parties, and you may need to communicate with the data provider to request re-providing of proof or solving data problems.

[0101] 436. Regularly update the verification process and regularly check the validity of public keys and certificates.

[0102] Understandably, since corporate credit data may change over time or new security vulnerabilities may be discovered in zero-knowledge proof protocols, third parties should regularly update the verification process.

[0103] Therefore, the validity of public keys and certificates is checked regularly to ensure the authenticity and reliability of data; the frequency of updates can be determined based on business needs and risk assessment.

[0104] As mentioned above, when a third party uses the received public key and certificate for verification, it needs to carefully follow the provisions of the zero-knowledge proof protocol to ensure the accuracy and reliability of the verification process. At the same time, it should remain vigilant and promptly handle problems that arise during the verification process to protect its own interests and data security.

[0105] 500. Receive verification results from third-party feedback.

[0106] Specifically, after completing the verification, the third party will provide feedback on the verification results to the enterprise to ensure that the verification process is transparent and traceable.

[0107] As described above, the embodiment of the present application obtains enterprise credit data and encrypts the data; adaptively selects a zero-knowledge proof protocol according to business needs; generates a pair of public keys and private keys, and selects a zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and the enterprise credit data; transmits the zero-knowledge proof and its public key to a third party, so that the third party uses the received zero-knowledge proof and public key for verification; receives the verification results fed back by the third party; through zero-knowledge proof, an enterprise can prove its credit status without disclosing specific credit data, so that sensitive information and business secrets can be protected, reducing the risk of data leakage. In addition, the enterprise does not need to share any sensitive data, does not need to decrypt and share the data, and only needs to provide zero-knowledge proof to complete credit verification, which greatly reduces the potential risks brought by data sharing.

[0108] The embodiments of the present application have a high degree of privacy protection: Information isolation: Through zero-knowledge proof, an enterprise can prove its credit status without disclosing specific credit data, which means that sensitive financial information and business secrets are protected, reducing the risk of data leakage; Prevention of side-channel attacks: Traditional encryption methods may expose certain information when data is used, while zero-knowledge proof avoids possible side-channel attacks by only verifying the authenticity of the statement.

[0109] The embodiments of the present application have an enhanced trust mechanism: Transparency: The third party only has access to the proof rather than the original data during the verification process, which enhances the transparency of the verification while retaining the company's trade secrets, which helps to build trust with partners, customers and regulators: Verifiability: All parties involved can independently verify the authenticity of the proof, thereby improving the credibility of the entire credit assessment process.

[0110] The embodiments of the present application have the advantages of reducing the risk of data leakage: minimizing data sharing: enterprises do not need to share any sensitive data, do not need to decrypt and share data, and only need to provide zero-knowledge proof to complete credit verification, which greatly reduces the potential risks brought by data sharing.

[0111] The above steps are not to be performed in a strict order as described in the numbers, but should be understood as an overall solution.

[0112] In the second aspect, based on the above embodiments, Figure 2 A schematic diagram of the structure of a corporate credit data privacy protection device based on zero-knowledge proof technology provided in an embodiment of the present application. Figure 2 The enterprise credit data privacy protection device based on zero-knowledge proof technology provided in this embodiment specifically includes: a data acquisition module 201, a protocol selection module 202, a proof generation module 203, a proof verification module 204 and a verification feedback module 205.

[0113] Among them, the data acquisition module 201 is used to obtain enterprise credit data and encrypt the data; the protocol selection module 202 is used to adaptively select the zero-knowledge proof protocol according to business needs; the proof generation module 203 is used to generate a pair of public keys and private keys, and based on the private key and enterprise credit data, select the zero-knowledge proof protocol to generate a zero-knowledge proof; the proof verification module 204 is used to transmit the zero-knowledge proof and its public key to a third party, so that the third party can use the received zero-knowledge proof and public key for verification; the verification feedback module 205 is used to receive the verification results fed back by the third party.

[0114] As described above, the embodiment of the present application obtains enterprise credit data and encrypts the data; adaptively selects a zero-knowledge proof protocol according to business needs; generates a pair of public keys and private keys, and selects a zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and the enterprise credit data; transmits the zero-knowledge proof and its public key to a third party, so that the third party uses the received zero-knowledge proof and public key for verification; receives the verification results fed back by the third party; through zero-knowledge proof, an enterprise can prove its credit status without disclosing specific credit data, so that sensitive information and business secrets can be protected, reducing the risk of data leakage. In addition, the enterprise does not need to share any sensitive data, does not need to decrypt and share the data, and only needs to provide zero-knowledge proof to complete credit verification, which greatly reduces the potential risks brought by data sharing.

[0115] The enterprise credit data privacy protection device based on zero-knowledge proof technology provided in the embodiment of the present application can be used to execute the enterprise credit data privacy protection method based on zero-knowledge proof technology provided in the above embodiment, and has corresponding functions and beneficial effects.

[0116] On the third aspect, the embodiments of the present application also provide an electronic device, which can integrate the enterprise credit data privacy protection device based on zero-knowledge proof technology provided by the embodiments of the present application. Figure 3 Schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 3 The electronic device includes: an input device 33, an output device 34, a memory 32 and one or more processors 31; the memory 32 is used to store one or more programs; when the one or more programs are executed by the one or more processors 31, the one or more processors 31 implement the enterprise credit data privacy protection method based on zero-knowledge proof technology as provided in the above embodiment. The input device 33, the output device 34, the memory 32 and the processor 31 can be connected by a bus or other means. Figure 3 The example of connecting through bus is taken in the following.

[0117] The processor 31 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 32, that is, implements the above-mentioned enterprise credit data privacy protection method based on zero-knowledge proof technology.

[0118] The electronic device provided above can be used to execute the enterprise credit data privacy protection method based on zero-knowledge proof technology provided in the above embodiment, and has corresponding functions and beneficial effects.

[0119] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the enterprise credit data privacy protection method based on zero-knowledge proof technology as described above, and can achieve the same beneficial effects.

[0120] Of course, the storage medium containing computer executable instructions provided in an embodiment of the present application is not limited to the enterprise credit data privacy protection method based on zero-knowledge proof technology as described above, and can also execute related operations in the enterprise credit data privacy protection method based on zero-knowledge proof technology provided in any embodiment of the present application.

[0121] In a fifth aspect, the embodiments of the present application also provide a computer program product, and the methods described in the various embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the processes or functions described in the various embodiments of the present application are executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, a core network device, an OAM (Open Application Model) or other programmable device.

[0122] The computer program or instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0123] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0124] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0125] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for enabling an electronic device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, and other media that can store program codes.

[0126] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0127] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0128] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A method for protecting the privacy of enterprise credit data based on zero-knowledge proof technology, characterized in that: The method comprises: Obtain enterprise credit data and encrypt the data; Adaptively select zero-knowledge proof protocols based on business needs; Generate a pair of public and private keys, and select the zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and corporate credit data; Transmitting the zero-knowledge proof and its public key to a third party, so that the third party can verify it using the received zero-knowledge proof and public key; Receive third-party feedback on validation results.

2. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 1 is characterized in that: The adaptive selection of the zero-knowledge proof protocol according to business needs includes: Adaptively select the zero-knowledge proof protocol based on data type, security requirements, performance requirements, and application scenarios.

3. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 1 is characterized in that: The method of selecting a zero-knowledge proof protocol to generate a zero-knowledge proof based on the private key and the enterprise credit data includes: Determine the zero-knowledge proof protocol and pre-process the enterprise credit data; Trusted setup for zero-knowledge proof protocols; Build a zero-knowledge proof system and input the enterprise credit data into the zero-knowledge proof system to generate a zero-knowledge proof; Perform preliminary verification on the generated zero-knowledge proof.

4. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 1 is characterized in that: The third party uses the received zero-knowledge proof and public key to perform verification, including: Confirm the origin of public keys and zero-knowledge proofs; Understand the zero-knowledge proof protocol, obtain the corresponding verification algorithm and parameters, parse the public key and zero-knowledge proof, execute the verification algorithm, and check the verification results; Record validation results, take appropriate actions, and update validation regularly.

5. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 2 is characterized in that: The adaptive selection of the zero-knowledge proof protocol according to the data type, security requirements, performance requirements and application scenarios includes: If the enterprise credit data is discrete numerical data, use a zero-knowledge proof protocol based on discrete logarithms; For cases involving continuous numerical data, a zero-knowledge proof protocol based on elliptic curve cryptography is used; If the data contains text information, encode the text into numerical data, and then select the zero-knowledge proof protocol based on the characteristics of the converted data; Analyze the type of attack faced and select the zero-knowledge proof protocol; To meet the needs of resisting quantum computing attacks, we choose a zero-knowledge proof protocol based on quantum-resistant cryptography; Determine the required security level based on the sensitivity of the enterprise credit data and select a protocol with strict security certification; Evaluate the enterprise's computing resources, including server performance and network bandwidth, consider the proof generation time and verification time of the protocol, and select a protocol that meets the enterprise's business needs; Consider the communication overhead of data transmission and the interactivity of the protocol, and select a protocol that meets your needs; Select the corresponding zero-knowledge proof protocol according to different enterprise credit data application scenarios.

6. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 3 is characterized in that: The zero-knowledge proof protocol is determined to pre-process the enterprise credit data, including: Select a zero-knowledge proof protocol based on the characteristics, security requirements, performance requirements, and application scenarios of corporate credit data; Clean and organize corporate credit data to remove noise and outliers; Convert enterprise credit data into a format that matches the zero-knowledge proof protocol; The trusted setting of the zero-knowledge proof protocol includes: When performing a trusted setup, select a scenario and random number generator that meet the requirements and generate public parameters; The step of constructing a zero-knowledge proof system and inputting the enterprise credit data into the zero-knowledge proof system to generate a zero-knowledge proof includes: According to the selected zero-knowledge proof protocol, define the logical structure of the proof, select the encryption algorithm and hash function to build the corresponding zero-knowledge proof system; For the polynomial commitment-based protocol, a polynomial commitment scheme is constructed and the enterprise credit data is encoded into a polynomial; Input the enterprise credit data into the zero-knowledge proof system and generate zero-knowledge proof through encryption and hash operations; The preliminary verification of the generated zero-knowledge proof includes: Sending the generated zero-knowledge proof and the corresponding statement to the verifier to instruct the verifier to verify the received proof using the verification algorithm of the zero-knowledge proof protocol; wherein the verification process includes decryption, hash operation and logic verification of the proof; If the certificate is verified, the enterprise credit data and the corresponding certificate will be stored in a secure database.

7. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 4 is characterized in that: The sources of the confirmed public key and zero-knowledge proof include: Verify the channel of the public key and zero-knowledge proof to confirm that the channel is relevant to the expected corporate credit data verification; Check the integrity of public keys and zero-knowledge proofs; The understanding of the zero-knowledge proof protocol, obtaining the corresponding verification algorithm and parameters, parsing the public key and the zero-knowledge proof, executing the verification algorithm, and checking the verification result include: Understand the principles and verification methods of the zero-knowledge proof protocol used; According to the zero-knowledge proof protocol, obtain the corresponding verification algorithm and parameters, wherein the parameters include protocol-specific mathematical constants and hash functions; Parse the public key and extract the key information contained therein, where the key information includes: encryption algorithm parameters and key length; Parse zero-knowledge proofs and understand their structure and content, where zero-knowledge proofs include encrypted data and logical assertions; Take the public key and zero-knowledge proof as input and run the verification algorithm, which includes a series of mathematical operations and logical judgments; Verify according to the steps specified in the protocol, including encryption and decryption operations, hash value calculation, and logical relationship checking; After the verification algorithm is executed, a verification result is output; If the verification result is true, it means that the enterprise credit data statement is credible; if the verification result is false, it means that the zero-knowledge proof is invalid and an investigation is conducted; The recording of verification results, taking corresponding actions, and regularly updating the verification include: Record the verification time, the source of the public key and zero-knowledge proof, and the verification result; If the verification result is false, record the relevant error information and abnormal conditions; Take appropriate actions based on the verification results; If the verification result is true, continue to use the enterprise credit data for subsequent business processing; If the verification result is false, refuse to use the data; The verification process is updated regularly, and the validity of public keys and certificates is checked regularly.

8. An enterprise credit data privacy protection device based on zero-knowledge proof technology, characterized in that: include: A data acquisition module is used to acquire enterprise credit data and encrypt the data; The protocol selection module is used to adaptively select the zero-knowledge proof protocol according to business needs; The proof generation module is used to generate a pair of public and private keys, and select the zero-knowledge proof protocol to generate zero-knowledge proof based on the private key and corporate credit data; A proof verification module, used to transmit the zero-knowledge proof and its public key to a third party, so that the third party can use the received zero-knowledge proof and public key for verification; The verification feedback module is used to receive verification results from third-party feedback.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the processor is connected to the memory via the bus, and the memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, they are used to implement the enterprise credit data privacy protection method based on zero-knowledge proof technology as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a server, implements the enterprise credit data privacy protection method based on zero-knowledge proof technology as described in any one of claims 1-7.

Images