A dynamic data desensitization method, apparatus, electronic device, and computer storage medium

Abstract

This invention discloses a dynamic data anonymization method, apparatus, electronic device, and computer storage medium, relating to the field of data processing technology. The method includes: responding to a received first query request, parsing the first query request through a policy decision point to obtain a user attribute set, the requesting user's private key, and a query target field; identifying the multi-user authentication identifier corresponding to the query target field; sending a second or third query request to a policy execution point according to a preset access policy; responding to a received second query request, obtaining first anonymized data corresponding to the query target field through the policy execution point; and responding to a received third query request, verifying the multi-user authentication key through the policy execution point and obtaining second anonymized data corresponding to the query target field according to the third query request. This invention is compatible with various access requirements and application scenarios, providing secure and flexible data anonymization processing.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and specifically to a dynamic data desensitization method, apparatus, electronic device, and computer storage medium. Background Technology

[0002] With the rapid development of information technology, the amount of data in all industries is exploding, making data security protection increasingly important. Traditional data protection methods typically rely on static, single access control and simple de-identification techniques, such as data encryption or replacement. However, these traditional measures are inadequate when faced with diverse and complex application scenarios, and cannot meet the needs for efficient and sophisticated data access and protection.

[0003] To address the ever-increasing demands for data security and privacy protection, several improved methods have emerged, including dynamic access control, role-based access control (RBAC), and attribute-based access control (ABAC). While these methods have improved the flexibility and security of data access control to some extent, they still struggle to balance security and flexible access requirements when it comes to multi-user authentication and data anonymization. Summary of the Invention

[0004] To address the problems existing in the above-mentioned background technology, the present invention adopts the following technical solution:

[0005] Firstly, a dynamic data anonymization method is provided, including the following steps:

[0006] Configure the multi-user authentication identifier and data anonymization rules for each target query field; the data anonymization rules include a first data anonymization rule, or include a first data anonymization rule and a second data anonymization rule;

[0007] In response to the first query request received, the user attribute set, the requesting user's private key, and the query target field are obtained by parsing the first query request through the policy decision point;

[0008] Identify the multi-user authentication identifier corresponding to the target query field; if multi-user authentication is not required, obtain the first data anonymization rule corresponding to the target query field based on the user attribute set; if multi-user authentication is required, obtain the first and second data anonymization rules corresponding to the target query field based on the user attribute set.

[0009] The second or third query request is sent to the policy execution point according to the preset access policy.

[0010] In response to the received second query request, the first de-identified data corresponding to the query target field is obtained through the policy execution point according to the second query request;

[0011] In response to the received third query request, the multi-user authentication key is verified through the policy execution point, and the second de-identified data corresponding to the query target field is obtained according to the third query request;

[0012] The preset access policy includes:

[0013] After obtaining the first data anonymization rule, execute:

[0014] A second query request is generated based on the first query request and the first data anonymization rule, and the second query request is transmitted to the policy execution point;

[0015] After obtaining the second data anonymization rule, execute:

[0016] Based on the user attribute set and the query target field, match the authentication client and generate an authentication request to be transmitted to the authentication client.

[0017] Receive the authentication result transmitted by the authentication client, and generate a multi-user authentication key based on the authentication result and the private key of the requesting user;

[0018] A third query request is generated based on the first query request and the second data anonymization rules. The multi-user authentication key and the third query request are then transmitted to the policy enforcement point.

[0019] As a preferred embodiment, after configuring the multi-user authentication identifier and data anonymization rules corresponding to each query target field, the method further includes:

[0020] Configure several combinations of private keys corresponding to the target query field and their corresponding authentication hash values, generate an authentication hash value set based on the authentication hash values ​​and store it;

[0021] Each combined private key is processed by a key-sharing algorithm to obtain several private key pairs corresponding to the combined private key; each private key pair includes a set of private keys for the requesting user and a set of private keys for the authenticating user.

