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

Abstract

The embodiment of the application provides a kind of enterprise credit data privacy protection method and device based on zero-knowledge proof technology, the method comprises: obtaining enterprise credit data, and the data is encrypted;According to the adaptive selection of zero-knowledge proof protocol according to business requirement;Generate a pair of public key and private key, based on private key and enterprise credit data, select zero-knowledge proof protocol to generate zero-knowledge proof;Zero-knowledge proof and its public key are transmitted to third party, so that third party uses received zero-knowledge proof and public key to verify;Receive the verification result fed back by third party;Through zero-knowledge proof, enterprise can prove its credit condition without opening specific credit data, so that sensitive information and business secrets are protected, the risk of data leakage is reduced, in addition, enterprise does not need to share any sensitive data, does not need to decrypt and share data, just need to provide zero-knowledge proof to complete credit verification, greatly reduce the potential risk brought by data sharing.

Description

Technical Field

[0001] This application relates to the field of credit data privacy protection technology, and more specifically, to a method and apparatus for protecting enterprise credit data privacy based on zero-knowledge proof technology. Background Technology

[0002] Data encryption transforms data into a form that only those with the correct key can decipher, thereby protecting the data's security during storage and transmission. Currently, 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 designed to replace the previous DES algorithm, providing higher security and the ability to adapt to future increases in computing power.

[0003] While AES encryption effectively protects corporate credit data, attackers can still deduce information by analyzing patterns, metadata, or other side-channel data. For example, frequent access patterns may reveal certain behaviors or trends. Furthermore, decryption is typically required before using encrypted data for computation or analysis, which can also expose corporate credit data to potential risks. Summary of the Invention

[0004] The purpose of this application is to provide a method and apparatus for protecting enterprise credit data privacy based on zero-knowledge proof technology, in order to solve the problem that existing methods usually require decryption before using encrypted data for calculation or analysis, which may expose enterprise credit data to potential risks and cause data leakage.

[0005] In a first aspect, embodiments of this application provide a method for protecting enterprise credit data privacy based on zero-knowledge proof technology, including:

[0006] Obtain enterprise credit data and encrypt the data;

[0007] Adaptively select the zero-knowledge proof protocol based on business needs;

[0008] Generate a public and private key pair, and based on the private key and enterprise credit data, select a zero-knowledge proof protocol to generate a zero-knowledge proof;

[0009] 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 to perform verification;

[0010] Receive verification results from third parties.

[0011] In the above implementation process, this application embodiment obtains enterprise credit data and encrypts the data; adaptively selects a zero-knowledge proof protocol according to business needs; generates a public key and a private key pair, and generates a zero-knowledge proof based on the private key and enterprise credit data; transmits 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 to verify; receives the verification results fed back by the third party; through zero-knowledge proof, enterprises can prove their credit status without disclosing specific credit data, thereby protecting sensitive information and trade secrets and reducing the risk of data leakage. In addition, enterprises do not need to share any sensitive data or decrypt and share the data; they only need to provide a zero-knowledge proof to complete credit verification, which greatly reduces the potential risks brought about by data sharing.

[0012] Furthermore, the adaptive selection of the zero-knowledge proof protocol based on business needs includes:

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

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

[0015] Furthermore, the step of generating a zero-knowledge proof based on the private key and enterprise credit data using a zero-knowledge proof protocol includes:

[0016] Determine a zero-knowledge proof protocol for preprocessing enterprise credit data;

[0017] Trust settings for zero-knowledge proof protocols;

[0018] Construct a zero-knowledge proof system and input enterprise credit data into the zero-knowledge proof system to generate zero-knowledge proofs;

[0019] The generated zero-knowledge proof is initially verified.

[0020] In the above implementation process, it is ensured that only the authenticity of the enterprise credit data is proven, without disclosing the specific data content.

[0021] Furthermore, the third party uses the received zero-knowledge proof and public key for verification, including:

[0022] Verify the source of the public key and zero-knowledge proof;

[0023] 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 result;

[0024] Record the verification results, take appropriate actions, and update the verification periodically.

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

[0026] Furthermore, the adaptive selection of a zero-knowledge proof protocol based on data type, security requirements, performance requirements, and application scenarios includes:

