KR20050008486A - method of administering access to database - Google Patents

Abstract

PURPOSE: A method for reinforcing access and authority management of a database based on the PKI(Public Key Infrastructure) is provided to prevent an internal or external hacker from accessing a business information database by authenticating a real user with an electronic signature based on the PKI. CONSTITUTION: A security layer(220) processing authentication by the PKI and authority assignment by the PMI(Privilege Management Infrastructure) is installed in the database for storing various kinds of information. To communicate information with a database communication module(210), the security layer is installed to the same layer section as the database communication module. The access to various kinds of information databases(230) is managed by commonly using an access mode through a database user ID/password and the access mode through the security layer.

Description

Method of administering access to database

The present invention relates to a method for strengthening database access and authority management. More specifically, the public key infrastructure when accessing an information DB by an information system, an external DB management tool, an internal DB management tool, etc., which can access various information DBs of a database. It greatly enhances security by installing an area that performs identity authentication and authorization processing in the database, and the authority transfer function that temporarily grants access to information DB to users who do not have access to information DB and database access. And strengthening database access and authorization management by adding information auditing functions such as information DB usage history.

As part of the "Administrative Computing Network Project," which has been implemented since 1987, government agencies at various levels have been implementing the administrative informatization project, and have established and operated important information on national administration as a database (hereinafter, simply referred to as a 'DB'). However, in the electronic administrative environment where non-face-to-face and anonymity exist, the basis of protection against various dysfunctions such as identity forgery of users, data forgery and alteration is relatively weak.

For example, in the case of educational administrative information system, security problems such as lack of information access and authority management system and management targets in the process of changing existing C / S environment system to NEIS (National Education Information System) Conflicts are intensifying due to inadequacy of information types.

In addition, the problem of data protection from internal users is becoming a big problem not only for the government but also for general enterprises.

1 is a diagram illustrating a conventional commercial database access route and security method. As shown in FIG. 1, the method of accessing various information DBs 34 in the database 30 can be broadly divided into three methods. The method of accessing the information through the A / P server information system 14 ( 1, a method of accessing through an external DB management tool 20 (indicated by a dashed line in FIG. 1) and a method of accessing through a DB management tool 50 provided inside the database 30 ( 1 as indicated by a dashed chain line).

In the above-described configuration, according to the access method through the information system (hereinafter, simply referred to as 'APPL'), most APPL clients (hereinafter also referred to as 'users') 10 are business information of the A / P server 12. When accessing the system 14, access the information system 14 of the A / P server 12 and enter the user's ID and password in the login screen for the first time, and the user authentication and access authority through the user information DB built in the database. Upon confirmation, the desired information DB 34 can be accessed.

In this case, the information system 14 accesses the database 30 by connecting to the DB communication module 32 of the database 30 through the client software (communication module) 16 installed in the A / P server 12. And a method of connecting to the database 30 through the middleware 18 and the Java DataBase Connectivity (JDBC) Thin Driver 40 in the A / P server 12 (indicated by a dotted line in FIG. 1). In the first case, because the DB USER information (DB_user ID and password) is embedded in the program system of the information system 14, it is a user who does not have access to the information DB 34 (Program developer, maintenance service personnel, etc.). However, there is a security vulnerability in that DB USER information (DB_user ID and password) can be easily obtained, so that various information DB 34 can be accessed without restriction. Furthermore, since the usage rights of the information system 14 and the various information DBs 34 are managed as data files (user information DBs) that can be arbitrarily changed, forgery and forgery of the information DB 34 can be easily performed. There is a problem that the reliability of the work information DB 34 is lowered.

In fact, a public service worker without permission from the car management information system accesses the information DB (automotive foreclosure information) by stealing the ID and password of a competent person in charge, and then randomly deletes the arrears, such as fines for the offending vehicle. The arrest of a criminal offense for giving and receiving money has been widely reported on the ground of the newspaper.

Second, when the A / P server 12 accesses the information DB 34 through the middleware 18 and the JDBC Thin Driver 40, the DB USER information (DB_User ID) is transmitted to the program system of the information system 14. And the DB USER information (DB_user ID and password) for accessing the database in the middleware 18 without inherent password). However, even in this case, the DB USER information (DB_user ID and password) is exposed to a user (Program developer, maintenance service personnel, etc.) who does not have access to the information DB 34, so that no information DB 34 has any information. There is a security vulnerability that allows access without restrictions.

