JP2012242872A - Log management system for software and control method thereof, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a log management system for preventing information specific to a user environment from being mixed in a log without losing information of a software operation log.
In a log management system, whether or not user data can be output to a log is determined based on a log output setting. If the output is impossible, a user data value is converted into a predetermined ID and a log is output. The association between user data and ID is managed separately from a normal log as a user data log.
[Selection] Figure 1

Description

  The present invention relates to a log management system showing a software operation history, a control method therefor, and a program.

  In recent years, as problems such as unauthorized access and information leakage increase, software log recording has become more important. There are various types of logs, such as those that record the operation history of software, those that show the user's access history to the system, and those that show the user's operation history. In these logs, it is necessary to record the user name and file name so that the user who executed the operation and the file that was the target of the operation can be identified. Therefore, the person who can view the log may be limited. For this reason, there is a risk of troublesome investigation in troubleshooting and forensic work based on logs.

  For example, even if the system developer requests provision of a log when a failure occurs in the system, there is a possibility that the user refuses to provide the log because confidential information is included in the log. In this case, it is necessary to mask the confidential information of the log at the user's site, but there are problems that it takes time and information necessary for the investigation is lost due to the masking process.

  On the other hand, a technique has been proposed in which a log is processed by specifying a user's desired log format, and the contents to be output to the log are manipulated (see Patent Document 1).

JP 2006-99442 A

  In the secondary log file creation method, information that is determined to be confidential can be prevented from being output, but the information is deleted thereby, which may hinder log analysis. In addition, since the log is subject to secondary modification, there is a risk that an error may occur in which the contents of the log are accidentally rewritten.

  The present invention has been made in view of the above problems, and converts confidential information in a log into a predetermined ID and manages the confidential information separately, thereby avoiding leakage of confidential information without loss of log information. It is an object to provide a log management system, a control method thereof, a program, and a program.

A log management system that outputs an operation history as a log according to the operation of the software,
Log output request receiving means (102) for receiving a log output request from software, log output setting means (109) for managing log output setting information,
Log output determination means (103) for determining whether user data to be output to the log is a replacement target according to the contents of the log output setting;
Log output means (104) for assigning a predetermined ID to a user data value to be replaced and outputting a log when the log output determination means determines that the replacement is necessary;
User data management means (105) for outputting the user data to be replaced and the ID assigned thereto as user data separately from the log output means;
Have
The log output request receiving means (102) returns a log output completion notification to software after completion of log output.

  According to the present invention, confidential information included in a log is converted into a predetermined ID, and the confidential information is managed separately, thereby preventing user data from being mixed into the operation log without missing log information.

  Further, according to the present invention, since log secondary modification is not involved, it is possible to easily guarantee log originality.