[0027] If the enterprise credit data is discrete numerical data, use a zero-knowledge proof protocol based on discrete logarithms;

[0028] For cases involving continuous numerical data, a zero-knowledge proof protocol based on elliptic curve cryptography is used.

[0029] If the data contains text information, the text is encoded and converted into numerical data, and then a zero-knowledge proof protocol is selected based on the characteristics of the converted data.

[0030] Analyze the types of attacks you face and select a zero-knowledge proof protocol;

[0031] To address the need to counter quantum computing attacks, a zero-knowledge proof protocol based on quantum-resistant cryptography is chosen.

[0032] Determine the required security level based on the sensitivity of the enterprise's credit data, and select protocols with stringent security certifications;

[0033] Assess the enterprise's computing resources, including server performance and network bandwidth, and consider the protocol's proof generation and verification time to select a protocol that meets the enterprise's business needs.

[0034] Considering the communication overhead of data transmission and the interactivity of protocols, select a protocol that meets the requirements;

[0035] Choose the appropriate zero-knowledge proof protocol based on the different application scenarios of enterprise credit data.

[0036] Furthermore, the determination of the zero-knowledge proof protocol and the preprocessing of enterprise credit data include:

[0037] Based on the characteristics, security requirements, performance requirements, and application scenarios of enterprise credit data, a zero-knowledge proof protocol is selected.

[0038] Clean and organize corporate credit data to remove noise and outliers;

[0039] Convert enterprise credit data into a format that matches zero-knowledge proof protocols;

[0040] The trusted configuration of the zero-knowledge proof protocol includes:

[0041] When setting up a trusted environment, select a suitable scenario and random number generator to generate common parameters;

[0042] The step of constructing a zero-knowledge proof system and inputting enterprise credit data into the zero-knowledge proof system to generate a zero-knowledge proof includes:

[0043] Based on the selected zero-knowledge proof protocol, define the logical structure of the proof, select the encryption algorithm and hash function to construct the corresponding zero-knowledge proof system;

[0044] For agreements based on multinomial commitments, construct a multinomial commitment scheme and encode corporate credit data as a multinomial;

[0045] Enterprise credit data is input into a zero-knowledge proof system, and zero-knowledge proofs are generated through encryption and hash operations.

[0046] The preliminary verification of the generated zero-knowledge proof includes:

[0047] The generated zero-knowledge proof and 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; the verification process includes proof decryption, hash operation and logical verification.

[0048] If the verification is successful, the company's credit data and the corresponding verification will be stored in a secure database.

[0049] Furthermore, the confirmation of the source of the public key and the zero-knowledge proof includes:

[0050] Verify the public key and zero-knowledge proof channels to confirm that the channels are relevant to the expected verification of enterprise credit data;

[0051] Check the integrity of the public key and zero-knowledge proof;

[0052] The process of understanding the zero-knowledge proof protocol, obtaining the corresponding verification algorithm and parameters, parsing the public key and zero-knowledge proof, executing the verification algorithm, and checking the verification result includes:

[0053] Understand the principles and verification methods of the zero-knowledge proof protocols used;

[0054] According to the zero-knowledge proof protocol, obtain the corresponding verification algorithm and parameters, where the parameters include protocol-specific mathematical constants and hash functions;

[0055] Parse the public key to extract the key information it contains, including: the parameters of the encryption algorithm and the key length;

[0056] This section analyzes zero-knowledge proofs, explaining their structure and content. Zero-knowledge proofs include encrypted data and logical assertions.

[0057] The public key and zero-knowledge proof are used as inputs to run a verification algorithm, which includes a series of mathematical operations and logical judgments.

[0058] The verification process is carried out according to the steps specified in the agreement, which include performing encryption and decryption operations, calculating hash values, and checking logical relationships.

[0059] After the verification algorithm completes its execution, it outputs a verification result.

[0060] If the verification result is true, it means that the enterprise's credit data claim is credible; if the verification result is false, it means that the zero-knowledge proof is invalid, and an investigation should be conducted.

[0061] The recording of verification results, taking corresponding actions, and periodically updating the verification include:

