User access data processing system, terminal and server

Abstract

The invention discloses a user access data processing system, a terminal and a server, and relates to the field of data processing, according to the scheme, whether an interface accessed by a user is a non-downloading interface or not is judged based on a non-downloading interface recognizer, and whether the interface accessed by the user is a downloading interface or not is judged based on a downloading interface recognizer; and the data access control unit grants the user with the permission of accessing the sensitive data through the sensitive data authorizer when the user meets the condition. When a user accesses the sensitive data, judging whether the user has the permission of accessing the sensitive data or not through a sensitive data authenticator, and when the user does not have the permission of accessing the sensitive data, performing corresponding desensitization processing on the sensitive data returned by an interface accessed by the user based on the type of the interface accessed by the user by adopting a data desensitization processing unit; and recording a sensitive data operation log generated when the user operates the sensitive data by adopting a sensitive log recording unit. Therefore, processing and protection of the sensitive data are realized when the user accesses the sensitive data.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to a processing system, a terminal and a server for user access data. Background Art

[0002] In the current digital age, the rapid development of information technology has provided unprecedented opportunities for enterprises and organizations, but it has also brought new risks and challenges. Among them, the risk of sensitive information leakage is a serious problem that may lead to huge financial losses, reputation damage and legal liability. At the same time, relevant laws are constantly being introduced, and countries have formulated a series of laws and regulations to regulate the handling of sensitive data. After the relevant policies and regulations were introduced one after another, user privacy and data security have received increasing attention. In addition, with the frequent occurrence of data leakage and illegal access incidents, security and compliance have become aspects that organizations and enterprises have to pay attention to. The security and privacy protection of sensitive data has become a key challenge in today's Internet era. In order to ensure the security and confidentiality of data and to meet regulatory requirements and customer expectations, many organizations are in urgent need of establishing sensitive information processing and protection measures. Summary of the invention

[0003] In view of this, an embodiment of the present invention provides a user access data processing system, a terminal and a server, so as to process and protect sensitive data when the user accesses the sensitive data.

[0004] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0005] A system for processing user access data, comprising:

[0006] A sensitive operation identification unit, used to determine whether the interface accessed by the user is a non-download interface based on a non-download interface identifier, and to determine whether the interface accessed by the user is a download interface based on a download interface identifier;

[0007] A data access control unit is used to grant a user access to sensitive data through a sensitive data authorizer when the user meets the conditions, and to determine whether the user has the permission to access sensitive data through a sensitive data authenticator;

[0008] A data desensitization processing unit, used to perform corresponding desensitization processing on sensitive data returned by the interface accessed by the user based on the type of the interface accessed by the user;

[0009] The sensitive log recording unit is used to record the sensitive data operation logs generated when users operate sensitive data.

[0010] Optionally, the above-mentioned user access data processing system includes:

[0011] The non-downloading interface identifier is used to: determine whether the interface accessed by the user is a non-downloading interface based on the annotations and annotations of the interface accessed by the user;

[0012] The downloading interface identifier is used to determine whether the interface accessed by the user is a downloading interface based on the annotations and labels of the interface accessed by the user.

[0013] Optionally, in the above-mentioned user access data processing system, the sensitive data authorizer is used to: confirm the user permission list to be reviewed, add the confirmed user permission list to the daily authorization list, and retain the authorization operation record;

[0014] The sensitive data authenticator is used to authenticate user permissions when a user access operation to sensitive data is detected.

[0015] Optionally, in the above-mentioned user access data processing system, when a user access operation to sensitive data is detected, user authority is authenticated, including:

[0016] Authenticate the user and determine whether the user ID or the user's access path is stored in the whitelist. If the user ID or the access path is stored in the whitelist, the user authority authentication is passed;

[0017] If the user ID and access path are not stored in the whitelist, obtain the user's current operation type and user token, and determine whether the operation type is included in the user permissions corresponding to the user token. When it is included in the user permissions corresponding to the user token, it is determined that the user permission authentication has passed; otherwise, the user permission authentication has failed.