On the other hand, various information DB management utilities are developed and utilized to support the information system 14 developer or database administrator to perform data change operations such as the construction of the information DB 34 or the addition, update and deletion of data. Enter DB USER information (DB_user ID and password) into such utilities, O / A programs such as Microsoft's Excel, and Report Tool (hereinafter referred to as 'external DB management tool') using information DB. It is possible to remotely access the various information DB (34). Therefore, if such DB USER information (DB_user ID and password) is leaked due to management neglect, even an unauthorized user can easily access the desired information DB without any restrictions through remote access.

In addition, the database 30, the SQL Interpreter, a data backup program (hereinafter, referred to as an 'internal DB') that can be used by a super administrator (DBA; Database Administrater) who is a database administrator who can manage various information DBs 34. Management tool), and the database administrator accesses the desired information DB 34 by inputting DB USER information (DB_user ID and password) into the internal DB management tool 50. And with absolute privileges to add, update, backup, etc., you can access without any restrictions. In this case, the DB USER information (DB_user ID and password) of the super user who has absolute authority for the maintenance of the database is often shared by various computer personnel and information system developers. .

In order to solve this problem, the identity and authority of the information system user is checked in the communication module 16 installed in the A / P server 12 of the information system 14 when accessing the database through the information system 14 as shown in FIG. 1. In order to provide access to the information DB 34, the identification and authorization system 13 is provided. However, when the information DB 34 is accessed through the information system, Client software (including communication module) provided by DBMS company must be installed in user's 10 machine to utilize high level security structure such as signature use. However, JDBC Thin Driver ( 40) In order to access the information DB 34 using the external DB management tool 20, middleware 18, etc., the client software provided by the DBMS company. It is difficult to expect a consistent security policy because the information DB 34 can be accessed without installing a software (including a communication module).

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and provides an area for performing identity authentication and authorization processing of a public key infrastructure between communication areas communicating with a database and accessing various information DBs. By adding the digital signature function to the system (APPL), external DB management tool, and internal DB management tool, it greatly enhances security by granting or denying access to the database in the areas of identity authentication and authorization that pass through the database access. The authority transfer function that grants temporary information DB access rights (temporary ID and password) to users who do not have access to information DB (program developer, maintenance service personnel, etc.), and the database access and information DB usage history of actual information users. It provides a method of strengthening database access and authority management by adding information auditing function. There is a purpose.

The database access and authority management strengthening method of the present invention is to install a security layer 220 for performing identity authentication by the PKI and authorization authorization by the PMI between the communication area and the database in which the various information is stored, within the database It is installed in the same layer area as the DB communication module 210 to exchange information with the DB communication module 210, and accesses to various information DBs in the database by using an approach through the security layer 220. Manage.

1 is a view for explaining a conventional commercial database access route and security method;

2 is a view for explaining the access route of the database access and authority management strengthening method of the present invention;

3 is a flow chart for explaining a database (DB) access and authority management strengthening method through the information system (Application) in the present invention,

Figure 4 is a flow chart for explaining a database (DB) access and authority management strengthening method through an external DB management tool in the present invention,

Figure 5 is a flow chart for explaining a database (DB) access and authority management strengthening method through the internal DB management tool in the present invention,

6 is a flowchart illustrating a temporary ID and password issuing method for a person in charge in the present invention to access a database (DB) for the transfer of authority;

FIG. 7 is a flowchart illustrating a method of accessing a database through a temporary ID and password by a privilege holder in the present invention.

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

10: APPL client, 12: A / P server,

13: identity and authorization system,

14: information system, 16: communication module,

18: middleware, 20: external DB management tool,

30: database, 32: DB communication module,

34: information DB, 40: JDBC Thin Driver,

50: internal DB management tool, 100: APPL client,

102: user PKC, 110: A / P server,

112: information system, 114: communication module,

120: external DB management tool, 122: administrator PKC,

130: authority management tool, 132: authority transfer PKC,