[0022] As a preferred embodiment, the verification of the multi-user authentication key specifically includes:

[0023] Obtain the set of authentication hash values ​​corresponding to the target query field. If the multi-user authentication key belongs to the set of authentication hash values, the verification is successful.

[0024] As a preferred embodiment, the step of generating a multi-user authentication key based on the authentication result and the requesting user's private key specifically involves:

[0025] Parse the authentication result to obtain the authenticated user's private key and authentication status;

[0026] Identify the authentication status and the requesting user's private key. If the identification is successful, reconstruct the combined private key based on the requesting user's private key and the authenticated user's private key.

[0027] The multi-user authentication key is obtained by hashing the combined private key.

[0028] As a preferred embodiment, the step of generating a second query request based on the first query request and the first data anonymization rule specifically includes:

[0029] According to the first data anonymization rule, the original query statements related to the target field in the first query request are anonymized; the original query statements related to the target field in the first query request are replaced with the anonymized query statements to generate the second query request.

[0030] As a preferred embodiment, the step of generating a third query request based on the first query request and the second data anonymization rules specifically involves:

[0031] According to the second data anonymization rule, the original query statements related to the target field in the first query request are anonymized; the original query statements related to the target field in the first query request are replaced with the anonymized query statements to generate the third query request.

[0032] As a preferred embodiment, before generating the second query request based on the first query request and the first data anonymization rule, the method further includes the following steps:

[0033] Obtain the access control tree corresponding to the target query field; the access control tree is a hierarchical structure composed of nodes and conditions.

[0034] The access control tree is recursively traversed based on the user attribute set until it is determined whether the user has permission to access the target field of the query.

[0035] Secondly, a dynamic data desensitization device is provided, including a communication connection configuration module, a strategy decision module, and a strategy execution module;

[0036] The configuration module is used to configure the multi-user authentication identifier and data anonymization rules corresponding to each query target field; the data anonymization rules include a first data anonymization rule, or include a first data anonymization rule and a second data anonymization rule;

[0037] The strategy decision module is used for:

[0038] Receive the first query request, parse the first query request to obtain the user attribute set, the requesting user's private key and the query target field;

[0039] Identify the multi-user authentication identifier corresponding to the target query field; if multi-user authentication is not required, obtain the first data anonymization rule corresponding to the target query field based on the user attribute set; if multi-user authentication is required, obtain the first and second data anonymization rules corresponding to the target query field based on the user attribute set.

[0040] The second or third query request is sent to the policy execution module according to the preset access policy.

[0041] The strategy execution module is used for:

[0042] Retrieve the first de-identified data corresponding to the target field of the query based on the second query request;

[0043] Verify the multi-user authentication key and obtain the second de-identified data corresponding to the target field of the query based on the third query request.

[0044] Thirdly, an electronic device is provided, including a processor and a memory, the memory being used to store computer program code, the computer program code including computer instructions, wherein when the processor executes the computer instructions, the electronic device performs a dynamic data desensitization method as described above.

[0045] Fourthly, a computer storage medium is provided, wherein a computer program is stored in the computer storage medium, the computer program including program instructions, and when the program instructions are executed by the processor of an electronic device, the processor executes a dynamic data desensitization method as described above.

[0046] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0047] This invention, by configuring a multi-user authentication identifier for each target query field, enables the setting of different authentication requirements based on data sensitivity and actual application scenarios, thereby achieving fine-grained access control. For fields that do not require multi-user authentication, only the first data anonymization rule is used to simplify the access process and ensure high access efficiency for smooth daily business operations. For fields that require multi-user authentication, two-level data anonymization rules are used to protect the data, thus being compatible with various access needs and application scenarios, and providing secure and flexible data anonymization processing while meeting compliance requirements.

