A data compliance design method based on a trusted data space scenario

Abstract

This invention proposes a data compliance design method based on a trusted data space scenario, aiming to ensure the security and compliance of data circulation. Before data operations, the agreed-upon usage contract is written into a blockchain contract chain to ensure the terms are immutable. All operations during circulation are recorded in real-time on another compliance record chain, achieving full auditability. An independent computing and boundary data sandbox is created for each user, providing an isolated operating environment. Data operations within the sandbox are dynamically controlled through machine-readable contract rules generated from the contract. By periodically comparing the content on the two chains, violations can be automatically identified. After contract termination, the sandbox and its data are securely destroyed. This invention achieves refined management, transparent supervision, and compliance assurance during data sharing and use.

Description

Technical Field

[0001] This invention belongs to the field of data security technology, specifically relating to a data compliance design method based on a trusted data space scenario. Background Technology

[0002] Data compliance design in a trusted data space scenario mainly involves ensuring the compliance of data security storage, transmission, sharing, and operations. Its purpose is to ensure that data use within a trusted data space complies with legal and regulatory requirements, while protecting data confidentiality, integrity, and availability.

[0003] Existing data compliance design schemes have achieved certain results in static data protection and auditing, but they still fall short in comprehensive compliance management of the dynamic use of data within a trusted data space. Current technologies primarily focus on protecting the static encrypted storage and transmission of data, as well as user authentication, lacking oversight of the dynamic use of data within the trusted data space. Because they mainly rely on access control policies to restrict user access, they cannot meticulously manage the specific actions taken by users after legitimate access, making it difficult to ensure the full lifecycle compliance of data within the trusted data space. Especially in data-sharing scenarios, the diverse and complex ways in which different participants use data make it difficult to clearly define the data compliance responsibilities of each party through access control alone, easily leading to the phenomenon of shirking responsibility. Summary of the Invention

[0004] According to a first aspect of the present invention, the present invention claims protection for a data compliance design method based on a trusted data space scenario, comprising:

[0005] Step S1: Before the data operation begins, the authorizing party and the authorized party sign a data usage contract and write the contract content into the contract chain of the blockchain. The contract content includes authorizing party information, authorized party information, authorization period, data usage scope, data processing method and data processing purpose.

[0006] Step S2: During the data circulation process, the data operation behavior is recorded and written into the compliance record chain of the blockchain. The data operation behavior includes data uploading, downloading, modifying and deleting.

[0007] Step S3: Create an independent data sandbox for each user, which includes a computing sandbox and a boundary sandbox to isolate the data operation environment;

[0008] Step S4: Generate contract rules based on the contract content. The contract rules include subjects, actions, objects, and domains. Control the operations within the data sandbox according to the contract rules.

[0009] Step S5: Periodically compare the contents of the contract chain with the compliance record chain to identify violations in data operations;

[0010] Step S6: When the data operation is completed or the contract is terminated, the data sandbox is destroyed in accordance with the contract rules.

[0011] Furthermore, in step S1, the contract chain uses blockchain technology to store the contract content, ensuring the immutability and traceability of the contract.

[0012] Furthermore, step S3, creating a data sandbox, also includes the following sub-steps:

[0013] Sub-step S3.1: Initialize the boundary sandbox according to the user's identity and contract content. The boundary sandbox includes a data input agent, a control center, and a bypass monitoring module.

[0014] Sub-step S3.2: Initialize the computing sandbox, which includes a distributed computing service, an encrypted computing service, and a control center;

[0015] Sub-step S3.3: Embed the contract rules into the control center of the data sandbox, and dynamically control data operations according to the contract rules;

[0016] Sub-step S3.4: Configure the data sandbox with a communication module, storage module, encryption module and computing module to provide distributed computing, distributed storage, user authentication, behavior authorization, auditing and data leakage prevention services.

[0017] Furthermore, in step S4, generating contract rules also includes the following sub-steps:

[0018] Sub-step S4.1: Define the subject of the contract rules, including the operation execution body, which includes at least an auditing procedure, a deep message detection procedure, or a sandbox control node;

[0019] Sub-step S4.2: Define the actions of the contract rules, including specific operation commands, at least including initialization, review, and destruction;

[0020] Sub-step S4.3: Define the object of the contract rule, including the operation object, which includes at least data, code, model, or sandbox;