200: database, 210: DB communication module,

220: security layer, 222: authentication processing unit,

224: authorization authority, 230: information DB,

232: history DB, 240: internal DB management tools,

242: superuser PKC, 300: identification system,

310: DS, 320: OCSP server,

400: authorization system

Hereinafter, with reference to the accompanying drawings will be described in detail with respect to the database access and authority management strengthening method of the present invention, first of all, a brief description of the identification system and the authorization system as a related system for the application of the present invention.

2 is a diagram illustrating an access route of a method for enhancing database access and authority management according to the present invention. As shown in FIG. 2, the identification system 300 for the application of the present invention may be implemented based on a public key infrastructure (PKI). In such a public key infrastructure (PKI), when a user (User or Client) requests issuance of a Public Key Certificate (PKC) from the Registration Authority (RA), the registrar first offlines the user's identity. After verifying with the certificate authority (CA), the certificate authority is issued to the certificate authority, and the certificate authority issues a certificate to the user and at the same time the contents of the certificate are stored in the directory system (DS) 310, preferably LDAP ( Lightweight Directory Access Protocol). Here, the directory system 310 refers to a place for storing and retrieving a user certificate and user related information, a mutual certificate pair, and a certificate revocation list. The directory system 310 may be managed or separately managed by a certification authority depending on the application method. It can also be installed on your directory server.

Subsequently, various PKC utilization information systems (APPL) and the like check the identity of the user by asking the directory system 310 whether or not to register the certificate presented by the user, and such user information (Distinguished Name: User) The distinguished name, hereinafter simply referred to as 'DN'), the issuer's distinguished name and signature, and the user's public key information are regularly recorded according to a specified protocol.

In addition, the identification system may further include an Online Certificate Status Protocol (OCSP) server 320. In the PKC Utilization Information System (APPL), the PKC presented by inquiring to the OCSP server 320 is valid or discarded. You can check in real time.

Next, the authorization system 400, which is a related system for applying the present invention, is responsible for confirming the authority to use the information DB for the user whose identity has been confirmed by the identification system 300, etc. A Source Of Authority (AA) or Attribute Authority (AA) issues a privileged attribute certificate (AC) to the user that contains information about the user's authority, status, or mission, and stores it in the directory system. Subsequently, when the user presents it to the information system APPL, the information system APPL queries the directory system 310 for the authority to permit the use of the system within the authority. In addition, when the DB USER information (DB_user ID and password) and DB user information (DN) are additionally established in the authorization check system 400, the system administrator and the database administrator (DBA) may use the DB USER information (DB_user). ID and password). In other words, it is possible to separate the security-related roles of the system administrator and database administrator (DBA) can further enhance the security.

In addition, a temporary ID and password that can be used temporarily can be created when a business person with access to the information DB 230 needs to request business cooperation to a service company manager or general user in charge of maintenance. You can add features that you can.

In addition, if the authorization check system 400 includes an information DB access pattern analysis function, when an authorized user requests access to the information DB through the information system (APPL), it checks whether the pattern is normal and performs the information DB 230 access pre-audit. It can be utilized. Representative examples of the currently published authority verification system 400 include PMI (Privilege Management Infrastructure) and EAM (Enterprise Access Management) (hereinafter, 'PMI' is used as a generic term), and AC is similar to PKC. The user ID and public key, the name of the licensor, the signature text, and the authority information are included. At this time, if the authorization check system cannot be built externally, the role of the authorization check system 400 may be configured using an internal database.

On the other hand, in the authorization system 400, the database information (DB NAME) and DB USER information (DB_user ID and password) accessible according to the user information (DN), the temporarily generated ID and password information for the transfer of authority, Information DB 230 of the information system manages information DB 230 access pattern information and the like for pre-audit.