[0018] Optionally, in the above-mentioned user access data processing system, the data desensitization processing unit is specifically used for:

[0019] When the type of the interface accessed by the user is a non-download interface:

[0020] When the sensitive data authenticator determines that the authentication fails, obtaining the attribute value corresponding to the data of the reference data type in the return data of the user access interface;

[0021] When the attribute value is of a set type, each member in the set is taken out in a loop, and the desensitization processing scheme is called recursively to perform desensitization processing on each member;

[0022] When the attribute value is of a custom type, a desensitization processing scheme is recursively called to perform desensitization processing on the data of the reference data type;

[0023] Acquire data of a sensitive field marked as such in the return data of the user access interface, determine the data type of the sensitive field based on the attribute value, and perform desensitization processing on the sensitive field based on a desensitization method corresponding to the data type of the sensitive field;

[0024] When the sensitive data authenticator determines that the authentication is successful, the real value returned by the interface accessed by the user is returned;

[0025] When the type of interface accessed by the user is a download interface:

[0026] When the sensitive data authenticator determines that the authentication fails, the user's download operation is released; when the sensitive data authenticator determines that the authentication passes, the user's download operation is released.

[0027] Optionally, in the user access data processing system, desensitizing the data of the reference data type and desensitizing the sensitive field include:

[0028] When the data of the reference data type or the data type of the sensitive field to be processed is a string, the data to be desensitized is desensitized by replacing the original string;

[0029] When the data of the reference data type or the data type of the sensitive field to be processed is non-string, a desensitization strategy matching the type of the processed data is called to perform desensitization processing.

[0030] Optionally, the above-mentioned user access data processing system further includes:

[0031] A buffer, the buffer being used to store user login information and user authority information;

[0032] A data storage device is used to store a list of authorized users, types of sensitive business data, and sensitive data operation logs.

[0033] A user access data processing terminal is provided, and any one of the user access data processing systems described above is applied thereto.

[0034] Optionally, the processing terminal for the above-mentioned user access data is a computer.

[0035] A server is provided with any one of the user access data processing systems described above.

[0036] Based on the above technical solution, the above solution provided by the embodiment of the present invention, the system for processing user access data, based on the non-download interface identifier, determines whether the interface accessed by the user is a non-download interface, based on the download interface identifier, determines whether the interface accessed by the user is a download interface, and the data access control unit grants the user access to sensitive data through the sensitive data authorizer when the user meets the conditions. When the user accesses sensitive data, the sensitive data authenticator is used to determine whether the user has the authority to access the sensitive data. When the user does not have the access right to the sensitive data, the data desensitization processing unit is used to perform corresponding desensitization processing on the sensitive data returned by the interface accessed by the user based on the type of interface accessed by the user; and a sensitive log recording unit is used to record the sensitive data operation log generated when the user operates the sensitive data. In this way, the processing and protection of sensitive data when the user accesses sensitive data is realized. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0038] Figure 1 A schematic diagram of the structure of a system for processing user access data disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0040] The present invention provides a scheme that proposes a processing system for user access data that can authorize, process and log sensitive data. The system realizes sensitive operation identification, data access control, data desensitization processing, sensitive log recording and other integrated sensitive data processing links, adopts modular and decoupled design ideas, supports developers to complete customized annotation of sensitive operations and sensitive data through annotations, and completes customized settings of sensitive data processing methods through policy classes, and the code has good maintainability and scalability. It aims to help developers establish a sound security control and compliance framework at the lowest cost, protect the security, privacy and integrity of sensitive data, and meet regulatory compliance and audit requirements.

[0041] See also Figure 1 , the user access data processing system disclosed in the embodiment of the present application may include: a sensitive operation identification unit 100, a data access control unit 200, a data desensitization processing unit 300, a data desensitization processing unit 400 and a sensitive log recording unit 500;

