KR101153969B1 - Query tool control method for preventing inner users from leaking the personal information and query tool control system therefor - Google Patents

Abstract

Query tool control method for preventing the leakage of personal information of the present invention, the agent distributed from the database (hereinafter, DB) firewall module is installed on the client system of the user, by hooking a specific event performed only by the query tool by the user Determining whether the filtered specific event occurs in a result window in which a result value of a query is output, and controlling an operation corresponding to the specific event that the user attempts according to the determination result. Include.

Description

QUERY TOOL CONTROL METHOD FOR PREVENTING INNER USERS FROM LEAKING THE PERSONAL INFORMATION AND QUERY TOOL CONTROL SYSTEM THEREFOR}

The present invention relates to a method and system for controlling a query tool for preventing leakage of personal information leakage by an internal user.

Database (DB) Firewall is a representative DB security solution that protects personal information. It performs user authentication, access control, and monitoring auditing.

By utilizing the functions of the existing DB security solution, it is possible to control the access of unauthorized users, thus preventing security incidents caused by unauthorized users. However, more than 70% of security incidents have been reported by insiders. In practice, therefore, more intensive management of misuse by insiders is required. In fact, GS Caltex also appears to have leaked after a person with internal authority copies the result value of personal information inquiry to EXCEL.

Especially during the development stage, personal information is easy to leak. The reason for this is that any developer and operator who has access to the personal information of a customer stored and managed in a database performs the inquiry on the personal information hundreds to thousands of times a day.

 When an internal user, a developer or operator accesses a DB, a solution called a query tool is generally used. For example, TOAD, SQL PLUS, Golden, etc.

When developing or operating an application related to a database, it is impossible to prevent an engineer, a developer or an operator, from using a query against the database. Because the work itself does not proceed.

However, if an engineer uses a query against a DB when developing or operating an application related to the DB, misuse of the result of the query is under control. Within a development or operating organization, there are people who have access to the results of a query and who do not have access to query results.

Leveraging the results of a query means outputting the results of the query, reprocessing the results of the query into a file, reprocessing it, or copying the contents of the query to other applications (for example, For example, excel) means to use the paste function.

It may also capture the screen itself. When capturing the screen itself, since it is an image, the amount of data that can be taken at a time is small, so it is less frequent than the above method. In other words, when capturing the screen itself, only information within one screen can be imaged, and depending on the screen resolution and other computing conditions, only about 50-100 pieces of data are displayed on one screen. This can be a hassle to reconstruct, so it's less frequently used.

Those who do not have access to query results include, for example, outsource developers, simple DB engineers, and system administrators. Unless the task itself requires the use of the contents of the DB, it becomes a person who does not have the authority to use the query results.

Therefore, technical protection measures are applied to those who do not have the right to use the query result value to control the use in the query tool.

Among the control mechanisms for the existing query tools, when using a specific query tool, one can implement a function to "COPY AND PAST" the query result value, to export to a file, and to control the output function.

However, it is meaningful when only one specific query tool is used in a company, but there are limitations that cannot be applied when using a plurality of various query tools.

Accordingly, an object of the present invention is to provide a query tool control method that can be applied to a general query tool, not limited to a specific query tool for preventing personal information leakage.

Query tool control method for preventing the leakage of personal information according to an aspect of the present invention for achieving the above object, the agent distributed from the database (hereinafter, DB) firewall module is installed on the client system of the user, Hooking and analyzing a specific event performed only by a query tool by the user; determining whether the filtered specific event occurs in a result window in which a result value of a query is output; and according to the determination result, Controlling an operation corresponding to the particular event being attempted.

According to an aspect of the present invention, a query tool control system is distributed from a database in which a customer's personal information is stored, and from a DB firewall module and the DB firewall module which block unauthorized users from accessing the database through a query. Hooking only a specific event performed in the query tool, and if the user indicating the hooked specific event is not authorized for the result value of the query, perform a user operation corresponding to the specific event attempted by the user. This includes the client system on which the controlling agent is installed.

According to the present invention, since all actions of copying and exporting to the output file from the client system are performed by the kernel of the operating system (for example, the windows system), this means that end point security functions regardless of the type of query tool. Can be performed. Therefore, the present invention is not limited to a specific query tool, but may be applied to a general query tool, thereby preventing unauthorized users from using a query tool to misuse a query result.