[0062] Record the verification time, public key and source of the zero-knowledge proof, and verification result;

[0063] If the verification result is false, record the relevant error information and abnormal situation;

[0064] Based on the verification results, take appropriate actions;

[0065] If the verification result is true, continue to use the enterprise credit data for subsequent business processing;

[0066] If the verification result is false, the data will be rejected.

[0067] The verification process is updated regularly, and the validity of the public key and proof is checked periodically.

[0068] Secondly, embodiments of this application provide a device for protecting enterprise credit data privacy based on zero-knowledge proof technology, comprising:

[0069] The data acquisition module is used to acquire enterprise credit data and encrypt the data.

[0070] The protocol selection module is used to adaptively select a zero-knowledge proof protocol based on business requirements.

[0071] The proof generation module is used to generate a pair of public and private keys, and generate a zero-knowledge proof based on the private key and enterprise credit data by selecting a zero-knowledge proof protocol.

[0072] The proof verification module is used to transmit zero-knowledge proofs and their public keys to third parties so that the third parties can use the received zero-knowledge proofs and public keys to perform verification.

[0073] The verification feedback module is used to receive verification results from third parties.

[0074] Thirdly, embodiments of this application provide an electronic device, including:

[0075] The system includes a processor, a memory, and a bus. The processor is connected to the memory via the bus. 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.

[0076] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a server, implements the enterprise credit data privacy protection method based on zero-knowledge proof technology as described above. Attached Figure Description

[0077] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0078] Figure 1 A flowchart illustrating a method for protecting enterprise credit data privacy based on zero-knowledge proof technology, provided for an embodiment of this application;

[0079] Figure 2 This is a schematic diagram of the structure of an enterprise credit data privacy protection device based on zero-knowledge proof technology provided in an embodiment of this application;

[0080] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0081] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0082] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0083] Data encryption transforms data into a form that can only be deciphered by those possessing the correct key, thereby protecting the data's security during storage and transmission. Currently, the AES algorithm is a common method for encrypting corporate credit data.

[0084] AES (Advanced Encryption Standard) is a widely used symmetric-key encryption standard. AES was designed to replace the previous DES algorithm, offering enhanced security and the ability to adapt to future increases in computing power. AES supports three key lengths: 128-bit, 192-bit, and 256-bit, with 128-bit being the most commonly used version.

[0085] The AES algorithm uses a fixed block size of 128 bits (16 bytes) for block encryption. Its core is a series of repeating permutation-permutation network (SPN) structures called "rounds." The AES encryption process typically involves multiple rounds (the specific number of rounds depends on the key length: 10 rounds for a 128-bit key, 12 rounds for a 192-bit key, and 14 rounds for a 256-bit key). Each round includes the following four basic operations: Subbytes: Each byte is non-linearly replaced using a fixed S-box (permutation box); ShiftRows: Each row in the data block is cyclically shifted left by a specified number of bits; MixColumns: Each column of the data block is mixed using matrix multiplication, except in the last round; AddRoundKey: The round key is XORed with the data block; the round key is derived from the original key using a key scheduling algorithm.

[0086] Decryption is the inverse operation of encryption, using the same key and inverse transformation to recover the original data. While AES encryption effectively protects corporate credit data, in some cases, attackers can still deduce information by analyzing patterns, metadata, or other side-channel information in the encrypted data. For example, frequent access patterns may reveal certain behaviors or trends. Furthermore, when encrypted data needs to be used for computation or analysis, decryption is usually required first, which can also expose corporate credit data to potential risks.

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

[0088] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a method for protecting enterprise credit data privacy based on zero-knowledge proof technology, provided as an embodiment of this application. The method includes:

[0089] 100. Obtain enterprise credit data and encrypt the data.

[0090] Optionally, necessary corporate credit data, such as financial statements, credit scores, and transaction records, should be collected first. The collected data should be encrypted before storage to prevent unauthorized access.

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

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

[0093] Among them, the zero-knowledge proof protocol is adaptively selected based on the data type.