[0048] This invention effectively prevents sensitive information from being leaked during transmission and processing by replacing the original query statement with a de-identified query statement. Compared to a static de-identified database, it dynamically generates second and third query requests when a query request is made, and can perform de-identification processing according to real-time needs and access conditions. Different de-identification rules can be applied according to different requests and scenarios to flexibly respond to different data sensitivity requirements.

[0049] For fields requiring multi-user authentication, this invention decomposes the combined private key into several private key pairs during the configuration phase. Each private key pair consists of the private key of the requesting user and the private key of the authenticating user, ensuring that each requesting user has appropriate permissions when accessing data, thereby enhancing the security of data access. By generating and storing a set of authentication hash values, multi-user authentication keys can be quickly verified, improving authentication efficiency and reducing real-time computation. Attached Figure Description

[0050] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0051] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0052] Figure 1 This is a flowchart illustrating the dynamic data desensitization method provided in an embodiment of the present invention.

[0053] Figure 2 This is a schematic diagram illustrating the process of generating a multi-user authentication key based on the authentication result and the private key of the requesting user, as provided in an embodiment of the present invention.

[0054] Figure 3 This is a schematic diagram of the dynamic data desensitization device provided in an embodiment of the present invention;

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

[0056] The technical solutions of the embodiments of the present invention 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 the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0057] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0058] Furthermore, the use of terms such as "first" and "second" in this invention is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" and "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of the various embodiments can be combined with each other, but only on the basis of being achievable by those skilled in the art. When the combination of technical solutions is contradictory or impossible to implement, such a combination of technical solutions should be considered non-existent and not within the scope of protection claimed by this invention.

[0059] With the rapid development of information technology, the amount of data in all industries is exploding, making data security protection increasingly important. Traditional data protection methods typically rely on static, single access control and simple de-identification techniques, such as data encryption or replacement. However, these traditional measures are inadequate when faced with diverse and complex application scenarios, and cannot meet the needs for efficient and sophisticated data access and protection.

[0060] To address the ever-increasing demands for data security and privacy protection, several improved methods have emerged, including dynamic access control, role-based access control (RBAC), and attribute-based access control (ABAC). While these methods have improved the flexibility and security of data access control to some extent, they still struggle to balance security and flexible access requirements when it comes to multi-user authentication and data anonymization.

[0061] Specifically, the following content provides a detailed description of the dynamic data desensitization method, apparatus, electronic device, and computer storage medium of the present invention:

[0062] Example 1

[0063] like Figure 1 As shown, a dynamic data anonymization method includes the following steps:

[0064] S1. Configure the multi-user authentication identifier and data anonymization rules corresponding to each target query field; the data anonymization rules include a first data anonymization rule, or include a first data anonymization rule and a second data anonymization rule;

[0065] S2. In response to the received first query request, the user attribute set, the requesting user's private key, and the query target field are obtained by parsing the first query request through the policy decision point;

[0066] Identify the multi-user authentication identifier corresponding to the target query field; if multi-user authentication is not required, obtain the first data anonymization rule corresponding to the target query field based on the user attribute set; if multi-user authentication is required, obtain the first and second data anonymization rules corresponding to the target query field based on the user attribute set.

[0067] The second or third query request is sent to the policy execution point according to the preset access policy.

[0068] S3. In response to the received second query request, obtain the first de-identified data corresponding to the query target field according to the second query request through the policy execution point;

[0069] S4. In response to the received third query request, verify the multi-user authentication key through the policy execution point, and obtain the second de-identified data corresponding to the query target field according to the third query request;

[0070] The preset access policy includes:

[0071] S21. After obtaining the first data anonymization rule, execute:

[0072] A second query request is generated based on the first query request and the first data anonymization rule, and the second query request is transmitted to the policy execution point;

[0073] S22. After obtaining the second data anonymization rule, execute:

[0074] Based on the user attribute set and the query target field, match the authentication client and generate an authentication request to be transmitted to the authentication client.

[0075] Receive the authentication result transmitted by the authentication client, and generate a multi-user authentication key based on the authentication result and the private key of the requesting user;