[0021] Sub-step S4.4: Define the domain of the contract rules, including the operating environment or rule set, including at least a list of trusted nodes, audit rules, or destruction rules;

[0022] Sub-step S4.5: Convert the contract rules into a machine-readable format and store them on the sandbox system server for controlling data operation processes.

[0023] Furthermore, in step S2, when the compliance record chain records data operation behavior, it also includes data entry time, data flow path, and compliance inspection results.

[0024] Furthermore, in step S5, when comparing the contract chain with the compliance record chain, it also includes checking whether the data operation exceeds the authorization period, whether the scope of data use is compliant, and whether the purpose of data processing is consistent with the contract.

[0025] Furthermore, in step S6, when destroying the data sandbox, it also includes cleaning up all data and computational traces within the sandbox and generating a destruction audit log.

[0026] Furthermore, in sub-step S3.1, the initialization of the boundary sandbox also includes configuring the listening rules of the data input agent and the contract execution logic of the control center.

[0027] Furthermore, the method also includes step S7: when a violation is identified, a violation alert is generated and the relevant responsible party is notified, while the data sandbox of the violation operation is suspended.

[0028] This invention proposes a data compliance design method based on a trusted data space scenario, aiming to ensure the security and compliance of data circulation. Before data operations, the agreed-upon usage contract is written into a blockchain contract chain to ensure the terms are immutable. All operations during circulation are recorded in real-time on another compliance record chain, achieving full auditability. An independent computing and boundary data sandbox is created for each user, providing an isolated operating environment. Data operations within the sandbox are dynamically controlled through machine-readable contract rules generated from the contract. By periodically comparing the content on the two chains, violations can be automatically identified. After contract termination, the sandbox and its data are securely destroyed. This invention achieves refined management, transparent supervision, and compliance assurance during data sharing and use. Attached Figure Description

[0029] Figure 1 A flowchart illustrating the workflow of a data compliance design method based on a trusted data space scenario, as claimed in an embodiment of the present invention.

[0030] Figure 2 A second flowchart of a data compliance design method based on a trusted data space scenario, as claimed in an embodiment of the present invention;

[0031] Figure 3 The third flowchart is a data compliance design method based on a trusted data space scenario, which is claimed in an embodiment of the present invention. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0033] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0034] According to the first embodiment of the present invention, referring to Figure 1 This invention claims protection for a data compliance design method based on a trusted data space scenario, comprising:

[0035] Step S1: Before the data operation begins, the authorizing party and the authorized party sign a data usage contract and write the contract content into the contract chain of the blockchain. The contract content includes authorizing party information, authorized party information, authorization period, data usage scope, data processing method and data processing purpose.

[0036] Step S2: During the data circulation process, the data operation behavior is recorded and written into the compliance record chain of the blockchain. The data operation behavior includes data uploading, downloading, modifying and deleting.

[0037] Step S3: Create an independent data sandbox for each user, which includes a computing sandbox and a boundary sandbox to isolate the data operation environment;

[0038] Step S4: Generate contract rules based on the contract content. The contract rules include subjects, actions, objects, and domains. Control the operations within the data sandbox according to the contract rules.

[0039] Step S5: Periodically compare the contents of the contract chain with the compliance record chain to identify violations in data operations;

[0040] Step S6: When the data operation is completed or the contract is terminated, the data sandbox is destroyed in accordance with the contract rules.

[0041] In this embodiment, the contract chain accurately records the details of the initial contract, including key information such as the authorizing party, the authorized party, the authorization period, and the scope of data use, ensuring that the contract content is tamper-proof and traceable.

[0042] The compliance record chain meticulously records all user actions on the trusted data space platform, such as uploading, downloading, modifying, and deleting data, forming a complete behavioral trajectory.

[0043] Finally, by periodically comparing the contract chain with the compliance record chain, violations in data operations can be quickly identified, providing a basis for data compliance management in a trustworthy data space and ensuring the transparency and auditability of data operations.

[0044] The contract is signed by the authorizing party and the authorized party, and the contract content is written into the contract chain. The contract content includes key information such as the information of the authorizing party and the authorized party, the authorization period, whether the data can be transferred, the scope of data transfer, the data processing method, and the purpose of data processing.

