JP7617210B2 - Personal information connection record management method and device - Google Patents

Description

The present invention relates to a technology for managing personal information connection records, and more specifically, to a method and device for managing personal information connection records that can accept and manage personal information connection reasons and control access when a web application server attempts to connect to personal information on a DB server without modifying the existing source of the web application server.

Personal information is generally defined as information that can identify a living individual through name, resident registration number, and image, etc., and includes information that cannot identify a specific individual by itself but can be easily combined with other information to identify the individual. The types of such personal information are extremely diverse, ranging from personal information such as an individual's name and resident registration number to inner secrets such as social and economic status and condition, education, health and medical care, assets, cultural activities, and political inclinations. Personal information can include not only information provided to a business by a user (customer) when subscribing or registering as a member to a business's service, but also call records, log records, purchase records, etc. generated in the course of the user's use of the service.

In accordance with the Personal Information Protection Act, companies and public institutions are required to collect evidence of the download of personal information files by internal personal information handlers, store it for two years, and manage it after receiving a justification (reason) for the use of personal information. Here, "connection records" refer to electronic records of the details of the work that personal information handlers performed by connecting to the personal information processing system, including the personal information handler's account, the date and time of connection, connection location information (terminal information such as the connected person's PC or mobile device, or the server's IP address), information on the subject of the processed information, and the work performed (collection, generation, linkage, interlocking, recording, storage, holding and processing, editing, searching, output, correction, recovery, use, provision, disclosure, destruction, etc.).

The "Personal Information Access Record Detection Device and Personal Information Access Record Detection Method" published in the Korean Intellectual Property Office's Registered Patent Gazette (B1) under Registration Number 10-1528437 (Patent Document 1) includes the steps of: confirming the first access time for an identifier that requested a login and the second access time of the most recent login closest to the first access time; extracting the first access region where the login was made and the second access region where the most recent login was made based on the network address used; first comparing the result of dividing the distance between the first and second access regions by the time interval between the first and second access times with a selected critical speed; and detecting that the identifier is related to unauthorized use if the result of the first comparison exceeds the critical speed.

In addition, the "Personal Information Connection Record Integrity Verification System and Verification Method" published under Registration No. 10-2013415 (Patent Document 2) is a system in which, for initial information exchange, an integrated management server and a connection record verification value storage server share each other's public keys and generate and transmit a secret key required to derive a verification value. To generate the verification value, the integrated management server periodically collects all log data generated from the personal information processing system, extracts only log data corresponding to the personal information connection record from the collected log data, generates an integrated verification value that can verify the individual verification values and the individual verification values generated in one collection period with one value, and transmits the generated individual verification value and integrated verification value to the connection record verification value storage server. To verify the integrity, the integrated management server generates the individual verification value and integrated verification value by itself, compares them with the verification value transmitted from the connection record verification value storage server, and determines that there is integrity if they match.

Korean Patent No. 10-1528437 Korean Patent No. 10-2013415

Since internal personal information handlers generally handle personal information through a web application server, which is an internal business system, it is necessary to implement a method that can automatically detect when a personal information file is downloaded by connecting to the web application server and accept the reason for the access, as well as additionally control access without modifying the existing source of the web application server.

The present invention has been proposed to meet these requirements, and the problem that the present invention aims to solve is to provide a personal information connection record management method and device that can accept and manage personal information connection reasons and control access when a web application server attempts to connect to personal information on a DB server without modifying the existing source of the web application server.

An embodiment of the present invention discloses a personal information connection record management device.

The disclosed personal information access record management device includes a privacy logging agent that collects all access records for HTTP requests and responses of information users and controls HTTP response data according to accounts; a access record data receiving unit that receives and stores the personal information access records collected from the privacy logging agent; a access record standardization unit that obtains information on actual information users for web access accounts from the access record data receiving unit and creates and stores personal information access records standardized based on the six-point rule; and a connection record standardization unit that searches for personal information stored in a database (DBMS) used by a web application server and analyzes the schema, table, and column information of the corresponding personal information to be used in personal information identification and judgment processing. a personal information analysis unit that obtains personal information schema, table, and column information from the personal information search unit and obtains standardized connection records according to the six-digit rule from the connection record standardization unit to identify personal information and calculate a risk index for determining the misuse, leakage, and modification of personal information; an information user authority management unit that grants authority to control access to personal information connection for each information user to prevent leakage and misuse of personal information; and a personal information file download control unit that, when it is determined that a personal information file is to be downloaded, compares the authority set for the web connection account with the risk index to determine whether or not to permit the download action for the corresponding requested file.

