KR100916668B1 - Database Security Device and Method Using Agent - Google Patents

Abstract

A database security apparatus and a method using agent are provided to increase control efficiency about a user and security of database at the same time. A hooking unit(452) moves a DBMS(DataBase Management System) server process corresponding with the user process. The hooking unit moves a relay process. Using a relay process, a relay unit(453) performs a communication between the DBMS server process and the user process. In order for applying a security policy to the corresponding communication data, the relay unit communicates with the security application unit(440). According to the predetermined security policy, the security application unit applies the security policy to communication data transmitted from the relay unit. A listener(456) delivers the session information of user to an agent(451).

Description

DATABASE SECURITY APPARATUS AND METHOD USING AGENT}

The present invention relates to an apparatus and a method for securing a database. More particularly, the present invention relates to a database security system and a method for installing an agent in a DB server, the database management system (DBMS) coupled to the client and the server process of the DBMS. The present invention relates to a database security device and a method using an agent which directly connects to a.

As the information and communication era enters, various systems have emerged to collect and utilize various information or to obtain business information (BI) .Based on such systems, advances in DBMS (DataBase Management System) -related technologies are the foundation. This has been.

This DBMS stores and manages a wide variety of data, including business-related information, customer information, product information, and content information, and is a relational database management system for effectively managing such information. Oracle and Sybase ), Various DBMS such as MySQL, Microsoft SQL Server, etc. are used.

The construction of a security system to enhance the security of the DBMS that manages important information is also commonly applied on a certain scale or more to prevent various security incidents such as information leakage and information manipulation that occur frequently in recent years. In order to prevent security incidents caused by insiders, it is being developed to manage the usage history of all users accessing the DBMS.

The security system to enhance the security of the DBMS can be controlled so that only the user authorized by the administrator can access the DBMS, or can monitor the DBMS access and usage history and terminate the forced session, and log the usage history. It can provide various security functions such as saving and setting access policy for each user.

Recently, various access rights of various users such as general DBMS users, DBMS administrators, security managers, and executives are managed as well as monitoring of access by users with the highest authority.

The general configuration of the DBMS security system includes a gateway method and a sniffing method.

1 illustrates a basic DBMS security system to which a security configuration is applied in a gateway manner. A plurality of client terminals 10 are configured to connect to a DBMS 16 through a communication network 11, and to a DBMS 16. The gateway security server 12 is configured between the client terminals and the DB server to manage security for the server. The gateway security server 12 is located between the client 10 and the DB server 15 and receives the data of the client in the middle and sends the data to the DB server, and receives the data of the DB server and applies the security to the client. . This gateway method can control TCP sessions because it controls all packets to DB server in the middle, but only TCP sessions can be controlled, so 100% access control is not possible and DB does not go through gateway security server. Internal users directly using the server cannot apply the security policy of the gateway security server. In addition, in case the gateway server goes down, the network must be duplexed to prepare for an accident by using a FOD (14: failover device).

2 illustrates a basic DBMS security system to which a security configuration is applied in a sniffing manner, wherein a plurality of client terminals 20 are configured to connect to the DBMS 26 through a communication network 21, and the client terminal 20 Port mirroring at the switch between DB server 25 and DB server 25 or TAP (equipment for monitoring data transmitted over network without interruption) is installed to establish communication packet between client 20 and DB server 25. Copy and analyze or store at sniffing security server 22. The sniffing security system has no effect on the DB server even if the sniffing security server 22 is down during communication, so there is no problem in the work, but the packet monitoring may occur and the DB monitoring may not be complete. Only manual database security management, which can monitor or log data, is possible. Active database security management such as access control is not possible.

As described above, since the gateway-based security system can only control access to the TCP session, 100% access control is not possible and internal users who directly use the DB server without the gateway security server apply the security policy of the gateway security server. Can not. In addition, the security system using the sniffing method may not complete DB monitoring due to packet loss, and only passive database security management that monitors the connection type or access method or stores it as a log is possible. Active database security management is not possible. In addition, since recent information leakage incidents of the database are mainly performed by internal users, even internal users that cannot be controlled in the security system using the gateway method or the sniffing method should be included in the database security policy.

