CN106295388B - A kind of data desensitization method and device - Google Patents

Abstract

The invention discloses a data desensitization method and device, which are used to solve the problems of low data desensitization efficiency and inflexible management and control existing in the prior art. The method includes: receiving a structured query language SQL instruction sent by a user; when it is judged that the data to be accessed by the SQL instruction contains sensitive data, and the user is not allowed to access the sensitive data, according to a preset The sensitive conversion rule converts the SQL command, so that the sensitive data accessed by the converted SQL command is desensitized data.

Description

A data desensitization method and device

technical field

The invention relates to the technical field of information security, in particular to a data desensitization method and device.

Background technique

With the growth of the market and business development, more and more customer information is stored in the enterprise database. Once leaked, it will bring huge trust crisis and economic loss to the enterprise. For this reason, all enterprises have attached great importance to data security, and have prevented the occurrence of data leakage incidents and traced the source of the incident through many management or technical means such as internal and external network isolation, firewall construction, and security audit. Among them, desensitization (or obfuscation) of sensitive data is an active and effective means to prevent data leakage.

The so-called data desensitization refers to the transformation of sensitive data through desensitization rules to achieve reliable protection of sensitive data, so that the desensitized real data can be safely used in development, testing and other non-production environments and outsourcing environments Collect (or desensitized data) without information leakage.

At present, data desensitization mainly adopts the following technologies:

1. Use the Update statement in the database to update the original data in the table to convert the sensitive data. This method is to log in to the database after the database synchronization is completed, use the Update statement to convert the sensitive data according to the specified desensitization rules, and submit it to take effect after the operation is completed.

2. Desensitize sensitive data during data migration based on technical tools. This method can separately encrypt the exported sensitive data table, so that the sensitive data can be displayed in the form of desensitized data. After obtaining the encrypted password, the desensitized data can be restored to the original data.

Among the above two desensitization technologies, the desensitization operation of the first desensitization technology using the Update statement is irreversible. When sensitive data needs to be accessed, the database needs to be re-synchronized, which is less flexible and cannot meet business needs. Since sensitive data with a large amount of data needs to be modified during the desensitization process, the desensitization process is inefficient and not suitable for scenarios that require high data timeliness. Although the second desensitization technology can restore the desensitized data to the original data after obtaining the encrypted password, that is, it is reversible, but since the sensitive data is also modified during the export and import process, there is also desensitization The problem of low process efficiency is not suitable for scenarios that require high data timeliness. In addition, the encryption password is fixed and cannot be changed flexibly. Once the user obtains the encryption password, the user's access right to sensitive data cannot be revoked, which is inconvenient for management and control.

In the actual production environment, due to security and system resource constraints, it is necessary to provide internal statisticians or auditors with a statistical and auditing data environment independent of production. In this scenario, the timeliness of data is highly required, so the data synchronization and desensitization operations must be completed periodically within the specified time window. At the same time, due to the advancement of the real-name system for customer data, it is necessary to support the needs of auditors to access raw data from time to time within the scope of security permits. In this case, none of the above techniques can meet the requirements.

Contents of the invention

Embodiments of the present invention provide a data desensitization method and device to solve the problems of low data desensitization efficiency and inflexible management and control existing in the prior art.

Embodiments of the present invention adopt the following technical solutions:

The first aspect provides a data desensitization method, including:

Receive the structured query language SQL command sent by the user;

When it is judged that the data to be accessed by the SQL instruction contains sensitive data, and the user is not allowed to access the sensitive data, the SQL instruction is converted according to the preset desensitization conversion rule, so that the converted Sensitive data accessed by SQL commands is desensitized data.

Optionally, when it is determined that the data to be accessed by the SQL instruction contains sensitive data, and the user is not allowed to access the sensitive data, the SQL instruction is converted according to a preset desensitization conversion rule, Make the sensitive data accessed by the converted SQL command desensitized data, including:

Judging whether the data to be accessed by the SQL command contains sensitive data;

When it is determined that the data to be accessed by the SQL instruction contains sensitive data, continue to determine whether the user is allowed to access the sensitive data;