The personal information connection record management device may further include a personal information connection justification processing unit that requests justification for personal information access of the corresponding account and records the input justification when the risk index is equal to or greater than a predetermined value.

The privacy logging agent operates in a plug-in manner in a web application server and compares the risk index of the personal information analysis unit for the requested personal information based on the authority and setting value of each information user, and provides a response such as automatic masking of personal information or excessive use of personal information.

The personal information analysis unit calculates a risk index based on the personal information type, the number of uses by personal information type, connection time, vacation or holiday, personal information usage authority, and unregistered IP.

Another embodiment of the present invention discloses a method for managing personal information connection records.

The disclosed method for managing personal information access records includes the steps of: setting authority for personal information access for each information user to prevent leakage and misuse of personal information; searching for personal information stored in a database (DBMS) and analyzing the schema, table, and column information of the personal information to construct a data map for use in personal information identification and judgment processing; receiving a request for personal information access or personal information file download from a web browser; collecting all access records for the information user's HTTP requests and responses; generating a personal information access record standardized based on the six principles from the collected access records; obtaining the schema, table, and column information of the personal information from the data map, obtaining the standardized personal information access record based on the six principles, identifying personal information, and calculating a risk index for determining personal information misuse, leakage, and modification; and if the calculated risk index value is equal to or greater than a predetermined value, requesting a justification and storing the input justification; if the information user's HTTP request is a personal information access request, responding with the risk index of the corresponding account, and if it is a personal information file download request, This includes a step of responding with Redirection.

According to an embodiment of the present invention, when a company or public institution is already providing a web service using a web application server and personal information stored in a database, it is possible to satisfy various guidelines required by the Personal Information Protection Act (e.g., connection log recording and explanation record management) at low cost without modifying the existing source of the web application server.

In addition, according to an embodiment of the present invention, a distinction is made between simply viewing or recording personal information and downloading a personal information file, and when downloading a personal information file, this is controlled by a separate personal information access record management and control server, thereby strengthening the protection of personal information through stricter procedures.

In accordance with an embodiment of the present invention, personal information connection logs can be recorded and managed in a standardized manner, and if the connection logs are analyzed to determine that the information is personal information, a risk index can be accurately calculated based on various factors such as the type of personal information, the number of uses per type of personal information, connection time, and authority to use personal information, and then access to personal information can be controlled in various ways according to the authority of the information user, thereby enabling efficient operation of the service.

1 is a schematic diagram illustrating the overall configuration of a personal information connection record management system according to an embodiment of the present invention; 4 is an operational flowchart of a privacy logging agent according to an embodiment of the present invention. 4 is an operational flowchart of a personal information search unit according to an embodiment of the present invention. 4 is an operational flowchart of an information user authority management unit according to an embodiment of the present invention. 11 is an operational flowchart of a connection record standardization unit according to an embodiment of the present invention. 4 is an operation flowchart of a personal information analysis unit according to an embodiment of the present invention. 4 is a flowchart illustrating a risk index calculation procedure of a personal information analysis unit according to an embodiment of the present invention. 5 is a flowchart illustrating an operation of a download control unit according to an embodiment of the present invention. 11 is a flowchart illustrating an operation of a clarification processing unit according to an embodiment of the present invention.

The present invention and the technical problems achieved by implementing the present invention will become clearer through the preferred embodiments of the present invention described below. The following embodiments are merely illustrative for explaining the present invention and are not intended to limit the scope of the present invention.

Figure 1 is a schematic diagram illustrating the overall configuration of a personal information connection record management system according to an embodiment of the present invention.

Referring to FIG. 1, in a web service system of a company or public institution including an information user terminal 10, a web application server (20; WAS), and a database system (30; DBMS) in which personal information 32 is stored, an information user such as a personal information handler can access personal information 32 in the database 30 and perform a specific task after logging in to the web application server 20 through the information user terminal 10. The information user terminal 10 is equipped with a web browser and can make an HTTP request or an HTTP file download request to the web application server 20, and the web application server 20 includes an HTTP filter 22 and a DB driver 24.

When a web browser installed on each terminal in such a web service system accesses personal information 32 in the database, the company or public institution must record and manage the personal information connection log of information users, such as personal information handlers, in accordance with the Personal Information Protection Act.