[0094] Optionally, if the enterprise credit data is discrete numerical data, a zero-knowledge proof protocol based on discrete logarithms can be used. For example, if the enterprise credit data is mainly discrete numerical data, such as credit rating, number of defaults, etc., a zero-knowledge proof protocol based on discrete logarithms, such as the Schnorr protocol or its variants, can be used. Such protocols are relatively efficient when handling integer operations.

[0095] Optionally, for cases involving continuous numerical data, a zero-knowledge proof protocol based on elliptic curve cryptography can be used. For example, for cases involving a large amount of continuous numerical data, such as monetary data in financial statements, a zero-knowledge proof protocol based on elliptic curve cryptography can be used, as elliptic curve cryptography may have higher security and efficiency when processing continuous numerical data.

[0096] Optionally, if the data contains text information, the text is encoded and converted into numerical data, and then a zero-knowledge proof protocol is selected based on the characteristics of the converted data.

[0097] Among them, the zero-knowledge proof protocol is adaptively selected based on the data scale.

[0098] Optionally, for small-scale enterprise credit data, a zero-knowledge proof protocol with relatively low computational complexity can be selected, such as the Groth16 protocol in concise 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.

[0099] Optionally, when dealing with large datasets, protocols with higher scalability should be considered. For example, the zk-STARKs protocol performs better on large datasets because it does not rely on trusted settings and the verification time is logarithmic with the proof size.

[0100] Among them, a zero-knowledge proof protocol is adaptively selected to meet security requirements.

[0101] Optionally, analyze the types of attacks you may be facing and select a zero-knowledge proof protocol. For example, analyze the types of attacks you may be facing, such as choosing a plaintext attack or a ciphertext attack. If there is a powerful attacker, you may need to choose a zero-knowledge proof protocol with higher security.

[0102] Optionally, to meet the need for resistance to quantum computing attacks, a zero-knowledge proof protocol based on quantum-resistant cryptography can be selected; for example, a protocol based on lattice cryptography.

[0103] Optionally, the required security level can be determined based on the sensitivity of the enterprise credit data, and a protocol with rigorous security proofs can be selected, such as a zero-knowledge proof protocol with rigorous mathematical proof. Additionally, the security assumptions of the protocol should be considered, such as whether they are based on strong cryptographic assumptions and the reliability of these assumptions in practical applications.

[0104] Optionally, assess the enterprise's computing resources, including server performance and network bandwidth. If computing resources are limited, a zero-knowledge proof protocol with lower computational overhead can be selected to ensure system efficiency. Optionally, consider the proof generation and verification times of the protocol and select a protocol that meets the enterprise's business needs; for example, in real-time credit assessment scenarios, a protocol with shorter verification time is required.

[0105] Optionally, considering the communication overhead of data transmission and the interactivity of the protocol, a protocol that meets the requirements can be selected. For example, 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. For example, considering the interactivity of the protocol, non-interactive zero-knowledge proof protocols generally have lower communication overhead and are suitable for use in poor network environments.

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

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

[0108] For example, considering the data privacy protection requirements of local laws and regulations, some regions may have recognition or restrictions on certain types of zero-knowledge proof protocols, and companies need to choose the appropriate protocol according to local laws.

[0109] In some embodiments, different zero-knowledge proof protocols are theoretically analyzed to compare their security, performance, and functional characteristics; for example, academic literature, evaluation reports from cryptography research institutions, etc., can be consulted.

[0110] In some embodiments, candidate zero-knowledge proof protocols are tested in a real-world environment to evaluate their practical effectiveness in protecting enterprise credit data privacy; for example, tests can be conducted using simulated data or subsets of real data to compare the performance and security of different protocols.

[0111] In some embodiments, the maintainability of the protocol is considered, including the protocol's update frequency, community support, etc.; for example, selecting a protocol with active community support can ensure that security vulnerabilities or performance issues can be fixed in a timely manner.

[0112] As described above, the embodiments of this application enable enterprises to adaptively select zero-knowledge proof protocols that suit their credit data privacy protection needs, thereby achieving efficient and secure data protection.

[0113] 300. Generate a public key and a private key pair. Based on the private key and enterprise credit data, select a zero-knowledge proof protocol to generate a zero-knowledge proof.

[0114] 310. Determine a zero-knowledge proof protocol to preprocess enterprise credit data.