[0076] A third query request is generated based on the first query request and the second data anonymization rules. The multi-user authentication key and the third query request are then transmitted to the policy enforcement point.

[0077] This invention, by configuring a multi-user authentication identifier for each target query field, enables the setting of different authentication requirements based on data sensitivity and actual application scenarios, thereby achieving fine-grained access control. For fields that do not require multi-user authentication, only the first data anonymization rule is used to simplify the access process and ensure high access efficiency for smooth daily business operations. For fields that require multi-user authentication, two-level data anonymization rules are used to protect the data, thus being compatible with various access needs and application scenarios, and providing secure and flexible data anonymization processing while meeting compliance requirements.

[0078] The dynamic data anonymization method of the present invention is suitable for scenarios that require fine-grained control over data access, especially when some data fields require multi-user authentication.

[0079] Step S1 is the initial configuration phase of the data masking method, the purpose of which is to configure the corresponding multi-user authentication identifier and data masking rules for each query target field.

[0080] The multi-user authentication flag for the target query field is configured with 0 to represent "no multi-user authentication required" and 1 to represent "multi-user authentication required," aiming to strike a balance between data access and security. For target query fields with a multi-user authentication flag of 0, users can obtain specific information without a complex authentication process. This setting is suitable for fields with low data sensitivity and application scenarios where detailed anonymization levels are not required, such as basic data needed for daily business operations, ensuring access efficiency. For target query fields with a multi-user authentication flag of 1, it is suitable for data scenarios with high data sensitivity and application scenarios requiring detailed anonymization levels.

[0081] Each query target field can have one or two desensitization rules. For query target fields with a multi-user authentication flag of 0 (meaning no multi-user authentication is required), configure them to correspond only to the first numeric desensitization rule; for query target fields with a multi-user authentication flag of 1 (meaning multi-user authentication is required), configure them to correspond only to the first numeric desensitization rule and the second numeric desensitization rule.

[0082] In step S2, after receiving the first query request initiated by the requesting user, the request is analyzed through policy decision points to extract the user attribute set (such as identity information), the requesting user's private key, and the query target field. Then, the query target field is checked to determine whether it requires multi-user authentication. If the field does not require multi-user authentication, the first data anonymization rule corresponding to that field is obtained. If the field requires multi-user authentication, the corresponding first data anonymization rule and second data anonymization rule are obtained.

[0083] After obtaining the first data anonymization rule, or after obtaining the first data anonymization rule and the second data anonymization rule, a second query request (for query target fields that do not require multi-user authentication) or a third query request (for query target fields that require multi-user authentication) is generated according to the preset access policy and sent to the policy execution point.

[0084] In step S3, after receiving the second query request transmitted by the strategy decision point, the strategy execution point obtains the first de-identified data of the target query field according to the second query request for fields that do not require multi-user authentication, and transmits it to the requesting user. The requesting user can perform visualization processing on the first de-identified data or use it for other business scenarios.

[0085] In step S4, after receiving the third query request transmitted by the policy decision point, the policy execution point verifies the multi-user authentication key for fields requiring multi-user authentication. If the verification is successful, the policy execution point requests the second de-identified data through the third query and transmits it to the requesting user. The requesting user can replace the first de-identified data in step S3 with the second de-identified data for visualization processing or use in other business scenarios.

[0086] It is understandable that for query target fields that do not require multi-user authentication, the policy enforcement point only responds to the received second query request, meaning that only step S3 needs to be executed, and step S4 is not required. For query target fields that require multi-user authentication, the policy enforcement point can respond to the received second or third query request, meaning that steps S3 and S4 can be executed.