1 is a block diagram schematically showing the overall configuration of a DB security system for preventing personal information leakage according to an embodiment of the present invention.
2 is a view showing a result screen blocked by the security policy when an event performed by the query tool according to the security policy according to an embodiment of the present invention.
3 is a flowchart illustrating a query tool control method for preventing personal information leakage according to an embodiment of the present invention.

The technique proposed in the present invention is not dependent on a specific query tool (QUERY TOOL0, but can be applied to all general-purpose query tools that are widely used commercially. This is the first function of the present invention.

The functions suggested by the present invention may be provided as an independent solution in a package form, but are preferably integrated as a function of a software product called a DB firewall.

In order to fully understand the present invention, the operational advantages of the present invention, and the objects achieved by the embodiments of the present invention, reference should be made to the accompanying drawings that illustrate embodiments of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram schematically showing the overall configuration of a DB security system for preventing personal information leakage according to an embodiment of the present invention.

Referring to FIG. 1, a DB security system for preventing personal information leakage according to an embodiment of the present invention includes a customer information database 100, a DB firewall 200, and a client 300.

The customer information database 100 stores various personal information of customers in the form of a database.

The user's client system 300 (hereinafter referred to as a 'client') is a query (a kind of command) that can retrieve the personal information (data) of customers stored in a database form through the DB firewall 200 in a desired structure and format. Write. Such a query is made using a query tool 320 installed in the client 300, for example, 'toad', 'orange', 'sql plus', and the like, and queries the DB. The customer information database 100 is provided with the customer information having a desired structure and format as desired as a result of the query according to the query made by the query tool 320. At this time, the client 300 to the query tool 310 Security agent module 310, hereinafter referred to as "agent" is installed, the query tool 310 in the "COPY AND PAST" function, the "File EXPORT" function, Output functions, etc. are controlled. Therefore, when the user of the client 300 is a user who does not have a right to use the query result value, such as an outsourced developer, a simple DB engineer, or a system administrator, the use of a query tool may be controlled for these users. Can be.

The DB firewall module 200 (referred to as DB firewall) interworks with the agent 310 of the client, distributes (or downloads) the security policy to the agent 310, and also collects user logs from the client 300. To manage. An agent 310 provided from the DB firewall 200 is installed in the client 300, and the agent 310 performs authentication and IP ROUTING. In particular, the agent 310 is added to the query tool control function proposed in the present invention.

As such, the DB firewall 200 serves to block unauthorized persons from accessing the DB, and the client 300 prevents an authorized user from misusing a query result value in a query tool by an agent installed therein. do. That is, a rating may exist within the authority. As a result, there are users who can utilize the customer's personal information and users who can inevitably query (queries) for the operation of the system, but who can not process or utilize the data itself.

 On the other hand, when a command execution such as "COPY AND PASTE", "File EXPORT", "Screen Output", etc. occurs in the query tool 300, in the present invention, it is controlled through the DB firewall 200 in conjunction with the agent 310 Can be operated in monitoring mode. Here, the monitoring mode captures the screen of the PC when a security event such as "COPY AND PASTE", "File EXPORT", "Screen output" occurs, and captures the captured screen with the agent 310 and the DB firewall 200. It will be sent to the DB security server (not shown) to be used in the future.

2 is a view showing a result screen blocked by the security policy when an event performed by the query tool according to the security policy according to an embodiment of the present invention. Reference is made together to FIG. 1 to help understand the description.

1 and 2, an agent 310 may perform an event corresponding to a query tool (executed) among an event occurring at a user's PC 300, or the like. In the kernel section of the Windows operating system).

If a COPY attempt is made to the result pane showing the result of the query during the event generated by the query tool 320, the DB security server logs the user through the DB firewall whether the user has the authority to use the result of the query. After checking, block if there is no authority and give an alarm.

In addition, the DB security server sends the contents to the DB firewall 200 to record that the user attempted to violate the security regulations. Likewise, control, alarm, and log management are performed for file export and output (eg print).

 Screen capture control can't take large amounts of customer data from a single capture, so it's not a threat to security and can be a rejection to users. That is, screen capture that is not related to privacy may be blocked. Therefore, it can be flexibly applied according to the security policy.

3 is a flowchart illustrating a query tool control method for preventing personal information leakage according to an embodiment of the present invention. For better understanding of the description, reference is made to FIG. 1 together.

1 and 3, the agent 310 installed in the client 300 filters an event performed by the query tool 320 as an analysis target (S310).

Subsequently, the agent 310 analyzes the filtered result, and the query tool 320 determines whether a COPY event occurs for the query output value by the user (S320).

If it is determined that the COPY event has occurred, it is determined whether the COPY event occurs in the result window instead of the query window (S360). Here, the query window is defined as an edit window that writes query statements for creating a query such as an SQL statement. The result window is defined as a space in which the result of the query statement, that is, the result value of the query is displayed (shown).

If it is determined that the COPY event has occurred in the query window (S360), then all processes are terminated.

If it is determined that the COPY event has occurred in the result window (S360), the DB security server (not shown in FIG. 1) analyzes the DB firewall or the user log received directly to determine whether the user has permission to utilize the result of the query. (S370).

If the authority is confirmed, then all processes are terminated.

If it is determined that there is no authority, the operation is attempted by the DB security server is controlled (S380). One example where such control is performed is as shown in FIG. 2.

Then, the DB security server to report and record the event sent to the DB firewall 200.

On the other hand, if it is determined in step S320 that the COPY event has not occurred (S320), the agent 310 determines whether the command of the EXPORT command by the client 300. If there is an instruction of the EXPORT command, then steps S370, S380, and S390 are performed.

If it is determined that the instruction does not indicate the EXPORT command, it is then determined whether the output command is indicated (S340). If there is an instruction of an output command, steps S370, S380, and S390 are then performed.

If it is determined that the output command is not instructed, it is then determined whether a screen capture command is instructed (S350). If it is determined that there is a screen capture command instruction, steps S370, S380, and S390 are then performed.

If it is determined that the screen capture command is not instructed, the process is finally terminated without determining that the user misuses the result value of the query in the query tool.

As described above, in the present invention, by hooking and analyzing only common events occurring in various query tools, the general-purpose query tool is used regardless of the type of query tool.

Although the contents of the present invention have been described with reference to one embodiment shown in the drawings, this is merely exemplary, and it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible therefrom. will be. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

Claims (10)

An agent distributed from a database firewall module, installed on a user's client system, hooking and analyzing a specific event instructing a " COPY " command executed on a kernel of an operating system;
Determining whether the filtered specific event occurs in a result window in which a result value of a query is output; And
Controlling an operation corresponding to the specific event that the user is attempting according to the determination result
Query tool control method for preventing personal information leakage, comprising the.
delete The method of claim 1, wherein when the copy event occurs in the result pane,
A database (hereinafter, referred to as DB) security server further comprising determining whether the user is authorized to utilize the result of the query;
If the user is not authorized, the query tool control method for preventing the leakage of personal information, characterized in that for controlling the operation corresponding to the copy event.
The method of claim 1, wherein when the specific event occurs in the result window,
And a DB security server sends the specific event to the DB firewall module to record an attempt by the user to violate a security rule in the DB firewall module.
An agent distributed from a database (hereinafter, referred to as DB) firewall module is installed in a user's client system, and hooks and analyzes a specific event performed on a kernel of an operating system;
Determining, by the DB security server, whether a user of the client system performing the analyzed specific event is authorized to use the result of the query by using user log information; And
Controlling an operation corresponding to the specific event that the user is attempting according to the determination result,
The specific event
A method for controlling a query tool for preventing personal information leakage, comprising an event indicating an "file EXPORT" command, an event indicating an output command, and an event indicating a screen capture command.
delete The method of claim 5, wherein a user of the client system that performs an event indicating a "file EXPORT" command, an event indicating an output command, and an event indicating a screen capture command is authorized to use the result value of the query. If not,
And transmitting, by the DB security server, the events to the DB firewall module to record the personal information.
A database storing customer personal information;
A DB firewall module that blocks unauthorized users from accessing the database through a query;
If the user that is distributed from the DB firewall module and hooks only a specific event performed by the user in a query tool and indicates the hooked specific event does not have the right to the result value of the query, by the user A client system having an agent installed that controls user operations corresponding to the specific event attempted,
The specific event may include an event indicating a "COPY" command, an event indicating a "file EXPORT" command, an event indicating an output command, and an event indicating a screen capture command. Query tool control system for prevention.
delete The method of claim 8, wherein the agent,
When an event indicating a "COPY" command is performed in the query tool by the user, whether an event indicating a "COPY" command occurs in a query window in which a query statement is written. In the result window showing the result value,
As a result of the determination, if it is determined to occur in the result window, it is determined whether the user instructing the "copy" command is authorized to use the result value of the query. Query Tool Control System.

Images