In order to meet the needs of such companies and public institutions, the personal information access record management system 100 according to an embodiment of the present invention installs a privacy logging agent 110 in a web application server 20 in a plug-in manner, receives real-time input of access records, records personal information access logs, receives input of reasons (proof) for personal information access, analyzes the personal information access patterns, and controls access to personal information according to the level of risk.

To this end, the personal information connection record management system 100 according to an embodiment of the present invention is composed of a privacy logging agent 110 installed in a plug-in manner in the web application server 20, and a data receiving unit 120, a connection record standardization unit 130, an information user authority management unit 140, a personal information search unit 150, a personal information analysis unit 160, a proof processing unit 170, a download control unit 180, and a web interface 190, which are implemented in the personal information connection record management and control server 102, as shown in FIG. 1, and the connection record manager 104 is able to connect to the connection record management and control server 102 to operate the connection record management system 100.

Returning to FIG. 1, after the web browser installed in the information user terminal 10 is executed, it connects to the web application server 20, logs in, and then requests a web URL. If the web URL request is an "HTTP Request", the web application server 20 responds with personal information authority applied and outputs a web browser screen. If the web URL request is an "HTTP file download request", the HTTP filter 22 of the web application server 20 performs "HTTP Redirection" to the connection record management and control server 102 to perform a file download with personal information authority applied so that the file can be saved.

The privacy logging agent 110 is installed in the web application server 20 in a plug-in manner and performs the role of collecting and controlling connection record data. That is, if the request received through the information user's web browser is an HTTP Request, the privacy logging agent 110 collects all connection records for the request and response, controls the HTTP Response data according to the login account, and if the request is an HTTP file download request, responds with Redirection so that the information user 10 can connect to the web interface 190 of the personal information connection record management and control server 102.

All connection records (HTTP Request + Response + Execution SQL) of the information user connecting to the web application server 20 are collected by the privacy logging agent 110 and transmitted in real time to the personal information connection record management and control server 102, which analyzes the personal information connection details of the corresponding information user, calculates a risk index, and then transmits it to the privacy logging agent 110. Accordingly, the privacy logging agent 110 provides an HTTP response result such as automatic masking of personal information or excessive use of personal information according to the authority and risk index of the corresponding information user, thereby performing authority-based control.

The web interface 190 of the personal information connection record management and control server 102 provides WAS personal information connection management and control, an external interface function (HTTP Request/Response), and a personal information file download function, and provides an administrator screen interface to the connection record manager terminal 104. That is, the web interface 190 waits for a web request, processes the administrator operation request if it is an administrator operation request, and processes the personal information file download redirection by referring to the control of the download control unit 180 if it is a personal information file download request.

The connection record data receiving unit 120 receives all information data of the personal information connection record (HTTP Request + Response) collected from the Privacy Logging Agent 110 via TCP/IP communication and stores it in a repository.

The connection record standardization unit 130 receives the connection record input from the data receiving unit 120, obtains actual information user information for the web connection account, creates a personal information connection record standardized according to the 6W1H principle, and stores it in a repository.

The information user authority management unit 140 sets and manages access control levels (authority) for personal information access for each information user on a level of 1 to 5 to prevent leakage and misuse of personal information.

The personal information search unit 150 searches in advance for personal information such as unique identification and sensitive information stored in the DBMS 30 used by the web application server 20, and constructs a data map so that the schema and table column information of the corresponding personal information can be used during the personal information identification judgment process of the risk analysis module.

The personal information analysis unit 160 obtains personal information schema, table, and column information from the personal information search unit 150, and obtains standardized connection records based on the six-point principle from the connection record standardization unit 130 to identify personal information and calculate a risk index to determine the misuse, leakage, and modification of personal information.

If the risk index is equal to or greater than a predetermined value, the explanation processing unit 170 requests explanation for the account's access to personal information and records and manages the input explanation.

If the download control unit 180 determines that the request is for downloading a personal information file, it compares the access control level and risk index of the web connection account to determine whether or not to permit the download of the requested file.

Figure 2 is a flowchart showing the operation of a privacy logging agent according to an embodiment of the present invention.

Referring to FIG. 2, when the privacy logging agent 110 is installed in the web application server 20, it operates in a plug-in manner and sets up an HTTP request filter and an HTTP response filter (S101 to S103). Then, it sets up a DBMS driver interceptor (S104).