[0045] Data entry involves the data resource supply platform entering the data tables into the database, while simultaneously writing information such as the authorizing party, the authorized party, the authorization period, and the data entry time into the compliance record chain to ensure the compliance of the data source.

[0046] Data tables circulate within a trusted data space. The process and status of data circulation are recorded and written into a compliant record chain to ensure the transparency and traceability of data circulation.

[0047] The data table processing method is recorded and written into the compliance record chain to ensure that the data processing process complies with the contract.

[0048] Purpose of data processing: The purpose of data processing is recorded and written into the compliance record chain to ensure the legality and compliance of data processing.

[0049] Personal information data within the data is subject to compliance checks, and the results are written into the compliance record chain to ensure the compliance of the data content.

[0050] By comparing contracts and compliance records, and by comparing the contract chain and the compliance record chain, violations in data operations can be discovered, providing a basis for data compliance management in a trustworthy data space and ensuring the transparency and auditability of data operations.

[0051] Furthermore, in step S1, the contract chain uses blockchain technology to store the contract content, ensuring the immutability and traceability of the contract.

[0052] Furthermore, referring to Figure 2 In step S3, creating a data sandbox further includes the following sub-steps:

[0053] Sub-step S3.1: Initialize the boundary sandbox according to the user's identity and contract content. The boundary sandbox includes a data input agent, a control center, and a bypass monitoring module.

[0054] Sub-step S3.2: Initialize the computing sandbox, which includes a distributed computing service, an encrypted computing service, and a control center;

[0055] Sub-step S3.3: Embed the contract rules into the control center of the data sandbox, and dynamically control data operations according to the contract rules;

[0056] Sub-step S3.4: Configure the data sandbox with a communication module, storage module, encryption module and computing module to provide distributed computing, distributed storage, user authentication, behavior authorization, auditing and data leakage prevention services.

[0057] In this embodiment, the sandbox is divided into a computation sandbox and a boundary sandbox. The computation sandbox consists of three parts: CEndpointA, CEndpointB, and CEndpointC. CEndpointA is a traditional distributed computing service; CEndpointA serves as the endpoint of the computation sandbox, connecting other CEndpointA instances to form a distributed computing environment, such as HDFS, MapReduce, Spark, Mahout, and MLLIB. CEndpointC is a distributed computing service based on homomorphic encryption; CEndpointC connects other CEndpointC instances to form an encrypted distributed computing environment, such as federated learning. CEndpointB is the control center of the computation sandbox, connecting to different boundary sandboxes through embedded contracts and controlling CEndpointA and CEndpointC according to the contract rules.

[0058] The boundary sandbox consists of three parts: BEndpointA, BEndpointB, and BEndpointC. BEndpointA—the endpoint of the boundary sandbox—receives user input and accepts bypass monitoring and control from BEndpointC, while also being controlled by both BEndpointB and BEndpointC. BEndpointB—the control center of the boundary sandbox—connects to the computation sandbox through an embedded contract and controls both BEndpointA and the data receiver's BEndpointC according to the contract rules. BEndpointC—acting as a proxy for the data input party—performs bypass monitoring and control of BEndpointA.

[0059] The entire sandbox system will provide four main services: distributed computing, distributed storage, user authentication and behavior authorization, and auditing and data leakage prevention. The system's technical architecture is divided into four modules: communication, storage, encryption, and computing. The communication module ensures dynamic networking of nodes, distributed consistency, and breakpoint resumption; the storage module ensures distributed encrypted data storage and disaster recovery; the encryption module ensures the confidentiality and integrity of data storage and transmission; and the computing module provides users with big data computing and analysis services. It requires the following technical support: key management, distributed consistency, redundancy backup, distributed authentication and access control, distributed computing, and deep packet inspection.

[0060] The external interface information of the sandbox system is shown in Table 1;

[0061] Table 1. External Interface Information of Sandbox System

[0062]

[0063] Furthermore, referring to Figure 3 In step S4, generating contract rules further includes the following sub-steps:

[0064] Sub-step S4.1: Define the subject of the contract rules, including the operation execution body, which includes at least an auditing procedure, a deep message detection procedure, or a sandbox control node;

[0065] Sub-step S4.2: Define the actions of the contract rules, including specific operation commands, at least including initialization, review, and destruction;