In the database 200 of FIG. 2, which is a representative diagram of the present invention, a variety of information DB 230, an information system 112 of an A / P server 110, or an external DB management tool 120 and an information DB 230 are provided. It may include a security layer (220) to allow or block the communication between the DB communication module 210, the DB communication module 210 and the information DB 230 is interposed to perform the two-way communication, The security layer 220 between the DB communication module 210 and the information DB 230 according to the result of checking to the identification system 300 and the authorization system 400 when there is a request for access to the specific information DB 230. Allow or block communication. In the above-described configuration, the security layer 220 is functionally responsible for authorization processing between the authentication processing unit 222 and the authority verification system 400 which are in charge of identification processing with the identification system 300. It may be made to include the authorization unit 224. In addition, in the information DB 230, a history DB 232 for which access rights are limited is assigned to specific information DB usage history, that is, user PKC information, type of information DB access tool, work date and time, information change command, and SQL statement. Can be stored and used for pre and post information auditing.

In FIG. 2, reference numeral 100 denotes an APPL client (user) using the information system 112. In the hard disk of the APPL client (user), an authorized and authenticated user PKC 102 uses a public key infrastructure (PKI). Must be stored in advance.

Reference numeral 120 denotes an external DB management tool capable of verifying an identity using a public key infrastructure (PKI). In order to use the external DB management tool 120, an external DB management tool 120 may also be connected to a hard disk of a terminal used by an information manager. The DB management tool user PKC 122 (hereinafter referred to as 'administrator PKC') must be stored in advance by the public key infrastructure (PKI).

Reference numeral 240 denotes an internal DB management tool that can access various information DBs without passing through the DB communication module 210, and can be identified by a public key infrastructure (PKI). In order to use 240, the superuser PKC 242 must be stored in advance by the public key infrastructure (PKI).

3 is a flowchart illustrating a method for enhancing database access and authority management through an information system (APPL) according to the present invention. In FIG. As shown in FIG. 3, the user of the information system 112 accesses the A / P server 110 in the method for strengthening database access and authority management in the information system 112 according to the present invention. When executed, a login screen is output to the user. In this state, when the user PKC 102 stored in the user's computer is output, the user selects his / her user PKC 102 and inputs a password (S2) to generate electronic signature information. Then, the generated digital signature information is transferred to the A / P server 110 (S4). Next, the A / P server 110 transmits the electronic signature information, the information system 112 information and the DB NAME of the A / P server 110 to the security layer 220 through the DB communication module 114. In step S6, a request for verification of an identity and an information system is requested. Thereafter, the authentication processing unit 222 of the security layer 220 transmits the user PKC 102 to the identification system 300 and requests the identity and the validity verification (S8). Next, the identification system 300 received such a request checks the user PKC 102 in the directory system 310 to confirm the identity of the user (S10), and inquires again to the OCSP server 320 to check the user PKC ( After confirming the validity of the method (S10), the user identity and the user PKC validation result are transmitted to the security layer 220 (S12). Thereafter, the security layer 220 transmits the user PKC 102, the information system information, and the DB NAME to the authorization system 400 through the authorization authority 224, so that the information system can access the information DB 230. If there is a check request (S14).

Next, the authorization confirmation system 400 receiving such a request retrieves the user AC from the directory system 310 and extracts DB USER information (DB_user ID and password), which is the access authority of the information system requested by the user (S16). After transmitting the result to the security layer 220 (S18), the security layer 200 allows or blocks the communication between the DB communication module 210 and the database according to the received authority inquiry result, that is, the user Allowing or blocking access to the specific information DB 230 (S20).

In the present invention, even if a legitimate user, such as the person in charge of the task, since the information manager can access only the information DB 230 belonging to the scope of the preset authority can be further enhanced security. Also, it is not necessary to embed DB USER information (DB_user ID and password) in the application program access information entered in the program source code to access the database, and thus impersonate DB USER information (DB_user ID and password). Access damage can be prevented in advance.

In addition, even when the user is permitted to access the specific information DB 230, the database 200 utilizes the information DB access pattern analysis function included in the authorization check system 400, and thus, the database 200 changes the information system APPL. In the case of requesting data change of the specific information DB 230 (S22), the information is compared with the normal information DB access pattern registered in the authorization check system 400 (S24), and the information is abnormal in the case of the abnormal information DB 230 access pattern. After the access to the DB 230, the information monitoring function to notify the information manager immediately, and the user information and data changes are stored in the history DB (232) (S26) so that it can be utilized for post-inspection audit. Can be.