The login ID extraction method is also set, authority information for each connection account is obtained from the information user authority management unit 140 to generate a data map, and schema, table, and column information is obtained from the personal information database from the personal information search unit 150 (S105 to S107).

Then wait for receiving the HTTP request.

When an HTTP request is received, the HTTP session information is extracted and stored in the session information data map (S108).

If the HTTP Session is a login page, the connection ID is extracted from the login ID object and then SQL execution is monitored; if it is not a login page, SQL execution is monitored immediately (S109, S110). HTTP collected information included in the HTTP Session includes the URL address, client ID, cookies, connection time, request parameters, etc.

After that, when SQL execution is detected, the SQL execution query is collected and the SQL Return ROW is collected (S111 to S113).

After collecting SQL data to determine whether SQL execution occurred, the HTTP Response Interceptor is referenced, and if a file is being downloaded, a download cookie is issued with the file ID (ID) and login ID (ID), and the "HTTP Request + Response + Download Cookie" is transmitted to the connection record management and control server 102 (S114 to S117).

Then, the download cookie is added to the response and the process is changed to HTTP Response Redirection, and the connection record management and control server 102 is connected to in response to HTTP Response Redirection, and the web application server 20 waits again to receive an HTTP Request (S118, S119).

If it is not a file download, the HTTP Request+Response information is stored and transmitted to the connection record management and control server 102, and personal information is detected from the HTTP Response data (S120, S121).

If personal information is detected, the personal information analysis unit 160 analyzes the personal information to calculate a risk index, and performs controls such as disconnection and masking of personal information based on the risk index value, masks the HTTP response or changes the response to a control response, then transmits the HTTP response to the web browser and waits for the HTTP request to be received again (S122 to S126).

If no personal information is detected, an HTTP Response is immediately sent to the web browser and the device waits again to receive an HTTP Request (S122, S126).

As such, in an embodiment of the present invention, when an information user attempts to download a personal information file, the connection record management and control server 102, rather than the web application server 20, manages the download of the personal information file through redirection, thereby enabling more strict management of the personal information file.

Figure 3 is a flowchart showing the operation of the personal information search unit in an embodiment of the present invention.

Referring to FIG. 3, the personal information search unit 150 obtains personal information search policies such as database connection information, number of samplings, personal information identification formula, and personal information confirmation frequency from the repository, and then connects to the database 30 to collect database meta information such as schema, tables, columns, views, procedures, functions, etc. (S201 to S203).

Then, a sampling number of items is obtained from the search target data DB, and the personal information type is determined using the personal information identification regular expression (S204, S205).

If the information is subsequently identified as personal information, the identification information is checked through checksum calculations of resident ID numbers, account numbers, credit cards, etc., and the occurrence frequency of the corresponding column compared to the number of personal information samples is calculated as a percentage (100%) (S206-S208).

If the calculation result shows that the current calculation frequency is equal to or greater than the determination frequency, the identified personal information schema, table, column and personal information data are stored in the repository, and a sampling is obtained from the search target data DB, and the above process is repeated (S209, S210).

In this way, the personal information search unit 150 checks identification information such as resident ID number, account number, credit card number, etc. through checksum calculation according to the personal information search policy, calculates the occurrence frequency of the corresponding column in comparison with the number of personal information samples as a percentage (100%), and if the calculated value is equal to or greater than a predetermined frequency value, it determines it to be personal information, extracts and stores the personal information data.

Figure 4 is a flowchart showing the operation of the information user authority management unit in an embodiment of the present invention.

Referring to FIG. 4, the information user authority management unit 140 obtains a web connection account and authority information from a repository and waits for an event (S301, S302).

If a rights information change event occurs, rights information synchronization is performed, the changed rights information is transmitted to the privacy logging agent 110 for synchronization, and then the event is waited for again (S303 to S305).

When an authority change operation event by an administrator occurs, the authority newly registered, modified, or deleted by the administrator's operation is stored in the repository, an authority information change event is generated to execute authority information synchronization, and then the system waits for the event again (S306 to S308).

In this way, the administrator can register, modify, or delete the personal information usage rights of the information user, and the changed rights information is synchronized with the privacy logging agent 110 through a synchronization procedure.

Figure 5 is a flowchart showing the operation of the connection record standardization unit in an embodiment of the present invention.