[0087] In typical application scenarios of this invention, for a query target field requiring multi-user authentication, the confidentiality of the first de-identified data obtained through the second query request is higher than that of the second de-identified data obtained through the third query request. For query target fields involving personal identity information, such as ID card numbers, addresses, and phone numbers, when the first query request is received, after processing by the strategy decision point in step S2, the strategy execution point in step S3 generates the first de-identified data based on the second query request, transmits the first de-identified data to the requesting user, and applies it. After multi-user authentication is completed, in step S4, the strategy execution point generates the second de-identified data based on the third query request, transmits the second de-identified data to the requesting user, and so on, overwriting the first de-identified data for business operations. It can be understood that the second data de-identification rule can be set to empty in some application scenarios, that is, the original data is directly displayed to the requesting user after multi-user authentication is completed.

[0088] In one embodiment, the first data anonymization rule can be data obfuscation, formatted anonymization, masked anonymization, replacement anonymization, randomization anonymization, and full encryption; the second data anonymization rule can be data obfuscation, formatted anonymization, masked anonymization, and replacement anonymization. Formatted anonymization involves adjusting the data structure to make it readable while hiding specific information; masked anonymization involves replacing sensitive data with special characters (such as X or *) while maintaining the data length; replacement anonymization involves replacing sensitive information with non-sensitive data; data obfuscation involves performing mathematical transformations or adding noise to the data to make it difficult to identify while retaining some analytical capabilities; randomization anonymization involves randomizing the sensitive information to generate a new value without practical meaning, and each generated new value is different.

[0089] This invention, by configuring a multi-user authentication identifier for each target query field, enables the setting of different authentication requirements based on data sensitivity and actual application scenarios, thereby achieving fine-grained access control. For fields that do not require multi-user authentication, only the first data anonymization rule is used to simplify the access process and ensure high access efficiency for smooth daily business operations. For fields that require multi-user authentication, two-level data anonymization rules are used to protect the data, thus being compatible with various access needs and application scenarios, and providing secure and flexible data anonymization processing while meeting compliance requirements.

[0090] In an embodiment of the present invention, after configuring the multi-user authentication identifier and data anonymization rules corresponding to each query target field, the method further includes:

[0091] Configure several combinations of private keys corresponding to the target query field and their corresponding authentication hash values, generate an authentication hash value set based on the authentication hash values ​​and store it;

[0092] Each combined private key is processed by a key-sharing algorithm to obtain several private key pairs corresponding to the combined private key; each private key pair includes a set of private keys for the requesting user and a set of private keys for the authenticating user.

[0093] The verification of the multi-user authentication key specifically involves:

[0094] Obtain the set of authentication hash values ​​corresponding to the target query field. If the multi-user authentication key belongs to the set of authentication hash values, the verification is successful.

[0095] In this embodiment, during the configuration phase, several combined private keys are generated for each target query field. Authentication hash values ​​are generated by associating these private keys, and the authentication hash values ​​are then organized into an authentication hash value set and stored. During the multi-user authentication key verification phase, the combined private keys are decomposed into several private key pairs. When a multi-user authentication key is received, it is compared to whether the key exists in the pre-generated and stored authentication hash value set. If it exists, the verification is successful.

[0096] Based on the above, this embodiment decomposes the combined private key into several private key pairs during the configuration phase. Each private key pair consists of the private key of the requesting user and the private key of the authenticating user, ensuring that each requesting user has appropriate permissions when accessing data, thereby enhancing the security of data access. By generating and storing a set of authentication hash values, multi-user authentication keys can be quickly verified, improving authentication efficiency and reducing real-time computation.

[0097] In an embodiment of the present invention, please refer to Figure 2 Step S22, generating a multi-user authentication key based on the authentication result and the requesting user's private key, specifically involves:

[0098] Parse the authentication result to obtain the authenticated user's private key and authentication status;

[0099] Identify the authentication status and the requesting user's private key. If the identification is successful, reconstruct the combined private key based on the requesting user's private key and the authenticated user's private key.

[0100] The multi-user authentication key is obtained by hashing the combined private key.