When it is determined that the user is not allowed to access the sensitive data, the SQL command is converted according to a preset desensitization conversion rule, so that the sensitive data accessed by the converted SQL command is desensitized data.

Optionally, receive the SQL command sent by the user, specifically including:

Receive the SQL command sent by the user at the first time; then

Determine whether the user is allowed to access the sensitive data, specifically including:

judging whether the user is an authorized user according to a pre-stored authorized user list;

When it is determined that the user is an authorized user, continue to determine whether the first time is within the access time range corresponding to the authorized user, and determine whether the sensitive data to be accessed by the SQL command is the one corresponding to the authorized user. authorized access object;

When it is determined that the user is not an authorized user, or that the first time is not within the access time range, or that the sensitive data to be accessed by the SQL instruction is not the authorized access object, determine the The user is not permitted to access said sensitive data;

When it is determined that the user is an authorized user, the first time is within the access time range, and the sensitive data to be accessed by the SQL instruction is the authorized access object, it is determined that the user is allowed to access the sensitive data.

Optionally, determine whether the data to be accessed by the SQL instruction contains sensitive data, specifically including:

Scanning the SQL instruction, when it is analyzed that the SQL instruction contains a query select statement, and the data table to be queried in the select statement contains a preset sensitive data table, and the included sensitive data table is to be queried When the data column contains a preset sensitive data column, it is determined that the data to be accessed by the SQL instruction contains sensitive data; otherwise, it is determined that the data to be accessed by the SQL instruction does not contain sensitive data.

Optionally, the desensitization conversion rules include:

The statement used to access the sensitive data in the SQL instruction is replaced with a preset conversion function, and the preset conversion function is used to convert the character at a specified position in the sensitive data into a preset special character; wherein, the Sensitive data includes at least: any one of ID number, phone number, name and address.

The second aspect provides a data desensitization device, including:

The SQL instruction receiving module is used to receive the structured query language SQL instruction sent by the user;

The SQL instruction conversion module is used to convert according to the preset desensitization when it is judged that the data to be accessed by the SQL instruction received by the SQL instruction receiving module contains sensitive data, and the user is not allowed to access the sensitive data The rule converts the SQL command, so that the sensitive data accessed by the converted SQL command is desensitized data.

Optionally, the SQL instruction conversion module specifically includes:

a first judging unit, configured to judge whether sensitive data is included in the data to be accessed by the SQL instruction;

The second judging unit is configured to continue judging whether the user is allowed to access the sensitive data when the first judging unit judges that the data to be accessed by the SQL instruction contains sensitive data;

A conversion unit, configured to convert the SQL instruction according to a preset desensitization conversion rule when the second judging unit judges that the user is not allowed to access the sensitive data, so that the converted SQL instruction can access The received sensitive data is desensitized data.

Optionally, the SQL instruction receiving module specifically includes:

Receive the SQL command sent by the user at the first time; then

The second judging unit is specifically used for:

According to the pre-stored authorized user list, determine whether the user is an authorized user; when it is determined that the user is an authorized user, continue to determine whether the first time is within the access time range corresponding to the authorized user, and determine Whether the sensitive data to be accessed by the SQL command is the authorized access object corresponding to the authorized user; when it is determined that the user is not an authorized user, or it is determined that the first time is not within the access time range, or it is determined that When it is determined that the sensitive data to be accessed by the SQL command is not the authorized access object, it is determined that the user is not allowed to access the sensitive data; when it is determined that the user is an authorized user, the first time is in the access When the time range is within the time range and the sensitive data to be accessed by the SQL instruction is the authorized access object, it is determined that the user is allowed to access the sensitive data.

Optionally, the first judging unit is specifically used for:

Scanning the SQL instruction, when it is analyzed that the SQL instruction contains a query select statement, and the data table to be queried in the select statement contains a preset sensitive data table, and the included sensitive data table is to be queried When the data column contains a preset sensitive data column, it is determined that the data to be accessed by the SQL command contains sensitive data; otherwise, it is determined that the data to be accessed by the SQL command does not contain sensitive data

Optionally, the desensitization conversion rules include:

The statement used to access the sensitive data in the SQL instruction is replaced with a preset conversion function, and the preset conversion function is used to convert the character at a specified position in the sensitive data into a preset special character; wherein, the Sensitive data includes at least: any one of ID number, phone number, name and address.

The beneficial effects of the embodiments of the present invention are as follows:

In the embodiment of the present invention, when the SQL command sent by the user is received, and it is judged that the data to be accessed by the SQL command contains sensitive data, and the user is not allowed to access the sensitive data, the SQL command is processed according to the pre-set desensitization conversion rule. Conversion, so that the sensitive data accessed by the converted SQL command is desensitized data. Compared with the existing technology, the sensitive data is not changed during the data desensitization process, but the SQL command sent by the user is converted to determine the data display mode, so as to achieve the effect of data desensitization and greatly improve the Improve the efficiency of data desensitization. In addition, the data display method is no longer controlled by encrypted passwords, but by the judgment result of whether users are allowed to access sensitive data, so as to achieve flexible control.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention, and constitute a part of the present invention. The schematic embodiments of the present invention and their descriptions are used to explain the present invention, and do not constitute improper limitations to the present invention. In the attached picture:

Fig. 1 is the implementation flowchart of a data desensitization method provided by the embodiment of the present invention;

Fig. 2 is a schematic diagram of the application scenario of the data desensitization method provided by the embodiment of the present invention in a specific application;

FIG. 3 is a specific flow chart of the data desensitization method in this application scenario;

Fig. 4 is the specific implementation flowchart of judging whether there is the content of extracting sensitive data in the SQL instruction;

FIG. 5 is a schematic structural diagram of a data desensitization device provided by an embodiment of the present invention.

Detailed ways

In order to solve the problems of low data desensitization efficiency and inflexible management and control existing in the prior art, an embodiment of the present invention provides a data desensitization solution. In this technical solution, the SQL command sent by the user is received, and when it is judged that the data to be accessed by the SQL command contains sensitive data, and the user is not allowed to access the sensitive data, the SQL command is converted according to the pre-set desensitization conversion rule , so that the sensitive data accessed by the converted SQL command is desensitized data. Compared with the existing technology, the sensitive data is not changed during the data desensitization process, but the SQL command sent by the user is converted to determine the data display mode, so as to achieve the effect of data desensitization and greatly improve the Improve the efficiency of data desensitization. In addition, the data display method is no longer controlled by encrypted passwords, but by the judgment result of whether users are allowed to access sensitive data, so as to achieve flexible control.

The embodiments of the present invention will be described below in conjunction with the accompanying drawings. It should be understood that the embodiments described here are only used to illustrate and explain the present invention, and are not intended to limit the present invention. And in the case of no conflict, the embodiments and the features of the embodiments in the present invention can be combined with each other.

The embodiment of the present invention provides a data desensitization method, as shown in FIG. 1 , which is a flow chart for the realization of the method, and specifically includes the following steps:

Step 11, receiving the SQL command sent by the user;

Step 12, when it is judged that the data to be accessed by the SQL command contains sensitive data, and the user is not allowed to access the sensitive data, the SQL command is converted according to the pre-set desensitization conversion rules, so that the converted SQL command The accessed sensitive data is desensitized data.

Wherein, this step 12 can be but not limited to realize according to the following process:

First determine whether the data to be accessed by the SQL command contains sensitive data;

Specifically, scan the SQL command, when it is analyzed that the SQL command contains a query select statement, and the data table to be queried in the select statement contains a preset sensitive data table, and the data column to be queried in the sensitive data table When contains the preset sensitive data columns, it is determined that the data to be accessed by the SQL instruction contains sensitive data; otherwise, it is determined that the data to be accessed by the SQL instruction does not contain sensitive data.

When it is determined that the data to be accessed by the SQL command contains sensitive data, continue to determine whether the user is allowed to access sensitive data;

In the case that the SQL command in step 11 is sent by the user at the first time, in the embodiment of the present invention, it may be determined, but not limited to, whether the user is allowed to access sensitive data in the following manner:

Determine whether the user is an authorized user according to the pre-stored authorized user list;

When it is judged that the user is an authorized user, continue to judge whether the first time is within the access time range corresponding to the authorized user, and judge whether the sensitive data to be accessed by the SQL command is an authorized access object corresponding to the authorized user;