[0115] 311. Based on the characteristics, security requirements, performance requirements, and application scenarios of enterprise credit data, select a zero-knowledge proof protocol.

[0116] 312. Clean and organize enterprise credit data to remove noise and outliers.

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

[0118] 313. Convert enterprise credit data into a format that matches zero-knowledge proof protocols;

[0119] Additionally, the data needs to be converted into a format suitable for zero-knowledge proof protocols. For example, some protocols may require the data to be represented as a polynomial or matrix.

[0120] 320. Set a trusted configuration for zero-knowledge proof protocols.

[0121] When setting up a trusted environment, select a suitable scenario and random number generator to generate common parameters.

[0122] 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 for the generation and verification of proofs. At the same time, the trusted setup needs to be carried out in a secure environment to ensure the security of the parameters.

[0123] In addition, during the trusted setup process, a suitable random number generator needs to be selected, and it is ensured that the generated parameters have sufficient randomness and security.

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

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

[0126] 332. For protocols based on polynomial commitments, build a polynomial commitment scheme and encode enterprise credit data as a polynomial.

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

[0128] Among them, during the process of generating the proof, attention needs to be paid to protecting the randomness of the proof to prevent attackers from inferring the content of enterprise credit data by analyzing the randomness of the proof.

[0129] 340. Conduct a preliminary verification of the generated zero-knowledge proof.

[0130] Specifically, send the generated zero-knowledge proof and the corresponding statement to the verifier to instruct the verifier to use the verification algorithm of the zero-knowledge proof protocol to verify the received proof. Among them, the verification process includes proof decryption, hash operation and logical verification.

[0131] Among them, the statement is usually an assertion about enterprise credit data, such as "The credit rating of the enterprise is A".

[0132] Specifically, if the proof passes the verification, store the enterprise credit data and the corresponding proof in a secure database.

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

[0134] If the proof is verified, the enterprise credit data and the corresponding proof can be stored in a secure database for later query and use. When storing the data, attention should be paid to protecting the privacy and security of the data, such as using encrypted storage or access control mechanisms.

[0135] Enterprise credit data may change over time, so zero-knowledge proofs need to be updated regularly. The process of updating proofs can be similar to the process of generating proofs, but the changes in data and the validity of proofs need to be taken into account.

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

[0137] As described above, the embodiments of this application ensure that only the authenticity of the enterprise credit data is proven, without disclosing the specific data content.

[0138] 400. 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 to verify it.

[0139] 410. Verify the source of the public key and zero-knowledge proof.

[0140] Specifically, the verification channels for public keys and zero-knowledge proofs are confirmed to be relevant to the intended enterprise credit data verification; the integrity of the public keys and zero-knowledge proofs is checked. This ensures that the public keys and proofs originate from trusted channels and are relevant to the intended enterprise credit data verification; the integrity of the public keys and proofs is checked to confirm that they have not been tampered with during transmission.

[0141] 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 result.

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

[0143] Specifically, familiarize yourself with the principles and verification methods of the zero-knowledge proof protocols used. Different protocols may have different verification processes and mathematical foundations. Understand the security assumptions of the protocols and the reliability guarantees of the verification.

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

[0145] This ensures the correctness and completeness of the verification algorithm and parameters.

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

[0147] 424. Explain zero-knowledge proofs, including their structure and content. Zero-knowledge proofs consist of encrypted data and logical assertions.

[0148] This allows for the verification of the authenticity of corporate credit data.

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

[0150] This ensures the validity of the statement.

[0151] 426. Verify according to the steps specified in the agreement, which include encryption and decryption operations, hash value calculation, and logical relationship checking.

[0152] 427. After the verification algorithm is completed, a verification result will be output.

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

[0154] 428. If the verification result is true, it means that the enterprise's credit data statement is credible; if the verification result is false, it means that the zero-knowledge proof is invalid, and an investigation should be conducted.

[0155] 430. Record the verification results, take appropriate actions, and update the verification periodically.

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

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

[0158] Optionally, the verification results should be recorded for future reference and auditing. The record should include the verification time, the source of the public key and proof, and the verification result. If the verification result is false, relevant error information and anomalies should be recorded for troubleshooting and problem resolution.