Therefore, access control is possible for all sessions, and is applied not only to external users accessing the communication server from outside the DB server but also to internal users directly accessing the DB server, and passive security management such as database monitoring and log management. In addition, there is a need for a database security system that has complete security for the database that is actively managed such as access control and various scalability of security methods.

An object of the embodiments of the present invention for improving the above-mentioned problems is to install an agent in a DB server and to communicate with the database only through the agent for various protocols with which the client communicates, thereby making it impossible to connect to the database through the agent. It is to provide a security device and method.

Another object of the embodiments of the present invention is to provide an apparatus and method for securing a database using an agent in which an agent installed in a DB server is executed in combination with a database management system so that the agent can control communication data of all users between a client and a database. It is.

Another object of the embodiments of the present invention is to provide an apparatus and a method for securing a database using an agent that allows an agent executed in combination with a database management system to directly communicate with a database security module to manage a function of a security server.

In order to achieve the above object, a database security device using an agent according to an embodiment of the present invention comprises an agent coupled to the DBMS, and a security application unit.

When a client or an internal user connects to a DBMS, the agent stores the connection information. When an agent requests a database statement within the connection, the agent executes the database statement through a general process as in a commercial DBMS. According to various security policies of the security application unit connected to the agent coupled to the DBMS, the security policy of the database statement is changed to the result of applying the security policy to the client or the internal user.

The security application unit performs a security policy such as rejecting the database statement, partially modifying the result of the database statement, or forwarding the result as it is, according to a previously stored database security policy. To achieve.

The agent coupled to the DBMS is composed of a hooking unit and a relay unit.

The hooking unit receives a session information processing unit for receiving and processing session information, a relay process starting unit for starting a relay process of a relay unit using user session information received from a listener of a commercial DBMS module, and session information of the activated relay process. It consists of a server process starting unit for starting the server process of the commercial DBMS module.

The relay unit includes a session information setting unit for setting session information necessary for relaying communication between the user process and the server process, a process communication unit communicating with the user process and the server process, and a security communication unit communicating with the security application unit.

The security application unit provides a security policy unit for storing a security policy, a security warning unit for sending a warning message for a security request or storing it in a log, and a security approval unit for providing a payment method when a database statement requiring payment is requested. And a security audit unit for determining whether or not the database statement is loaded on the database system, and a log storage unit for storing the execution statement or the execution result through the security application unit as a log.

The apparatus and method for securing a database using an agent according to an embodiment of the present invention installs an agent in a DB server and communicates with the database only through an agent for various protocols with which the client communicates. There is an effect that can enhance the sex.

In accordance with an embodiment of the present invention, an apparatus and method for securing a database using an agent may be executed by an agent installed in a DB server in combination with a database management system, thereby allowing the agent to control communication data of all users between the client and the database. It has the effect of enhancing control.

An apparatus and method for database security using an agent according to an embodiment of the present invention allow an agent executed in combination with a database management system to directly communicate with a database security module to manage the function of a security server, thereby increasing the scalability of database security management. It works.

The present invention as described above will be described in detail with reference to the accompanying drawings and embodiments.

3 shows a configuration of a general database system including a database security apparatus using an agent according to an embodiment of the present invention. As shown in FIG. 3, a plurality of client terminals 30, a DB server 32, and a communication network ( 31, an internal user 33 accessing the database directly from the DB server 32, a DBMS 34 configured in the DB server 32, an agent 35 coupled to the DBMS, and security applications. The configuration of the unit 36 is schematically shown.

The internal user 33 is used directly connected to the DB server 32 without using the communication network 31, for example, a batch program that accesses the DB directly through the console or operates inside the DB server. Since the internal user 33 directly accesses and works with the DBMS 34, security cannot be maintained in a database security system using a gateway method or a sniffing method. However, in the above example, since the agent 35 works in conjunction with the DBMS, an internal user must also access the database through the agent 35, thereby maintaining security.

The DBMS 35 is a combination of commercially available DBMS and agent 35 such as Oracle, Sybase, and MS-SQL. Externally, the DBMS 35 operates in the same manner as a commercial DBMS. You can use it just like a DBMS. However, internally, it is possible to directly connect various modules that control the database, such as connecting the security module 36 for the purpose of database management, to the agent 35 combined with the DBMS. There is an advantage that can be delivered by controlling according to the desired purpose without passing it as it is.

The agent 35 coupled to the DBMS stores the connection information when the client or internal user accesses the DBMS, and executes the database statement through a general process as in a commercial DBMS when requesting a database statement within the connection. After that, the result is changed to a result of applying the security policy of the database statement according to various security policies of the security application unit 36 connected to the agent 35 coupled to the DBMS. 33).