[0042] Regarding the sensitive operation identification unit 100, the sensitive operation identification unit 100 includes a non-download interface identifier 101 and a download interface identifier 102. The sensitive operation identification unit 100 is used to obtain the interface type of the sensitive interface accessed by the user, and the interface type includes a non-download interface and a download interface. When the sensitive interface is a non-download interface, the non-download interface identifier is called to process the access data. When the sensitive interface is a non-download interface, the download interface identifier is called to process the access data.

[0043] Specifically, the non-download interface identifier 101 and the download interface identifier 102 can be pre-annotated and marked respectively with custom annotations. The annotations and markings can be used to screen and identify different sensitive data interfaces. When a certain interface is accessed by a user, by identifying the custom annotations and markings, it can be determined whether it is a sensitive data interface and the specific type of the sensitive data interface. The user's access to the non-download interface mainly includes viewing, adding, modifying, and deleting sensitive data, which mainly involves the access control of the operating user and the recording of sensitive logs. For viewing operations, it also involves the desensitized display of sensitive data. The data processing process of the non-download interface mainly includes: customizing the global processing class of the return value of each non-download interface, and uniformly processing the exceptions and return data in each non-download interface layer. Based on user permissions and judging whether it is necessary to call a custom processing method, the custom method designed in this solution includes desensitizing the sensitive data corresponding to the user access interface and recording sensitive data access logs. For download interfaces, the focus is on completing the authentication operation before the user downloads, that is, determining whether the user has the permission to download such sensitive information. When the user has the permission and the download is completed, the log record is completed, but it does not involve the desensitization of sensitive data. The main data processing process of the download interface includes: writing custom processing for the return value of the download interface, the custom processing is to perform the corresponding sensitive data authentication operation, and according to the user's permissions, before the interface returns the data, the output data of this type of interface is desensitized.

[0044] Regarding the data access control unit 200, data access control is an important part of sensitive data processing. The main function of the data access control unit 200 is to ensure that only authorized users can access and operate sensitive data. The data access control unit 200 includes two parts: a sensitive data authorizer 201 and a sensitive data authenticator 202. The data access control unit 200 is used to grant the user access to sensitive data through the sensitive data authorizer 201 when the user meets the conditions, and to determine whether the user has the permission to access sensitive data through the sensitive data authenticator 202;

[0045] The sensitive data authorizer 201 is mainly used to complete the authorization operation for a specific user. The process includes two steps: review list authorization and daily authorization.

[0046] Step 1, review list authorization. This process mainly confirms the user permission list to be reviewed, adds the confirmed user permission list to the daily authorization list, and retains the authorization operation record. The user permission list and the daily authorization list can be obtained from the cache. The user permission list is valid for half a year or other duration, and the validity period is refreshed after each review is completed.

[0047] Step 2, daily authorization, refers to the process of granting sensitive data access rights to designated users in the system every day. When the administrator clicks the authorization button or detects that the user meets the preset conditions, a token will be created based on the daily authorization list in the database, and the authorization operation record will be retained. It will be stored in the user's corresponding token as the user's sensitive data permission information for use by the sensitive data authenticator. The sensitive data permission information stored in the token expires in one day or other time, and re-authorization is required after the expiration date.

[0048] The sensitive data authenticator 202 has the following main functions: when a user accesses sensitive resources or performs operations involving sensitive data, the sensitive data authenticator will check the user's permissions to verify whether the user has the permission to access or operate sensitive data, and then perform corresponding release or interception operations. The authentication process of the sensitive data authenticator needs to be implemented with the help of a data storage device. The storage device stores a whitelist and a user token. During the authentication process, the user's permissions need to be authenticated based on the whitelist and the user token respectively. Specifically, it is determined whether the user is a user in the whitelist, and the authentication is passed. If not, the user token and the type of operation currently performed by the user are obtained. Based on the sensitive data permission information in the user token, it is determined whether the user has the permission for the current operation type of the sensitive data. If the user has the permission, the authentication is passed, otherwise the authentication is passed.

[0049] The data desensitization processing unit 300 is used to desensitize sensitive data. Data desensitization is an important technical means in the field of data security, mainly used to protect sensitive information and prevent sensitive data leakage and abuse. The main function of the data desensitization processing unit 300 is to realize the classification and desensitization of different sensitive data. The data desensitization processing unit 300 mainly includes a sensitive data identifier 301 and a data desensitization processor 302.