[0159] 433. Based on the verification results, take appropriate actions.

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

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

[0162] For example, based on the verification results, appropriate actions should be taken; if the verification result is true, the enterprise credit data can continue to be used for subsequent business processing, such as loan approval and cooperation decisions; if the verification result is false, the data should be refused to be used, and the relevant parties should be notified. It may be necessary to communicate with the data provider to request that proof be provided again or the data issue be resolved.

[0163] 436. Regularly update the verification process and periodically check the validity of the public key and proof.

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

[0165] Therefore, it is essential to regularly check the validity of public keys and proofs to ensure the authenticity and reliability of data; the frequency of updates can be determined based on business needs and risk assessments.

[0166] As stated above, when using the received public key and proof for verification, third parties must carefully follow the provisions of the zero-knowledge proof protocol to ensure the accuracy and reliability of the verification process. At the same time, they should remain vigilant and promptly address any issues that arise during the verification process to protect their own interests and data security.

[0167] 500. Receive verification results from third parties.

[0168] Specifically, after the third party completes the verification, it provides feedback on the verification results to the enterprise, ensuring that the verification process is transparent and traceable.

[0169] As described above, this application embodiment acquires enterprise credit data and encrypts the data; adaptively selects a zero-knowledge proof protocol according to business needs; generates a public key and a private key pair, and generates a zero-knowledge proof based on the private key and enterprise credit data using the selected zero-knowledge proof protocol; transmits 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; receives the verification results from the third party; through zero-knowledge proof, enterprises can prove their credit status without disclosing specific credit data, thereby protecting sensitive information and trade secrets and reducing the risk of data leakage. In addition, enterprises do not need to share any sensitive data or decrypt and share the data; they only need to provide a zero-knowledge proof to complete credit verification, which greatly reduces the potential risks brought about by data sharing.

[0170] The embodiments of this application have a high degree of privacy protection: Information isolation: Through zero-knowledge proof, enterprises can prove their credit status without disclosing specific credit data, which means that sensitive financial information and trade secrets are protected and the risk of data leakage is reduced; 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 truthfulness of the statements.

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

[0172] The embodiments of this application reduce the risk of data leakage by minimizing data sharing: enterprises do not need to share any sensitive data or decrypt the data before sharing. They only need to provide zero-knowledge proofs to complete credit verification, which greatly reduces the potential risks associated with data sharing.

[0173] The steps described above are not strictly performed in the order of their numbers; they should be understood as a whole.

[0174] Secondly, based on the above embodiments, Figure 2 This is a schematic diagram of a corporate credit data privacy protection device based on zero-knowledge proof technology, provided as an embodiment of this application. (Reference) 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.

[0175] The data acquisition module 201 is used to acquire enterprise credit data and encrypt the data; the protocol selection module 202 is used to adaptively select a zero-knowledge proof protocol according to business needs; the proof generation module 203 is used to generate a public key and a private key pair, and generate a zero-knowledge proof based on the private key and enterprise credit data by selecting a zero-knowledge proof protocol; 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 to verify it; and the verification feedback module 205 is used to receive the verification results fed back by the third party.

[0176] As described above, this application embodiment acquires enterprise credit data and encrypts the data; adaptively selects a zero-knowledge proof protocol according to business needs; generates a public key and a private key pair, and generates a zero-knowledge proof based on the private key and enterprise credit data using the selected zero-knowledge proof protocol; transmits 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; receives the verification results from the third party; through zero-knowledge proof, enterprises can prove their credit status without disclosing specific credit data, thereby protecting sensitive information and trade secrets and reducing the risk of data leakage. In addition, enterprises do not need to share any sensitive data or decrypt and share the data; they only need to provide a zero-knowledge proof to complete credit verification, which greatly reduces the potential risks brought about by data sharing.

[0177] The enterprise credit data privacy protection device based on zero-knowledge proof technology provided in this application embodiment 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.