[0066] Sub-step S4.3: Define the object of the contract rule, including the operation object, which includes at least data, code, model, or sandbox;

[0067] Sub-step S4.4: Define the domain of the contract rules, including the operating environment or rule set, including at least a list of trusted nodes, audit rules, or destruction rules;

[0068] Sub-step S4.5: Convert the contract rules into a machine-readable format and store them on the sandbox system server for controlling data operation processes.

[0069] In this embodiment, the contract is a series of activity rules within the sandbox system, including node allocation and data verification. These rules are jointly formulated and signed by the data requester and data provider, and govern behavior within the boundary sandbox and computation sandbox. Each service requires a contract, which includes the following sections, each further divided into four parts: Subject (the entity executing the contract rules), Action (the specific command to be executed), Object (the recipient of the action), and Domain (the environment or rules in which the command operates). The contract format is shown in Table 2.

[0070] Table 2 Overall Design of Contract Rules

[0071]

[0072] (1) List of nodes that start the boundary sandbox: Subject-ClientsList (a list of nodes that can have control over the boundary sandbox), Action-init (command to start the sandbox), Object-BoundarySandbox (the boundary sandbox), Domain-HostsList (a list of trusted nodes for running the boundary sandbox).

[0073] (2) List of startup nodes for the computing sandbox: Subject-SandboxServer (sandbox service), Action-init (start sandbox command), Object-ComputeSandbox (computation sandbox), Domain-HostsList (list of trusted nodes for running the computing sandbox);

[0074] (3) Code upload review rules: Subject-AduitProgram (review program), Action-reviewCode (review code), Object-Code (uploaded code), Domain-HostsList (code review rules);

[0075] (4) Data upload review rules: Subject-AduitProgram (review program), Action-reviewInputData (review data), Object-InputData (uploaded data), Domain (shared data rules);

[0076] (5) Download model monitoring rules: Subject-DPI (deep message detection program), Action-reviewModel (detection training model), Object-Model (the model obtained after calculation), Domain (model detection rules);

[0077] (6) Download data monitoring rules: Subject-DPI (deep packet inspection program), Action-reviewOutputData (detect download data), Object-OutputData (downloaded data), Domain (shared data rules);

[0078] (7) Boundary Sandbox Destruction Rules: Subject-BoundarySandboxOwner (Boundary Sandbox Control Node), Action-burn (Destruction), Object-BoundarySandbox (Boundary Sandbox), Domain-BurningRules (Destruction Rules);

[0079] (8) Calculation sandbox destruction rules: Subject-SandboxServer (sandbox service), Action-burn (destruction), Object-BoundarySandbox (computation sandbox), Domain-BurningRules (destruction rules);

[0080] Furthermore, in step S2, when the compliance record chain records data operation behavior, it also includes data entry time, data flow path, and compliance inspection results.

[0081] Furthermore, in step S5, when comparing the contract chain with the compliance record chain, it also includes checking whether the data operation exceeds the authorization period, whether the scope of data use is compliant, and whether the purpose of data processing is consistent with the contract.

[0082] Furthermore, in step S6, when destroying the data sandbox, it also includes cleaning up all data and computational traces within the sandbox and generating a destruction audit log.

[0083] Furthermore, in sub-step S3.1, the initialization of the boundary sandbox also includes configuring the listening rules of the data input agent and the contract execution logic of the control center.

[0084] In this embodiment, the sandbox processing flow includes:

[0085] The data requester downloads the contract form from the system, fills it out, and uploads it to the sandbox system server.

[0086] The sandbox system server reviews the contract submitted by the data requester to determine if it complies with system rules. If it does not, the data requester is notified to modify the contract or abandon the application; if it complies, the data provider receives the contract submitted by the data requester, reviews it, and signs it.

[0087] The data provider reviews and signs the contract. If the review fails, the data applicant A is notified to modify the contract or abandon the application. After the review is approved, the sandbox system server verifies the contract, opens the boundary sandbox between the data applicant and the data provider, and embeds the contract.

[0088] After the sandbox system server verifies the contract, the data requester activates the relevant service programs in the boundary sandbox, reviews the code according to the contract requirements, and uploads the code to the boundary sandbox; the data provider activates the relevant service programs in the boundary sandbox as needed, reviews the data according to the contract, uploads it to the boundary sandbox, connects with the data requester, and activates the monitoring service program.

