Comprehensive security management system for trusted data space
Through the dynamic permission analysis, nonlinear positioning and encryption operation chain technology of the comprehensive security management system, the problems of insufficient security and difficult to guarantee data integrity in the distributed data environment are solved, and the security and integrity guarantee of data access is achieved. Improves transparency and security of data management.
Patent Information
- Application Number
- CN202411534762.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-31
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2044-10-31
AI Technical Summary
The prior art has problems such as insufficient security and difficult to guarantee data integrity in complex distributed data environments, especially in terms of permission control and data verification, which are difficult to meet high security needs.
Provide a comprehensive security management system to ensure data access security through dynamic permission analysis, use key parameters to nonlinear position target blocks to improve retrieval efficiency, verify data integrity, and realize full traceability and audit of operations by generating an encrypted operation chain, enhancing Transparency and security of data management.
It realizes the security and integrity of data access, improves the transparency and security of data management, prevents data leakage and tampering, and meets high security needs.
Smart Images

Figure CN119046912A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data management technology, and in particular to a comprehensive security management system for a trusted data space. Background Art
[0002] With the continuous advancement of digital transformation, data security and privacy protection have become the focus of attention in various industries. In particular, in data space management, how to ensure the trustworthiness and security of data is an urgent problem to be solved.
[0003] Existing technical solutions typically employ single-method access control and data verification, but this approach suffers from insufficient security and difficulty in guaranteeing data integrity when facing complex distributed data environments. For example, some existing technologies lack granular management of user access control and data extraction processes, increasing the risk of data leakage or tampering. Furthermore, existing technologies employ relatively simple methods for monitoring and storing user operations, which are insufficient to meet high security requirements.
[0004] Therefore, the present invention provides a comprehensive security management system for trusted data spaces. Summary of the Invention
[0005] This invention provides a comprehensive security management system for trusted data spaces, which ensures data access security through dynamic permission analysis, improves retrieval efficiency by using key parameters to nonlinearly locate target blocks, verifies data integrity to prevent tampering, and achieves full traceability and auditing of operations by generating encrypted operation chains, thereby enhancing the transparency and security of data management.
[0006] This invention provides a comprehensive security management system for trusted data spaces, comprising: Permission determination module: When a user sends a data extraction request to a blockchain node, the node obtains and analyzes the user's data to determine whether to grant the user extraction permission. Request location module: Locates the target block in the distributed ledger based on the key parameters of the extraction request; Data verification module: Extracts target data from the target block and verifies the integrity of the data; Data monitoring module: When a user operates on the target data, the module monitors the user's data operation, generates an operation chain, and stores it in encrypted form. The data monitoring module includes: Operation capture unit: When a user performs data operations, it monitors the user's data operations based on a preset multi-level capture mechanism and records relevant information for each data operation; Operation chain generation unit: Generates corresponding operation chains based on relevant information of user data operations; Operation chain encryption unit: Based on a preset two-layer encryption strategy, each operation node in the operation chain is individually encrypted using a preset node encryption algorithm, while the entire operation chain is encrypted as a whole using a preset chain encryption algorithm. Operation chain storage unit: Stores the encrypted operation chain based on a preset storage method, generates a new chain when storing the operation chain, and links the new chain with the previous storage chain to form a storage chain; The operation chain generation unit includes: Data computation subunit: performs hash calculations on the data involved in the data operation based on a preset combined hash algorithm to generate a unique hash value for the operation data; Data chain generation subunit: Generates a data chain based on the data version affected by each data operation, the specific data operation summary of each data operation, the dependency relationship between the data and related data in each data operation, and the hash value of the data and related data in each data operation. Permission chain generation subunit: Generates a permission chain based on user information and authorization records of data operations; Behavior chain generation subunit: Generates behavior chains based on the type of data operation performed by the user, the time of the operation, and the context information of the operation. Operation chain determination sub-unit: The data chain, permission chain, and behavior chain are associated based on a preset association algorithm to generate the corresponding operation chain.
[0007] This invention provides a comprehensive security management system for trusted data spaces, including an access control module comprising: Data Acquisition Unit: When a user sends a data extraction request to a blockchain node, the unit analyzes the data extraction request and acquires the relevant data for the data extraction request. Permission determination unit: Acquires and analyzes user data to determine user access permissions; Permission determination unit: Based on the user's access permissions and the relevant data of the data extraction request, it determines whether to grant the user extraction permission.
[0008] This invention provides a comprehensive security management system for trusted data spaces, including an access control unit comprising: Information extraction subunit: Obtains basic user information and extracts user security level and historical access records from the user database; Level determination sub-unit: Based on user roles and departments, retrieve the data access permission level corresponding to the user from the preset permission rule database; Record Analysis Subunit: Analyzes the user's historical access records, and then combines this with the user's basic information to determine the user's behavioral trust level. ;in, The trust level of user behavior, where F represents the frequency of user access to the system. The average access frequency for all users. This represents the normalized frequency of user access to the system, where β is a preset adjustment coefficient for the access frequency. The preset weight for access frequency, where t is the total time a user spends accessing the system. The preset expected total access time, These are preset adjustment parameters used to control the impact of access time deviation on behavioral trust. Score users for abnormal behaviors identified based on their historical access records. These are preset adjustment parameters used to control the impact of abnormal behavior on behavioral trust levels. It is the hyperbolic tangent function. This is the mapping value of the basic information of the i-th user. This is a preset standard mapping value corresponding to the basic information of the i-th user. This is a preset adjustment parameter used to control the impact of differences in users' basic information on behavioral trust, where n is the number of items in the user's basic information. Score Determination Sub-unit: Based on the user's behavioral trust level and corresponding data access permission level, determine the user's comprehensive access permission score. ;in, The overall access permission score for the user, where L represents the user's basic data access permission level. Trust in user behavior Preset weights are used to control data access permissions. To control the preset weights of user behavior trust, To adjust the impact weights of scores on differences in data access permissions and user behavior trust, The conversion coefficient corresponding to the user's basic data access permission level. The conversion coefficient corresponding to the user's level of trust in their behavior. A preset adjustment coefficient corresponding to the difference between data access permissions and user behavior trust level. For preset adjustment items, To provide a smooth transition between user behavior trust and data access permissions, This is a preset scaling factor used to adjust the overall calculation results; Permission determination subunit: Determines whether to grant the user extraction permission based on the user's comprehensive access permission score and the preset permission score.
[0009] This invention provides a comprehensive security management system for trusted data spaces, including a request location module, comprising: Parameter extraction unit: Analyzes the user's data extraction request and then obtains several request parameters of the user's data extraction request; Data determination unit: Determines the matching hash value of the target dataset to be extracted based on the request parameters. ;in, The matching hash value of the target dataset to be extracted. Here, t is the first nested hash value, and t is the timestamp corresponding to the current time. , These are the preset first random salt value and second random salt value, respectively. For user ID, This is the second nested hash value. This is the status data for the currently requested operation; Data matching unit: Based on the matching hash value of the target dataset to be extracted, match the corresponding block on the blockchain, and extract the hash value of each transaction record in the corresponding block; Block location unit: The hash values of all transaction records in the corresponding block are matched with the matching hash values of the target dataset to be extracted. If the hash value of the corresponding block exists in the matching hash value of the target dataset to be extracted, the corresponding block is located as the target block.
[0010] This invention provides a comprehensive security management system for trusted data spaces, including a data verification module, comprising: Data extraction unit: Extracts target data from the located target block and determines the hash value of the target data that needs to be verified; Data Validation Unit: Based on the hash value of the target data to be verified, the completeness of the extracted target data is verified by matching the hash value with the target dataset. ;in, For the integrity of the target data, The hash value of the target data that needs to be verified. For the matching hash value of the target dataset, The hash value that needs to be verified is the j-th data block of the target data. Let be the matching hash value of the j-th data block in the target dataset, and m be the number of hash values of the target block appearing in the target dataset. This is the bitwise XOR operator, used to compare the differences between two hash values. To preset the hash judgment threshold, To perform modulo operations.
[0011] This invention provides a comprehensive security management system for trusted data spaces, wherein the node encryption algorithm is a symmetric encryption algorithm and the chain encryption algorithm is an asymmetric encryption algorithm.
[0012] This invention provides a comprehensive security management system for trusted data spaces. It ensures data access security through dynamic permission analysis, improves retrieval efficiency by using key parameters to nonlinearly locate target blocks, verifies data integrity to prevent tampering, and achieves full traceability and auditing of operations by generating encrypted operation chains, thereby enhancing the transparency and security of data management. Attached Figure Description
[0013] In order to more clearly illustrate the technical solutions in the present invention or the prior art, a brief introduction is given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0014] Figure 1 This is a schematic diagram of the structure of a comprehensive security management system for a trusted data space provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0015] To make the objectives, technical solutions, and advantages of the present invention more clear, the technical solutions of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the embodiments described are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.
[0016] Example 1 like Figure 1 As shown in the figure, an embodiment of the present invention provides a comprehensive security management system for a trusted data space, comprising: Permission determination module: When a user sends a data extraction request to a blockchain node, the node obtains and analyzes the user's data to determine whether to grant the user extraction permission. Request location module: Locates the target block in the distributed ledger based on the key parameters of the extraction request; Data verification module: Extracts target data from the target block and verifies the integrity of the data; Data monitoring module: When a user operates on the target data, the module monitors the user's data operation, generates an operation chain, and stores it in encrypted form. The data monitoring module includes: Operation capture unit: When a user performs data operations, it monitors the user's data operations based on a preset multi-level capture mechanism and records relevant information for each data operation; Operation chain generation unit: Generates corresponding operation chains based on relevant information of user data operations; Operation chain encryption unit: Based on a preset two-layer encryption strategy, each operation node in the operation chain is individually encrypted using a preset node encryption algorithm, while the entire operation chain is encrypted as a whole using a preset chain encryption algorithm. Operation chain storage unit: Stores the encrypted operation chain based on a preset storage method, generates a new chain when storing the operation chain, and links the new chain with the previous storage chain to form a storage chain; The operation chain generation unit includes: Data computation subunit: performs hash calculations on the data involved in the data operation based on a preset combined hash algorithm to generate a unique hash value for the operation data; Data chain generation subunit: Generates a data chain based on the data version affected by each data operation, the specific data operation summary of each data operation, the dependency relationship between the data and related data in each data operation, and the hash value of the data and related data in each data operation. Permission chain generation subunit: Generates a permission chain based on user information and authorization records of data operations; Behavior chain generation subunit: Generates behavior chains based on the type of data operation performed by the user, the time of the operation, and the context information of the operation. Operation chain determination sub-unit: The data chain, permission chain, and behavior chain are associated based on a preset association algorithm to generate the corresponding operation chain.
[0017] In this embodiment, a blockchain node is a computing device participating in a blockchain network. It is responsible for maintaining and verifying data records in the blockchain. Nodes share data and jointly execute network protocols. For example, in a blockchain network, each node keeps a complete copy of the ledger. When a user sends a data retrieval request, these nodes process the request and verify the authenticity of the data. In this embodiment, a data extraction request is a request sent by a user to the blockchain network to extract or access specific data from the blockchain. For example, a company sends a data extraction request to the blockchain to obtain a contract document that they previously stored on the blockchain. In this embodiment, extraction permission refers to a user's permission to extract specific data from the blockchain. The granting of permission is based on analysis of the user's identity and the content of the request. For example, if a user wants to extract contract data for a project, the system analyzes the user's identity and permission configuration to determine whether to allow them to obtain the data. If the user is a signatory to the contract, extraction permission is granted.
[0018] In this embodiment, the key parameters of the extraction request are specific information used to locate the target data in the blockchain, including: the unique identifier of the data, the timestamp, or the data category. For example, when a user requests to retrieve a transaction record, the key parameters include the transaction ID, the timestamp, or the public keys of both parties to the transaction.
[0019] In this embodiment, the target block refers to the block in the blockchain that contains the data requested by the user. For example, the contract data requested by the user may be stored in the 500th block, which is the target block. In this embodiment, the target data refers to the specific data that the user hopes to obtain from the blockchain through the extraction request. The target data may be the encrypted hash of a contract document, which the user needs to verify the authenticity of the contract. In this embodiment, data integrity means that the data in the blockchain is not tampered with during the extraction process and maintains its original state. For example, when a user extracts a contract document, the system will verify whether the hash value of the file is consistent with that at the time of storage to ensure data integrity.
[0020] In this embodiment, user data operations refer to various operations performed by the user on target data in the blockchain, such as reading, modifying or deleting. For example, the user can view, update notes or sign the extracted contract documents. In this embodiment, the operation chain refers to the record chain generated by the system when the user operates on the data, which records the order and details of the operation. For example, every read and modify operation performed by the user on contract data will be recorded in the operation chain for auditing and traceability. In this embodiment, encrypted storage refers to storing user operation chains and other sensitive data after encrypting them to protect data privacy and security. For example, the system will encrypt all user operation records of contracts and store them on the blockchain, so that even if an unauthorized user obtains these data, they will not be able to read the contents.
[0021] In this embodiment, the target block is located in the distributed ledger based on the key parameters of the extraction request. The location of blockchain data may depend on the chain structure of blocks, either by sequential traversal or by searching based on the block hash value. A complex hash function is used to map the key parameters to a specific block location in the blockchain, rather than traversing every block in the blockchain one by one. This hash mapping can quickly narrow down the search range and directly locate the target block.
[0022] In this embodiment, when a user operates on target data, the user's data operations are monitored to generate an operation chain, which is then encrypted and stored. When a user performs an operation on specific data (such as a file, record, or database entry), the module records these operations and generates an operation chain. The operation chain is a chain-like log that records the order and content of user operations, enabling detailed tracking of each action. The generated operation chain is encrypted to ensure the security and integrity of the operation records, and then stored in the system, on the blockchain, or in other secure storage media. It not only records user behavior but can also be regarded as a "tamper-proof" and "accountability" mechanism, providing a highly efficient way to track and verify the legality of any data operation, and even auditing in the event of internal malicious behavior. The encrypted storage of the operation chain ensures that even if the system is attacked or data is leaked, the operation records remain private and immutable.
[0023] In this embodiment, the multi-layered capture mechanism is divided into three types: real-time capture, timed capture, and triggered capture. Real-time capture is used for real-time monitoring of critical data operations, timed capture is used for periodically recording non-critical operations, and triggered capture is used for monitoring specific events or abnormal situations.
[0024] In this embodiment, the preset dual-layer encryption strategy is a double encryption method adopted by the system to ensure the security of the operation chain. This strategy includes two layers: first, each operation node in the operation chain is encrypted individually, and then the entire operation chain is encrypted as a whole, thereby providing multi-layer security protection. Suppose a user performs "read" and "modify" operations on certain data, the system will first encrypt the "read" and "modify" operation nodes separately, and then encrypt the entire operation chain as a whole, ensuring that the operation information cannot be tampered with or leaked at multiple levels.
[0025] In this embodiment, the operation chain not only includes timestamps, user IDs, and data digests, but also needs to generate a multi-chain structure, including data chains, permission chains, and behavior chains. Each chain records information of different dimensions and is interconnected through specific algorithms.
[0026] In this embodiment, the storage chain is a chain structure formed by storing encrypted operation chains sequentially and generating a new chain linked to the previously stored operation chains. This storage method ensures the continuity and integrity of the operation chain, while facilitating traceability and auditing. For example, when a user completes a series of operations and generates an encrypted operation chain, the system links this operation chain to the previous operation chains. For instance, if operation chain 1 records the user's data operations from last week, and operation chain 2 records the operations from this week, the system will link operation chain 2 to operation chain 1, forming a continuously growing storage chain that ensures the traceability of all operations. In this embodiment, the data involved in the data operation refers to the data content that is processed, modified, or accessed in a specific operation. For example, if an update operation is performed on a record in a database, the data involved in the data operation may be all fields of that record. In this embodiment, the preset combined hash algorithm is a combination of encryption algorithms used to generate unique identifiers for data. It usually combines multiple hash algorithms to increase security and collision resistance. For example, SHA-256 and MD5 can be used together. First, the data is hashed using SHA-256, and then the result is processed by MD5 hashing to enhance the uniqueness of the data. In this embodiment, the operation data hash value is a unique identifier generated by calculating the data involved in the operation using a hash algorithm. It is used to ensure the integrity and immutability of the data. If a piece of text data "data123" is processed, the operation data hash value generated by the SHA-256 algorithm may be "e1a0f68e...".
[0027] In this embodiment, the data version refers to the new version generated after each data operation, so as to track the historical changes of the data. For example, a document is version 1 when it is first saved, and is saved as version 2 after modification. A new version number will be created every time it is updated. In this embodiment, the data operation summary is a brief description of each data operation, which usually includes the content and result of the operation. For example, the summary of updating a record in the database may be "update the value of field X to Y". In this embodiment, the data dependency relationship describes the association between different data items, especially how a change in one data item affects other related data. If there is a foreign key relationship between two database tables, when the data in one table is modified, it may affect the data in the other table. This is the data dependency relationship.
[0028] In this embodiment, the authorization record for data operations involves multiple levels of authorization or crosses permission boundaries, and records the user IDs and authorization timestamps of all users involved in the authorization. In this embodiment, the operation types are read, write, delete, and modify; In this embodiment, the context information of the operation includes: the source IP of the operation, the device type, and the operating environment (such as the operating system, software version, etc.).
[0029] The beneficial effects of the above technical solution are: ensuring data access security through dynamic permission analysis, improving retrieval efficiency by using key parameters to non-linearly locate target blocks, verifying data integrity to prevent tampering, and realizing full traceability and auditing of operations by generating encrypted operation chains, thereby enhancing the transparency and security of data management.
[0030] Example 2 This invention provides a comprehensive security management system for trusted data spaces, including an access control module comprising: Data Acquisition Unit: When a user sends a data extraction request to a blockchain node, the unit analyzes the data extraction request and acquires the relevant data for the data extraction request. Permission determination unit: Acquires and analyzes user data to determine user access permissions; Permission determination unit: Based on the user's access permissions and the relevant data of the data extraction request, it determines whether to grant the user extraction permission.
[0031] In this embodiment, a blockchain node refers to an independent participant or computer in a blockchain network. It stores all or part of the blockchain data and participates in the blockchain's consensus mechanism. Each node can send, receive, verify, and store transaction and block data, forming a decentralized network structure. For example, in a blockchain-based file-sharing system, suppose there are five nodes (A, B, C, D, E). These nodes all participate in the maintenance of the blockchain network. Each node stores the hash value and metadata of all files. When a user sends a data retrieval request, node A receives the request and is responsible for verifying the user's permissions, deciding whether to allow access to the requested data. In this embodiment, the relevant data for a data extraction request refers to the information associated with the request when a user sends a data extraction request to a blockchain node. This includes the user's identity information, the type of data requested, the timestamp of the request, and specific conditions of the request. For example, user B sends a request to node A to obtain the content of a certain file. The relevant data may include: user B's identity information (e.g., user ID), the identifier of the requested file, the request time (2024-08-22 12:00), and other request parameters (such as the specified file version number).
[0032] In this embodiment, user access permissions refer to the permission level or access rights assigned to a specific user by the blockchain system, determining which data the user can access or which operations they can perform. These permissions are typically determined based on the user's identity, role, or organization, and are closely related to the blockchain network's access control policies. For example, in a company's internal blockchain system, user C, as a project manager, has permission to access project documents but not financial records. Access permission determination will be based on user C's role and the specific data type of the request.
[0033] In this embodiment, permission determination is the process by which the system, upon receiving a data extraction request, determines whether to allow the user to access the requested data based on the user's access permissions and the relevant data in the request. This process is typically executed by the permission determination unit, based on preset access control rules or policies. For example, when user D requests access to a sensitive data file, the system first obtains user D's access permissions and finds that user D only has ordinary access permissions. According to the rules of the permission determination unit, the system decides to reject user D's request and returns a "no access" response.
[0034] The beneficial effects of the above technical solution are: by integrating blockchain nodes and dynamic permission analysis, it achieves accurate and real-time permission control, enhances the security of the data space, ensures the immutability of the permission determination process, prevents malicious access, and improves the system's adaptability to complex permission scenarios.
[0035] Example 3 This invention provides a comprehensive security management system for trusted data spaces, including an access control unit comprising: Information extraction subunit: Obtains basic user information and extracts user security level and historical access records from the user database; Level determination sub-unit: Based on user roles and departments, retrieve the data access permission level corresponding to the user from the preset permission rule database; Record Analysis Subunit: Analyzes the user's historical access records, and then combines this with the user's basic information to determine the user's behavioral trust level. ;in, The trust level of user behavior, where F represents the frequency of user access to the system. The average access frequency for all users. This represents the normalized frequency of user access to the system, where β is a preset adjustment coefficient for the access frequency. The preset weight for access frequency, where t is the total time a user spends accessing the system. The preset expected total access time, These are preset adjustment parameters used to control the impact of access time deviation on behavioral trust. Score users for abnormal behaviors identified based on their historical access records. These are preset adjustment parameters used to control the impact of abnormal behavior on behavioral trust levels. It is the hyperbolic tangent function. This is the mapping value of the basic information of the i-th user. This is a preset standard mapping value corresponding to the basic information of the i-th user. This is a preset adjustment parameter used to control the impact of differences in users' basic information on behavioral trust, where n is the number of items in the user's basic information. Score Determination Sub-unit: Based on the user's behavioral trust level and corresponding data access permission level, determine the user's comprehensive access permission score. ;in, The overall access permission score for the user, where L represents the user's basic data access permission level. Trust in user behavior Preset weights are used to control data access permissions. To control the preset weights of user behavior trust, To adjust the impact weights of scores on differences in data access permissions and user behavior trust, The conversion coefficient corresponding to the user's basic data access permission level. The conversion coefficient corresponding to the user's level of trust in their behavior. A preset adjustment coefficient corresponding to the difference between data access permissions and user behavior trust level. For preset adjustment items, To provide a smooth transition between user behavior trust and data access permissions, This is a preset scaling factor used to adjust the overall calculation results; Permission determination subunit: Determines whether to grant the user extraction permission based on the user's comprehensive access permission score and the preset permission score.
[0036] In this embodiment, the frequency of user access to the system is an average value, representing the number of times a user accesses the system within a certain period of time; In this embodiment, the system retrieves the user's corresponding data access permission level from the preset permission rule database based on the user's role and department. This is done by extracting the user's corresponding permission level from the database according to the user's role and department within the organization. Users with different roles and departments will have different access permissions, ensuring that each type of user can only access data related to their work. For example, in a company, the finance manager and the engineers in the technical department have different roles and permissions. The finance manager may be granted permission to view financial statements, while the engineer may be restricted to accessing technical documents. The system will retrieve the corresponding permission level from the permission rule database based on their roles and departments.
[0037] In this embodiment, the total access time refers to the total amount of time a user spends accessing the system within a certain period of time, which measures the length of time a user stays or uses the system. For example, if a user accesses the system for a total of 3 hours in a day, then these 3 hours are the user's total access time. In this embodiment, the preset expected total access time is the ideal access time range that the system pre-sets for different types of users to measure whether the user's access behavior is normal. Suppose that the system stipulates that the ideal time for ordinary employees to access the system is 2 hours per day. If a user's access time is significantly higher or lower than this expected value, the system may consider the user's behavior to be abnormal. In this embodiment, the preset adjustment parameter used to control the impact of access time deviation on the score is a parameter pre-set in the system. It is used to adjust the degree of influence of the deviation between the user's actual access time and the expected access time on the final score. If a user's total access time deviates significantly from the preset expected time, the adjustment parameter can amplify or reduce the impact of this deviation on the user's behavior trust level, ensuring that the score reasonably reflects the user's behavior. In this embodiment, the preset adjustment parameter used to control the impact of abnormal behavior on the score is a pre-set parameter used to adjust the degree of impact of abnormal behavior in the user's historical access records on the overall score. If a user has had abnormal access behavior in the past, such as frequently accessing the system outside of working hours, this parameter can amplify or reduce the impact of such abnormal behavior on the user's trust level. In this embodiment, the abnormal behavior score determined based on historical access records is a score assigned by the system to a user for potential abnormal behavior based on the user's past access records. This score is used to assess whether a user has engaged in risky behavior. If a user repeatedly attempts to access data beyond their authorized permissions, their abnormal behavior score may be very high, thereby lowering their overall trust score. In this embodiment, the preset standard mapping value corresponding to the user's basic information is a set of standard values preset by the system for the user's basic information, which are used to compare and evaluate whether the user's basic information is within the normal range. Assuming that the system presets the user's years of work experience to be 5 years, then the difference between the basic information of a user with only 1 year of work experience and the standard mapping value may affect their permission score.
[0038] In this embodiment, user behavior trust level is a scoring index used to measure the reliability and security of user behavior. It is calculated based on multiple factors such as user access frequency, total time, and abnormal behavior. If a user's access behavior is consistent and compliant, their behavior trust level will be high; conversely, users who frequently exhibit abnormal behavior will have a lower trust level. In this embodiment, the weighting factor used to adjust the impact of the difference in data access permissions and user behavior trust scores is an adjustment factor used to control the degree of influence of the difference in data access permissions and user behavior trust scores on the final comprehensive score. If the user's behavior trust score is significantly different from their preset data access permissions, this weighting factor can adjust the impact of this difference on the final access score, making the score more fair.
[0039] The beneficial effects of the above technical solution are: by comprehensively analyzing user roles, access frequency, historical behavior and basic information, it achieves refined permission management, integrates a dual evaluation mechanism of behavioral trust level and data access permission level, dynamically adjusts user permission scores, improves the security and credibility of the data space, and effectively prevents potential risks of abnormal behavior.
[0040] Example 4 This invention provides a comprehensive security management system for trusted data spaces, including a request location module, comprising: Parameter extraction unit: Analyzes the user's data extraction request and then obtains several request parameters of the user's data extraction request; Data determination unit: Determines the matching hash value of the target dataset to be extracted based on the request parameters. ;in, The matching hash value of the target dataset to be extracted. Here, t is the first nested hash value, and t is the timestamp corresponding to the current time. , These are the preset first random salt value and second random salt value, respectively. For user ID, This is the second nested hash value. This is the status data for the currently requested operation; Data matching unit: Based on the matching hash value of the target dataset to be extracted, match the corresponding block on the blockchain, and extract the hash value of each transaction record in the corresponding block; Block location unit: The hash values of all transaction records in the corresponding block are matched with the matching hash values of the target dataset to be extracted. If the hash value of the corresponding block exists in the matching hash value of the target dataset to be extracted, the corresponding block is located as the target block.
[0041] In this embodiment, the request parameters include: a unique identifier for the data (such as a file hash), the data generation time, the uploader ID, and metadata related to the data.
[0042] In this embodiment, the first nested hash value is an initial hash value generated based on a set of key parameters of the user request. It is obtained by combining and hashing multiple parameters (such as timestamp, random salt value, user ID, etc.). For example, if a user requests to extract a dataset, the system combines the current timestamp, the randomly generated salt value, and the user ID, and then performs a hash operation to obtain the first nested hash value. This hash value is used to uniquely identify a specific part of the parameters in the current request. In this embodiment, the second nested hash value is obtained by further hashing the first nested hash value with additional state data or other parameters. This is used to more accurately identify the target dataset. In the system, in addition to the first nested hash value, the system may also add the requested state data for a second hash operation to generate the second nested hash value. This further ensures the uniqueness and security of the data request. In this embodiment, the user ID is an encoded value used to identify the user who initiated the operation.
[0043] In this embodiment, addition in the formula represents string concatenation or binary concatenation.
[0044] In this embodiment, matching analysis refers to the system comparing the hash value of the extracted target dataset with the hash values recorded in the blockchain to determine whether a matching hash value exists, thereby identifying the block where the target dataset is located. For example, in the system, a user requests to extract a dataset, generating a corresponding matching hash value. The system then performs matching analysis on the hash values of all transaction records in the blockchain. If it finds that the hash value of a certain block matches the matching hash value of the target dataset, the system determines that the block contains the data requested by the user.
[0045] The beneficial effects of the above technical solution are as follows: by introducing multiple hashes and random salt values, even if the input content changes slightly, the output hash value will be completely different, ensuring the integrity of the data. The irreversibility of the hash function ensures that the original data cannot be easily deduced from the hash value. The use of salt values increases randomness, effectively ensuring the uniqueness and accuracy of the target data, while improving the efficiency of data location and extraction, preventing data tampering and mis-retrieval, and enhancing the reliability of the system.
[0046] Example 5 This invention provides a comprehensive security management system for trusted data spaces, including a data verification module, comprising: Data extraction unit: Extracts target data from the located target block and determines the hash value of the target data that needs to be verified; Data Validation Unit: Based on the hash value of the target data to be verified, the completeness of the extracted target data is verified by matching the hash value with the target dataset. ;in, For the integrity of the target data, The hash value of the target data that needs to be verified. For the matching hash value of the target dataset, The hash value that needs to be verified is the j-th data block of the target data. Let be the matching hash value of the j-th data block in the target dataset, and m be the number of hash values of the target block appearing in the target dataset. This is the bitwise XOR operator, used to compare the differences between two hash values. To preset the hash judgment threshold, To perform modulo operations.
[0047] In this embodiment, the hash value that needs to be verified for the target data is the hash value extracted from the target data to verify its integrity. By calculating this hash value, it is determined whether the data has been tampered with during transmission or storage. Suppose that a certain target data extracted from the blockchain is file A, the system will generate a hash value based on the content of file A, which is the hash value that needs to be verified for the target data. This hash value is an important identifier for verifying the integrity of the data. In this embodiment, the matching hash value of the target data dataset is a hash value generated by the system for the dataset to which the target data belongs. This hash value is used to match the extracted hash value to verify the integrity and correctness of the data. For example, assuming file A belongs to dataset B, the system will generate a hash value for dataset B, which is the matching hash value of the target data dataset. This value is an important reference for the system to verify whether the extracted data is consistent with the original data. In this embodiment, the preset hash judgment threshold is a system-preset threshold used to measure whether the difference between two hash values is acceptable. If the difference between the two hash values is less than this threshold, the data is considered complete; otherwise, there may be a problem, for example... Set a preset hash judgment threshold of "0", which means that only completely identical hash values can pass the verification; if the threshold is set to "1", a certain range of differences is allowed, such as hash values that are only 1 bit different. In this embodiment, Returns a value representing the difference, 0 for the same and 1 for different; In this embodiment, the data verification module assumes the system manages data from a highly sensitive research project. Researcher B manipulated a dataset, such as exporting data and deleting the original files. For example, the system detects that Researcher B typically only views data and doesn't delete anything; this action could be a sign of a potential mole or stolen account activity, triggering additional security checks. The operation chain serves not only for auditing and tracing but also as a tool for proactive defense and anomaly detection. This encrypted operation chain not only verifies the authenticity of the operation but also prevents the operator from tampering with or erasing their actions.
[0048] The beneficial effects of the above technical solution are: by combining bitwise XOR operation and preset hash judgment threshold, the hash value of the target data is verified block by block, ensuring that the data is error-free during extraction and transmission, and effectively preventing potential tampering and damage, thereby improving the security and reliability of the system.
[0049] Example 6 The present invention provides a comprehensive security management system for trusted data spaces, wherein the node encryption algorithm is a symmetric encryption algorithm and the chain encryption algorithm is an asymmetric encryption algorithm.
[0050] In this embodiment, a symmetric encryption algorithm is an encryption method in which the same key is used for both encryption and decryption. That is, the key used for encryption is the same as the key used for decryption. Symmetric encryption algorithms have the advantages of fast encryption speed and high computational efficiency, but key management and transmission security are critical issues. Suppose a node in the operation chain records a user's "read" operation on certain data. The system will use a symmetric encryption algorithm (such as AES) to encrypt the information from that "read" operation. If the key used for encryption is "key123", then the same "key123" must also be used for decryption to recover the original operation information. In this embodiment, the asymmetric encryption algorithm uses a pair of related keys: a public key and a private key. The public key is used to encrypt data, and the private key is used to decrypt data. Asymmetric encryption algorithms solve the security problem in key transmission because encryption and decryption use different keys. Even if the public key for encryption is made public, the data remains secure because decryption requires the corresponding private key. For example, after generating the entire operation chain, the system uses an asymmetric encryption algorithm (such as RSA) to encrypt the entire operation chain. Assuming the system uses the public key "publicKey123" to encrypt the operation chain, only a user or system holding the private key "privateKey123" that matches "publicKey123" can decrypt and view the entire contents of the operation chain. This encryption method ensures that even if the operation chain is intercepted, only an authorized party can read its contents.
[0051] The beneficial effects of the above technical solution are as follows: by combining symmetric and asymmetric encryption, a highly efficient and secure two-layer encryption strategy is provided: symmetric encryption ensures fast encryption and decryption of operation nodes, while asymmetric encryption ensures the security of the entire operation chain, preventing unauthorized access. This combination effectively improves the system's security and encryption efficiency, making it suitable for the secure management of complex data spaces.
[0052] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention.
Claims
1. A comprehensive security management system for a trusted data space, characterized in that: include: Permission determination module: The user sends a data extraction request to the blockchain node, obtains the user's data and analyzes it to determine whether to grant the user extraction permission; Request location module: locates the target block in the distributed ledger according to the key parameters of the extraction request; Data verification module: extracts target data from the target block and verifies the integrity of the data; Data monitoring module: When a user operates on target data, the user's data operation is monitored to generate an operation chain, which is then encrypted and stored; The data monitoring module includes: Operation capture unit: When a user operates on data, it monitors the user's data operation based on a preset multi-level capture mechanism and records the relevant information of each data operation; Operation chain generation unit: generates a corresponding operation chain based on the relevant information of the user's data operation; Operation chain encryption unit: Based on the preset double-layer encryption strategy, each operation node in the operation chain is individually encrypted based on the preset node encryption algorithm, and the entire operation chain is encrypted as a whole based on the preset chain encryption algorithm; Operation chain storage unit: stores the encrypted operation chain based on a preset storage method, generates a new chain when storing the operation chain, and links the new chain with the previous storage chain to form a storage chain; The operation chain generation unit includes: Data calculation subunit: performs hash calculation on the data involved in the data operation based on a preset combined hash algorithm to generate a unique hash value of the operation data; Data chain generation subunit: Generates a data chain based on the data version affected by each data operation, the specific data operation summary of each data operation, the dependency relationship between the data and related data for each data operation, and the hash value of the data and related data for each data operation; Permission chain generation subunit: generates permission chains based on user information and authorization records of data operations; Behavior chain generation subunit: generates a behavior chain based on the type of data operation performed by the user, the time when the operation occurs, and the context information of the operation; Operation chain determination subunit: associate the data chain, permission chain and behavior chain based on a preset association algorithm to generate a corresponding operation chain.
2. A comprehensive security management system for a trusted data space according to claim 1, characterized in that: The permission determination module includes: Data acquisition unit: when a user sends a data extraction request to a blockchain node, the data extraction request is analyzed to obtain relevant data of the data extraction request; Permission determination unit: obtains user data and analyzes it to determine the user's access rights; Permission determination unit: performs permission determination based on the user's access rights and the relevant data of the data extraction request to determine whether to grant the user extraction permission.
3. A comprehensive security management system for a trusted data space according to claim 2, characterized in that: The authority determination unit includes: Information extraction subunit: obtains the user's basic information and extracts the user's security level and historical access records from the user database; Level determination subunit: Based on the user role and department, obtain the user's corresponding data access permission level from the preset permission rule database; Record analysis subunit: Analyze the user's historical access records, and then determine the user's behavior trustworthiness based on the user's basic information: ;in, is the user's behavior trust, F is the frequency of the user accessing the system, is the average access frequency of all users, is the normalized frequency of user access to the system, β is the preset adjustment coefficient of the access frequency, is the preset weight of the access frequency, t is the total time the user visits the system, is the expected total access time. is a preset adjustment parameter used to control the impact of access time deviation on behavior trust. Score the user's abnormal behavior based on historical access records. is a preset adjustment parameter used to control the impact of abnormal behavior on behavior trust. is the hyperbolic tangent function, Mapping value for the basic information of the i-th user, is the preset standard mapping value corresponding to the basic information of the i-th user, is a preset adjustment parameter for controlling the impact of differences in users’ basic information on behavior trust, and n is the number of items of users’ basic information; Score determination subunit: Determines the user's comprehensive access rights score based on the user's behavior trust and the corresponding data access rights level: ;in, is the user's comprehensive access permission score, L is the user's basic data access permission level, The user's behavioral trust, To control the preset weights of data access permissions, To control the preset weight of user behavior trust, is the influence weight used to adjust the data access rights and user behavior trust difference scores, is the conversion coefficient corresponding to the user's basic data access permission level, is the conversion coefficient corresponding to the user's behavior trust, The preset adjustment coefficient corresponding to the difference between data access rights and user behavior trust, is the preset adjustment item. To smooth the transition between the trust of user behavior and data access rights, is a preset scaling factor used to adjust the overall calculation result; Permission determination subunit: determines whether to grant the user's extraction permission based on the user's comprehensive access permission score and the preset permission score.
4. The integrated security management system for a trusted data space according to claim 1, characterized in that: Request positioning module, including: Parameter extraction unit: analyzes the user's data extraction request, and then obtains several request parameters of the user's data extraction request; Data determination unit: determines the matching hash value of the target data set to be extracted based on the request parameters: ;in, is the matching hash value of the target dataset to be extracted, is the first nested hash value, t is the timestamp corresponding to the current time, and are respectively the preset first random salt value and the second random salt value, is the user ID, is the second nested hash value, Status data of the current request operation; Data matching unit: extracting the hash value of each transaction record in the corresponding block based on the matching hash value of the target data set to be extracted and the corresponding block on the blockchain; Block positioning unit: The hash values of all transaction records in the corresponding block are matched and analyzed with the matching hash values of the target data set to be extracted. If the hash value in the corresponding block exists in the matching hash value of the target data set to be extracted, the corresponding block is positioned as the target block.
5. A comprehensive security management system for a trusted data space according to claim 4, characterized in that: Data validation module, including: Data extraction unit: extracts target data from the located target block and determines the hash value of the target data that needs to be verified; Data verification unit: Verifies the integrity of the extracted target data based on the hash value of the target data to be verified and the matching hash value of the target data set: ;in, For the integrity of the target data, The hash value of the target data that needs to be verified. is the matching hash value of the target dataset, The hash value of the j-th data block of the target data that needs to be verified, is the matching hash value of the jth data block of the target data set, m is the number of hash values of the target block appearing in the target data set, is a bitwise XOR operator, used to compare the difference between two hash values. To preset the hash judgment threshold, For modulo operation.
6. The integrated security management system for a trusted data space according to claim 1, characterized in that: The node encryption algorithm is a symmetric encryption algorithm, and the chain encryption algorithm is an asymmetric encryption algorithm.
Citation Information
Patent Citations
Data security protection method based on blockchain cloud computing
CN111917761A
Credible traceability system realized based on block chain
CN117076245A
Data management method and device based on block chain, storage medium and electronic equipment
CN117077171A
Electronic certificate user information security and privacy protection method
CN118395477A
Distributed governance for sharing of big data
US20220092209A1
Cited By
Security protection system of trusted data space
CN120200864A
Authority dynamic authentication management method and system for trusted data space
CN120896792A
Block chain multi-platform data trusted management method and system based on user portraits
CN120934909A
Console identity recognition method based on block chain
CN120995440A
A blockchain-based console identity recognition method
CN120995440B