When it is determined that the user is an authorized user, the first time is within the access time range, and the sensitive data to be accessed by the SQL command is an authorized access object, it is determined that the user is allowed to access the sensitive data;

When it is determined that the user is not an authorized user, or it is determined that the first time is not within the access time range, or it is determined that the sensitive data to be accessed by the SQL command is not an authorized access object, it is determined that the user is not allowed to access the sensitive data.

When it is determined that the user is not allowed to access sensitive data, the SQL instruction is converted according to the pre-set desensitization conversion rule, so that the sensitive data accessed by the converted SQL command is desensitized data.

Among them, the desensitization conversion rule can be but not limited to:

Replace the statement used to access sensitive data in the SQL command with a preset conversion function; where the preset conversion function is used to convert characters at specified positions in the sensitive data into preset special characters; where the sensitive data includes at least: ID card Any one of data such as numbers, phone numbers, names, and addresses.

Compared with the prior art, the embodiment of the present invention does not change the sensitive data in the data desensitization process, but adopts the method of converting the SQL command sent by the user to determine the data display mode, so as to achieve the effect of data desensitization. Greatly improved the efficiency of data desensitization. In addition, the data display method is no longer controlled by encrypted passwords, but by the judgment result of whether users are allowed to access sensitive data, so as to achieve flexible control.

In order to better understand the embodiments of the present invention, the specific implementation process of the embodiments of the present invention will be described below in combination with specific implementations.

The above-mentioned data desensitization method provided by the embodiment of the present invention can be implemented by adding a data desensitization server and an authorization approval server during specific application. As shown in FIG. 2 , it is a schematic diagram of an application scenario of the above-mentioned data desensitization method provided by an embodiment of the present invention in a specific application.

The permission approval server is responsible for user authentication and provides interfaces (user whitelist, authorization time window, authorized access objects, etc.) to the data desensitization server.

Among them, user white list: the authorized user list, users in the authorized user list are allowed to access sensitive data;

Authorization time window: the access time range within which users in the authorized user list are allowed to access sensitive data.

Authorized access object: the database object (such as: table, view or the same name, etc.) that users in the authorized user list are allowed to access.

When a user needs to access sensitive data, he or she initiates an application to the authority approval server, and the application includes applicant information, access object, access time, access reason and other information. The application is submitted to the superior leader through the authority approval server for manual review. When it is confirmed as a legitimate access, the applicant information in the application is added to the user white list, and the access time is converted into the authorization time window. Converted to an authorized access object.

The data desensitization server is responsible for recording the desensitization conversion rules for sensitive data, and judging the SQL commands sent by users. If it is found that the content to be accessed by the SQL commands sent by users involves , address, etc.), continue to judge whether the user is an illegally authorized user (that is, not allowed to access sensitive data) according to the interface provided by the authority approval server, and if the user is found to be an illegally authorized user, immediately apply the desensitization conversion rule Convert the SQL command submitted by the user so that the data presented to the user is desensitized data; if it is found that the content to be accessed by the SQL command sent by the user does not involve sensitive data, or it is found that the content to be accessed by the SQL command sent by the user involves sensitive data At the same time, if the user is a legally authorized user, the SQL command submitted by the user will not be processed, and will be directly distributed to the background database for execution.

When recording the desensitization conversion rules for sensitive data in the data desensitization server, the following information also needs to be recorded:

Configuration information of all database instances connected to the data desensitization server, including database instance name, IP address, listening port, etc. for which sensitive data desensitization needs to be performed;

Database user mode: record account information including sensitive data tables under specific database instances.

Sensitive data table: A data table, view or the same name that stores sensitive data.

Sensitive data column: the column name of the data object (table, view or the same name) that stores sensitive information.

The desensitization conversion rules recorded in the data desensitization server, that is, the rules used when performing desensitization conversion on sensitive data columns, are generally written using built-in functions in the database. These functions are used to convert characters at specified positions in sensitive data to preset Special characters.

Take sensitive data including ID number, phone number, name and address as an example:

Desensitization of the ID card number: Replace the characters in the specified position of the ID card (assumed to be CERITID) or directly replace all characters of the entire ID card number with special characters (such as '*') as required. If the last three digits are desensitized, the specified function is SUBSTR(CERITID, 1, LENGTH(CERITID)-3)||'***'.

Desensitization of phone numbers: Through number pattern analysis, judge whether the first 3-5 digits are area codes or special numbers (such as: 021, 12580, 17951, etc.), intercept valid numbers, and then blur the numbers in corresponding positions as needed or directly replace all characters of the entire phone number with special characters (such as '*') as required. If the last 4 digits need to be fuzzy for fixed-line phones, the specified function is: SUBSTR(phone, 1, LENGTH(phone)-4)||'****'.

Desensitization of the name: Determine whether the user’s surname is included, select any character after the surname and replace it with a special character (such as ‘*’), or directly replace all characters of the entire name with special characters as needed.

Desensitization of residential addresses: Judging whether keywords such as "city", "district", "town", "township", "village", "street", "number" and "building" are contained, and the Randomly replace characters outside the address, or directly replace all characters in the entire address with special characters (eg '*') as needed.

After adding a desensitization conversion rule, the data desensitization server will automatically scan the database dictionary based on the information provided above, find out all data object names and column names that refer to sensitive data, and iteratively update them to the above rule set.

As shown in FIG. 3 , it is a specific flow chart of the data desensitization method in this application scenario. Specifically include the following steps:

Step 31, the user connects to the specified database instance through any tool, and submits an SQL command.

Step 32, the data desensitization server determines whether there is content to extract sensitive data according to the database instance selected by the user and the SQL command submitted. If not, execute step 37, and if yes, continue to execute step 33.

Step 33, check whether the user is an authorized user according to the user white list provided by the authority approval server. If not in the user whitelist, execute step 36, and if in the user whitelist, continue to execute step 34.

Step 34, according to the authorization time window and the current time provided by the authority approval server, judge whether the current time is within the authorization time window, if not, execute step 36, if so, continue to execute step 35.

Step 35, according to the authorized access object provided by the authority approval server and the sensitive data to be extracted by the SQL command, judge whether the sensitive data to be extracted by the SQL command is an authorized access object, if not, perform step 36, and if so, perform step 37.

Step 36, process the submitted SQL command according to the desensitization conversion rule, so that the sensitive data accessed by the converted SQL command is desensitized data.

Step 37, forwarding to the background database for execution and feeding back the result.

As shown in Figure 4, it is a specific implementation flowchart for judging whether there is content to extract sensitive data in the SQL command. Specifically include the following steps:

Step 41 scans the SQL command submitted by the user to determine whether the SQL command includes the SELECT statement (comprising the addition, deletion and modification of the query containing the SELECT. If not, then determine that the SQL command does not extract the content of sensitive data, if any , proceed to step 42.

Step 42, intercept the table name used in the SELECT statement, and check whether it contains a sensitive data table, if not, determine that there is no sensitive data extracted in the SQL command, and if so, continue to step 43.

Step 43, check the column name used in querying the sensitive data table in the SQL statement, and determine whether the sensitive data column is used. If not, determine that the content of the sensitive data is not extracted in the SQL command, and if so, determine the SQL statement The instruction contains the content of extracting sensitive data.

Furthermore, in the above step 36, the SQL instruction is converted.

It should be noted that if the word '*' is used in the SELECT statement, it is directly replaced with all column names of the sensitive data table, and the sensitive data columns are converted according to the conversion rules.

Compared with the prior art, the embodiment of the present invention does not change the sensitive data in the data desensitization process, but adopts the method of converting the SQL command sent by the user to determine the data display mode, so as to achieve the effect of data desensitization. Greatly improved the efficiency of data desensitization. In addition, the data display method is no longer controlled by encrypted passwords, but by the judgment result of whether users are allowed to access sensitive data, so as to achieve flexible control.

Based on the same inventive concept, a data desensitization device is also provided in the embodiment of the present invention. Since the problem-solving principle of the above-mentioned device is similar to the data desensitization method, the implementation of the above-mentioned device can refer to the implementation of the method, and the repetition is no longer repeat.

As shown in Figure 5, it is a schematic structural diagram of the data desensitization device provided by the embodiment of the present invention, including:

SQL instruction receiving module 51, is used for receiving the structured query language SQL instruction that user sends;

The SQL instruction conversion module 52 is used for desensitization according to preset when it is judged that the data to be accessed by the SQL instruction received by the SQL instruction receiving module contains sensitive data, and the user is not allowed to access the sensitive data The conversion rule converts the SQL command, so that the sensitive data accessed by the converted SQL command is desensitized data.

Optionally, the SQL instruction conversion module 52 specifically includes:

A first judging unit 521, configured to judge whether sensitive data is included in the data to be accessed by the SQL instruction;

The second judging unit 522 is configured to continue judging whether the user is allowed to access the sensitive data when the first judging unit 521 judges that the data to be accessed by the SQL instruction contains sensitive data;

The conversion unit 523 is configured to convert the SQL instruction according to a preset desensitization conversion rule when the second determination unit 522 determines that the user is not allowed to access the sensitive data, so that the converted SQL The sensitive data accessed by the command is desensitized data.

Optionally, the SQL instruction receiving module 51 specifically includes:

Receive the SQL command sent by the user at the first time; then

The second judging unit 522 is specifically used for:

According to the pre-stored authorized user list, determine whether the user is an authorized user; when it is determined that the user is an authorized user, continue to determine whether the first time is within the access time range corresponding to the authorized user, and determine Whether the sensitive data to be accessed by the SQL command is the authorized access object corresponding to the authorized user; when it is determined that the user is not an authorized user, or it is determined that the first time is not within the access time range, or it is determined that When it is determined that the sensitive data to be accessed by the SQL command is not the authorized access object, it is determined that the user is not allowed to access the sensitive data; when it is determined that the user is an authorized user, the first time is in the access When the time range is within the time range and the sensitive data to be accessed by the SQL instruction is the authorized access object, it is determined that the user is allowed to access the sensitive data.

Optionally, the first judging unit 521 is specifically configured to:

Scanning the SQL instruction, when it is analyzed that the SQL instruction contains a query select statement, and the data table to be queried in the select statement contains a preset sensitive data table, and the included sensitive data table is to be queried When the data column contains a preset sensitive data column, it is determined that the data to be accessed by the SQL command contains sensitive data; otherwise, it is determined that the data to be accessed by the SQL command does not contain sensitive data

Optionally, the desensitization conversion rules include:

The statement used to access the sensitive data in the SQL instruction is replaced with a preset conversion function, and the preset conversion function is used to convert the character at a specified position in the sensitive data into a preset special character; wherein, the Sensitive data includes at least: any one of ID number, phone number, name and address.

For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Certainly, when implementing the present invention, the functions of each module (or unit) can be implemented in one or more pieces of software or hardware.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

While preferred embodiments of the invention have been described, additional changes and modifications to these embodiments can be made by those skilled in the art once the basic inventive concept is appreciated. Therefore, it is intended that the appended claims be construed to cover the preferred embodiment as well as all changes and modifications which fall within the scope of the invention.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (8)

1. A data desensitization method, comprising: Receive the structured query language SQL command sent by the user; When it is judged that the data to be accessed by the SQL instruction contains sensitive data, and the user is not allowed to access the sensitive data, the SQL instruction is converted according to the preset desensitization conversion rule, so that the converted Sensitive data accessed by SQL commands is desensitized data; The desensitization conversion rule includes: replacing the statement used to access sensitive data in the SQL instruction with a preset conversion function, and the preset conversion function is used to convert the character at a specified position in the sensitive data into a preset special characters; wherein, the sensitive data includes at least any one of ID number, phone number, name and address. 2. The method according to claim 1, wherein when it is judged that the data to be accessed by the SQL command contains sensitive data, and the user is not allowed to access the sensitive data, according to the preset The sensitive conversion rule converts the SQL command, so that the sensitive data accessed by the converted SQL command is desensitized data, specifically including: Judging whether the data to be accessed by the SQL command contains sensitive data; When it is determined that the data to be accessed by the SQL instruction contains sensitive data, continue to determine whether the user is allowed to access the sensitive data; When it is determined that the user is not allowed to access the sensitive data, the SQL command is converted according to a preset desensitization conversion rule, so that the sensitive data accessed by the converted SQL command is desensitized data. 3. The method according to claim 2, wherein receiving the SQL command sent by the user specifically comprises: Receive the SQL command sent by the user at the first time; then Determine whether the user is allowed to access the sensitive data, specifically including: judging whether the user is an authorized user according to a pre-stored authorized user list; When it is determined that the user is an authorized user, continue to determine whether the first time is within the access time range corresponding to the authorized user, and determine whether the sensitive data to be accessed by the SQL command is the one corresponding to the authorized user. authorized access object; When it is determined that the user is not an authorized user, or that the first time is not within the access time range, or that the sensitive data to be accessed by the SQL instruction is not the authorized access object, determine the The user is not permitted to access said sensitive data; When it is determined that the user is an authorized user, the first time is within the access time range, and the sensitive data to be accessed by the SQL instruction is the authorized access object, it is determined that the user is allowed to access the sensitive data. 4. The method according to claim 2, wherein judging whether sensitive data is included in the data to be accessed by the SQL instruction, specifically comprises: Scanning the SQL command, when it is analyzed that the SQL command contains a query select statement, and the data table to be queried in the select statement contains a preset sensitive data table, and the sensitive data table to be queried contains When the data column contains a preset sensitive data column, it is determined that the data to be accessed by the SQL instruction contains sensitive data; otherwise, it is determined that the data to be accessed by the SQL instruction does not contain sensitive data. 5. A data desensitization device, comprising: The SQL instruction receiving module is used to receive the structured query language SQL instruction sent by the user; The SQL instruction conversion module is used to convert according to the preset desensitization when it is judged that the data to be accessed by the SQL instruction received by the SQL instruction receiving module contains sensitive data, and the user is not allowed to access the sensitive data The rule converts the SQL command, so that the sensitive data accessed by the converted SQL command is desensitized data; The desensitization conversion rule includes: replacing the statement used to access sensitive data in the SQL instruction with a preset conversion function, and the preset conversion function is used to convert the character at a specified position in the sensitive data into a preset special characters; wherein, the sensitive data includes at least any one of ID number, phone number, name and address. 6. The device according to claim 5, wherein the SQL instruction conversion module specifically comprises: a first judging unit, configured to judge whether sensitive data is included in the data to be accessed by the SQL instruction; The second judging unit is configured to continue judging whether the user is allowed to access the sensitive data when the first judging unit judges that the data to be accessed by the SQL instruction contains sensitive data; A conversion unit, configured to convert the SQL instruction according to a preset desensitization conversion rule when the second judging unit judges that the user is not allowed to access the sensitive data, so that the converted SQL instruction can access The received sensitive data is desensitized data. 7. The device according to claim 6, wherein the SQL instruction receiving module specifically comprises: Receive the SQL command sent by the user at the first time; then The second judging unit is specifically used for: According to the pre-stored authorized user list, determine whether the user is an authorized user; when it is determined that the user is an authorized user, continue to determine whether the first time is within the access time range corresponding to the authorized user, and determine Whether the sensitive data to be accessed by the SQL command is the authorized access object corresponding to the authorized user; when it is determined that the user is not an authorized user, or it is determined that the first time is not within the access time range, or it is determined that When it is determined that the sensitive data to be accessed by the SQL instruction is not the authorized access object, it is determined that the user is not allowed to access the sensitive data; when it is determined that the user is an authorized user, the first time is in the access When the time range is within the time range and the sensitive data to be accessed by the SQL instruction is the authorized access object, it is determined that the user is allowed to access the sensitive data. 8. The device according to claim 6, wherein the first judging unit is specifically configured to: Scanning the SQL instruction, when it is analyzed that the SQL instruction contains a query select statement, and the data table to be queried in the select statement contains a preset sensitive data table, and the included sensitive data table is to be queried When the data column contains a preset sensitive data column, it is determined that the data to be accessed by the SQL instruction contains sensitive data; otherwise, it is determined that the data to be accessed by the SQL instruction does not contain sensitive data.