[0101] In this embodiment, the authentication user's private key and authentication status are obtained by parsing the authentication result. The authentication status is then reviewed to determine if it meets the target requirements (e.g., whether it is in an "authenticated" state). The pre-stored request user's private key is compared with the currently received request user's private key to confirm its legitimacy and avoid invalid requests. Finally, a combined private key is reconstructed based on the request user's private key and the authentication user's private key and then hashed. Therefore, even for the same request user's private key, different authentication user private keys corresponding to different query target fields can result in different multi-user authentication keys, thus reducing the risk of individual leakage of the request user's private key or the authentication user's private key, thereby ensuring the data security of sensitive fields.

[0102] In an embodiment of the present invention, step S22, generating a third query request based on the first query request and the second data anonymization rule, specifically involves:

[0103] According to the second data anonymization rule, the original query statements related to the target field in the first query request are anonymized; the original query statements related to the target field in the first query request are replaced with the anonymized query statements to generate the third query request.

[0104] This embodiment enhances the security of the system when processing sensitive data by employing a multi-user authentication key validity verification step and a method for generating query requests based on data anonymization rules. During the query request generation process, compliance and user information protection are ensured, laying a secure foundation for subsequent data operations.

[0105] In an embodiment of the present invention, step S21, which involves generating a second query request based on the first query request and the first data anonymization rule, specifically includes:

[0106] According to the first data anonymization rule, the original query statements related to the target field in the first query request are anonymized; the original query statements related to the target field in the first query request are replaced with the anonymized query statements to generate the second query request.

[0107] In this embodiment, for both the second and third query requests, the original query statements related to the target field in the first query request are replaced with the anonymized query statements. For example, the data anonymization rule is...

[0108] Partially mask the field content, such as displaying some characters while hiding others. Generate a second query request based on the first query request and the first data anonymization rules.

[0109] For example, the first query request is: SELECT name, ssn, address FROM users WHERE user_id = 123;

[0110] The second query request is: SELECT name,CONCAT(SUBSTRING(ssn,1,3),'*****')AS ssn,address FROM users WHERE user_id=123.

[0111] This embodiment effectively prevents sensitive information from being leaked during transmission and processing by replacing the original query statement with the anonymized query statement. Compared with a static anonymized database, the second and third query requests are dynamically generated when a query request is made. Anonymization processing can be performed according to real-time needs and access conditions. Different anonymization rules can be applied according to different requests and scenarios to flexibly respond to different data sensitivity requirements.

[0112] In an embodiment of the present invention, before generating the second query request based on the first query request and the first data anonymization rule, the method further includes the following steps:

[0113] Obtain the access control tree corresponding to the target query field; the access control tree is a hierarchical structure composed of nodes and conditions.

[0114] The access control tree is recursively traversed based on the user attribute set until it is determined whether the user has permission to access the target field of the query.

[0115] The user attribute set may include, but is not limited to, information such as role, department, and access time. This embodiment uses an access control tree to manage and verify data access permissions. The access control tree is a hierarchical structure composed of nodes and conditions, with each node representing a permission condition. When a user requests access to a target query field, this embodiment verifies permissions through the access control tree. During this process, the access control tree verifies the user's permissions level by level based on the user attribute set to determine whether the user has the necessary permissions to access the target query field. Since each node in the access control tree corresponds to a permission condition, these conditions can be matched against the user attribute set. If the user attributes meet the conditions of a node, the verification continues downwards, selecting a path that matches the conditions. Finally, upon reaching the terminal node, a final decision is made based on the access control policy of that node—allowing or denying the user access to the corresponding target query field.

[0116] This embodiment introduces an access control tree for the target query field before generating the second query request, enabling finer-grained access control. The access control tree verifies permissions level by level based on the user attribute set, ensuring that each access request undergoes dynamic permission checks. This improves the system's flexibility and security when handling different user requests, ensuring that only qualified users can access sensitive data.