The security application unit 36 is an example of various modules that can be connected to the agent 35 is coupled to the DBMS, according to the security policy of the database to reject the database statement or partially modify the results of the database statement Or by delivering it as it is, to achieve the purpose of the database security policy applied to the client or internal user.

4 and 5 show in more detail the configuration of a general database system including a database security device using an agent according to an embodiment of the present invention, in particular the configuration of an Oracle DBMS. A general database system configuration including a database security device using an agent includes an external user 400 requesting a database statement from the outside through the communication network 410, the DB server 420, and the DB server 420. An internal user 430 requesting a database statement in the DB, a DBMS 450 coupled to the agent, and a security application unit 440 connected to the coupled agent 451.

DBMS 450 coupled with the agent is composed of an agent 451 and a commercial DBMS module 455, the agent 451 is composed of a hooking unit 452 and a relay unit 453.

The commercial DBMS module 455 is a commonly used Oracle DBMS, and shows the listener 456, the server process 457, and the database 458, which are important parts of the configuration.

4 illustrates a data flow when a user first connects in a configuration of a general database system including a database security device using an agent according to an embodiment of the present invention.

The external user 400 and the internal user 430 request a connection to an Oracle database through a listener 456 or a hooking unit 452. The external user 400 is a user accessing from the outside of the DB server 420 and the internal user 430 is a user accessing from within the DB server 420. In general, there are two main ways to connect to an Oracle database: the TCP protocol and the BEQ protocol. When the user connects to a client program such as SQL PLUS or Toad from the DB server 420, the TCP protocol is used, and the BEQ protocol may be used for a program or console connection inside the DB server 420. In Oracle, when a user uses the TCP protocol, the user connects to the Oracle database through a listener. When using the BEQ protocol, the user connects directly to the Oracle database instead of through a listener.

The listener 456 receives session information of the corresponding user and delivers the session information to the agent 451. In the commercial Oracle DBMS, the listener starts the user's server process. In the database security apparatus using the agent according to the present embodiment, the listener starts the hooking unit 452 of the agent instead of starting the server process. The hooking part of the agent may be started instead of the process of the hooking part, replacing the executable file name of the DBMS called by the listener 456, and the hooking part analyzing a DBMS internal protocol (for example, SQL * NET). It becomes possible by doing this. Alternatively, the hooking unit 452 of the agent may be started even when the Oracle database is directly connected to the Oracle database without using a listener using the BEQ protocol. The hooking unit replaces the execution file name of the DBMS, and the hooking unit analyzes the DBMS internal protocol. Become. Therefore, it is possible to apply universally to both external users accessing through the communication network outside the DB server and internal users directly accessing from the DB server.

The hooking unit 452 starts the server process 457, transfers the session information of the corresponding user received from the listener 456 to the security application unit 440, and according to the security policy of the security application unit 440. Determine session information to be passed to server process 457. In the security policy of the security application unit, if the user does not need to apply the security policy, the hooking unit transmits the session information of the user to the server process. Alternatively, if the user is a user to which the security policy is to be applied, the hooking unit requests the relay unit 453 to start the relay process in charge of the user together with the session information of the user. After the relay process is started, session information of the started relay process is transmitted to the server process. Thereafter, session information of the server process is transmitted to the relay process.

In the case of a user to which a security policy is to be applied, the relay process in the relay unit stores the session information of the user received from the hooking unit and the session information of the activated server process, and stores the session of the server process to the user. Pass your own session information instead. Since the user's process receives session information of the relay process instead of session information of the server process, a database statement made in the user's connection thereafter communicates with the server process 457 via the relay unit 453. do. Although not shown, a user who does not need to apply a security policy, since the user's session information is transmitted to the server process, the user 400, 430 is then directly communicated with the server process (457).