[0050] (1) Sensitive Data Identifier 301

[0051] The sensitive data identifier 301 implements classification and labeling of different sensitive data based on custom annotations. Taking the enterprise information entity class as an example, the legal representative's ID type, email address, name, etc. are labeled separately, and these data are labeled as sensitive data to facilitate subsequent desensitization and identification. According to the authentication result of the sensitive data authenticator mentioned above, when a user who does not have the permission to view sensitive data accesses sensitive data, the return value of the interface to which he applies for access needs to be desensitized. At this time, it is necessary to perform corresponding identification operations on the sensitive data type in the return value, so as to adopt different processing schemes. The sensitive data identification process of the sensitive data identifier 301 is mainly carried out using the Java reflection mechanism, and mainly includes the following steps:

[0052] Step 1: Since all interface return values ​​are packaged, this solution first filters non-reference data types. For reference data types returned by the interface, all attribute values ​​in the return class are obtained through the Java reflection mechanism. It should be noted that when obtaining class attributes, it is necessary to recursively check whether it has a custom parent class and recursively obtain the attribute values ​​of the parent class.

[0053] Step 2, after obtaining the attributes of all the data of the reference data type in the return value, when the attribute value is a set type, each member in the data set is taken out in a loop, and the sensitive data processing scheme is called recursively to desensitize each member. If the attribute value of the return value is a custom type, there is no need to take it out in a loop, and the sensitive data processing method is directly called recursively to desensitize the data of the custom type. At the same time, it is also necessary to determine whether the returned data has been marked with the custom annotation mentioned above. If it is marked, these returned data are also sensitive fields. The attribute values ​​of these returned data are obtained by reflection, and the sensitive data type marked in the annotation in the early stage is obtained based on the attribute value. Then, according to the sensitive data type obtained, the corresponding desensitization method is used to classify and desensitize the returned data. At this point, the classification and identification process of sensitive data is completed.

[0054] (2) Data desensitization processor 302

[0055] The sensitive data processor is used to: when the type of the interface accessed by the user is a non-download interface:

[0056] Determine whether the user requests the interface accessed by the user to return real data. If it is detected that the user requests the interface accessed by the user to return real data of sensitive data, determine whether the user has access rights to the real data of the sensitive data. If the user does not have access rights, stop responding to the user request. If the user has access rights, respond to the user request (feed back the real data of the sensitive data to the user). If the user does not request the interface accessed by the user to return the real value of the sensitive data, further determine the authentication result of the sensitive data authenticator. If the sensitive data authenticator determines that the authentication fails, obtain the attribute value corresponding to the data of the referenced data type in the return data of the user access interface. ; When the attribute value is a set type, loop to take out each member in the set, and recursively call the desensitization processing scheme to desensitize each member; when the attribute value is a custom type, recursively call the desensitization processing scheme to desensitize the data of the reference data type; obtain the data of the sensitive field marked as in the return data of the user access interface, determine the data type of the sensitive field based on the attribute value, and desensitize the sensitive field based on the desensitization method corresponding to the data type of the sensitive field; when the sensitive data authenticator determines that the authentication is passed, return the true value returned by the interface accessed by the user;

[0057] When the type of interface accessed by the user is a download interface:

[0058] When the sensitive data authenticator determines that the authentication fails, the user's download operation is released; when the sensitive data authenticator determines that the authentication passes, the user's download operation is released.

[0059] When desensitizing the data of the reference data type and desensitizing the sensitive field, it is necessary to use a data desensitizing processor 302 to implement the desensitization process. The processing process of the data desensitizing processor 302 is as follows: obtain the return data to be desensitized and its attribute values, determine the sensitive type of each return data to be desensitized based on the attribute values, and desensitize the return data based on a desensitization strategy that matches the sensitive type. In this solution, multiple desensitization strategies can be pre-configured, and different sensitive types of data correspond to different desensitization strategies. By or reasonably configuring the desensitization strategy, the processing of sensitive data such as three certificate information, amount information, and communication information can be completed.