It is a block diagram which shows the structure of the log management system which concerns on 1st Embodiment. It is a block diagram which shows the structure of the hardware which the log management system of FIG. 1 operate | moves. It is an example of the log output format which software has internally. 4 is an example of information input to the log output module 101 by software. 4 is a flowchart showing log output processing in a log output module 101. 6 is a diagram illustrating an example of an operation screen of a log output setting unit 109. FIG. It is an example of the operation log when the user data is not concealed. It is an example of the operation log when the user data is concealed. It is an example of the user data log 107 corresponding to the operation log 106 of FIG. 4 is a flowchart showing log output processing in a log output module 101. It is an example of the operation log when the user data is concealed. It is an example of the user data log 107 corresponding to the operation log 106 of FIG.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram showing the configuration of a software log management system according to the first embodiment of the present invention. The log output module 101 includes a log output request receiving unit 102, a log output determining unit 103, a log output unit 104, and a user data management unit 105. The log output module 101 receives a log output request from software, creates a log based on the log output setting, and outputs an operation log 106 and a user data log 107. Here, the operation log includes all logs related to software operations such as a so-called operation log indicating a user operation history and a so-called authentication log indicating a user authentication history.

  The log output request receiving unit 102 receives a log output request from software. The log output request needs to be input to the log output module 101 in a predetermined format that can be interpreted by the log output module.

  The log output determination unit 103 determines the output method of the log received by the log output request reception unit 102 based on the setting contents of the log output setting 108. Specifically, user data that is permitted to be output in the log output setting 108 is directly output as the operation log 106 via the log output unit 104. On the other hand, for user data whose output is prohibited by the log output setting 108, the corresponding user data is replaced with an appropriate ID (predetermined ID), and the operation log 106 is output. The appropriate ID is acquired by the log output determination unit 103 inquiring of the user data management unit 105. The user data replaced with the ID is output as the user data log 107 via the user data management unit 105. Note that user data refers to data specific to the user environment, such as a user name and an IP address.

  The log output unit 104 receives an operation log to be output from the log output determination unit 103 and outputs an operation log 106. The operation log is output in a state in which the value of user data prohibited from being output by the log output setting 108 is not included.

  The user data management unit 105 issues an appropriate ID for the value of user data determined to be output prohibited from the log output determination unit 103. An ID that does not overlap with other user data values is used. The issued ID and the user data assigned with the ID are output to the user data log 107 in association with each other.

  The log output setting unit 109 provides an interface for editing the log output setting 108 to the user. The log output setting unit 109 operates as a Web application, for example, and the user accesses the log output setting screen using a browser and edits the log output setting 108.

  The log output module 101 may be built by being built in software to output a log, and may be operated as a part of the software, or may be operated separately from the software, and a log output request may be issued from the software by a general-purpose protocol. You may comprise so that it may receive.

  Further, the operation log 106 and the user data log 107 may have any storage format as long as the log can be recorded. For example, the operation log 106 and the user data log 107 may be stored in a file format on a file system or stored in a database. May be.

  FIG. 2 is a block diagram showing a hardware configuration of an information processing apparatus (server and PC) on which the log management system of FIG. 1 operates.

  In FIG. 2, a CPU 201 is a processing device that performs calculations for various data processing related to log output and controls each component connected to the bus 208. The ROM 202 is a data read-only memory and stores a basic control program. A RAM 203 is a memory for reading and writing data, and is used for various arithmetic processes of the CPU 201 and temporary storage of data. The external storage device 204 is used as a system program of an operating system (OS) of the information processing apparatus, a log management system program, and a temporary storage area during data processing. The external storage device 204 is slower in data input / output than the RAM 203, but can hold a large amount of data. The external storage device 204 is mainly composed of a magnetic storage device (HDD), but may be a device that loads and records data by loading an external medium such as a CD, DVD, or memory card. The input device 205 is a device for inputting characters and data to the information processing device, and corresponds to various keyboards and mice. The display device 206 is a device for displaying the processing result of the information processing device, and corresponds to a CRT or a liquid crystal monitor. The communication device 207 is used when connecting to a LAN to perform data communication by TCP / IP and to communicate with other information processing devices.

  FIG. 3 is an example of a log output format that the software has internally. The software outputs logs appropriately during operation. FIG. 3 is an example of a log output when the software receives a request from a user. The two fields, DateTime and RequestID, enclosed in inequality signs, are set to specific values by the software when they are input to the log output request receiving unit 102. DateTime represents the system time, and RequestID is an ID that the software issues uniquely for each request in order to identify a request from the user. Two fields, UserName and IPAddress, enclosed in braces are fields that handle user data values, not software-specific values such as the above-mentioned DateTime and RequestID. Therefore, the log output determination unit 103 determines whether or not to output the UserName and IPAddress values to the operation log 106.

  FIG. 4 is an example of information input to the log output module 101 by software. Information input to the log output module 101 by the software is composed of a combination of log contents and specific values that enter a field for handling user data included in the log contents. In the example of FIG. 4, the first character string enclosed in double quotations is the log contents, and the second and third character strings enclosed in double quotations are fields for handling user data included in the log contents. It is a specific value that falls into. In the log contents of FIG. 4, the specific values of DateTime and RequestID in the example of FIG. 3 are already set by software. On the other hand, UserName and IPAddress that handle user data values have not yet been set to specific values. Specific values corresponding to UserName and IPAddress are specified as “Sato” and “192.168.0.5” following the contents of the log.

  FIG. 5 is a flowchart showing a flow of log output processing in the log output module 101. In this specification, the PC and server on which the log output module 101 operates includes a CPU, a RAM, a ROM, an HDD, and the like. Note that the procedure shown in the flowchart is stored in one of RAM, ROM, and HDD, and is executed by the CPU.

  In step S501, the log output determination unit 103 determines whether the type of user data included in the output log is a concealment target. Whether or not the type of user data is a concealment target is determined based on a preset log output setting 108.

  If the type of user data to be output is a concealment target, the log output determination unit 103 acquires an ID corresponding to the user data value from the user data management unit 105 in step S502. Specifically, the log output determination unit 103 transmits the type and value of the user data to be concealed to the user data management unit 105, and the user data management unit 105 issues a unique ID for the user data value. To the log output determination unit 103. The user data management unit 105 manages user data values and issued IDs as the user data log 107.

  In step S503, the log output determination unit 103 replaces user data included in the log with the ID acquired in step S502.

  In step S504, the log output determination unit 103 requests the log output unit 104 to output a log. The log output unit 104 outputs the character string received from the log output determination unit 103 to a file or the like as the operation log 106.