[0178] Thirdly, embodiments of this application also provide an electronic device that can integrate the enterprise credit data privacy protection device based on zero-knowledge proof technology provided in embodiments of this application. Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. (Reference) 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 stores 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 provided in the above embodiments. The input device 33, output device 34, memory 32, and processors 31 can be connected via a bus or other means. Figure 3 Taking the example of a connection between China and Israel via a bus.

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

[0180] 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 embodiments, and has corresponding functions and beneficial effects.

[0181] Fourthly, embodiments of this application also provide a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located 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.

[0182] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the enterprise credit data privacy protection method based on zero-knowledge proof technology as described above, but can also perform related operations in the enterprise credit data privacy protection method based on zero-knowledge proof technology provided in any embodiment of this application.

[0183] Fifthly, embodiments of this application also provide a computer program product. The methods described in the various embodiments of this application can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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 instructions are loaded and executed on a computer, the processes or functions described in the various embodiments of this application are executed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, core network equipment, OAM (Open Application Model), or other programmable devices.

[0184] The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that a computer can access, 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, hard disk, or magnetic tape; or an optical medium, such as a digital video optical disc; or 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.

[0185] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0186] In addition, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0187] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0188] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application. It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0189] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0190] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A method for protecting enterprise credit data privacy based on zero-knowledge proof technology, characterized in that, The method includes: Obtain enterprise credit data and encrypt the data; The zero-knowledge proof protocol is adaptively selected based on business needs; specifically, the zero-knowledge proof protocol is adaptively selected based on data type, security requirements, performance requirements, and application scenarios. If the enterprise credit data is discrete numerical data, a zero-knowledge proof protocol based on discrete logarithms is used; enterprise credit data includes credit rating and number of defaults. For cases involving continuous numerical data, a zero-knowledge proof protocol based on elliptic curve cryptography is used. If the data contains text information, the text is encoded and converted into numerical data, and then a zero-knowledge proof protocol is selected based on the characteristics of the converted data. Generate a public and private key pair, and based on the private key and enterprise credit data, select a zero-knowledge proof protocol to generate a zero-knowledge proof; 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 to perform verification; Verify the source of the public key and zero-knowledge proof; specifically, verify the channel through which the public key and zero-knowledge proof are obtained, confirming that the channel is related to the expected enterprise credit data verification; check the integrity of the public key and zero-knowledge proof. Regularly update zero-knowledge proofs; Receive verification results from third parties.

2. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 1, characterized in that, The process of generating a zero-knowledge proof based on a private key and enterprise credit data, using a zero-knowledge proof protocol, includes: Determine a zero-knowledge proof protocol for preprocessing enterprise credit data; Trust settings for zero-knowledge proof protocols; Construct a zero-knowledge proof system and input enterprise credit data into the zero-knowledge proof system to generate zero-knowledge proofs; The generated zero-knowledge proof is initially verified.

3. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 1, characterized in that, The third party uses the received zero-knowledge proof and public key for verification, including: 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 result; Record the verification results, take appropriate actions, and update the verification periodically.

4. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 1, characterized in that, The adaptive selection of zero-knowledge proof protocols based on data type, security requirements, performance requirements, and application scenarios includes: For cases involving continuous numerical data, a zero-knowledge proof protocol based on elliptic curve cryptography is used. If the data contains text information, the text is encoded and converted into numerical data, and then a zero-knowledge proof protocol is selected based on the characteristics of the converted data. Analyze the types of attacks you face and select a zero-knowledge proof protocol; To address the need to counter quantum computing attacks, a zero-knowledge proof protocol based on quantum-resistant cryptography is chosen. Determine the required security level based on the sensitivity of the enterprise's credit data, and select protocols with stringent security certifications; Assess the enterprise's computing resources, including server performance and network bandwidth, and consider the protocol's proof generation and verification time to select a protocol that meets the enterprise's business needs. Considering the communication overhead of data transmission and the interactivity of protocols, select a protocol that meets the requirements; Choose the appropriate zero-knowledge proof protocol based on the different application scenarios of enterprise credit data.

5. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 2, characterized in that, The determination of the zero-knowledge proof protocol includes preprocessing enterprise credit data, including: Based on the characteristics, security requirements, performance requirements, and application scenarios of enterprise credit data, a zero-knowledge proof protocol is selected. Clean and organize corporate credit data to remove noise and outliers; Convert enterprise credit data into a format that matches zero-knowledge proof protocols; The trusted configuration of the zero-knowledge proof protocol includes: When setting up a trusted environment, select a suitable scenario and random number generator to generate common parameters; The step of constructing a zero-knowledge proof system and inputting enterprise credit data into the zero-knowledge proof system to generate a zero-knowledge proof includes: Based on the selected zero-knowledge proof protocol, define the logical structure of the proof, select the encryption algorithm and hash function to construct the corresponding zero-knowledge proof system; For agreements based on multinomial commitments, construct a multinomial commitment scheme and encode corporate credit data as a multinomial; Enterprise credit data is input into a zero-knowledge proof system, and zero-knowledge proofs are generated through encryption and hash operations. The preliminary verification of the generated zero-knowledge proof includes: The generated zero-knowledge proof and 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; the verification process includes proof decryption, hash operation and logical verification. If the verification is successful, the company's credit data and the corresponding verification will be stored in a secure database.

6. The enterprise credit data privacy protection method based on zero-knowledge proof technology according to claim 3, characterized in that, The process of understanding the zero-knowledge proof protocol, obtaining the corresponding verification algorithm and parameters, parsing the public key and zero-knowledge proof, executing the verification algorithm, and checking the verification result includes: Understand the principles and verification methods of the zero-knowledge proof protocols used; According to the zero-knowledge proof protocol, obtain the corresponding verification algorithm and parameters, where the parameters include protocol-specific mathematical constants and hash functions; Parse the public key to extract the key information it contains, including: the parameters of the encryption algorithm and the key length; This section analyzes zero-knowledge proofs, explaining their structure and content. Zero-knowledge proofs include encrypted data and logical assertions. The public key and zero-knowledge proof are used as inputs to run a verification algorithm, which includes a series of mathematical operations and logical judgments. The verification process is carried out according to the steps specified in the agreement, which includes encryption and decryption operations, hash value calculation, and logical relationship checking. After the verification algorithm completes its execution, it outputs a verification result. If the verification result is true, it means that the enterprise's credit data claim is credible; if the verification result is false, it means that the zero-knowledge proof is invalid, and an investigation should be conducted. The recording of verification results, taking corresponding actions, and periodically updating the verification include: Record the verification time, public key and source of the zero-knowledge proof, and verification result; If the verification result is false, record the relevant error information and abnormal situation; Based on the verification results, take appropriate actions; If the verification result is true, continue to use the enterprise credit data for subsequent business processing; If the verification result is false, the data will be rejected. The verification process is updated regularly, and the validity of the public key and proof is checked periodically.

7. A device for protecting enterprise credit data privacy based on zero-knowledge proof technology, characterized in that, include: The data acquisition module is used to acquire enterprise credit data and encrypt the data. The protocol selection module is used to adaptively select a zero-knowledge proof protocol based on business needs; specifically, it adaptively selects a zero-knowledge proof protocol based on data type, security requirements, performance requirements, and application scenarios. If the enterprise credit data is discrete numerical data, a zero-knowledge proof protocol based on discrete logarithms is used; enterprise credit data includes credit rating and number of defaults. For cases involving continuous numerical data, a zero-knowledge proof protocol based on elliptic curve cryptography is used. If the data contains text information, the text is encoded and converted into numerical data, and then a zero-knowledge proof protocol is selected based on the characteristics of the converted data. The proof generation module is used to generate a pair of public and private keys, and generate a zero-knowledge proof based on the private key and enterprise credit data by selecting a zero-knowledge proof protocol. The proof verification module is used to transmit zero-knowledge proofs and their public keys to third parties so that the third parties can use the received zero-knowledge proofs and public keys to perform verification. Verify the source of the public key and zero-knowledge proof; specifically, verify the channel through which the public key and zero-knowledge proof are obtained, confirming that the channel is related to the expected enterprise credit data verification; check the integrity of the public key and zero-knowledge proof. Regularly update zero-knowledge proofs; The verification feedback module is used to receive verification results from third parties.

8. An electronic device, characterized in that, include: The processor, memory, and bus are provided, 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-6.

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

Images