[0060] Specifically, when the data type of the return data to be desensitized (data of reference data type or sensitive field) is a string (such as a mobile phone number, customer name, etc.), the data to be desensitized is desensitized by replacing the original string. For example, the processing solution is to retain a fixed number of bits in the string and replace the remaining fields with *.

[0061] When the return data to be processed (data of reference data type or sensitive field) is non-string (such as sensitive amount (large number type), date (date type), etc.), it is difficult to directly perform character replacement operations on these types of data. It is necessary to call a desensitization strategy that matches the type of the processed data (such as large number type, date type, etc.) for desensitization processing. Taking the desensitization processing of large number types as an example, the processing logic adopted by this solution is to use a custom proxy class to inherit the original type, add a construction method to receive the corresponding policy processing implementation object, and rewrite the serialization method. Different policy methods are called in the serialization method, so as to intercept the string for desensitization processing when the object is serialized.

[0062] Regarding the sensitive log recording unit 400, the sensitive log recording unit 400 is used to record the sensitive data operation log generated when the user operates sensitive data.

[0063] The sensitive log recording unit 400 mainly completes the functions of recording, querying, and archiving sensitive logs generated when users operate on sensitive data. Sensitive data operation log recording is an important means to ensure the security and compliance of sensitive data, including the recording of sensitive data access and the tracking of data processing operations, which can not only ensure real-time monitoring and responsibility tracing of data security, but also meet regulatory compliance and security audit requirements. The content recorded in the sensitive data operation log includes the accessed module, page, interface, time, sensitive operation type, etc. For non-download interfaces for file download, the downloaded file information must also be recorded.

[0064] The main work contents of the sensitive log recording unit 400 include:

[0065] Step 1: embed the log records into the sensitive data processing method. The interface description, sensitive operation type and other information required to be recorded in the sensitive data operation log are mainly obtained directly through the annotations on the custom annotations. The module, page, specific interface URL information and other information of the operation required to be recorded in the sensitive data operation log depend on the front-end provision.

[0066] Step 2: After the sensitive data operation log is completed, the sensitive data operation log is stored in the database, and then it can be queried and traced by administrators who meet the permissions.

[0067] Step 3: According to the preset time interval, the sensitive data operation logs in the library are regularly archived through the batch centralized scheduling platform.

[0068] To facilitate user authentication, the above system may further include a cache 500 and a data storage device 600. The cache may be a high-speed cache device for storing user login information and user authority information; the data storage device is for storing a list of authorized users, types of sensitive business data, and sensitive data operation logs.

[0069] In addition to the above modules, the above system may also include an input unit 700, which is used to support users to implement functions such as interface access, list authorization, and log query.

[0070] It can be seen from the above scheme that the present application provides a processing system for user access data, which determines whether the interface accessed by the user is a non-download interface based on a non-download interface identifier, and determines whether the interface accessed by the user is a download interface based on a download interface identifier. The data access control unit grants the user access to sensitive data through a sensitive data authorizer when the user meets the conditions. When the user accesses sensitive data, the sensitive data authenticator determines whether the user has the authority to access the sensitive data. When the user does not have the access right to the sensitive data, the data desensitization processing unit is used to perform corresponding desensitization processing on the sensitive data returned by the interface accessed by the user based on the type of interface accessed by the user; and a sensitive log recording unit is used to record the sensitive data operation log generated when the user operates the sensitive data. In this way, the processing and protection of sensitive data when the user accesses sensitive data is realized.

[0071] Corresponding to the above system, the present application also discloses a user access data processing terminal, which can be applied with any of the above user access data processing systems. The processing terminal can be a computer, a mobile phone or other intelligent terminal with data processing function.

[0072] A server is provided with any one of the user access data processing systems described above.

[0073] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0074] For the convenience of description, the above system is described as being divided into various modules according to their functions. Of course, when implementing the present invention, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0075] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referenced to each other, and each embodiment focuses on the differences from other embodiments. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. A person of ordinary skill in the art may understand and implement it without creative work.