5 illustrates a communication flow in a state where a user to which a security policy is to be applied via a relay unit after an initial connection is configured in a general database system including a database security device using an agent according to an embodiment of the present invention.

The external user 400 and the internal user 430 request a database statement to the relay unit 453.

The relay unit 453 transfers the database statement received from the user to the security application unit 440 in the DB server 420 and checks whether it can be executed according to the security policy. The database statement classified as unable to execute because the check is completed is transmitted to the users 400 and 430 together with an error message in the relay unit 453. Alternatively, the executable database statement calls the database statement to the linked server process using the session information of the server process linked with the session information of the user in the relay unit, and receives the result of the statement to apply the security. The result is passed to the unit 440. The result of the database statement is modified according to the security policy of the security application unit, and the modified result is transmitted to the user as a result of applying the security policy of the database statement requested by the user.

Although the database security device using the gateway method or the sniffing method, which is a conventional method, access control or monitoring is possible only to an external user who has a security server installed, as shown in this embodiment, an agent combined with a DBMS is configured and a user and server process are performed at the relay unit in the agent. By controlling the communication between them, even the internal user 420 using the database by directly accessing the DB server can apply a security policy.

Figure 6 shows the configuration of the hooking unit 600 according to an embodiment of the present invention, the session information processing unit 602 for receiving and processing session information and the relay unit using the user session information received from the listener of the commercial DBMS module And a relay process starting unit 603 for starting a relay process and a server process starting unit 601 for starting a server process of the commercial DBMS module using session information of the activated relay process.

The session information processing unit 602 receives the session information of the user and transfers it to the relay process starting unit 603, and the user session information is connected to the user process ID as well as the connection information and the user process ID according to the connection location of the user process. Protocol information such as TCP or BEQ may be included.

The relay process activation unit 603 is a relay unit which is in charge of communication between the user process 611 and the server process 622 when the corresponding user is connected by using the session information of the user input from the session information processing unit 602. The relay process 641 of 640 is started.

When the relay process 641 of the relay unit 640 is activated, the session information processor 602 receives session information of the relay process and transmits the session information to the server process activation unit 601.