4 is a flowchart illustrating a method for strengthening database access and authority management through an external DB management tool 120 including an identity verification function using a public key infrastructure (PKI) in FIG. Is shown. As shown in FIG. 4, when the administrator executes the external DB management tool 120 in the method of strengthening database access and authority management through the external DB management tool 120 according to the present invention, the administrator checks the PKC 122 and database information. (DB NAME) input login screen is output, in this state, the administrator selects the corresponding digital signature certificate (PKC) and enters the password to create the digital signature information, and again can access the desired information DB (230) The database information (DB NAME) is input (S30), and the electronic signature information and the database information (DB NAME) generated in this way is transferred to the security layer 220 (S32) to request identification and authority verification. Thereafter, the authentication processing unit 222 of the security layer 220 transmits the manager PKC 122 to the identification system 300 and requests the identity and the validity verification (S34). Next, the identification system 300 receives such a request, checks the administrator PKC 122 in the directory system 310 to confirm the identity of the administrator, and inquires again to the OCSP server 320 to confirm its validity. After S36), the administrator identity and the administrator PKC validation result are transmitted to the security layer 220 (S38). As such, after confirming the identity of the administrator, the security layer 220 transmits the administrator PKC 122 and the database information (DB NAME) to the authority verification system 400 through the authority authorization unit 224 to external DB management tool ( 120 checks whether there is access authority to the information requesting DB (230) (S40).

Next, the authorization check system 400 receiving such a request checks the administrator AC in the directory system 310 to check whether the user has the authority to access the requested information DB 230 (S42), and then checks the result. The security layer 220 is transferred (S44), and the security layer 200 allows or blocks communication between the DB communication module 210 and the database according to the received authority inquiry result, that is, to the corresponding information DB 230. Access is allowed or blocked (S46).

In addition, even when access to the specific information DB 230 by the external DB management tool 120 is permitted, the administrator of the information in the database 200 when the administrator requests a data change request (S48) of the specific information DB 230. And by storing the data changes in the history DB (232) (S50) can be used in the later information audit. As such, in the present invention, since the authority of the information is managed by the user's identity without exposing DB USER information (DB_user ID and password), an unauthorized person accesses the information DB 230 through the remote access utility. I can prevent it.

FIG. 5 is a flowchart illustrating a method for enhancing database access and authority management through an internal DB management tool 240 capable of verifying identity by a public key infrastructure (PKI) in FIG. have. As shown in FIG. 5, when the super user executes the internal DB management tool 240 in the method of enhancing database access and authority management through the internal DB management tool 240 according to the present invention, the superuser PKC 242 is checked and The database information (DB NAME) input login screen is displayed. In this state, the super user selects the digital signature certificate (PKC) and inputs the password to generate the electronic signature information, and accesses the desired information DB 230 again. The database information (DB NAME) can be input (S50), and the electronic signature information and the database information (DB NAME) generated in this way are transferred to the security layer 220 (S52) to request identification and authorization. Thereafter, the authentication processing unit 222 of the security layer 220 transfers the superuser PKC 242 to the identification system 300 and requests the identification thereof (S54). Next, the identification system 300 receives the request, checks the superuser PKC 242 in the directory system 310 to confirm the identity of the superuser, and inquires the OCSP server 320 again to confirm its validity. After confirmation (S56), the superuser identification and the superuser PKC validation result are transmitted to the security layer 220 (S58). As such, after confirming the identity of the super user, the security layer 220 delivers the super user PKC 242 and database information (DB NAME) to the authorization system 400 through the authorization unit 224. Check request (S60) whether there is an access authority to the access requesting information DB (230).

Next, the authorization check system 400 receiving such a request checks the AC of the superuser in the directory system 310 to confirm whether the superuser has permission to access the specific information DB 230 requested (S62). The result is transmitted to the security layer 220 (S64), and the security layer 220 allows or blocks communication between the internal DB management tool 240 and the information DB 230 according to the received authority inquiry result. In addition, the access to the information DB 230 is allowed or blocked (S66).

In addition, even when the superuser is permitted to access the specific information DB 230, the security layer 220, when the superuser requests a data change of the specific information DB 230 (S68), the superuser information and data. The change and the like can be stored in the history DB 232 (S70) so that it can be utilized in subsequent information audit.

In addition, the security layer including the public key infrastructure (PKI) identification function is included in a database backup program (Export, Unload, etc.) that can be executed without the security layer 220 during the operation performed by the superuser. In step 220, the identity and authority may be checked to allow or block information access.

As described above, even in the present invention, the security layer 220 controls the access to the information DB 230 through identity and authority verification, thereby preventing unauthorized access to information.

FIG. 6 is a flowchart illustrating a method for transferring a privilege through a rights management tool 130 capable of verifying an identity by a public key infrastructure (PKI) in the present invention. Digital signature certificate (PKC) is required to access database by strengthening database access and authority management. However, if a digital signature certificate is issued to a service company management personnel in charge of maintenance or a general user who has been requested to cooperate with the service, access to the information DB 230 may be freed and may cause a security problem. Therefore, the privilege transfer method generates a temporary ID and password that can be used temporarily by a person in charge of access to the information DB 230 so that the authority holder can access the information DB 230 only when a necessary matter occurs. This is a way to transfer authority. As shown in FIG. 6, when the privilege transfer person executes the authority management tool 130 in the authority transfer method through the authority management tool 130 according to the present invention, the authority transfer PKC 132 confirmation screen is output. In this state, the transfer of authority selects the digital signature certificate (PKC) and then inputs the password (S80) to generate the digital signature information, and transfers the generated electronic signature information to the security layer 220 (S82) for identification. You will be asked to confirm. Thereafter, the authentication processing unit 222 of the security layer 220 transmits the PKC 132 of the privilege transfer to the identification system 300 and requests the identity and the validity verification (S84). Next, the identification system 300 receives such a request, checks the PKC 132 of the privilege transfer in the directory system 310 to confirm the identity of the privilege transfer, and inquires again to the OCSP server 320. After checking the validity (S86), the authority transfer identity verification and the privilege transfer PKC validation result are transmitted to the security layer 220 (S88). After confirming the identity of the privilege transfer as described above, the security layer 220 passes the privilege transfer PKC 132 to the authority verification system 400 through the authority authorization unit 224 and has the information DB ( 230) Request for confirmation of access authority (S90).

Next, the authorization confirmation system 400 receiving such a request checks the access authority AC in the directory system to check the access authority of the information DB 230 having the privilege transfer (S92), and then secures the result. Transfer to the layer 220 (S94), and transmits the database information (DB NAME) accessible to the authority transfer to the rights management tool 130 through the DB communication module. The privilege transfer selects the target database information (DB NAME) to which the authority is to be transferred among the output database information (DB NAME) and then inputs the authority delegate information such as authority holder information and working hours (S96). Next, the input information is transmitted to the authority verification system 400 to request the generation of a temporary ID and password (S98).

Next, in response to such a request, the authorization confirmation system 400 generates a temporary ID and password (S100) and delivers it to the authorization management tool 130 through the security layer 220 (S102). Notify the authorized person of the temporary ID and password.

In addition, by storing the privilege transfer information, the temporary ID, the password generated in the history DB (232) (S104) can be utilized in the later information audit. As such, the present invention provides temporary ID and password generation functions when requesting business cooperation to a service company management agent or a general user who does not have access to a specific information DB 230, without having to issue an electronic signature certificate. You can make DB accessible.

FIG. 7 illustrates the authority holder using the temporary ID and password generated by the authority transfer method through the authority management tool 130 capable of verifying the identity by the public key infrastructure (PKI) in the specific information DB 230. This is a flowchart to explain how you can access it As shown in FIG. 7, when the authority holder according to the present invention executes the external DB management tool 120 to access a specific information DB using a temporary ID and password, a login screen is output. When the person in charge enters the temporary ID and password received from the authority transfer (S110), the external DB management tool 120 checks this and reads the information input by the person in charge of authority, and delivers it to the security layer 220 (S112). To request permission confirmation (S114). Thereafter, the authentication processing unit 222 of the security layer 220 transmits the information input by the authority holder to the authority verification system 400 through the authority authorization unit 224, and the authority holder has access to the information DB 230. Request confirmation (S114).

Next, the authorization check system 400 receives the request, checks whether the authority holder has the right to access the specific information DB 230 (S116), and then transfers the result to the security layer 220 (S118). The security layer 220 allows or blocks communication between the DB communication module 210 and the external DB management tool 120 according to the received authority inquiry result, that is, permits or blocks access to the corresponding information DB 230. (S120).

On the other hand, when the authority holder whose authority has been verified requests a data change request of a specific information DB (S122), the authority holder information and data changes are stored in the history DB 232 (S124) so that the information can be utilized in subsequent information audit. can do. As such, in the present invention, although there is no access to the specific information DB (230), the authority management tool 130 is possible to verify the identity when a necessary matter arises and temporarily asks the service coordinator or general user for business cooperation By creating a temporary ID and password through the transfer of authority through), you can prevent access to illegal information by allowing access to a specific information DB.