If the type of user data to be output is not a concealment target in step S501, the log output determination unit 103 outputs the log output to the log output unit 104 as it is in step S504 without replacing the log contents. Request. The log output unit 104 outputs the character string received from the log output determination unit 103 to a file or the like as the operation log 106. FIG. 6 is a diagram illustrating an example of an operation screen of the log output setting unit 109. The user selects whether to output user data to a log. Types of user data include an IP address, a MAC address, a user name, a host name, and a file name. The contents set by the user using the log output setting unit 109 are stored as the log output setting 108. The user data set to be concealed here is converted into an appropriate ID by the log output determination unit 103 and output to the operation log 106. The association between user data and ID is managed in the user data log 107. If the log output setting unit 109 is set so that all user data is not concealed, the user data log 107 is not created because all user data is output to the operation log 106.

  FIG. 7 is an example of the operation log 106 when user data is not concealed. Since the user data is not concealed, for example, the user name (Sato) and the IP address (192.168.0.5) are output on the first line in FIG.

  FIG. 8 is an example of the operation log 106 when user data is concealed. Here, it is assumed that the user name and the IP address are concealed. The basic contents are the same as in the example of FIG. 7, but in the first line of FIG. 8, for example, the user name is replaced with the ID [User_00000001] and the IP address is replaced with the ID [IP_00000001]. Yes. As described above, by setting the user data as a concealment target, a specific value of the user data is not output to the operation log 106. The actual user data value is associated with the ID and managed in the user data log 107.

  FIG. 9 is an example of the user data log 107 corresponding to the operation log 106 of FIG. The user data management unit 105 issues an ID for the value of the user data received from the log output determination unit 103 and appends it to the user data log 107. In the example of FIG. 9, [User_00000001] that is the ID output in the operation log of FIG. 8 is managed in association with the actual value “Sato”. Similarly, the specific value of the ID [IP_00000001] is “192.168.0.5”.

  According to the first embodiment, the confidential information in the log is converted into an appropriate ID, and the confidential information is managed separately, thereby preventing user data from being mixed into the operation log without missing log information. Can do.