[0089] After the data provider connects with the data requester and starts the monitoring service program, the sandbox system server selects trusted computing nodes and starts the computing sandbox according to the contract requirements.

[0090] After the sandbox system server selects trusted computing nodes and starts the computing sandbox according to the contract requirements, the data requester uploads data and sends the analysis model according to the contract requirements; the data provider monitors and reviews the data call of the data requester according to the contract.

[0091] Finally, the boundary sandbox is destroyed after the data requester completes the upload; the boundary sandbox is destroyed after the data provider completes the monitoring; and the computation sandbox is destroyed after the sandbox system server completes the calculation.

[0092] Furthermore, the method also includes step S7: when a violation is identified, a violation alert is generated and the relevant responsible party is notified, while the data sandbox of the violation operation is suspended.

[0093] The technical effects achieved by this invention include at least the following:

[0094] By integrating blockchain and sandbox technologies, this innovative approach combines the immutability and traceability of blockchain with the isolation and security of a data sandbox, enabling comprehensive monitoring and refined management of data operations.

[0095] The dual-chain data monitoring system employs two independent blockchains: a contract chain and a compliance record chain. These blockchains separately record contract details and operational behaviors, forming a complete behavioral trajectory. By comparing the two chains, violations can be quickly identified, providing a basis for data compliance management and ensuring operational transparency and auditability.

[0096] A contract-driven sandbox system defines data operation rules in the form of contracts, covering elements such as subjects, actions, objects, and domains, enabling fine-grained control over data operations. Based on these contractual rules, the sandbox system rigorously reviews and monitors the behavior of data requesters and providers, ensuring the legality and compliance of data processing.

[0097] Multi-dimensional data security is ensured through a collaborative computing sandbox and boundary sandbox, which are responsible for data computation and boundary control respectively, creating a multi-layered isolation environment to prevent data leakage and misuse. The sandbox system provides services such as distributed computing, storage, user authentication, behavior authorization, auditing, and data leakage prevention, comprehensively protecting data security.

[0098] Process data compliance management records and monitors all data operations from signing, storage, transfer, processing to destruction, ensuring compliance throughout the data lifecycle. Real-time monitoring and auditing promptly identify and intervene in violations, preventing potential losses and promoting the security and reliability of data sharing and circulation.

[0099] To enhance the transparency and auditability of data operations, blockchain technology records the entire data operation process, forming an immutable audit record. This allows regulatory agencies and internal audit departments to view the data operation history at any time, quickly detect violations, and improve the transparency and trustworthiness of data management.

[0100] To enhance data security, data sandboxes provide an isolated environment for data operations, preventing data leaks and misuse. Even during data sharing and computation, data remains under the protection of the sandbox, ensuring its confidentiality, integrity, and availability. Furthermore, the sandbox system has data leakage prevention capabilities, further reducing data security risks.

[0101] This invention enables compliant management of data throughout its entire lifecycle, covering all stages from data generation to destruction. It ensures that the use of data within a trusted data space complies with legal and regulatory requirements, such as the Data Security Law and the Personal Information Protection Law, effectively avoiding legal risks and economic losses caused by data violations.

[0102] Promoting data sharing and circulation involves clarifying the responsibilities of all parties in data sharing scenarios, resolving trust issues between data providers and users, providing reliable technical support for data sharing and circulation, promoting the healthy development of the data element market, and unlocking the value of data.

[0103] The specific embodiments of the invention have been described in detail above, but they are only examples, and this application is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications or substitutions to the invention are also within the scope of this application. Therefore, all equivalent changes, modifications, and improvements made without departing from the spirit and principles of this application should be covered within the scope of this application.

Claims