Referring to FIG. 5, the connection record standardization unit 130 obtains the connection record source data from the connection record data receiving unit 120, extracts the login ID (Who), extracts the HTTP request time (When), and grasps system information (Where) such as the connection IP and server IP (S401 to S404).

Next, the system extracts personal information from the HTTP response (What), and uses the JDBC driver to understand SQL text actions (How) such as save, change, and delete to generate a connection record based on the 5W1H principle, and then saves it as a file in JSON format (S405-S408).

Figure 6 is a flowchart showing the operation of the personal information analysis unit according to an embodiment of the present invention.

Referring to FIG. 6, the personal information analysis unit 160 obtains a personal information identification regular expression, and obtains personal information schema, table, and column information from the personal information search unit 150 (S501, S502). In addition, it obtains a connection record in JSON format based on the six-digit principle from the connection record standardization unit 130 and reads the connection record data to be analyzed (S503).

Then, the SQL statement in the connection record to be analyzed is analyzed to extract the schema, table, and column information, and it is determined whether it is a personal information schema, table, or column (S505 to S506).

If it is not a personal information schema, table, or column, the personal information regular expression is executed to determine whether or not there is personal information. If personal information is detected or it is a personal information schema, table, or column, the risk index calculation procedure of FIG. 7 is performed to process the personal information confirmation (S507, S512, S513). The risk index calculation procedure generates the total number of uses by personal information type, risk index conversion, and a justification event.

After that, the unstructured data is extracted from the HTTP response, the data is generated by removing HTML tags, pure text data is extracted, and the personal information regular expression is executed on the pure text data (S508 to S511).

When personal information is detected through the execution of the regular expression, the risk index calculation procedure of FIG. 7 is executed again for personal information confirmation processing, and then the process returns to reading the connection record data to be analyzed (S514, S515).

Figure 7 is a flowchart illustrating the risk index calculation procedure of the personal information analysis unit in an embodiment of the present invention.

First, in an embodiment of the present invention, the method for controlling access to personal information based on risk level is as shown in Table 1 below.

In the embodiment of the present invention, the risk index can be classified according to the period as shown in Table 2 below.

In an embodiment of the present invention, risk index calculation factors include personal information type risk level, number of uses by personal information type, access time, vacation or holiday, personal information use authority, unregistered IP, and the like.

In addition, to control personal information users through the risk index value, the personal information authority risk index (PRIVACY_RULE_RISK_V) is defined as shown in Table 3 below.

The personal information authority risk index (PRIVACY_RULE_RISK_V) is a level value corresponding to the risk index of an information user.

The time-specific risk index weighting (TIME_RISK_V) is defined as shown in Table 4 below, and weighting is applied to access outside working hours or on holidays/vacations by information user or department to reflect it in the risk index.

In addition, a risk level (PRIVACY_RISK_V) and a weight value are defined for each personal information type as shown in Table 5 below, and are reflected when calculating a risk index.

In addition, the risk weight value (PRIVACY_ACTION_V) for personal information data inquiry/change/deletion is defined as shown in Table 6 below, and a risk weight value is assigned according to personal information SQL DML (insert, update, delete) and DROP of the information user or department unit, and reflected in the risk index.

Using such weight definition, the total risk weight (RISK_V_TOTAL) can be calculated by the time-based risk index weight (TIME_RISK_V) + the risk level by personal information type (PRIVACY_RISK_V) + the personal information data inquiry/change/deletion (PRIVACY_ACTION_V).

Referring to FIG. 7, the risk index calculation module of the personal information analysis unit 160 receives a risk index calculation input value in the form of connection record data including information such as connection time, personal information type, number of uses, logged-in user, and data action (query, deletion, change, execution SQL, etc.) (S601).

Next, the connection count risk index (WAS_CONNECT_RISK_V; WCRV) is calculated using the following equation 1 (S602).

First, in this embodiment of the present invention, the connection count risk index stage is defined as shown in Table 7 below.

In Equation 1, the connection count risk index (WAS_CONNECT_RISK_V; 100 points or less) can be calculated by ((total number of personal information uses/maximum number of risk grades)+RISK_V_TOTAL)*personal information authority level risk index.

For example, if the condition is a level 1 personal information authority user and the total number of connection records is 250, it can be calculated as WAS_CONNECT_RISK_V(16) = ((250/300) + RISK_V_TOTAL) * 20 (personal information level 1 alert risk index value). A calculation formula can be added to the above value that applies weighting values for access outside of business hours, holidays, and multiple IP users.