[Second Embodiment]
In the second embodiment of the present invention, the configuration shown in FIGS. 1 to 4 and FIGS. 6 to 7 is the same as that of the first embodiment, and the same parts as those of the first embodiment are described. The description will be omitted using the same reference numerals. Only differences from the first embodiment will be described below.

  FIG. 10 is a flowchart showing a flow of log output processing in the log output module 101. Steps S501 to S504 in FIG. 10 are the same steps as those shown in FIG.

  In step S <b> 1001, the user data management unit 105 confirms whether or not the user data value determined to be concealed in step S <b> 501 exists in the user data log 107. When the value of user data to be concealed exists in the user data log 107, an ID is already assigned to the value of the user data.

  If the user data value exists in the user data log 107 in step S1001, the user data management unit 105 acquires an ID corresponding to the value of the user data to be concealed from the user data log 107 in step S1002, and determines log output. Return to section 103.

  If the user data value does not exist in the user data log 107 in step S1001, the user data management unit 105 issues a unique ID for the user data value in step S502, as in the first embodiment. And returns to the log output determination unit 103. The user data management unit 105 manages user data values and issued IDs as the user data log 107.

  FIG. 11 is an example of the operation log 106 when user data is concealed with respect to the contents of the operation log of FIG. The difference from FIG. 8 is the DocName ID on the sixth line. In FIG. 8, the ID of DocName on the sixth line is [DocName_00000002], whereas in FIG. 11, the ID is [DocName_00000001]. In the second embodiment, for user data of the same type and the same value, the user data management unit 105 acquires the same ID and returns it to the log output determination unit 103. In the example of FIG. 7, the values of the file name (DocName) are the same in the logs on the second and sixth lines. Therefore, in FIG. 11, which is the result of concealing the file name, the DocName IDs in the second and sixth lines are the same.

  FIG. 12 is an example of the user data log 107 corresponding to the operation log 106 of FIG. The difference from FIG. 9 is the value of DocName ID = 00000002. In FIG. 9 as the first embodiment, the user data management unit 105 issues a new ID for the same user data value. On the other hand, in FIG. 12, which is the second embodiment, the user data management unit does not issue a new ID for a user data log that already has a value, and obtains an ID corresponding to the value of the user data. To do. As a result, as in the example of FIG. 11, user data of the same type and the same value is replaced with the same ID, and the operation log 106 is output.

  According to the second embodiment, since the same user data is replaced with the same ID and the operation log 106 is output, the user data is mixed in the operation log while maintaining a larger amount of information in the operation log. Can be prevented.

101 log output module 102 log output request receiving unit 103 log output determining unit 104 log output unit 105 user data management unit 106 operation log 107 user data log 108 log output setting 109 log output setting unit

Claims (6)

A log management system that outputs an operation history as a log according to the operation of the software,
Log output request receiving means (102) for receiving a log output request from software, log output setting means (109) for managing log output setting information,
Log output determination means (103) for determining whether user data to be output to the log is a replacement target according to the contents of the log output setting;
Log output means (104) for assigning a predetermined ID to a user data value to be replaced and outputting a log when the log output determination means determines that the replacement is necessary;
User data management means (105) for outputting the user data to be replaced and the ID assigned thereto as user data separately from the log output means;
Have
The log output request receiving means (102) returns a log output completion notification to software after completion of log output. The log management system according to claim 1, wherein the user data management means (105) uses the ID when an ID is already assigned to the user data. In the control method of the log management system that outputs the operation history as a log according to the operation of the software,
A log output request receiving step (102) for receiving a log output request from software, a log output setting step (109) for managing log output setting information,
A log output determination step (103) for determining whether user data to be output to the log is a replacement target according to the contents of the log output setting;
A log output step (104) for assigning a predetermined ID to a user data value to be replaced and outputting a log when the log output determination means determines that the replacement is necessary;
A user data management step (105) for outputting the user data to be replaced and the ID assigned thereto as user data separately from the log output means;
Have
The log output request receiving step (102) returns a log output completion notification to software after completion of log output. 4. The method of controlling a log management system according to claim 3, wherein, in the user data management step (105), when an ID is already assigned to the user data, the ID is used. In a program for causing an information processing apparatus to execute a control method of a log management system that outputs an operation history as a log according to the operation of software,
Log output request receiving means for receiving a log output request from software (102)
Log output setting means (109) for managing log output setting information;
Log output determination means (103) for determining whether user data to be output to the log is a replacement target according to the contents of the log output setting;
Log output means (104) for assigning a predetermined ID to a user data value to be replaced and outputting a log when the log output determination means determines that the replacement is necessary;
User data management means (105) for outputting the user data to be replaced and the ID assigned thereto as user data separately from the log output means,
Have
The log output request receiving means (102) is a computer-readable program for causing a computer to execute a control method of a log management system, wherein a log output completion notification is returned to software after log output is completed. 6. The method of controlling a log management system according to claim 5, wherein the user data management means (105) uses the ID when the user data has already been assigned an ID. A program that can be read by a computer.

Images