The server process starting unit 601 starts a server process 622 for executing a database statement of a corresponding user by using the relay process session information input from the session information processing unit 602. In a typical commercial Oracle DBMS, when a server process is started, a listener transmits session information of a user process, such as a user process ID, which requested a server process, to the server process. However, the server process activator 601 according to the present embodiment is a server process ( 622 transfers relay process session information of the relay unit 603 to the server process 622 to communicate with the relay unit 603.

When the server process 622 is started, the session information processor receives the server process session information and transmits the received server process session information to the relay process 641 of the relay unit 640. Thereafter, the relay process session information is transmitted to the user process.

Thereafter, communication is possible between the user process 611 and the server process 622 via the relay process 641.

7 shows a configuration of a relay unit 700 according to an embodiment of the present invention, a session information setting unit 701 for setting session information necessary for relaying communication between a user process 710 and a server process 730; A process communication unit 702 communicating with the user process 710 and the server process 730, and a security communication unit 703 communicating with the security application unit 740.

The session information setting unit 701 stores the user process session information input from the hooking unit 720 and the session information of the server process started from the hooking unit 720 when starting the relay process. Link with and establish session information required for the relay process to communicate with user processes and server processes.

When the process communication unit 702 is requested to execute a database statement from the user process 710 corresponding to the user session information among the session information set in the session information setting unit, the corresponding server process of the server process session information linked with the user session information. Call 730 to request an execution statement and receive the result. The process communication unit 702 may use the security communication unit 703 to apply a security policy with the security communication unit 703 with the result of the execution statement requested from the user process 710 or the execution statement received from the server process 730. You can make a security request. The process communication unit 702 transmits a result of applying a security policy to the user process 710 corresponding to the user process session information linked with the relay process session information.

The security communication unit 703 communicates with the security application unit 740 and makes a security application request to the security application unit 740 by using the result of the execution statement or the execution statement from the process communication unit 702. When the user process 710 requests a performance statement from the process communication unit 702, the process communication unit 702 may request security application to determine an authority that is available to the user, or from the server process 730. The application of security may be requested to determine whether the authority to inquire about the performance of the performance statement is transmitted. Therefore, the result of applying the security policy transmitted from the security application unit 740 may be secured from the statement or may be secured to the result of the statement. Therefore, when a user requests a performance statement, it may not be performed according to the security policy, and only a part of the results of the performance statement may be masked and transmitted.

8 illustrates a configuration of a security application unit 800 according to an exemplary embodiment of the present invention. The security policy unit 810 stores a security policy, and a security warning unit for sending a warning message or storing a warning message for a security request ( 820, a security approval unit 830 which provides a means of payment when a database statement requiring approval is requested, a security auditing unit 840 for determining whether a database statement is loaded on the database system, etc., It consists of a log storage unit 850 for storing the execution statement or the performance result, etc. that go through the security application.

The security policy unit 810 stores a policy regarding whether security is applied to the security alert unit, the security approval unit, the security audit unit, and the log storage unit.

The security warning unit 820 applies security to the warning policy of the security policy of the security policy unit 810, and the user has no authority or too much authority over the result of the execution statement or the execution statement requesting the application of the warning policy. When sending a large amount of queries continuously, security warning policies such as sending a warning message to the user as a result of applying security, or storing the user's information, access information, and execution statement information in a log To perform.

The security approval unit 830 applies security to a payment policy of the security policy of the security policy unit 810, and a pre-payment requesting the payment in advance before the execution statement requesting the application of the payment policy is performed. In the process of execution, the security payment policy such as payment is requested immediately after the payment is requested, or after the payment is requested for the result of the execution statement requesting the application of the payment policy.

The security audit unit 840 applies security to an audit policy of the security policy of the security policy unit 810, and the time of the execution statement is too long for the result of the execution statement or the execution statement requesting the application of the audit policy. If it takes a long time or is a statement about the audited target table, the security audit policy such as monitoring the user's information and blocking the user's access is executed.

The log storage unit 850 stores a log of a warning policy, a payment policy, and an audit policy among the security policies of the security policy unit 810, and various security applied results generated due to the security policies, and the like. Unnecessary parts such as user information can be removed or compressed and saved as a log.

9 is a flowchart illustrating a method for securing a database using an agent according to an embodiment of the present invention, in which a relay process is performed using a session information processing step S90 for receiving and processing session information and user session information received from a listener. A relay process activation step (S91) for starting, a server process activation step (S92) for starting a server process of the commercial DBMS module using session information of the activated relay process, and a relay process for determining whether the relay process has been started A startup confirmation step (S93) and a server process execution step (S98) for performing a server process if the relay process is not started, and setting up session information necessary for relaying communication between the user process and the server process if the relay process is activated. Relay session information setting step (S94), Ray process consists of a user process and the server process and the communication process, a communication step (S95) that, with the relay process and the security application unit communication security communication step (S96) to secure the secured application step is applied (S97).

In the relay process activation step S91, the user of the user session information is classified as a security policy using the session information of the user received in the session information processing step S90. If it is determined that there is no violation, the relay process may not be started so that the user process and the server process communicate directly without passing through the process communication step S95 and the secure communication step S96.

In the relay process activation confirmation step (S93), if the relay process is classified as not started, the user process communicates directly with the server process without going through the relay process as with a general commercial Oracle DBMS.

In the above described and illustrated with respect to preferred embodiments according to the present invention. However, the present invention is not limited to the above-described embodiment, and various modifications can be made by those skilled in the art without departing from the gist of the present invention attached to the claims. .

1 is a configuration diagram of a basic DBMS security system to which a security configuration is applied in a gateway manner.

2 is a configuration diagram of a basic DBMS security system to which a security configuration is applied by a sniffing method.

3 is a block diagram of a basic DBMS security system to which a security configuration is applied in an agent manner according to an embodiment of the present invention.

4 and 5 are configuration diagrams of a database security device using an agent according to an embodiment of the present invention.

Figure 6 is a block diagram of a hooking portion according to an embodiment of the present invention.

7 is a configuration diagram of a relay unit according to an embodiment of the present invention.

8 is a block diagram of a security application unit according to an embodiment of the present invention.

9 is a flowchart illustrating a database security device using an agent according to an embodiment of the present invention.

** Description of symbols for the main parts of the drawing **

30: Client

32: DB server 34: DBMS

35: agent 452: hooking part

453: relay unit 456: listener

457: Server Process

Claims (14)

A database security device configured on the same server as a database management system (DBMS), A database user process, including an online user and a local access user, is executed by replacing a database executable file upon request for a database connection, starting up a corresponding DBMS server process and communicating between the user process and the DBMS server process. A hooking unit for starting a relay process for relaying the relay; A relay unit in charge of communication between the user process and the DBMS server process using the relay process and communicating with a security application unit to apply a security policy to corresponding communication data; A security applying unit for applying and transmitting a security policy to communication data transmitted from the relay unit according to a preset security policy; The security application unit includes a security policy unit that stores a security policy, a security warning unit that sends a warning about a security request, a security approval unit that provides a means of payment when a database statement requiring payment is requested, and a database statement is stored in a database. And at least one of a security auditing unit for determining whether a system is loaded and a log storage unit for storing a database execution statement or a result thereof as a log. The method according to claim 1, wherein the hooking portion A session information processor for receiving and transmitting user process session information of a database user, session information of a DBMS server process corresponding to the user process, and session information of a relay process relaying communication data between the user process and the DBMS server process; ; A relay process activation unit for starting the relay process by using user process session information received from a session information processing unit; And a server process activator for starting the DBMS server process by using session information of the relay process started from the relay process activator. The method according to claim 1, wherein the hooking portion And if the user corresponding to the user process is a user who does not use the relay process, causing the user process and the DBMS server process to directly communicate with each other without starting the relay process. The method of claim 1, wherein the relay unit A session information setting unit for linking session information necessary for relaying communication between the user process and the DBMS server process, with session information of the relay process; A process communication unit for communicating between the user process and the DBMS server process via the relay process; And a secure communication unit in communication with the security applying unit and making a security application request to the security applying unit using a result of a database statement or a database statement from the process communication unit. delete The database security device of claim 1, wherein the database management system is Oracle. The apparatus of claim 1, wherein the OS of the server is Unix or Linux. In the database security method using a database security device configured on the same server as the database management system (DBMS), A database user process, including an online user and a locally connected user, replaces the database executable file upon request for database connection, starts the corresponding DBMS server process, and relays communication between the user process and the DBMS server process. A hooking step of starting a relay process; And relaying between the user process and the DBMS server process using the relay process and applying and transmitting a security policy according to a security policy set in the communication data. The hooking step receives and transmits user process session information of a database user, session information of a DBMS server process corresponding to the user process, and session information of a relay process relaying communication data between the user process and the DBMS server process. Session information processing step; A relay process activation step of starting the relay process using the user process session information received from the session information processing step; And a server process starting step of starting the DBMS server process using session information of the relay process started from the relay process starting step. delete The method of claim 8, wherein the hooking step And if the user corresponding to the user process is a user who does not use the relay process, directly communicating the user process with the DBMS server process without starting the relay process. The method of claim 8, wherein the relay step A session information setting step of linking session information necessary for relaying communication between the user process and the DBMS server process, with session information of the relay process; A process communication step of communicating between the user process and the DBMS server process via the relay process; And a security application step of applying security according to a predetermined security policy by using a result of a database statement or a database statement among the communication data in the process communication step. The method of claim 11, wherein the security application step A security policy step that stores the security policy, a security warning step that sends an alert for security requests, a security approval step that provides a means of payment when a database statement that requires a payment is requested, and a database statement loads the database system. And at least one of a security audit step of determining whether or not to be caught, and a log storing step of storing a database execution statement or a result thereof as a log. The method of claim 8, wherein the database management system is Oracle. The method of claim 8, wherein the OS of the server is Unix or Linux.

Images