In addition, if the risk value of the condition is greater than severe, it will be classified as a "Connection record with the highest risk of abnormal signs" and given five stars, and will be considered as a primary management target.

On the other hand, the connection risk index classification (WAS CONNECTION RISK VALUE; WCRV) is defined as shown in Table 8 below.

Next, a personal information overlook risk index (PRIVACY_OVERLOOK_V; POV) is calculated as shown in Equation 2 below (S603).

First, the personal information overlookup stage (PRIVACY_OVERLOOK_V) is defined as shown in Table 9 below.

According to Equation 2, the personal information overlook risk index (PRIVACY_OVERLOOK_V) (100 points or less) can be calculated by (total number of personal information uses/maximum number of risk grades*RISK_V_TOTAL)*personal information authority level risk index.

For example, if the condition is a level 1 personal information authority user and the number of personal information uses is 400, the personal information excessive inquiry risk index value (PRIVACY_OVERLOOK_V;12) = ((400/500) + RISK_V_TOTAL) * 15 (personal information level 1 caution risk index value) can be calculated based on the PRIVACY_RULE_RISK_V, where the personal information excessive inquiry risk index value (PRIVACY_OVERLOOK_V) = ((number of excessive inquiries/number of level category definitions) + RISK_V_TOTAL) * PRIVACY_RULE_RISK_V. A calculation formula can be added to the above value to assign weighting values for access outside business hours, holidays, and multiple IP users.

In addition, if the risk level of a condition is greater than the severe level (20), it will be classified as a "highest risk connection record with abnormal signs" and given five stars, and will be considered a primary management target.

Meanwhile, the risk index classification for excessive personal information inquiries can be defined as shown in Table 10 below.

Next, a personal information change risk index (PRIVACY_CHANGE_V; PCV) is calculated as shown in Equation 3 (S604).

First, the personal information change risk index (PRIVACY_CHANGE_V) is defined as shown in Table 11 below.

According to Equation 3, the personal information change risk index (PRIVACY_CHANGE_V) (100 points or less) can be calculated as ((total number of personal information uses/maximum number of risk grades)+RISK_V_TOTAL)*personal information authority level risk index.

For example, if the condition is that the user has one level of personal information authority and the number of personal information uses is 400, the personal information change risk index (PRIVACY_CHANGE_V;12) = ((400/500) + RISK_V_TOTAL) * 15 (personal information one level caution risk index value) can be calculated using Equation 3.

A calculation formula can be added to the above values that adds weighting for access outside of business hours, holidays, and multiple IP users.

In addition, if the risk value of the condition is greater than the severe level (20), it will be classified as a "highest risk connection record with abnormal signs" and given five stars, and will be considered as a primary management target.

Meanwhile, the personal information data change risk index (PCV) classification can be defined as shown in Table 12 below.

Next, the information user risk value (URV) is calculated according to the formula in Table 13 (S605).

In an embodiment of the present invention, the information user risk index calculation classification is defined as shown in Table 13 below.

In Table 13, MV is a reduction value of the access count ratio, and is recognized as only 33.3% by dividing by 3. The information user risk index can be applied to all personal information processing systems such as databases and web servers.

Next, if the calculated risk index is determined to be an abnormal sign, an alarm is generated and an alarm email is sent to the information user and administrator (S606).

Then, the calculated risk index value is stored in the repository (S607).

Figure 8 is a flowchart showing the operation of the download control unit according to an embodiment of the present invention.

Referring to FIG. 8, when a request for storing and analyzing an HTTP download file is received, the download control unit 180 extracts the file ID and login ID from the HTTP cookie and stores the original file (S701 to S703).

Next, the file type such as Office, Hwp, PDF, image, etc. is extracted, text is extracted from the file, and personal information is detected based on the personal information analysis unit 160, and the personal information detection result and HTTP cookie are saved (S704 to S707). The HTTP cookie includes the File ID, Login ID, Filename, etc., and the personal information detection result includes the total number of uses by personal information type, risk index conversion, etc.

If the request is for an HTTP file download, the File ID and Login ID are extracted from the HTTP cookie to search for the requested file (S708-S710). The personal information risk index and number of uses are obtained from the repository, and personal information usage authority information is obtained. If the personal information risk index is greater than the permitted authority, a download request failure is sent in the HTTP response, and if the personal information risk index is less than the permitted authority, the file download is accepted and the file is transmitted (S711-S715).