[0076] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0077] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0078] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0079] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one 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 present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A system for processing user access data, characterized in that: include: A sensitive operation identification unit, used to determine whether the interface accessed by the user is a non-download interface based on a non-download interface identifier, and to determine whether the interface accessed by the user is a download interface based on a download interface identifier; A data access control unit is used to grant a user access to sensitive data through a sensitive data authorizer when the user meets the conditions, and to determine whether the user has the permission to access sensitive data through a sensitive data authenticator; A data desensitization processing unit, used to perform corresponding desensitization processing on sensitive data returned by the interface accessed by the user based on the type of the interface accessed by the user; The sensitive log recording unit is used to record the sensitive data operation logs generated when users operate sensitive data.

2. The user access data processing system according to claim 1, characterized in that: include: The non-downloading interface identifier is used to: determine whether the interface accessed by the user is a non-downloading interface based on the annotations and annotations of the interface accessed by the user; The downloading interface identifier is used to determine whether the interface accessed by the user is a downloading interface based on the annotations and labels of the interface accessed by the user.

3. The user access data processing system according to claim 1, characterized in that: The sensitive data authorizer is used to: confirm the user permission list to be reviewed, add the confirmed user permission list to the daily authorization list, and keep the authorization operation record; The sensitive data authenticator is used to authenticate user permissions when a user access operation to sensitive data is detected.

4. The user access data processing system according to claim 3, characterized in that: When a user accesses sensitive data, the user's permissions are authenticated, including: Authenticate the user and determine whether the user ID or the user's access path is stored in the whitelist. If the user ID or the access path is stored in the whitelist, the user authority authentication is passed; If the user ID and access path are not stored in the whitelist, obtain the user's current operation type and user token, and determine whether the operation type is included in the user permissions corresponding to the user token. When it is included in the user permissions corresponding to the user token, it is determined that the user permission authentication has passed; otherwise, the user permission authentication has failed.

5. The user access data processing system according to claim 4, characterized in that: The data desensitization processing unit is specifically used for: When the type of the interface accessed by the user is a non-download interface: When the sensitive data authenticator determines that the authentication fails, obtaining the attribute value corresponding to the data of the reference data type in the return data of the user access interface; When the attribute value is of a set type, each member in the set is taken out in a loop, and the desensitization processing scheme is called recursively to perform desensitization processing on each member; When the attribute value is of a custom type, a desensitization processing scheme is recursively called to perform desensitization processing on the data of the reference data type; Acquire data of a sensitive field marked as such in the return data of the user access interface, determine the data type of the sensitive field based on the attribute value, and perform desensitization processing on the sensitive field based on a desensitization method corresponding to the data type of the sensitive field; When the sensitive data authenticator determines that the authentication is successful, the real value returned by the interface accessed by the user is returned; When the type of interface accessed by the user is a download interface: When the sensitive data authenticator determines that the authentication fails, the user's download operation is released; when the sensitive data authenticator determines that the authentication passes, the user's download operation is released.

6. The user access data processing system according to claim 5, characterized in that: Desensitizing the data of the reference data type and desensitizing the sensitive field, including: When the data of the reference data type or the data type of the sensitive field to be processed is a string, the data to be desensitized is desensitized by replacing the original string; When the data of the reference data type or the data type of the sensitive field to be processed is non-string, a desensitization strategy matching the type of the processed data is called to perform desensitization processing.

7. The user access data processing system according to claim 1, characterized in that: Also includes: A buffer, the buffer being used to store user login information and user authority information; A data storage device is used to store a list of authorized users, types of sensitive business data, and sensitive data operation logs.

8. A user access data processing terminal, characterized in that: A system for processing user access data according to any one of claims 1 to 7 is applied.

9. The user access data processing terminal according to claim 8, characterized in that: The processing terminal for the user to access data is a computer.

10. A server, characterized in that: A system for processing user access data according to any one of claims 1 to 7 is applied.

Images