Enterprise user data security protection system based on national secret algorithm and block chain storage
By constructing a four-layer collaborative architecture based on national cryptographic algorithms and blockchain for evidence storage, the problems of centralized key leakage, lack of traceability certificates for data operations, and unauthorized access across enterprises in existing technologies are solved, realizing full lifecycle security protection and compliant evidence storage for enterprise user data.
Patent Information
- Application Number
- CN202611484040.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-22
- Publication Date
- 2026-11-17
AI Technical Summary
Existing enterprise data security protection solutions have problems such as the risk of centralized key leakage, lack of judicial traceability for data operations, non-compliant overseas cryptographic algorithms, unauthorized access to cross-enterprise data, and cumbersome offline evidence collection processes. They lack an integrated enterprise user data security protection architecture.
A four-layer collaborative architecture based on national cryptographic algorithms and blockchain evidence storage is constructed, including an enterprise business interaction terminal, a secure encryption middleware platform, a distributed blockchain evidence storage network, and an enterprise local encrypted storage cluster. It integrates multi-level national cryptographic operations, dynamic role authentication, real-time data traffic risk identification, and hierarchical permission consortium blockchain evidence storage to achieve full lifecycle data security protection.
It achieves encrypted, compliant, and controllable enterprise user data, hierarchical management of access permissions, tamper-proof blockchain evidence storage of all operational behaviors, real-time interception of data theft risks, full traceability of cross-enterprise cooperation data authorization, and one-click automatic verification of judicial evidence, thereby improving data security and compliance.
Smart Images