[0117] Example 2

[0118] Please see Figure 3 This embodiment provides a dynamic data desensitization device, including a communication connection configuration module, a strategy decision module, and a strategy execution module;

[0119] The configuration module is used to configure the multi-user authentication identifier and data anonymization rules corresponding to each query target field; the data anonymization rules include a first data anonymization rule, or include a first data anonymization rule and a second data anonymization rule;

[0120] The strategy decision module is used for:

[0121] Receive the first query request, parse the first query request to obtain the user attribute set, the requesting user's private key and the query target field;

[0122] Identify the multi-user authentication identifier corresponding to the target query field; if multi-user authentication is not required, obtain the first data anonymization rule corresponding to the target query field based on the user attribute set; if multi-user authentication is required, obtain the first and second data anonymization rules corresponding to the target query field based on the user attribute set.

[0123] The second or third query request is sent to the policy execution module according to the preset access policy.

[0124] The strategy execution module is used for:

[0125] Retrieve the first de-identified data corresponding to the target field of the query based on the second query request;

[0126] Verify the multi-user authentication key and obtain the second de-identified data corresponding to the target field of the query based on the third query request.

[0127] This invention, by configuring a multi-user authentication identifier for each target query field, enables the setting of different authentication requirements based on data sensitivity and actual application scenarios, thereby achieving fine-grained access control. For fields that do not require multi-user authentication, only the first data anonymization rule is used to simplify the access process and ensure high access efficiency for smooth daily business operations. For fields that require multi-user authentication, two-level data anonymization rules are used to protect the data, thus being compatible with various access needs and application scenarios, and providing secure and flexible data anonymization processing while meeting compliance requirements.

[0128] Example 3

[0129] This embodiment provides an electronic device 2, such as... Figure 4 As shown, there is a processor 21 and a memory 22. The memory 22 is used to store computer program code, which includes computer instructions. When the processor 21 executes the computer instructions, the electronic device performs the dynamic data desensitization method described above.

[0130] The electronic device 2 includes a processor 21, a memory 22, an output device 23, and an input device 24. The processor 21, memory 22, output device 23, and input device 24 are coupled together via connectors, which may include various interfaces, transmission lines, or buses, etc., and are not limited in this embodiment of the invention. It should be understood that in various embodiments of the invention, coupling refers to mutual connection through a specific method, including direct connection or indirect connection through other devices, such as through various interfaces, transmission lines, buses, etc.

[0131] Processor 21 can be one or more graphics processing units (GPUs). If processor 21 is a GPU, the GPU can be a single-core GPU or a multi-core GPU. Optionally, processor 21 can be a processor group composed of multiple GPUs, with the multiple processors coupled to each other via one or more buses. Optionally, processor 21 can also be other types of processors, etc., which are not limited in this embodiment of the invention.

[0132] The memory 22 can be used to store computer program instructions, as well as various types of computer program code, including program code for executing the present invention. Optionally, the memory 22 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and the memory 22 is used for related instructions and data.

[0133] Input device 24 is used to input data and / or signals, and output device 23 is used to output data and / or signals. Output device 23 and input device 24 can be independent devices or an integrated device.

[0134] Example 4

[0135] A computer storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor of an electronic device, cause the processor to perform a dynamic data desensitization method.

[0136] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features of the invention herein.

Claims