Figure 9 is a flowchart showing the operation of the clarification processing unit according to an embodiment of the present invention.

Referring to FIG. 9, when a "proof event" occurs from the personal information analysis unit 160, the proof processing unit 170 extracts the personal information risk index and user information from the repository, obtains information user authority information, and issues a connection record proof ID if the personal information risk index is greater than the permitted authority, issues a connection record proof including the connection record according to the six-point rule, the current status of personal information use, and the proof ID, and then sends a proof email (S801-S807).

When a "proof processing completion event" occurs from the web browser, a web screen is opened through the personal information proof URL of the relevant information user, and a screen for outputting personal information usage details and inputting proof is provided (S808-S810). Subsequently, the proof contents input (entered) through the input screen are stored in the repository (S811).

The present invention has been described above with reference to one embodiment shown in the drawings, but a person having ordinary skill in the art will appreciate that various modifications and equivalent alternative embodiments are possible.

10: Information User 20: Web Application Server (WAS)
30: Database (DBMS)
32: Personal information 100: Personal information access record management system 102: Personal information access record management and control server 104: Access record manager 110: Privacy logging agent 120: Data receiving unit 130: Access record standardization unit 140: Information user authority management unit 150: Personal information search unit 160: Personal information analysis unit 170: Clarification processing unit 180: Download control unit 190: Web interface

Claims (5)

a privacy logging agent for collecting all connection records for HTTP requests and responses of information users and controlling HTTP response data according to accounts;
a connection record data receiving unit for receiving and storing the personal information connection record collected from the privacy logging agent;
a connection record standardization unit for acquiring information of actual information users of the web connection account from the connection record data receiving unit, and generating and storing a personal information connection record standardized based on the six-point rule;
a personal information search unit for searching for personal information stored in a database (DBMS) used by the web application server, analyzing the schema, table, and column information of the personal information, and constructing a data map for use in a personal information identification and judgment process;
a personal information analysis unit for acquiring personal information schema, table, and column information from the personal information search unit, acquiring personal information access records standardized according to the six-point rule from the access record standardization unit, identifying personal information, and calculating a risk index for determining the misuse, abuse, leakage, and modification of personal information based on personal information type, number of uses by personal information type, access time, vacation or holiday, personal information use authority, and unregistered IP;
An information user authority management department that grants authority to control access to personal information for each information user in order to prevent leakage and misuse of personal information;
and a personal information file download control unit which, when it is determined that a personal information file is to be downloaded, compares the authority set in the web connection account with the risk index to determine whether or not to permit the download action of the personal information file . The personal information connection record management device includes:
2. The personal information access record management device of claim 1, further comprising a personal information access justification processing unit that requests justification for the information user 's access to personal information when the risk index is equal to or greater than a predetermined value and records the input justification. The privacy logging agent includes:
The personal information access record management device according to claim 1 or 2, characterized in that while operating in a plug-in manner in a web application server, the personal information analysis unit compares the risk index of the personal information of the HTTP request based on the authority and setting value of each information user, and provides a response of automatic masking of personal information or excessive use of personal information. setting the authority for personal information access for each information user in order to prevent leakage and misuse of personal information;
searching for personal information stored in a database (DBMS) and analyzing the schema, table, and column information of the personal information to construct a data map for use in a personal information identification and judgment process;
receiving a request for accessing personal information or downloading a personal information file from a web browser;
collecting all connection records for HTTP requests and responses of information users;
generating a standardized personal information access record based on six principles from the collected access records;
obtaining personal information schema, table, and column information from the data map, obtaining personal information access records standardized according to the six-point rule to identify personal information, and calculating a risk index for determining personal information misuse, leakage, and modification based on personal information type, number of uses by personal information type, access time, vacation or holiday, personal information use authority, and unregistered IP ;
requesting a justification if the calculated risk index value is equal to or greater than a predetermined value and storing the justification;
responding according to the risk index if the HTTP request of the information user is a personal information access request, and judging whether to allow the personal information file to be downloaded according to the risk index if the HTTP request is a personal information file download request. The step of constructing the data map comprises:
The method for managing personal information connection records according to claim 4, characterized in that a personal information search policy including database connection information, the number of samplings, a personal information identification regular expression, and a personal information confirmation frequency is obtained, a schema, a table, a column, a view, a procedure, a function and database meta information are collected by connecting to the database, and then the personal information type is determined by utilizing the personal information identification regular expression.