The database access and rights management strengthening method of the present invention is not limited to the above, and various modifications can be made without departing from the spirit of the present invention.

As described above, the method for strengthening database access and authority management according to the present invention provides an identity verification method for accessing information to an internal and external hacker illegally using the public key infrastructure (PKI). You can prevent access.

In addition, even internal users such as task managers and information managers can control access to information DB by using predetermined information usage authority and information DB access pattern analysis function. Can be prevented.

In addition, it separates security-related functions from system administrators and database administrators by adding DB USER information (DB_user ID and password) and DB USER user information (DN) in the authorization system to be built internally or externally. The security of the information DB can be greatly improved, and the information audit function is enhanced by utilizing the information DB access pattern analysis function and recording and managing the information utilization status in the history information (DB) as real user information. Therefore, the security of the information DB of the preventive aspect can be greatly improved.

In addition, the information DB of the enhanced security information system (Application) ensures the safety of information because it enables separate construction of specific information (personnel, accounting, membership, technology, etc.) that requires limited management in the existing DB. Will contribute greatly.

Claims (8)

A security layer 220 is installed in a database in which various kinds of information are stored to perform identity authentication by PKI and authorization by PMI, and the DB communication module for information exchange with the DB communication module 210 in the database. A database access for managing access to various information DBs in the database by installing in the same hierarchical area as 210 and using an access method through DB_user ID and password and an access method through the security layer 220. How to strengthen rights management. Database access that manages access to various information DBs in the database by using an approach through the security layer 220 that performs identity authentication by PKI and authorization authorization by PMI in a database storing various kinds of information. How to strengthen rights management. (a) Add identity verification function of public key infrastructure (PKI) to information system (Application), external DB management tool 120 and internal DB management tool 240 that can access various information DB, and to PKI A security layer 220 for performing identity authentication and authorization processing by PMI is installed in a database, and the same layer as that of the DB communication module 210 for information exchange with the DB communication module 210 in the database. Installing in the area; (b) An identity verification system in the security layer 220 when the information system (Application), the external DB management tool 120 and the internal DB management tool 240 requests access to the information DB 230 in the database. Verifying identity and authority in association with 300 and the authorization check system 400; and (c) allowing access to the information DB only if the identity and authority are verified in step (b). 4. The method of claim 3, further comprising checking whether the user has access authority through DB_user ID and password matching before or after step (b) or simultaneously with step (b). How to strengthen database access and rights management, characterized in that. 4. The method of claim 3, further comprising generating and storing the information DB usage history in a history DB in which access rights are restricted in the database. 4. The method of claim 3, wherein when accessing the information DB by the information system after checking the identity and authority, accessing the information DB in the case of abnormal information DB access pattern by utilizing an information DB access pattern analysis function included in the authorization check system. Method for strengthening database access and authority management, comprising the step of using in advance information audit to notify the information manager immediately after blocking. According to claim 3, After the identity and authority confirmation, the person in charge of the task to create a temporary ID and password further comprises the function to temporarily transfer the authority to maintenance service personnel or general users to have a work agency system How to enhance database access and privilege management. 4. The method of claim 3, further comprising: separating DB-USER information (DB_user ID and password) and DB-USER-specific user information (DN) in the authorization system to separate security-related functions from system administrators and database administrators (DBAs). How to strengthen the database access and rights management, characterized in that further comprises.