1. A dynamic data de-sensitization method, characterized in that, The method comprises the steps of: a configuration step of configuring a multi-user authentication identifier for each query target field, the multi-user authentication identifier being used to indicate whether a multi-user authentication process needs to be performed when accessing the field; and configuring a data desensitization rule for each query target field, wherein for a field indicated by the multi-user authentication identifier as not needing multi-user authentication, a first data desensitization rule is configured; and for a field indicated by the multi-user authentication identifier as needing multi-user authentication, a first data desensitization rule and a second data desensitization rule are configured; a policy decision step of: in response to a received first query request, resolving the first query request by a policy decision point to obtain a user attribute set, a request user private key, and a query target field; identifying the multi-user authentication identifier corresponding to the query target field; if the multi-user authentication identifier is identified as indicating that multi-user authentication is not needed, obtaining the first data desensitization rule corresponding to the query target field according to the user attribute set, generating a second query request according to the first query request and the first data desensitization rule, and transmitting the second query request to a policy execution point; if the multi-user authentication identifier is identified as indicating that multi-user authentication is needed, obtaining the first data desensitization rule and the second data desensitization rule corresponding to the query target field according to the user attribute set, and performing a multi-user authentication process; the multi-user authentication process comprises: matching an authentication user end according to the user attribute set and the query target field, generating an authentication request and transmitting the authentication request to the authentication user end; receiving an authentication result transmitted by the authentication user end, and resolving the authentication result to obtain an authentication user private key and an authentication state; identifying the authentication state and the request user private key, and if the identification is passed, recombining a combined private key according to the request user private key and the authentication user private key; hash processing the recombined combined private key to obtain a multi-user authentication key; generating a third query request according to the first query request and the second data desensitization rule; transmitting the multi-user authentication key and the third query request to the policy execution point; a policy execution step of: in response to the received second query request, obtaining the first desensitized data corresponding to the query target field according to the second query request by the policy execution point; in response to the received third query request, checking the multi-user authentication key by the policy execution point, and obtaining the second desensitized data corresponding to the query target field according to the third query request. 2.The dynamic data de-sensitization method of claim 1, wherein: The configuration step further comprises: configuring a number of combined private keys corresponding to the query target field and their corresponding authentication hash values, generating an authentication hash value set according to the authentication hash values and storing the authentication hash value set; processing each combined private key by a key sharing algorithm to obtain a number of private key pairs corresponding to the combined private key; each private key pair comprises a set of request user private keys and authentication user private keys.

3. The dynamic data de-sensitization method of claim 2, wherein: The checking of the multi-user authentication key is specifically: obtaining the authentication hash value set corresponding to the query target field, and if the multi-user authentication key belongs to the authentication hash value set, the checking is qualified.

4. The dynamic data de-sensitization method of claim 1, wherein: The generation of the second query request according to the first query request and the first data desensitization rule is specifically: According to the first data desensitization rule, the original query statement related to the query target field in the first query request is desensitized; the original query statement related to the query target field in the first query request is replaced by the desensitized query statement to generate the second query request.

5. The dynamic data de-sensitization method of claim 1, wherein: The third query request is generated according to the first query request and the second data desensitization rule, and specifically: According to the second data desensitization rule, the original query statement related to the query target field in the first query request is desensitized; the original query statement related to the query target field in the first query request is replaced by the desensitized query statement to generate the third query request.

6. The dynamic data de-sensitization method of claim 1, wherein: According to the first query request and the first data desensitization rule to generate the second query request, and before that, it further includes the following steps: Obtain the access control tree corresponding to the query target field; The access control tree is a hierarchical structure composed of nodes and conditions; According to the user attribute set, recursively traverse the access control tree until it is determined whether the user has the right to access the query target field.

7. A dynamic data desensitization apparatus, characterized by: It includes a configuration module, a policy decision module and a policy execution module connected in communication; The configuration module is used to execute the configuration steps of claim 1; The policy decision module is used to execute the policy decision steps of claim 1; The policy execution module is used to execute the policy execution steps of claim 1.

8. An electronic device, comprising: It includes a processor and a memory, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor executes the computer instructions, the electronic equipment executes a kind of dynamic data desensitization method described in any one of claims 1 to 6.

9. A computer storage medium, characterized in that: The computer storage medium stores a computer program, and the computer program includes program instructions. When the program instructions are executed by the processor of the electronic device, the processor executes a kind of dynamic data desensitization method described in any one of claims 1 to 6.

Images