Figure CN123122981A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of enterprise data security technology, specifically to an enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage. Background Technology
[0002] Against the backdrop of digital transformation, the volume of enterprise customer operational data, financial data, and supply chain privacy data continues to expand. Enterprise user data covers internal employee personnel information, external customer privacy information, and core sensitive business data of partners. Existing enterprise data protection solutions have multiple technical deficiencies and cannot simultaneously meet the multiple industry-specific needs of commercial cryptography compliance, data tamper-proof retention, real-time blocking of leakage risks, and cross-entity data ownership and traceability.
[0003] Current mainstream enterprise data security protection solutions fall into two categories. The first category is centralized encrypted storage solutions, which use only a single overseas symmetric encryption algorithm for local static encrypted storage, and have three major flaws. First, the keys are centrally stored on a centralized application server. If the server is compromised by a network intrusion, all keys will be leaked in batches, and all encrypted data of the enterprise's users can be directly decrypted and stolen. Second, there is no distributed on-chain evidence storage link. Data tampering, batch export, and unauthorized access operations lack immutable traceability certificates. In the event of data leakage or data infringement disputes, the enterprise cannot submit legally valid operation log evidence to the judicial authorities. Third, it only achieves static storage encryption and lacks a real-time risk identification mechanism for transmission link traffic. When hackers steal user data through API crawlers or unauthorized access from different locations, the system cannot identify and block the attack in real time.
[0004] The second category is general-purpose blockchain-based data storage management systems, which suffer from inherent flaws such as non-compliant cryptographic algorithms, single encryption layers, and low overall computational efficiency. Existing blockchain platforms commonly use foreign SHA hash algorithms and RSA asymmetric encryption algorithms, making them unsuitable for data storage scenarios in government, finance, and high-end manufacturing sectors involving sensitive information. Most solutions directly upload plaintext business data to on-chain storage, resulting in extremely high on-chain storage costs and the visibility of original sensitive data to all chain nodes, leading to a lack of enterprise data privacy protection. Furthermore, they lack a layered, isolated key management architecture, storing public and private root keys, long-term business keys, and temporary session keys in a mixed manner. They lack standardized key derivation and timed destruction processes, and short-term session keys reside on server disks for extended periods, creating a persistent risk of key leakage. Finally, they lack a refined authentication system adapted to the enterprise's organizational structure, relying solely on simple account passwords for access verification. Cross-enterprise collaborative data interaction lacks a temporary authorization digital signature solidification mechanism, making it highly susceptible to external partners unauthorized access to the enterprise's core user privacy data.
[0005] Existing technologies generally suffer from the core pain point of a disconnect between national cryptographic encryption modules and blockchain evidence storage modules. Independently deployed national cryptographic computing units are only responsible for data encryption and decryption, and cannot automatically push operation digital signatures and data hash metadata to the blockchain for evidence storage. Independent blockchain consensus nodes only complete block packaging consensus, and the underlying nodes do not have built-in national cryptographic batch signature verification logic. During the judicial evidence collection stage, commercial cryptographic equipment needs to be deployed offline for secondary verification of data authenticity, making the evidence collection process cumbersome and time-consuming. There is no integrated risk control architecture in the industry that coordinates and links the terminal, encryption intermediate platform, local encrypted storage cluster, and consortium blockchain network. The three types of security risks—abnormal terminal access, tampering with stored encrypted data, and forgery of on-chain metadata—cannot be identified and handled synchronously across modules.
[0006] Meanwhile, existing technologies do not design hierarchical national cryptographic operation logic for the complete lifecycle of enterprise user data. They use completely consistent encryption strength and key type for three different sensitive data categories: customer mobile phone numbers, daily transaction records, and core business secrets. Over-encryption of low-sensitivity data leads to a large waste of server computing resources, while insufficient encryption layers for high-sensitivity core data pose a risk of leakage. Furthermore, general consortium blockchains do not have differentiated node permission division logic, and regulatory agencies and judicial verification nodes do not have dedicated data verification interfaces. Any enterprise consensus node can access all evidence storage blocks of other enterprises, making it impossible to achieve subject isolation protection for enterprise commercial sensitive data.
[0007] In summary, existing technologies lack an integrated enterprise user data security protection architecture that combines three-level hardware isolation key management, layered national cryptographic operations, dynamic role-based access authentication, real-time transmission traffic risk control, hierarchical permission consortium blockchain evidence storage, and four-terminal collaborative risk control. This architecture cannot simultaneously address multiple technical challenges such as centralized key leakage, lack of judicial traceability for data operations, non-compliant overseas cryptographic algorithms, unauthorized cross-enterprise data access, inability to block data theft attacks in real time, and complex offline judicial evidence collection processes. Therefore, this invention urgently needs to propose a novel integrated technical solution. Summary of the Invention
[0008] To address the shortcomings of existing centralized encrypted storage and general blockchain evidence preservation solutions, such as insufficient key security protection, cryptographic algorithms that do not comply with national cryptographic standards, lack of tamper-proof evidence for data operations, lack of real-time risk blocking mechanisms for transmission traffic, lack of refined hierarchical access permissions for enterprises, cumbersome offline judicial evidence collection processes, and fragmented protection modules across multiple devices, this invention provides an enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence preservation. It constructs a four-layer collaborative architecture comprising an enterprise business interaction terminal, a secure encryption middleware platform, a distributed blockchain evidence preservation network, and an enterprise local encrypted storage cluster. This system integrates multi-level national cryptographic operation units to achieve hierarchical encryption, digital signatures, and integrity verification throughout the entire lifecycle of enterprise data. It is complemented by a dynamic role authentication system, a real-time data traffic risk identification system, a hierarchical permission consortium blockchain evidence preservation system, and a three-level hardware isolation key management system. This achieves multiple superimposed technical effects, including compliant and controllable enterprise user data encryption, hierarchical access control, tamper-proof blockchain evidence preservation of all operations, real-time interception and blocking of data theft risks, full traceability of cross-enterprise collaborative data authorization, and one-click automatic national cryptographic verification of judicial evidence.
[0009] To achieve the above objectives, the present invention adopts the following technical solution: A data security protection system for enterprise users based on national cryptographic algorithms and blockchain evidence storage includes an enterprise business interaction terminal, a secure encryption middleware platform, a distributed blockchain evidence storage network, and an enterprise local encrypted storage cluster. The enterprise business interaction terminal establishes a bidirectional communication connection with the secure encryption middleware platform, and the secure encryption middleware platform establishes communication connections with both the distributed blockchain evidence storage network and the enterprise local encrypted storage cluster. The secure encryption middleware platform integrates multi-level national cryptographic operation units, a data access authentication unit, an on-chain evidence storage packaging unit, and a data risk identification unit. The multi-level national cryptographic operation units are used to perform hierarchical encryption, digital signature, and integrity verification operations on all enterprise business user data. The data access authentication unit is used to verify data access requests according to enterprise role permissions. The on-chain evidence storage packaging unit is used to extract metadata corresponding to encrypted data and assemble blocks for uploading to the blockchain network. The data risk identification unit is used to collect and transmit data streams in real time to identify abnormal access behavior. The distributed blockchain evidence storage network is used to persistently store immutable evidence metadata, and the enterprise local encrypted storage cluster is used to store the encrypted original business encrypted data.
[0010] The multi-level national cryptographic operation unit includes an SM4 symmetric encryption subunit, an SM2 asymmetric signature key exchange subunit, an SM3 hash check subunit, and a key hierarchical management subunit. The SM4 symmetric encryption subunit is used to perform batch encryption and decryption of plaintext business data blocks for enterprises. The SM2 asymmetric signature key exchange subunit is used to implement enterprise entity identity signing, public and private key distribution, and cross-enterprise data interaction key negotiation. The SM3 hash check subunit is used to calculate plaintext and ciphertext hash digests to complete data integrity comparison. The key hierarchical management subunit hierarchically stores the enterprise root key, long-term business key, and single-interaction temporary session key. The key hierarchical management subunit establishes communication connections with the SM4 symmetric encryption subunit, the SM2 asymmetric signature key exchange subunit, and the SM3 hash check subunit through the platform's internal high-speed encryption bus.
[0011] The key hierarchical management subunit constructs a three-tiered isolated key storage architecture. The first-tier storage area stores the offline enterprise root key and deploys a national cryptographic physical encryption machine to achieve hardware-network isolation of the key. The second-tier storage area stores long-term valid business keys and is equipped with a memory encryption module. Business keys are only loaded into memory during program execution and are not persistently written to disk storage. The third-tier storage area stores temporary session keys dedicated to single data interactions and is equipped with a timed key destruction module that automatically clears all temporary session keys after a single interaction process ends. The second-tier storage area sends key derivation parameters and temporary session keys unilaterally to the third-tier storage area. The third-tier storage area can only initiate key validity verification requests to the multi-level national cryptographic operation unit and cannot reverse read or tamper with the original key data in the second-tier storage area.
[0012] The data access authentication unit includes an enterprise role database submodule, a dynamic token verification submodule, an access behavior log collection submodule, and a cross-enterprise data authorization submodule. The enterprise role database submodule stores the data read and write permission thresholds corresponding to each position within the enterprise. The dynamic token verification submodule connects to the enterprise's business interaction terminal to complete real-time dynamic password legality verification. The access behavior log collection submodule collects all data operation records of the terminal in real time and transmits them to the on-chain evidence storage and packaging unit. The cross-enterprise data authorization submodule generates temporary data access authorization certificates with time limits. The authorization certificate is transmitted to the SM2 asymmetric signature key exchange subunit to complete digital signature solidification. The signed authorization certificate is synchronously pushed to the on-chain evidence storage and packaging unit for block evidence storage. When cross-enterprise data interaction is initiated, in addition to generating time-limited authorization certificates and performing SM2 signature evidence storage, the SM2 key negotiation process is also invoked. Both parties generate independent temporary session keys and deliver them to the SM4 subunit for use. After the interaction ends, the session key is destroyed along with the three-level keys.
[0013] The on-chain evidence storage and packaging unit includes a metadata extraction submodule, a block assembly submodule, a consensus node distribution submodule, and an evidence storage index mapping submodule. The metadata extraction submodule extracts the data subject identifier, operation timestamp, operation account, SM3 hash digest, and SM2 digital signature value from the encrypted business data. The block assembly submodule concatenates all extracted metadata to generate a block body to be uploaded to the chain and writes it to the current consortium chain block height. The consensus node distribution submodule synchronously pushes the assembled block to be uploaded to the chain to all consensus nodes in the distributed blockchain evidence storage network. The evidence storage index mapping submodule establishes a mapping table that corresponds one-to-one between the local encrypted shard storage address and the on-chain block height. The mapping table is synchronously generated into multiple copies and stored in the backup nodes of the enterprise's local encrypted storage cluster.
[0014] The distributed blockchain evidence storage network adopts a consortium blockchain architecture, which includes enterprise-owned consensus nodes, third-party regulatory evidence storage nodes, and judicial verification nodes. All nodes uniformly execute the PBFT consensus mechanism to complete the legality verification of blocks. Third-party regulatory evidence storage nodes are only configured with read-only query permissions for all evidence storage blocks on the network. Judicial verification nodes are configured with a dedicated national cryptographic signature verification interface to retrieve block metadata to solidify electronic evidence with judicial validity. Enterprise-owned consensus nodes are only allowed to submit evidence storage blocks containing their own enterprise's business data and cannot modify or write on-chain metadata corresponding to other enterprises.
[0015] The data risk identification unit includes a traffic feature collection submodule, an anomaly rule matching submodule, a risk classification and determination submodule, and a blocking command issuance submodule. The traffic feature collection submodule captures bidirectional data packets transmitted between the enterprise's business interaction terminal and the secure encryption middleware platform in real time. The anomaly rule matching submodule has built-in risk rule libraries for three categories: batch data export, high-frequency cross-regional access, and large-scale data reading during non-working hours. The rule thresholds include dimensions such as access frequency, access time period, and data volume, and support custom configuration in the enterprise backend. The risk classification and determination submodule classifies data leakage risks into low, medium, and high levels based on the rule matching results. When the blocking command issuance submodule determines that there is a high-risk behavior, it simultaneously issues access blocking signals to the enterprise's business interaction terminal, the enterprise's local encrypted storage cluster, and the secure encryption middleware platform, and forcibly destroys all session channels corresponding to the current account.
[0016] The enterprise business interaction terminals include enterprise office terminals, customer mobile terminals, and third-party cooperation terminals. Each type of terminal has a built-in lightweight Chinese cryptographic computing plugin. The lightweight Chinese cryptographic computing plugin has a simplified SM2 identity negotiation module, which is only used to complete lightweight identity interaction during the Chinese cryptographic TLS handshake phase. At the same time, it performs local plaintext pre-hashing calculation and forwards business signature applications. The complete SM2 digital signature calculation and SM4 encryption and decryption calculation are all performed by the multi-level Chinese cryptographic computing unit in the secure encryption middleware platform. All transmission links between the enterprise business interaction terminals and the secure encryption middleware platform continuously use the Chinese cryptographic TLS encryption channel. The Chinese cryptographic TLS completes identity negotiation based on the SM2 algorithm and completes link encryption based on the SM4 algorithm.
[0017] The enterprise local encrypted storage cluster adopts a distributed sharded multi-replica storage architecture. The enterprise local encrypted storage cluster includes sharded encrypted storage nodes, encrypted backup and synchronization nodes, and data retrieval and decryption nodes. The sharded encrypted storage nodes split the business ciphertext generated by SM4 encryption into multiple replica shards according to business type and distribute them to different physical servers. The encrypted backup and synchronization nodes periodically perform sharded cross-node backup and synchronization operations. After receiving the terminal's decryption request, the data retrieval and decryption nodes send a key verification application to the secure encryption middleware platform. Only after the key verification is successful can the encrypted decryption operation be performed. The decrypted plaintext is only pushed unidirectionally to the terminal that initiated the request. No plaintext copies are retained on any node of the storage cluster.
[0018] The distributed blockchain evidence storage network incorporates an on-chain data verification smart contract, which integrates national cryptographic batch signature verification logic. Upon receiving a data retrieval request from a judicial verification node, the smart contract automatically invokes the SM2 signature verification logic to verify the legality of the digital signature used in the block operation, and invokes the SM3 hash logic to recalculate the block metadata hash digest and compare it with the original on-chain storage digest. Once both digital signature verification and hash digest comparison are passed, the smart contract automatically generates an electronic evidence certificate with judicial acceptance validity. This electronic evidence certificate includes the current on-chain block height and the collective digital signatures of all consensus nodes.
[0019] The complete implementation logic of the core national cryptographic algorithm is as follows: This invention fully integrates the SM2 elliptic curve signature key negotiation algorithm, SM3 cryptographic hash algorithm, and SM4 block symmetric encryption algorithm, which conform to the national cryptographic standards GM / T 0003, GM / T 0004, and GM / T0006, into a multi-level national cryptographic operation unit. All operation parameters, letter identifiers, and operation formulas are fully disclosed, with no hidden technical features, and fully meet the patent disclosure examination standard.
[0020] Complete operation flow and parameter explanation of SM4 symmetric encryption algorithm The SM4 algorithm uses a standardized block size and key length of 128 bits. SM4 employs a standard balanced Feistel iterative architecture, with the round function iterating for 32 rounds. For plaintext data of length other than 128 bits, it is padded to the standard block size according to the national cryptographic rules before encryption. All parameters are fully defined as follows: M: 128-bit plaintext business data packet for enterprise business data to be encrypted by the system; K: 128-bit business session symmetric key, derived from the secondary storage area of the key hierarchical management subunit; MK: SM4 initial input master key, 128 bits in length. MK is split into four groups of 32-bit unsigned integers: mk0, mk1, mk2, and mk3. rk: 32 independent round keys, including rk0 to rk31, each rk is 32 bits, generated by MK through the standard key expansion function; X: Array of intermediate states in the encryption iteration, where X0, X1, X2, and X3 are four 32-bit initial blocks after plaintext splitting; F: Feistel standard round function, input parameters include the current X array and the corresponding round key rk, output a single 32-bit iterative operation result; T: Nonlinear composite transformation function, which internally includes standard Chinese cryptographic S-box byte substitution and linear cyclic shift transformation; S: 8-bit input dedicated national cryptographic S-box replacement function, to complete byte non-linear obfuscation and eliminate plaintext linear characteristics; L: Linear shift transformation function, takes 32-bit operation data as input, performs 0-bit, 8-bit, 16-bit, and 24-bit cyclic shifts respectively, and then XORs and combines the outputs; C: 128-bit encrypted output ciphertext block. C is split into four groups of 32-bit data: C0, C1, C2, and C3. The decryption process uses the ciphertext blocks as iterative input. The round key is iterated in reverse order from rk31 to rk0. After the iteration is completed, the output block order is reversed to restore the original plaintext M.
[0021] Complete SM4 encryption steps: Step 1: Divide the 128-bit plaintext M into four equal groups of 32-bit data: X0, X1, X2, and X3. Step 2: Call the key expansion function to generate all 32 round keys rk0 to rk31 based on the initial master key MK; Step 3: Execute the Feistel round function F for 32 rounds. In each round, the X array and the corresponding round key rk are updated in real time. The intermediate state is continuously updated and iterated. Step 4: After all 32 rounds of iterative operations are completed, reverse the output order of the X array groups to obtain a complete 128-bit ciphertext block C; Step 5: The ultra-long plaintext data of the enterprise is encrypted in a cyclical manner in groups of 128 bits of fixed length. All generated ciphertext fragments are pushed to the enterprise's local ciphertext storage cluster.
[0022] Complete SM4 decryption steps: Step 1: Divide the 128-bit ciphertext C into four equal groups of 32-bit data C0, C1, C2, and C3 as the initial iteration array for decryption; Step 2: Reuse all round keys generated by the key expansion function in the encryption stage, and use the reverse order rk31 to rk0 for the decryption iteration; Step 3: Execute the Feistel round function 32 times in a loop, with the current iteration array and the reverse round key as input for each round; Step four: After 32 rounds of reverse iteration, the array blocks are directly output to restore the original 128-bit plaintext block M. SM4 decryption uses only the reverse round key, without the need for a second block reversal, strictly adhering to the national cryptographic standard.
[0023] Complete flowchart and parameter explanation of the SM2 elliptic curve asymmetric signature and key negotiation algorithm The SM2 algorithm is based on the elliptic curve of the prime field recommended by the national cryptographic standard. The underlying parameters of the curve strictly follow the GM / T 0003 standard, and all operational parameters are fully defined. G: Fixed reference point for generating elliptic curves, with publicly available standard elliptic coordinates G=(XG,YG); p: Prime number field with large modulus prime number, elliptic curve finite field operation boundary; n: The order of the elliptic curve corresponding to the generation point G, and the legal value range of the private key is 1≤dA≤n-1; dA: The main signature private key of this enterprise, stored offline in the first-level physical encryption machine of the key hierarchical management subunit; PA: This is the main public key of the enterprise, PA=[dA] G, which is generated by scalar multiplication of the private key dA and the generation point G. The public key is publicly available on the entire network. Mdata: Enterprise business metadata string to be signed, including user data operation account, operation timestamp, and data subject identifier; ZA: The hash value of the signer's corporate identity, which follows the GM / T 0003 standard and is generated by the SM3 algorithm in combination with the user identifier, elliptic curve system parameters, and the corporate public key PA. In this scheme, the user identifier adopts the corporate unified credit code. e: The final hash value of the message to be signed, e=SM3 (ZA||Mdata), || represents the sequential merging operation of bit strings; k: A unique random temporary integer for each signature, 1≤k≤n-1. Each data operation signature is regenerated by a unique k value from the built-in random cryptographic source of the secure encryption intermediate platform. (x1,y1): Temporary elliptic curve operation point, (x1,y1)=[k] G; r: the first component of the signature, r = (e + x1) mod n; s: The second component of the signature, s=((kr・dA)・(1+dA)⁻¹) mod n; This formula is mathematically equivalent to the GM / T 0003 standard SM2 signature formula, and the order of operations follows the national cryptographic standards; the on-chain smart contract signature verification logic is completely compatible with this signature rule; (1+dA)⁻¹ represents the modular multiplicative inverse, and the formula is a perfect match for the national cryptographic standard GM / T 0003; Sign: The complete SM2 digital signature result. Sign consists of two sets of values, r and s, which are appended to the block metadata and uploaded to the blockchain storage simultaneously. Ver: Standardized signature verification function. It takes the enterprise public key PA, message hash e, signature components r and s as inputs and outputs a boolean value to determine whether the digital signature is legal and valid.
[0024] SM2 cross-enterprise key negotiation supplementary parameters: PB: The public key that the partner company publishes to the outside world; DB: The private key stored by the partner company. kA, kB: Random temporary integers independently generated by each negotiating party; W: Coordinates of the intermediate elliptic curve point derived from the key; KDF: National Cryptographic Standard Key Derivation Function. It takes as input the complete coordinate bit string of elliptic curve points and the target key length, and outputs a 128-bit session symmetric key K, which is directly supplied to the SM4 symmetric encryption subunit for calling.
[0025] Complete SM3 cryptographic hash algorithm process and parameter explanation The SM3 algorithm outputs a fixed 256-bit hash digest for triple integrity verification of enterprise plaintext, encrypted ciphertext, and on-chain metadata. All operational letter parameters are fully defined as follows: IN: Input bit string of arbitrary length. The input content can be plaintext business data, SM4 ciphertext, or complete block metadata. V: Iteration register vector, V0 is a fixed initial value according to the national cryptographic standard, with a fixed length of 256 bits; Bi: Input grouping for single operation, each group is fixed at 512 bits. If the original input is less than 512 bits, the normalized padding function PAD is executed. PAD: Standard padding function, appends 1 bits to the end of the original bit string, then adds 0 bits until the block length modulo 512 equals 448, and finally stores the total bit length of the original input IN in the last 64 bits; W: Message extension word array, containing 68 groups of 32-bit operation words from W0 to W67, generated by linear shifting and XOR operations from group Bi; SS1, SS2: Temporary variables in the intermediate stages of a single compression round iteration; TT1, TT2: Temporary variables used in the iterative calculation of the compression function; FF is a Boolean logic permutation function: in iterations 0-15, FF(X,Y,Z)=X⊕Y⊕Z; in iterations 16-63, FF(X,Y,Z)=(X∧Y)∨(¬X∧Z); GG is a Boolean logic permutation function: for iterations 0-15, GG(X,Y,Z)=X⊕Y⊕Z; for iterations 16-63, GG(X,Y,Z)=(X∧Z)∨(¬Y∧Z); Vnew: A 256-bit register vector updated after a single 512-bit block compression operation; Hash: SM3 ultimately outputs a 256-bit integrity check hash digest. The hash is equal to the register vector V64 after 64 rounds of compression operations and is stored in on-chain metadata for cross-stage integrity comparison.
[0026] Complete SM3 calculation steps: Step 1: Perform PAD normalization padding on the original input bit string IN to split it into all 512-bit independent blocks B1 to Bn; Step 2: Load the fixed initial register vector V0 of the national cryptographic standard; Step 3: Read each 512-bit group Bi sequentially to generate a message extension array W, and execute the compression function 64 times in a loop. In each round, select the corresponding FF and GG permutation functions according to the round number to continuously update the register vector. Step four: After all inputs are processed through grouping and compression, the register vector outputs a 256-bit final hash digest. Step 5, the judicial verification and data integrity check stage, involves the system recalculating the local original data hash value and comparing it with the hash value persistently stored on the blockchain. If the values do not match, it is directly determined that the target data has been tampered with.
[0027] The enterprise user data security protection system based on national cryptographic algorithms and blockchain notarization of the present invention has the following advantages compared with the prior art: This invention innovatively designs a four-layer integrated protection architecture comprising a terminal, an encrypted intermediate platform, a local encrypted storage cluster, and a consortium blockchain network. It deeply integrates four core modules: lightweight pre-computation at the terminal, three-level hardware isolation national cryptographic encryption, real-time risk control of transmission traffic, and hierarchical permission consortium blockchain evidence storage. This completely overcomes the inherent defects of existing technologies where encryption and evidence storage modules are fragmented and lack a unified cross-module linkage risk control link. It achieves closed-loop security protection for enterprise user data throughout its entire lifecycle, from terminal collection, transmission encryption, local encrypted fragment storage, to on-chain solidification of operation metadata, possessing outstanding substantive features. Existing technologies only disclose independent national cryptographic encryption storage systems or independent blockchain evidence storage systems, lacking an integrated protection architecture with four-terminal collaboration. This invention organically combines multiple technical features such as multi-level hierarchical national cryptographic operations, dynamic and refined role authentication, hierarchical risk identification of transmission traffic, and three-level permission isolation consortium blockchain evidence storage.
[0028] This invention features a unique three-level hardware isolation hierarchical key storage architecture, which strictly distinguishes between three types of key carriers: offline root keys, long-term business keys, and single-session temporary key. Each type is equipped with a dedicated protection mechanism, including offline isolation via physical encryption machines, memory encryption that does not reside on disk, and automatic destruction after a single interaction. This completely solves the technical defects of existing technologies, such as centralized storage of keys and long-term key resident on disk, which leads to continuous leakage risks. It is equipped with SM2 standardized key negotiation and derivation logic, which automatically generates independent temporary session keys for cross-enterprise collaborative data interaction and automatically destroys them immediately after the interaction process ends, significantly improving the overall key security strength.
[0029] The distributed blockchain evidence storage network innovatively sets up a differentiated permission isolation logic for consortium chain nodes, dividing them into three completely isolated node types: enterprise-owned consensus nodes, third-party regulatory evidence storage nodes, and judicial verification nodes. The underlying chain smart contract has built-in national cryptographic automatic batch verification and signature calculation logic. During the judicial evidence collection stage, there is no need to deploy commercial cryptographic equipment offline. It can complete SM2 digital signature legality verification and SM3 hash integrity comparison with one click, and automatically generate electronic evidence storage certificates with judicial acceptance. Existing general blockchain evidence storage systems do not have a node hierarchical permission isolation design, nor do they have a blockchain-based underlying automatic verification smart contract with national cryptographic rules, and the offline evidence collection process is cumbersome and time-consuming.
[0030] The secure encryption middleware platform independently integrates a dedicated data risk identification unit, which captures bidirectional network traffic between the terminal and the encryption platform in real time around the clock. It has a built-in standardized risk rule library for three types of high-frequency data theft attacks, classifies the leakage risk into three levels based on the matching results, and executes differentiated handling logic. When a high-risk attack behavior is determined, it simultaneously blocks the access channels of the terminal, storage cluster, and middleware platform and destroys the current session, realizing dynamic front-end protection of the transmission link. Existing traditional protection solutions only realize static data storage encryption and lack a real-time risk control and blocking mechanism for transmission traffic, and cannot intercept web crawlers and unauthorized batch data export network attacks from other locations in advance.
[0031] The multi-level national cryptographic computing unit fully integrates the complete set of domestic commercial cryptographic algorithms SM2, SM3, and SM4. The data collection, transmission, storage, digital signature, and full verification links all adopt national cryptographic standard operations, solving the industry pain point of existing blockchain systems relying on non-compliant foreign RSA and SHA cryptographic algorithms. The terminal only deploys a lightweight SM3 pre-hash forwarding plugin, while the complete high-strength national cryptographic operations are centrally deployed on a secure encryption middleware platform, balancing the computing power load of various types of terminals with the overall data security protection strength, and adapting to various business terminal scenarios such as enterprise office PCs, customer mobile terminals, and third-party cooperative servers.
[0032] The data access authentication unit establishes a refined role and permission library adapted to the enterprise's organizational structure, and is equipped with a dynamic token real-time verification and a cross-enterprise collaborative data temporary authorization digital signature solidification and traceability mechanism. All authorization credentials for external partners to access enterprise user data are solidified through SM2 digital signature and synchronously stored on the blockchain. Every external cross-entity data access retains a permanent and tamper-proof traceability record, eliminating the security risk of unauthorized access to the enterprise's core privacy data. Existing traditional protection solutions only rely on simple account passwords to complete access verification, and do not have a refined job-level permission and cross-enterprise temporary authorization traceability logic.
[0033] The enterprise's local encrypted storage cluster adopts a distributed sharded multi-replica independent storage architecture. After the decryption operation is completed, plaintext data is only pushed to the requesting terminal in one direction. All storage nodes do not retain any plaintext copies, thus avoiding the risk of mass leakage of plaintext in the storage cluster. The evidence storage index mapping submodule establishes a one-to-one mapping relationship between the encrypted sharded storage disk address and the block height on the blockchain, realizing bidirectional fast matching of local encrypted retrieval and on-chain operation tracing, which greatly reduces the data retrieval time for enterprise security audits and judicial evidence collection. Attached Figure Description
[0034] Figure 1 This is a block diagram of the overall four-layer system architecture of the present invention; Figure 2A block diagram of multi-level national cryptographic operation units within a secure encryption intermediate platform; Figure 3 A block diagram showing the combination of the data access authentication unit, on-chain evidence storage and packaging unit, and data risk identification unit for a secure encryption intermediate platform; Figure 4 This is a block diagram of the distributed blockchain evidence storage network and enterprise local encrypted storage cluster architecture of the present invention. Detailed Implementation
[0035] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.
[0036] Example 1: An enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage. The overall four-layer collaborative architecture includes enterprise business interaction terminals, a secure encryption middleware platform, a distributed blockchain evidence storage network, and an enterprise local encrypted storage cluster. The enterprise business interaction terminals are further divided into three types of terminal devices: enterprise office PCs, customer mobile phones, and third-party supply chain servers. All terminal devices have built-in lightweight national cryptographic operation plugins. The lightweight plugins only perform local plaintext SM3 pre-hash operations, while the complete SM2 digital signature and SM4 encryption / decryption high-strength operations are all uploaded to the secure encryption middleware platform for centralized processing. All network transmission links between the terminals and the encryption middleware platform continuously use national cryptographic TLS encryption channels, completely eliminating plaintext hijacking and man-in-the-middle attacks.
[0037] The secure encryption middleware platform is the core carrier of the overall protection system of this invention. The platform has four core units that operate in parallel and collaboratively: a multi-level national cryptographic operation unit, a data access authentication unit, an on-chain evidence storage and packaging unit, and a data risk identification unit. All internal data exchanges between the units are completed through the platform's high-speed encrypted bus. The data transmitted on the bus is protected by SM4 encryption in real time throughout the process, thus avoiding the risk of data theft within the platform.
[0038] The multi-level national cryptographic operation unit comprises four sub-units: the SM4 symmetric encryption sub-unit, which batch processes various types of plaintext data with different sensitivity levels, including enterprise customer mobile phone numbers, online transaction records, employee salary and personnel information, and supply chain commercial contracts, performing standardized SM4 encryption operations according to 128-bit fixed blocks to output ciphertext; the SM2 asymmetric signature key exchange sub-unit, which stores the enterprise's global offline public and private key pairs, generating an independent SM2 standard digital signature for each enterprise data write, batch export, and cross-enterprise retrieval operation; and the SM3... The hash verification subunit calculates the original plaintext hash, the encrypted ciphertext hash, and the complete metadata hash of the block in real time, completing triple data integrity verification. The key hierarchical management subunit builds a three-level hardware-isolated storage area. The first-level storage area deploys a physical encryption machine that conforms to the national cryptographic level 2 standard, storing the enterprise's root private key offline. The physical encryption machine is disconnected from the external network throughout the process, allowing only local manual key derivation command input. The second-level storage area is equipped with a memory encryption module. Long-term business keys are only loaded into memory during program execution. All keys in memory are automatically cleared immediately when the server is powered off, eliminating the risk of leakage to disk. The third-level storage area is responsible for storing temporary session keys for single data interaction. The third-level storage area has a built-in timed key destruction module, which automatically clears all temporary session keys after the closed-loop process of a single data interaction ends. The second-level storage area sends key derivation parameters and temporary session keys unilaterally to the third-level storage area. The third-level storage area can only initiate key validity verification requests to the multi-level national cryptographic operation unit and cannot reverse read or tamper with the original key data in the second-level storage area, preventing reverse key leakage.
[0039] When internal employees, external customers, or third-party supply chain partners initiate arbitrary data read / write requests, the request data packet first enters the data access authentication unit to complete a multi-level verification process. The enterprise role library submodule pre-stores the data read / write permission thresholds for all organizational positions within the enterprise. Financial positions are only allowed to read transaction log data, while HR positions can only access employee personnel information. Unauthorized access across positions is directly intercepted and anomaly logs are retained. The dynamic token verification submodule connects to the enterprise's unified identity authentication platform to verify the six-digit national cryptographic dynamic token uploaded by the terminal in real time. Token verification failure directly blocks the data request. The access behavior log collection submodule synchronously captures the requesting account, terminal public IP, operation initiation time, and operation data type. All collected logs are pushed in real time to the on-chain evidence storage and packaging unit for on-chain solidification. When the cross-enterprise data authorization submodule receives a data retrieval request from a third-party supply chain enterprise, it generates a temporary data access authorization certificate with a validity period of 72 hours, starting from the certificate generation time. This embodiment defaults to a 72-hour validity period, but enterprises can adjust the authorization duration in the background. The authorization certificate is transmitted to SM2. The asymmetric signature key exchange subunit completes the digital signature solidification. The signed authorization certificate is synchronously pushed to the on-chain evidence storage and packaging unit to complete the tamper-proof evidence storage. After the authorization period expires, the system automatically reclaims all access permissions. There is no permanently open cross-enterprise data access channel.
[0040] After all authentication and verification passes, the plaintext business data is pushed to a multi-level national cryptographic operation unit to complete hierarchical encryption, digital signature, and hash verification. The encrypted ciphertext is then pushed to the enterprise's local ciphertext storage cluster for distributed sharding and multi-replica storage. The metadata extraction submodule simultaneously extracts the ciphertext shard storage address, operation timestamp, operation account, SM3 ciphertext hash digest, and SM2 operation digital signature value. The block assembly submodule concatenates all extracted metadata to generate a standardized block body to be added to the chain and writes it to the current consortium chain block height. The consensus node distribution submodule simultaneously pushes the assembled block to be added to the chain to all consensus nodes of the distributed blockchain evidence storage network to perform PBFT standardized consensus verification. After the consensus verification passes, the block is permanently written to the consortium chain's immutable ledger. The evidence storage index mapping submodule establishes a mapping table that corresponds one-to-one between the ciphertext shard storage disk address and the on-chain block height. The mapping table is simultaneously stored in multiple replicas to the ciphertext storage cluster backup nodes, facilitating quick matching of local ciphertext with on-chain operation records during enterprise security audits and judicial evidence collection.
[0041] The distributed blockchain evidence storage network adopts an enterprise consortium blockchain architecture. Internally, the network is divided into three categories of consensus nodes with completely isolated permissions. The first category consists of enterprise-owned consensus nodes, which are only allowed to submit their own enterprise's business data evidence storage blocks and do not have write, modify, or delete permissions for other enterprises' blocks. The second category consists of third-party regulatory evidence storage nodes, which only have read-only query permissions for all evidence storage blocks across the entire network, used for routine compliance audits by industry regulatory departments. The third category consists of judicial verification nodes, which are dedicated to connecting to the court's electronic evidence platform. The nodes have a built-in on-chain data verification smart contract. After judicial personnel initiate an electronic evidence retrieval request, the smart contract automatically calls the SM2 signature verification logic to verify the legality of the digital signature of the block's internal operations, and calls the SM3 hash algorithm to recalculate the complete metadata hash digest of the block and compare it with the original on-chain storage digest. After both the digital signature verification and hash comparison verifications are successful, the contract automatically generates a standardized electronic evidence certificate affixed with the collective digital signatures of all consensus nodes. This certificate can be directly used as legal electronic evidence in civil litigation without the need for secondary offline deployment of commercial cryptographic equipment for verification.
[0042] During the entire data transmission phase, the data risk identification unit provides 24 / 7 real-time protection. The traffic feature collection submodule continuously captures bidirectional data packets transmitted between the terminal and the secure encryption intermediate platform. The anomaly rule matching submodule incorporates three types of standardized data theft risk rules, including configurable threshold rules for batch data export, high-frequency cross-regional access, and large-scale data reading during off-peak hours. Rule thresholds include dimensions such as access frequency, access time, and data volume, and support custom configuration in the enterprise backend. The high-frequency cross-regional access rule identifies IPs from different locations. More than 20 data retrieval requests per hour are considered a violation. The following are the system's default thresholds, which enterprises can modify as needed. The off-peak reading rule identifies large-scale batch user data reading behavior between midnight and 6 AM. The risk classification and judgment submodule matches risk rules and classifies leakage risks into low, medium, and high levels. Low-level risks only retain operation logs and upload them to the blockchain, without blocking the current access operation. Medium-level risks push real-time alarm SMS and background pop-up prompts to the enterprise security administrator. High-level risks trigger the blocking command issuance submodule, which simultaneously issues multi-layer access blocking signals to the requesting terminal, the enterprise's local encrypted storage cluster, and the secure encryption middleware platform, and forcibly destroys all session channels of the current operating account. This blocking record is simultaneously uploaded to the blockchain for permanent evidence storage.
[0043] The enterprise's local encrypted storage cluster adopts a distributed sharded multi-replica independent storage architecture. The sharded encrypted storage nodes split the SM4-encrypted business ciphertext into three replicas according to customer, finance, human resources, and supply chain business types, and distribute them to different physical servers. The failure of a single hardware node will not cause the complete loss of ciphertext. The ciphertext backup and synchronization node automatically performs sharded cross-node backup and synchronization operations during the low business load period at midnight every day to ensure the disaster recovery capability of the ciphertext data. When enterprise employees or external partners initiate data decryption and read requests, the data retrieval and decryption node sends a key verification application to the secure encryption middleware platform. After the key hierarchical management subunit verifies that the operation account permissions and SM2 temporary authorization digital signature are all compliant, it issues a dedicated decryption session key for one-time use. After the data retrieval and decryption node completes the ciphertext decryption operation, it only pushes the decrypted plaintext to the terminal that initiated the request in one direction. No plaintext copies are retained on any server nodes in the storage cluster. The decryption session key is automatically destroyed immediately after a single use. Key destruction is divided into regular automatic destruction (triggered at the end of a single interaction) and risk-forced destruction (triggered by high-risk access). Risk-forced destruction has a higher priority than regular destruction.
[0044] The system standardizes the complete data writing closed-loop workflow: Step 1: The enterprise business interaction terminal collects the original plaintext business data of enterprise users, completes local SM3 pre-hash calculation with the built-in national cryptographic lightweight computing plugin, and uploads the plaintext, pre-hash value, and terminal device identity to the secure encryption middleware platform through the national cryptographic TLS encryption channel. Step 2: The data access authentication unit performs layered verification of the terminal's dynamic token and the corresponding job role permissions of the operation account. In cross-enterprise data retrieval scenarios, it additionally verifies the pre-stored SM2 signed temporary authorization certificate. If the authentication verification fails, it directly returns an interception prompt to the terminal and records the abnormal operation log. Step 3: After all authentications are passed, the plaintext data is pushed to the multi-level national cryptographic operation unit. The key hierarchical management subunit derives the business session key that matches the data sensitivity level and transmits it to the SM4 subunit to complete the plaintext block encryption. The SM2 subunit generates an independent digital signature for this data writing operation based on the enterprise's offline private key. The SM3 subunit calculates the final hash digest of the ciphertext after encryption. Step 4: The ciphertext fragments generated by SM4 encryption are pushed to the enterprise's local ciphertext storage cluster for multi-replica distributed storage, and the storage address of the ciphertext fragments is synchronously transmitted to the on-chain evidence storage and packaging unit. Step 5: The metadata extraction submodule extracts the storage address, operation timestamp, operation account, SM3 ciphertext hash, and SM2 operation digital signature; the block assembly submodule splices them together to generate standardized blocks to be added to the chain; and the consensus node distribution submodule pushes them to all nodes of the consortium chain to perform PBFT consensus verification. Step 6: After consensus verification is completed, the block is permanently written to the distributed blockchain evidence storage network. The evidence storage index mapping submodule establishes a mapping table between the encrypted storage address and the on-chain block height and stores multiple copies synchronously. All metadata from this operation is permanently and immutably stored in the on-chain ledger. Step 7: The data risk identification unit captures the entire transmission traffic and completes risk rule matching. If there is no risk, the writing process ends in a closed loop. If there is low or medium risk, an alarm message is pushed to the enterprise security administrator. If a high-risk theft behavior is determined, the terminal, storage cluster, and intermediate platform access channels are immediately blocked at multiple levels, and the blocking record is stored on the blockchain.
[0045] The system standardizes and completes the closed-loop workflow for judicial evidence collection and verification: Step 1: The judicial verification node initiates an electronic evidence retrieval request to the on-chain data verification smart contract within the distributed blockchain evidence storage network, and inputs the on-chain block height corresponding to the data to be retrieved. Step 2: The on-chain smart contract automatically retrieves all complete storage metadata of the target block, automatically calls the underlying SM2 signature verification operation logic, and uses the enterprise's publicly available public key to verify the legality of the digital signature of the block's internal operation. Step 3: The smart contract uses the built-in standardized SM3 operation logic to recalculate the hash digest of all metadata of the block and compare it item by item with the hash values stored on the original blockchain. Step 4: Once both the digital signature verification and hash integrity comparison are successfully matched, the smart contract automatically generates an electronic evidence certificate with judicial validity. The certificate includes the collective digital signatures of all consensus nodes, the on-chain standard timestamp, and the target block height. Step 5: The judicial verification node downloads standardized electronic evidence certificates for direct use in civil litigation. If any verification fails, the system determines that the block metadata has been tampered with, automatically generates a data tampering anomaly report, and pushes it to the enterprise security management terminal and third-party supervision node to complete the risk warning.
[0046] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.
Claims
1. A data security protection system for enterprise users based on national cryptographic algorithms and blockchain evidence storage, comprising an enterprise business interaction terminal, a secure encryption intermediate platform, a distributed blockchain evidence storage network, and an enterprise local encrypted storage cluster; the enterprise business interaction terminal establishes a bidirectional communication connection with the secure encryption intermediate platform, and the secure encryption intermediate platform establishes communication connections with the distributed blockchain evidence storage network and the enterprise local encrypted storage cluster respectively; characterized in that, The secure encryption middleware platform integrates multi-level national cryptographic operation units, data access authentication units, on-chain evidence storage and packaging units, and data risk identification units. The multi-level national cryptographic operation units are used to complete hierarchical encryption, digital signature, and integrity verification operations for all business user data of the enterprise. The data access authentication unit is used to verify data access requests according to the enterprise's role permissions. The on-chain evidence storage and packaging unit is used to extract the metadata corresponding to the encrypted data and assemble blocks to upload to the blockchain network. The data risk identification unit is used to collect the transmitted data stream in real time to identify abnormal access behavior. The distributed blockchain evidence storage network is used to store evidence storage metadata. The enterprise's local encrypted storage cluster is used to store the original encrypted business encrypted data.
2. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The multi-level national cryptographic operation unit includes an SM4 symmetric encryption subunit, an SM2 asymmetric signature key exchange subunit, an SM3 hash check subunit, and a key hierarchical management subunit. The SM4 symmetric encryption subunit is used to perform batch encryption and decryption of plaintext business data blocks for enterprises. The SM2 asymmetric signature key exchange subunit is used to implement digital signature of enterprise entity identity, public and private key distribution, and cross-enterprise data interaction key negotiation. The SM3 hash check subunit is used to calculate the hash digest of plaintext and ciphertext to complete data integrity comparison. The key hierarchical management subunit stores the enterprise root key, long-term business key, and single-interaction temporary session key in a hierarchical manner. The key hierarchical management subunit establishes communication connections with the SM4 symmetric encryption subunit, the SM2 asymmetric signature key exchange subunit, and the SM3 hash check subunit respectively through the platform's internal high-speed encryption bus.
3. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 2, characterized in that, The key hierarchical management subunit constructs a three-level isolated key storage architecture; The primary storage area stores the enterprise root key in an offline state, and a national cryptographic hardware encryption machine is deployed in the primary storage area to achieve hardware network isolation of the key; The secondary storage area stores long-term valid business keys. The secondary storage area is equipped with a memory encryption module. The business keys are only loaded into memory during program execution and are not persistently stored on disk. The tertiary storage area stores temporary session keys for single data interaction. The tertiary storage area is equipped with a timed key destruction module that automatically clears all temporary session keys after a single interaction process ends. The secondary storage area sends key derivation parameters and temporary session keys unilaterally to the tertiary storage area. The third-level storage area can only send key validity verification requests to the multi-level national cryptographic operation unit. It cannot read or tamper with the original key data in the second-level storage area, thus preventing reverse key leakage.
4. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The data access authentication unit includes an enterprise role library submodule, a dynamic token verification submodule, an access behavior log collection submodule, and a cross-enterprise data authorization submodule; The Enterprise Role Library submodule stores the data read and write permission thresholds for each position within the enterprise; the Dynamic Token Verification submodule connects to the enterprise business interaction terminal to complete real-time dynamic password legality verification; and the Access Behavior Log Collection submodule collects all data operation records from the terminal in real time and transmits them to the on-chain evidence storage and packaging unit. The cross-enterprise data authorization submodule generates a temporary data access authorization certificate with a customizable validity period starting from the certificate generation time. The authorization certificate is transmitted to the SM2 asymmetric signature key exchange subunit to complete the digital signature solidification. The signed authorization certificate is then synchronously pushed to the on-chain evidence storage and packaging unit to perform block evidence storage.
5. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The on-chain evidence storage and packaging unit includes a metadata extraction submodule, a block assembly submodule, a consensus node distribution submodule, and an evidence storage index mapping submodule. The metadata extraction submodule extracts the data subject identifier, operation timestamp, operation account, SM3 hash digest, and SM2 digital signature value from the encrypted business data. The block assembly submodule concatenates all extracted metadata to generate a block body to be uploaded to the chain and writes it to the current consortium chain block height. The consensus node distribution submodule synchronously pushes the assembled block to be uploaded to the chain to all consensus nodes in the distributed blockchain evidence storage network. The evidence storage index mapping submodule establishes a mapping table that corresponds one-to-one between local encrypted shard storage addresses and on-chain block heights. The mapping table is synchronously generated into multiple copies and stored in the backup nodes of the enterprise's local encrypted storage cluster.
6. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The distributed blockchain evidence storage network adopts a consortium blockchain architecture, comprising enterprise-owned consensus nodes, third-party regulatory evidence storage nodes, and judicial verification nodes. All nodes uniformly execute the PBFT consensus mechanism to complete block legality verification. Third-party regulatory evidence storage nodes are only configured with read-only query permissions for all evidence storage blocks across the network. Judicial verification nodes are configured with a dedicated national cryptographic signature verification interface to retrieve block metadata and solidify legally valid electronic evidence. Enterprise-owned consensus nodes are only allowed to submit evidence storage blocks containing their own enterprise's business data and cannot modify or write on-chain metadata corresponding to other enterprises.
7. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The data risk identification unit includes a traffic feature collection submodule, an anomaly rule matching submodule, a risk classification determination submodule, and a blocking command issuance submodule; The traffic feature collection submodule captures bidirectional data packets between enterprise business interaction terminals and the secure encryption middleware platform in real time. The anomaly rule matching submodule has built-in risk rule bases for three types of risks: batch data export with configurable thresholds, high-frequency cross-regional access, and large-scale data reading during non-working hours. The rule thresholds include dimensions such as access frequency, access time period, and data volume, and support custom configuration in the enterprise backend. The risk classification and judgment submodule classifies data leakage risks into three levels: low, medium, and high, based on the rule matching results. When the blocking instruction issuance submodule determines that there is a high-risk behavior, it simultaneously issues access blocking signals to the enterprise business interaction terminal, the enterprise local encrypted storage cluster, and the secure encryption middleware platform, and forcibly destroys all session channels corresponding to the current account.
8. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The enterprise business interaction terminals include enterprise office terminals, customer mobile terminals, and third-party cooperation terminals. All types of terminals have built-in lightweight Chinese cryptographic computing plugins. The lightweight Chinese cryptographic computing plugins have a simplified SM2 identity negotiation module, which is only used to complete lightweight identity interaction during the Chinese cryptographic TLS handshake phase. At the same time, it performs local plaintext SM3 pre-hashing operation and forwards business signature applications. The complete SM2 digital signature operation and SM4 encryption and decryption operation are all performed by the multi-level Chinese cryptographic computing units in the secure encryption middleware platform. All transmission links between the enterprise business interaction terminals and the secure encryption middleware platform use the Chinese cryptographic TLS encryption channel. The Chinese cryptographic TLS completes identity negotiation based on the SM2 algorithm and link encryption based on the SM4 algorithm. During the handshake phase, only the lightweight SM2 interaction capability built into the terminal is called. The high-strength cryptographic operations on the business side are uniformly carried out by the secure encryption middleware platform.
9. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The enterprise local encrypted storage cluster adopts a distributed sharded multi-replica storage architecture, which includes sharded encrypted storage nodes, encrypted backup and synchronization nodes, and data retrieval and decryption nodes. The sharded encrypted storage node splits the ciphertext generated by SM4 encryption into multiple replica shards according to the business type and stores them on different physical servers. The ciphertext backup and synchronization node performs shard cross-node backup and synchronization operations on a regular basis. After receiving a decryption request from a terminal, the data retrieval and decryption node sends a key verification application to the secure encryption intermediate platform. Only after the key verification is successful can the ciphertext decryption operation be performed. The plaintext generated by decryption is only sent to the terminal that initiated the request. None of the nodes in the enterprise's local ciphertext storage cluster store plaintext data.
10. The enterprise user data security protection system based on national cryptographic algorithms and blockchain evidence storage as described in claim 1, characterized in that, The distributed blockchain evidence storage network incorporates an on-chain data verification smart contract, which integrates national cryptographic batch signature verification logic. Upon receiving a data retrieval request from a judicial verification node, the smart contract automatically invokes the SM2 signature verification logic to verify the legality of the digital signature used in the block operation, and invokes the SM3 hash logic to recalculate the block metadata hash digest and compare it with the original on-chain storage digest. Once both digital signature verification and hash digest comparison are passed, the smart contract automatically generates an electronic evidence certificate with judicial acceptance validity. This electronic evidence certificate includes the current on-chain block height and the collective digital signatures of all consensus nodes.