1. A data compliance design method based on a trusted data space scenario, characterized in that, include: Step S1: Before the data operation begins, the authorizing party and the authorized party sign a data usage contract and write the contract content into the contract chain of the blockchain. The contract content includes authorizing party information, authorized party information, authorization period, data usage scope, data processing method and data processing purpose. Step S2: During the data circulation process, the data operation behavior is recorded and written into the compliance record chain of the blockchain. The data operation behavior includes data uploading, downloading, modifying and deleting. Step S3: Create an independent data sandbox for each user, which includes a computing sandbox and a boundary sandbox to isolate the data operation environment; Step S4: Generate contract rules based on the contract content. The contract rules include subjects, actions, objects, and domains. Control the operations within the data sandbox according to the contract rules. Step S5: Periodically compare the contents of the contract chain with the compliance record chain to identify violations in data operations; Step S6: When the data operation is completed or the contract is terminated, destroy the data sandbox according to the contract rules; In step S3, creating a data sandbox also includes the following sub-steps: Sub-step S3.1: Initialize the boundary sandbox according to the user's identity and contract content. The boundary sandbox includes a data input agent, a control center, and a bypass monitoring module. Sub-step S3.2: Initialize the computing sandbox, which includes a distributed computing service, an encrypted computing service, and a control center; Sub-step S3.3: Embed the contract rules into the control center of the data sandbox, and dynamically control data operations according to the contract rules; Sub-step S3.4: Configure the data sandbox with a communication module, storage module, encryption module and computing module to provide distributed computing, distributed storage, user authentication, behavior authorization, auditing and data leakage prevention services; The sandbox is divided into a computational sandbox and a boundary sandbox. The computational sandbox consists of three parts: CEndpointA, CEndpointB, and CEndpointC. CEndpointA---Traditional distributed computing service. CEndpoint is the endpoint of the computing sandbox. Connecting other parties' CEndpointA forms a distributed computing environment. CEndpointC is a distributed computing service based on homomorphic encryption, connecting CEndpointC instances from other parties to form an encrypted distributed computing environment. CEndpointB is the control center of the computation sandbox. It connects to different boundary sandboxes through embedded contracts and controls CEndpointA and CEndpointC according to the contract rules. The boundary sandbox consists of three parts: BEndpointA, BEndpointB, and BEndpointC. BEndpointA is the endpoint of the boundary sandbox. BEndpointA receives user input and accepts bypass listening and control from BEndpointC, while also accepting control from BEndpointB and BEndpointC. BEnpointB is the control center of the boundary sandbox. It connects to the computation sandbox through an embedded contract and controls BEndpointA and the data receiver's BEndpointC according to the contract rules. BEndpointC acts as a proxy for the data input side, bypassing and controlling BEndpointA.

2. The data compliance design method based on a trusted data space scenario as described in claim 1, characterized in that, In step S1, the contract chain uses blockchain technology to store contract content, ensuring the immutability and traceability of the contract.

3. The data compliance design method based on a trusted data space scenario as described in claim 1, characterized in that, In step S4, generating contract rules further includes the following sub-steps: Sub-step S4.1: Define the subject of the contract rules, including the operation execution body, which includes at least an auditing procedure, a deep message detection procedure, or a sandbox control node; Sub-step S4.2: Define the actions of the contract rules, including specific operation commands, at least including initialization, review, and destruction; Sub-step S4.3: Define the object of the contract rule, including the operation object, which includes at least data, code, model or sandbox; Sub-step S4.4: Define the domain of the contract rules, including the operating environment or rule set, including at least a list of trusted nodes, audit rules, or destruction rules; Sub-step S4.5: Convert the contract rules into a machine-readable format and store them on the sandbox system server for controlling data operation processes.

4. The data compliance design method based on a trusted data space scenario as described in claim 1, characterized in that, In step S2, when the compliance record chain records data operation behavior, it also includes data entry time, data flow path and compliance inspection results.

5. The data compliance design method based on a trusted data space scenario as described in claim 1, characterized in that, In step S5, when comparing the contract chain with the compliance record chain, it is also necessary to check whether the data operation exceeds the authorization period, whether the scope of data use is compliant, and whether the purpose of data processing is consistent with the contract.

6. The data compliance design method based on a trusted data space scenario as described in claim 1, characterized in that, In step S6, when destroying the data sandbox, it also includes cleaning up all data and computational traces within the sandbox and generating a destruction audit log.

7. The data compliance design method based on a trusted data space scenario as described in claim 3, characterized in that, In sub-step S3.1, the initialization of the boundary sandbox also includes configuring the listening rules of the data input agent and the contract execution logic of the control center.

8. The data compliance design method based on a trusted data space scenario as described in claim 1, characterized in that, It also includes step S7: when a violation is detected, a violation alert is generated and the relevant responsible party is notified, while the data sandbox of the violation operation is suspended.

Images