JP6753819B2 - Collation information generator, management system and collation information generation method - Google Patents

Description

The present invention relates to a collation information generation device, a management system, and a collation information generation method.

Conventionally, a digital content falsification monitoring device has been proposed that creates a standard summary value of digital content and checks the content for falsification (see, for example, Patent Document 1). This falsification monitoring device monitors not only Web contents but also falsification and shortage of file sets. In this device, the system administrator creates a snapshot of the clean environment and uses it as collation information.

In addition, as a function for the software provider to provide data for confirming the completeness of the file set that constitutes the software, there is RPM, which is a software package management function that is installed as standard in UNIX (registered trademark) operating systems (RPM). For example, see Non-Patent Documents 1 and 2). RPM is provided with a file digest and signature for each package and registered in the RPM database. Then, in RPM, the file installed in the file system can be collated with the digest value of the database.

Japanese Unexamined Patent Publication No. 2001-265217

RPM Package Manager, [online], [Search on June 3, 2017], Internet <URL: http://rpm.org/> and Internet <URL: http://fedoranews.org/alex/tutorial/rpm /14.shtml ＞ All you have to know about RPM, [online], [Search on June 3, 2017], Internet <URL: http://fedoranews.org/alex/tutorial/rpm/14.shtml>

However, the conventional technique has a problem that the burden on the administrator is heavy for file management. In addition, in the conventional technology, there are cases where it is not possible to check the excess or deficiency of files such as log files for which the digest value cannot be defined, or it is not possible to exclude directories that should not be checked for excess or deficiency from the management target. There is a problem that it can be difficult to do. Also, in the prior art, if some of the files belonging to a software package can be modified, the software provider cannot provide accurate matching information for such files, and the administrator can ensure the integrity of the files. There was a problem that it could not be confirmed.

Specifically, in the device described in Patent Document 1, it is necessary for the system operator to create and maintain snapshots in each system, which increases the burden on the system operator and the total cost of the system, and also the system. Since it often depends on the skill of the operator, it may not be possible to maintain a certain level of accuracy.

In the apparatus described in Patent Document 1, this snapshot contains a file whose data should not be confirmed. For example, log files and databases. If these are not excluded from the collation information, false positives will occur. However, in order to extract these, the administrator needs to be familiar with the operating specifications of the software, which may be difficult.

Further, in the apparatus described in Patent Document 1, the snapshot contains directories that should not be checked for excess or deficiency. For example, files that are added or deleted by the legitimate operation of the software. If these are not excluded from the collation information, false positives will occur. However, it is difficult for the administrator to be familiar with the operating specifications of the software in order to extract them. As described above, in the prior art, there is a problem that the burden on the administrator is heavy for file management and it may be difficult to accurately confirm the file to be managed.

In addition, in the functions described in Non-Patent Documents 1 and 2, when a part of the file path of the file belonging to the software package can be customized (prefix specification, wildcard specification, etc.), the software provider collates these files. The information file path cannot be specified. In addition, in the functions described in Non-Patent Documents 1 and 2, when a part of the files belonging to the software package can be deleted at the time of installation (manual file, etc.), the software provider uses these files as collation information. I can't decide whether or not to post it. Further, in the functions described in Non-Patent Documents 1 and 2, when a part of the file data belonging to the software package can be changed at the time of installation (setting file, etc.), the software provider can check the collation information of these files. The file data digest value cannot be specified. Therefore, in the prior art, if some of the files belonging to a software package could be modified, the software provider could not provide accurate matching information for such files.

The present invention has been made in view of the above, and can reduce the burden on the administrator regarding file management and can accurately confirm the file by using appropriate collation information according to the file to be managed. An object of the present invention is to provide a collation information generation device, a management system, and a collation information generation method.

In order to solve the above-mentioned problems and achieve the object, the collation information generation device according to the present invention is a collation information generation device that generates collation information used by a file management device that manages arranged files. Regarding the collation information to be collated when confirming file tampering or excess / deficiency in any file management device, the definition of a common list, which is a list of files and directories that may be described in the collation information, and individual files. In the management device, the acquisition unit that acquires at least a part of the shared common definition information indicating the definition of the element attribute, which is a condition for determining the elements of the file and directory list of the collation information, and the common acquisition unit acquired by the acquisition unit. The first indicating the combination of the file path of the file that should be arranged as the collation information and the file data does not change based on the common list of definition information and the element attribute, and the digest value of the file data. List, a second list showing the file path of the file that should be placed and the file data can change, and the file directly below is the first list or the second list that belongs to the same collation information. The first directory condition which is the file described in the above, and the directory immediately below is the second directory condition which is a directory in which one or more files described in the first list or the second list belonging to the same collation information are arranged under it. , A generator that generates collation information with a third list showing the directory paths of directories that do not place files or directories that do not meet the first or second directory condition directly under it, and that satisfy the third directory condition. And, characterized by having.

According to the present invention, it is possible to reduce the burden on the administrator regarding file management and to accurately confirm the file by using appropriate collation information according to the file to be managed.

FIG. 1 is a schematic diagram showing a schematic configuration of a management system having a file management device according to the embodiment. FIG. 2 is a schematic diagram showing a schematic configuration of the file management device shown in FIG. FIG. 3 is a diagram showing an example of a data structure of the confirmation content information shown in FIG. FIG. 4 is a diagram for explaining the contents of the list included in the collation information shown in FIG. FIG. 5 is a diagram showing an example of the collation information shown in FIG. FIG. 6 is a diagram for explaining the contents defined by the common definition information shown in FIG. FIG. 7 is a diagram illustrating element attributes defined by the common definition information shown in FIG. FIG. 8 is a diagram showing an example of the common definition information shown in FIG. FIG. 9 is a diagram for explaining the item extraction information shown in FIG. FIG. 10 is a diagram for explaining the individual definition information shown in FIG. FIG. 11 is a diagram showing an example of the individual definition information shown in FIG. FIG. 12 is a diagram for explaining the condition information shown in FIG. FIG. 13 is a diagram illustrating a process of generating collation information by the generation unit shown in FIG. FIG. 14 is a diagram illustrating the processing of the collating unit shown in FIG. FIG. 15 is a diagram illustrating the processing of the collating unit shown in FIG. FIG. 16 is a flowchart of a processing procedure of the collation information generation processing according to the embodiment. FIG. 17 is a flowchart of the processing procedure of the collation information generation process shown in FIG. FIG. 18 is a flowchart of the processing procedure of the list B1 setting process shown in FIG. FIG. 19 is a flowchart of the processing procedure of the list B2 setting process shown in FIG. FIG. 20 is a flowchart of the processing procedure of the list B3 setting process shown in FIG. FIG. 21 is a flowchart of the processing procedure of the file confirmation process according to the embodiment. FIG. 22 is a flowchart showing a processing procedure of the collation process shown in FIG. FIG. 23 is a flowchart showing a processing procedure of the confirmation process shown in FIG. FIG. 24 is a diagram showing an example of the data structure of the correspondence information shown in FIG. FIG. 25 is a diagram illustrating a process of generating collation information in the second modification of the embodiment. FIG. 26 is a diagram illustrating another example of the collation information generation process in the second modification of the embodiment. FIG. 27 is a diagram illustrating another example of the collation information generation process in the second modification of the embodiment. FIG. 28 is a schematic diagram showing another schematic configuration of the management system having the file management device according to the embodiment. FIG. 29 is a schematic diagram showing a schematic configuration of the collation information generation device shown in FIG. 28. FIG. 30 is a configuration of the file management device shown in FIG. 28. FIG. 31 is a diagram showing an example of a computer in which a file management device is realized by executing a program.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment. Further, in the description of the drawings, the same parts are indicated by the same reference numerals.

[Embodiment]
First, the outline configuration, the flow of the file confirmation process, and specific examples of the file management device according to the embodiment will be described. In the present embodiment, collation information for applying to the device is created based on the shared common definition information created in advance and the definition information of each device, and the collation information is used to falsify the file. Check for either deleting files or adding files that should not be placed in the database.

FIG. 1 is a schematic diagram showing a schematic configuration of a management system having a file management device according to the embodiment. As shown in FIG. 1, the management system according to the embodiment has a configuration in which the common definition information database (DB) 2 and a plurality of file management devices 3X to 3Z are communicably connected to each other.

The common definition information DB2 has shared common definition information G1, G2, and G3. The common definition information DB2 transmits the shared common definition information G1, G2, and G3 required by the respective file management devices 3X to 3Z to the file management devices 3X to 3Z. The shared common definition information G1, G2, and G3 are created and provided by, for example, a software provider. The storage and distribution of the shared common definition information G1, G2, and G3 are not limited to the centralized management method as shown in FIG. 1, and various existing means can be applied.

The file management devices 3X to 3Z manage a plurality of files F arranged (installed) in the file management device 3 to be managed. The file management devices 3X to 3Z are a PC (Personal Computer), a server device, or the like equipped with a general operating system. The number of file management devices 3X to 3Z shown in FIG. 1 is merely an example and is not limited to this. Further, when a plurality of file management devices 3X to 3Z will be described without particular distinction, the file management device 3 will be described.

The file set managed by the file management devices 3X to 3Z is specifically a file set that constitutes a software package. The file set includes, for example, a program file that executes a program and a setting file that defines the execution order of the program files. The file path and directory structure of these file sets are often the same regardless of the installation destination. And, the program files and the like are often the same data regardless of the installation destination. On the other hand, the data of configuration files and the like is often edited according to the installation destination.

The file management devices 3X to 3Z identify the file data of the managed file by the file path, classify the file path by the directory, and identify the directory by the directory path.

The file management devices 3X to 3Z acquire at least a part of the shared common definition information G1, G2, and G3 in the common definition information DB2. Further, the file management devices 3X to 3Z acquire the individual definition information L1x, L2x, L3x, L1y, L1z, L2z of each own device. The individual definition information L1x, L2x, L3x, L1y, L1z, and L2z provide conditions to be individually provided for the file sets to be arranged in the file management devices 3X to 3Z according to the file management devices 3X to 3Z. This is the information to be shown. Then, the file management devices 3X to 3Z are collation information R1x, R2x, R3x, R1y, R1z that satisfy both the acquired common definition information G1, G2, G3 and the individual definition information L1x, L2x, L3x, L1y, L1z, L2z. , R2z is generated.

Then, the file management devices 3X to 3Z collate the generated collation information R1x, R2x, R3x, R1y, R1z, R2z with the file to be managed. Based on the collation result, the file management devices 3X to 3Z confirm one of the confirmation items A1 to A3 of falsification of the file, deletion of the file, and addition of the file that should not be placed in the database, and confirm the confirmation result. Output.

[File management device configuration]
Next, the configuration of the file management device 3 shown in FIG. 1 will be described with reference to FIG. FIG. 2 is a schematic diagram showing a schematic configuration of the file management device 3 shown in FIG. As shown in FIG. 2, it has a storage unit 10, a communication unit 13, a control unit 14, an input unit 15, and an output unit 16.

The storage unit 10 is a storage device such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or an optical disk. The storage unit 10 may be a semiconductor memory in which data such as a RAM (Random Access Memory), a flash memory, and an NVSRAM (Non Volatile Static Random Access Memory) can be rewritten. The storage unit 10 stores an OS (Operating System) and various programs executed by the file management device 3. Further, the storage unit 10 stores various information used in executing the program. The storage unit 10 has a file storage unit 11 and a confirmation information storage unit 12.

The file storage unit 11 arranges a plurality of file sets Fs composed of a plurality of files F. As described above, the file set Fs is, for example, a set of files constituting a software package.

The confirmation information storage unit 12 stores information used by the control unit 14 (described later) for confirming the integrity of the file. The confirmation information storage unit 12 has confirmation content information 121, collation information 122, common definition information 123, item extraction information 124, individual definition information 125, condition information 126, and correspondence information 127.

First, the confirmation content information 121 will be described. FIG. 3 is a diagram showing an example of the data structure of the confirmation content information 121 shown in FIG. As shown in FIG. 3, the confirmation content information 121 is associated with confirmation items and their contents. Here, the file set to be placed is a file set in a state in which the software package has not been tampered with (due to an attack or misoperation), added, or deleted from the program or configuration file. On the other hand, the file set arranged in the file management device 3 may not maintain these states. Therefore, it becomes necessary for the file management device 3 to confirm the integrity.

In the file management device 3, confirmation items A1 to A3 shown in FIG. 3 are set as the confirmation contents of completeness. Specifically, the confirmation item A1 (first confirmation content) is that the file to be arranged in the file storage unit 11 has not been tampered with. The confirmation item A2 (second confirmation content) is that the file to be arranged in the file storage unit 11 has not been deleted. The confirmation item A3 (third confirmation content) is that files that should not be placed in the database have not been added. The file management device 3 confirms all or at least one of these confirmation items A1 to A3.

Next, the collation information 122 will be described. The collation information 122 is generated by the file management device 3 as collation information corresponding to the file set managed by the file management device 3. The collation information 122 is composed of list B1 (first list), list B2 (second list), and list B3 (third list). The lists B1 to B3 will be described with reference to FIG.

FIG. 4 is a diagram for explaining the contents of lists B1 to B3 included in the collation information 122 shown in FIG. As shown in Table 122a of FIG. 4, the list B1 shows the file path and the digest value of the file data of the file that should be arranged in the file storage unit 11 and the file data does not change. A list of combinations is shown. Here, the digest value is, for example, a hash value of file data. The hash value is a value obtained by converting the original data with a hash function such as SHA256, and since the size is small and the hash value changes when the original data changes (tampers), it is used for tampering determination.

Then, the list B2 shows a list of file paths of files that should be arranged in the file storage unit 11 and whose file data can change.

In addition, list B3 shows a list of directory paths of directories that satisfy the following directory conditions b31 to b33. In the directory condition b31 (first directory condition), the files directly under the directory condition b31 are the files described in the list B1 or the list B2 that belong to the same collation information. The condition b32 (second directory condition) is a directory in which one or more files described in the list B1 or the list B2 belonging to the same collation information are arranged under the directory directly under the directory. Condition b33 (third directory condition) is that a file or directory that does not correspond to the directory condition b31 or the directory condition b32 is not placed directly under the condition b33 (third directory condition).

FIG. 5 is a diagram showing an example of the collation information 122 shown in FIG. As shown in FIG. 5, the collation information Rxx has lists Rxx-B1 to Rxx-B3. Specifically, the list Rxx-B1 describes a combination of the file paths "file paths 11 to 13" of the files F11 to F13 and the digest values "digest values 1 to 3" of the file data. The files F11 to F13 are files that should be arranged in the file storage unit 11, and the file data does not change. Further, in the list Rxx-B2, the file paths "file paths 21 to 23" of the files F21 to 23 are described. The files 21 to F23 are files to be arranged in the file storage unit 11, and the file data can be changed. Further, in the list Rxx-B3, "directory paths 1 to 3" of directory paths satisfying the directory conditions b31 to b33 are described.

Next, the common definition information 123 will be described. The common definition information 123 is shared information acquired from the common definition information DB2. The common definition information 123 is a common list that is a list of files and directories that may be described in the collation information for collation information to be collated when confirming falsification or excess / deficiency of files in an arbitrary file management device. Define. Then, the common definition information 123 defines an element attribute which is a condition for determining an element of a list of files and directories of collation information in each file management device.

FIG. 6 is a diagram for explaining the contents defined by the common definition information 123 shown in FIG. As shown in Table 123a of FIG. 6, the definition D1 and the definition D2 are defined in the common definition information 123. That is, the content of the definition D1 is the definition of the common list J1, J2, J3, which is a list of files and directories that may be described in the list B1, B2, B3 of the collation information in any file management device. .. The content of the definition D2 is a definition of an element attribute which is a condition for determining the elements of the collation information lists B1, B2, and B3 in the individual file management device. In the collation information 122, the elements of the lists B1 to B3 are determined based on the element attributes of the definition D2 with respect to the common lists J1 to J3 of the definition D1.

Subsequently, the common definition information 123 defines a common list of files described in the collation information lists B1 and B2 of the file set and a common list of directories described in the collation information B3. Then, the common definition information 123 describes and defines the attributes E1 to E4 described below as element attributes for these files and directories. Define E1, E2, E3 for the file and E4 for the directory.

FIG. 7 is a diagram illustrating element attributes defined by the common definition information 123 shown in FIG. As shown in Table 123b of FIG. 7, E1 to E4 are defined as element attributes. First, the element attribute E1 is the first flag (T) indicating that the file described in the common list of the lists B1 and B2 of the collation information 122 is essential to be arranged in the file management device, or the first flag (T) indicating that the file is not essential. 2 Define the required flag that defines the flag (F). The element attribute E2 defines a file path condition which is a condition for creating a file path notation of the file described in the common list of lists B1 and B2 of the collation information 122. The element attribute E3 defines the digest value of the files listed in the common list of the collation information list B1 whose file data cannot be changed when the files are arranged. The element attribute E4 defines a directory path condition that is a condition for creating the directory path notation of the directory described in the common list of the collation information list B3.

A specific example of the common definition information 123 will be described. FIG. 8 is a diagram showing an example of the common definition information 123 shown in FIG. In FIG. 8, the common definition information Gx has common lists J1 to J3.

The common list J1 is a common list of files described in the list B1 of the collation information 122. In this common list J1, a file path condition (element attribute E2), a digest value (element attribute E3), and a required flag (element attribute E1) are associated with each file as element attributes H1. Specifically, in the common list J1, "file path condition 11", "digest value 11", and "essential flag 11 = T" correspond to the file "# 11". In the common list J1, the file "# 12" corresponds to the "file path condition 12", the "digest value 12", and the "essential flag 12 = F".

The common list J2 is a common list of files described in the list B2 of the collation information 122. In this common list J2, a file path condition (element attribute E2) and a required flag (element attribute E1) are associated as common attributes H2 as element attributes of each file. Specifically, in the common list J2, "file path condition 21" and "essential flag 21 = T" correspond to the file "# 21". In the common list J2, the file "# 22" corresponds to the "file path condition 22" and the "essential flag 22 = F".

The common list J3 is a common list of directories described in the list B3 of the collation information 122. In this common list J3, a directory path condition (element attribute E4) is associated as a common attribute H3 as an element attribute of each directory. Specifically, in the common list J3, the directory "# 31" corresponds to the "directory path condition 31". In the common list J3, the "directory path condition 32" corresponds to the directory "# 32".

Next, the item extraction information 124 will be described. The item extraction information 124 is information indicating the extraction items from the common definition information 123. The extracted items are contents that should be defined as individual information of the file management device 3. FIG. 9 is a diagram illustrating the item extraction information 124 shown in FIG. As shown in Table 124a of FIG. 9, the item extraction information 124 indicates the extraction content from each target of the common definition information 123, and the extraction target and the extraction content from the extraction target are associated with each other. There is.

For example, when the file defined in the common definition information 123 to be described in the list B1 of the collation information 122 is the target, the extraction contents are the following three. The first is a file whose required flag is "F", which is the element attribute E1. The second is an element that is individually determined by the file management device 3 among the file path notations that satisfy the file path condition of the element attribute E2 for the file to be arranged. The third is the digest value of the file in which the digest value of the element attribute E3 is not defined for the file to be arranged.

When the file defined in the common definition information 123 to be described in the list B2 of the collation information 122 is the target, the extraction contents are the following two. The first is a file whose required flag is "F", which is the element attribute E1. The second is an element that is individually determined by the file management device 3 among the file path notations that satisfy the file path condition of the element attribute E2 for the file to be arranged.

Further, when the directory defined in the common definition information 123 to be described in the list B3 of the collation information 122 is the target, the extracted content is the directory path that satisfies the file path condition of E2 in the element attribute for the file to be arranged. Of the notations, it is an element that is individually determined by the file management device. The individual definition item extraction unit 145 (described later) extracts an item from the file or directory that is the target of the common definition information 123 according to the item extraction information 124, and defines it as an item of the individual definition information 125.

Next, the individual definition information 125 will be described. The individual definition information 125 is information indicating conditions to be individually provided according to the file management device 3 for the items extracted from the common definition information 123 according to the item extraction information 124. For example, the individual definition information 125 is information input from the outside. Specifically, the individual definition information 125 is input from the outside by the operation of the input unit 15 by the administrator of the file management device 3. Of course, not limited to this, the individual definition information 125 may be input from the outside via the communication unit 13. FIG. 10 is a diagram for explaining the individual definition information 125 shown in FIG. As shown in Table 125a of FIG. 10, the individual definition information 125 is associated with the input contents for the input target.

Specifically, when the file defined in the common definition information 123 to be described in the list B1 of the collation information 122 is the target, the input contents are three. The first is whether or not a file whose required flag is "F", which is the element attribute E1, is arranged. The second is the value of an element that is individually determined by the file management device 3 among the file path notations that satisfy the file path condition of the element attribute E2 for the file to be arranged. The third is the digest value of the file in which the digest value of the element attribute E3 is not defined for the file to be arranged.

Then, when the file defined in the common definition information 123 to be described in the list B2 of the collation information 122 is the target, the input contents are the following two. The first is whether or not a file whose required flag is "F", which is the element attribute E1, is arranged. The second is the value of an element that is individually determined by the file management device 3 among the file path notations that satisfy the file path condition of the element attribute E2 for the file to be arranged.

Further, when the directory defined in the common definition information 123 to be described in the list B3 of the collation information 122 is the target, the input content is the directory path satisfying the file path condition of the element attribute E2 for the file to be arranged. Of the notations, it is a value that is an element that is individually determined by the file management device 3. The individual definition information 125 is acquired by the individual definition information input unit 146 (described later). Then, the collation information 122 is generated based on the common definition information 123 and the individual definition information 125.

A specific example of the individual definition information 125 will be described. FIG. 11 is a diagram showing an example of the individual definition information 125 shown in FIG. The individually defined information Lxx shown in FIG. 11 has lists Wc1 to Wc3.

The list Wc1 of the individual definition information Lxx is a condition that should be individually provided according to the file management device 3 for the file defined to be described in the list B1 of the collation information 122 in the common definition information Gx, that is, FIG. This is a list showing the input contents described in the first row shown in Table 125a of.

For example, in the list Wc1, the files "# 11" to "# 16" are associated with the file path notation, the digest value, or the necessity of arranging the files according to the files. Specifically, in the list Wc1, the file path notation "file path notation (individual element) 11" corresponding to the file "# 11" is shown on the first line (see column Lc11). In addition, on the second line, "file path notation (individual element) 12" which is the file path notation corresponding to the file "# 12" and "arrangement required" which is the necessity of arranging the file "# 12". (See column Lc13). Further, on the fourth line, "file path notation (individual element) 14" which is the file path notation corresponding to the file "# 14" and "digest value 14" (see column Lc12) of the file "# 14". It is shown.

The list Wc2 of the individual definition information Lxx is provided with each condition that should be individually provided according to the file management device 3 for the file defined to be described in the list B2 of the collation information 122 in the common definition information Gx, that is, FIG. This is a list showing the input contents described in the second row shown in Table 125a of.

For example, in the list Wc2, the file "# 21" to "# 23" are associated with the necessity of file path notation or file arrangement according to the file. Specifically, in the list Wc2, the file path notation "file path notation (individual element) 21" corresponding to the file "# 21" is shown on the first line (see column Lc21). In addition, on the second line, "file path notation (individual element) 22" which is the file path notation corresponding to the file "# 22" and "arrangement required" which is the necessity of arranging the file "# 22". (See column Lc22).

The list Wc3 of the individual definition information Lxx is provided with each condition individually provided according to the file management device 3 for the directory defined to be described in the list B3 of the collation information 122 in the common definition information Gx, that is, FIG. This is a list showing the input contents described in the third row shown in Table 125a of.

For example, in the list Wc3, the directory path notation is associated with the directories "# 31" and "# 32" according to the directories. Specifically, in the list Wc3, "directory path notation (individual element) 31", which is the directory path notation corresponding to the directory "# 31", is shown on the first line (see column Lc31). Further, on the second line, "directory path notation (individual element) 32" which is a directory path notation corresponding to the directory "# 32" is shown.

Next, the condition information 126 will be described. The condition information 126 is information indicating the collation condition used by the file management device 3 when collating the file set Fs arranged in the file storage unit 11 with the collation information 122 and determining whether or not the confirmation contents are satisfied. ..

FIG. 12 is a diagram for explaining the condition information 126 shown in FIG. As shown in FIG. 12, the file management device 3 uses collation condition C1 (first collation condition), collation condition C2 (second collation condition), and collation condition C3 (third collation condition) as collation conditions. Use.

The collation condition C1 is that all the files that match the combination of the file path shown in the list B1 and the digest value of the file data are arranged in the file management device 3. The collation condition C2 is that all the files matching the file path shown in the list B2 are arranged in the file management device 3. In the collation condition C3, all directories matching the directory path shown in the list B3 are arranged in the file management device 3, and files or directories that do not correspond to the directory condition b31 or the directory condition b32 are arranged directly under the directory. It has not been done. The file management device 3 determines whether or not at least one of the collation conditions C1 to C3 is satisfied.

The correspondence information 127 is information indicating the correspondence between the confirmation items A1 to A3 and the lists B1 to B3 of the collation information 122 required for that purpose. Correspondence information 127 indicates that all of the lists B1 to B3 are required when confirming all of the confirmation items A1 to A3. Further, when confirming any of the confirmation items A1 to A3, it is shown that only a part of the lists B1 to B3 is sufficient.

Therefore, the file management device 3 refers to the correspondence information 127, and only lists B1 to B3, which are required depending on whether or not the confirmation items A1 to A3 are confirmed, are displayed from the shared information Rs1 to Rs3 in the shared information DB2. You just have to get it. That is, the file management device 3 may acquire a list of the shared information Rs1 to Rs3 in the shared information DB2 used for the confirmation items to be confirmed by itself. In this embodiment, a case where the file management device 3 confirms all of the confirmation items A1 to A3 will be described as an example.

The communication unit 13 is a communication interface for transmitting and receiving various information to and from other devices connected via a network or the like. The communication unit 13 is realized by a NIC (Network Interface Card) or the like, and is a control unit 14 (described later) and another device (for example, common definition information DB2) via a telecommunication line such as a LAN (Local Area Network) or the Internet. Communicate with. For example, the communication unit 13 receives the common definition information G1 to G3 transmitted from the common definition information DB 2, and outputs the confirmation result by the file management device 3 to an external corresponding device for file tampering, file deletion, or the like.

The control unit 14 controls the entire file management device 3. The control unit 14 is, for example, an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). In addition, the control unit 14 has an internal memory for storing programs and control data that define various processing procedures, and executes each process using the internal memory. In addition, the control unit 14 functions as various processing units by operating various programs. The control unit 14 has a file management unit 141, a collation information generation unit 142, and a file confirmation unit 143.

The file management unit 141 identifies the file data of the file of the file storage unit 11 to be managed by the file path, classifies the file path by the directory, and identifies the directory by the directory path.

The collation information generation unit 142 generates collation information 122 to be used in the file management device 3 based on the shared common definition information 123 and the individual definition information 125. The collation information generation unit 142 includes a common definition information acquisition unit 144, an individual definition item extraction unit 145, an individual definition information input unit 146, and a generation unit 147.

The common definition information acquisition unit 144 acquires at least a part of the shared common definition information stored in the common definition information DB2. The common definition information acquisition unit 144 acquires the common definition information 123 corresponding to the file set Fs arranged in the file storage unit 11 by downloading it from the external common definition information DB 2 via a network or the like. Alternatively, the common definition information acquisition unit 144 acquires the common definition information 123 by inputting a file or the like by the administrator of the file management device 3. The common definition information acquisition unit 144 stores the acquired common definition information 123 in the confirmation information storage unit 12.

The individual definition item extraction unit 145 extracts an item to be defined as the individual definition information 125 from the common definition information 123 acquired by the common definition information acquisition unit 144. The individual definition item extraction unit 145 extracts items from the common definition information 123 according to the item extraction information 124. The items to be extracted are the items shown in Table 124a of FIG. 9 described above, and are set for each file or directory defined to be described in each list B1 to B3 of the collation information 122. The description of each item will be omitted because it is described with reference to FIG.

The individual definition information input unit 146 accepts input of individual definition information for the items extracted from the common definition information 123 by the individual definition item extraction unit 145. The content of the information for accepting input is the item shown in Table 125a of FIG. 10 described above, and is set for each file or directory defined to be described in each list B1 to B3 of the collation information 122. The description of each input information will be omitted because it is described with reference to FIG. The individual definition information 125 based on the information received by the individual definition information input unit 146 is, for example, the individual definition information Lxx shown in FIG. The individual definition information input unit 146 stores the acquired individual definition information 125 in the confirmation information storage unit 12.

The individual definition information input unit 146 presents to the administrator of the file management device 3 an operation screen showing each extraction item and an input field for its value or the like on the screen. At this time, for example, a structured file format such as XML (Extensible Markup Language) or a graphical UI (User Interface) is used. Then, the individual definition information input unit 146 acquires the individual definition information 125 by accepting the information input in each input field by the operation of the input unit 15 (described later) by the administrator of the file management device 3. Alternatively, the individual definition information input unit 146 outputs a transmission request such as a value for each extraction item to the external device via the communication unit 13. Then, the individual definition information input unit 146 may acquire the individual definition information 125 by receiving each information transmitted from the external device in response to the transmission request.

The generation unit 147 generates the collation information 122 based on the common list and the element attributes of the common definition information 123. The generation unit 147 provides both the shared common definition information 123 and the individual definition information 125 indicating the conditions to be individually provided according to the file management device 3 for the file set to be arranged in the file management device 3. The matching information 122 to be satisfied is generated.

The generation unit 147 determines the files to be arranged in the lists B1 to B3 of the collation information 122 based on the common definition information 123 and the individual definition information 125, and sets the file path, digest value, and directory path described in the lists B1 to B3. To determine. When the file data is input instead of the digest value as the individual definition information, the generation unit 147 also calculates the digest value of the file data of the file to be arranged in the list B1. The generation unit 147 stores the generated collation information 122 as a file in the confirmation information storage unit 12. Alternatively, the generation unit 147 may directly import the generated collation information 122 into the integrity confirmation function operated by the file management device 3, that is, the file confirmation unit 143.

The file confirmation unit 143 confirms the integrity of the file of the file storage unit 11 by using at least a part of the shared collation information. The file confirmation unit 143 determines the collation information to be used for confirmation according to the file set to be confirmed, and confirms the integrity of the file arranged in the file storage unit 11. The file confirmation unit 143 has a collation unit 148 and a confirmation unit 149.

The collation unit 148 uses the file path of the file arranged in the file storage unit 11, the file path indicated by the collation information 12, the digest value of the file data of the file arranged in the file storage unit 11, and the file data indicated by the collation information 122. The digest value, the directory path of the file arranged in the file storage unit 11, and the directory path indicated by the collation information 122 are collated. Then, the collation unit 148 determines whether or not at least one of the collation condition C1, the collation condition C2, or the collation condition C3 is satisfied.

The confirmation unit 149 confirms at least one of the confirmation items A1 to A3 based on the collation result by the collation unit 148. The confirmation unit 149 determines that the confirmation item A1 is satisfied when the collation condition C1 is satisfied for the file arranged in the file storage unit 11, and satisfies the confirmation item A2 when the collation condition C1 and the collation condition C2 are satisfied. If the collation condition C3 is satisfied, it is determined that the confirmation item A3 is satisfied. In the present embodiment, a case where the file management device 3 determines all the collation conditions C1 to C3 for the file of the file set to be managed and confirms all the confirmation items A1 to A3 will be described as an example.

The input unit 15 is an input interface that receives various operations from the administrator of the file management device 3. For example, the input unit 15 is composed of an input device such as a touch panel, a voice input device, and a keyboard and a mouse. The output unit 16 is realized by, for example, a display device such as a liquid crystal display, a printing device such as a printer, an information communication device, or the like, and outputs information related to file management processing.

[Processing of generator]
Next, the processing of the collation information 122 by the generation unit 147 will be described. FIG. 13 is a diagram illustrating a process of generating the collation information 122 by the generation unit 147 shown in FIG.

FIG. 13 shows the common definition information Gx on the left side, the individual definition information Lxx in the center, and the collation information Rxx on the right side. The common definition information Gx is acquired by the common definition information acquisition unit 144. The individual definition information Lxx is based on the information received by the individual definition information input unit 146 as a condition to be individually provided in the file management device 3 for the items extracted from the common definition information Gx by the individual definition item extraction unit 145. .. The collation information Rxx is generated by the generation unit 147 based on the individual definition information Lxx and the collation information Rxx so as to satisfy both the individual definition information Lxx and the collation information Rxx.

First, a case where the generation unit 147 creates the list B1 of the collation information Rxx will be described. In this case, the generation unit 147 performs the following determination process with reference to the list Wc1 of the individual definition information Lxx for the file defined in the list B1 of the collation information Rxx in the common list J1 of the common definition information Gx. Do.

Whether or not the generation unit 147 refers to the list Wc1 of the individual definition information Lxx and arranges the file in which "F" is added as an essential flag which is the element attribute E1 in the common list J1 of the common definition information Gx. To decide.

For example, the files "# 12" and "# 15" that are the flags "F" of the common definition information Gx are "arrangement required" in the list Wc1 of the individual definition information Lxx, so that the generation unit 147 is a file. It is decided to place "# 12" and "# 15" in the list B1. On the other hand, regarding the file "# 13" which is the flag "F" of the common definition information Gx, the generation unit 147 is "arrangement unnecessary" in the list Wc1 of the individual definition information Lxx, so that the file "# 13" Is not placed in list B1.

Then, the generation unit 147 sets the file with the flag "F" and the file with the flag "T" whose arrangement is determined as the file of the list B1. Specifically, the generation unit 147 lists the files "# 12" and "# 15" of the flag "F" whose arrangement is determined and the files "# 11" and "# 14" of the flag "T" in the list B1. Decide on a file.

Subsequently, the generation unit 147 determines the file path notation that satisfies the file path condition that is the element attribute E2 of the common list J1 of the common definition information Gx for these files. Then, the generation unit 147 describes the file path described according to the determined notation as the file path of the list B1.

That is, the generation unit 147 refers to the files "# 11", "# 12", "# 14", and "# 15" in the "file path notation (individual element) 11, 12, 14" of the list Wc1 of the individual definition information Lxx. , 15 ”is determined to be the file path notation“ file path 11, 12, 14, 15 ”that satisfies the“ file path condition 11, 12, 14, 15 ”of the common definition information Gx, and is described in the list B1 of the collation information Rxx. To do.

Then, the generation unit 147 calculates the hash value of the file data for the file in which the digest value of the element attribute E3 is not defined in the common list J1 of the common definition information Gx for the file to be arranged. The generation unit 147 determines the calculated hash value as a digest value. Then, the generation unit 147 sets the determined digest value as the digest value in the list B1.

For example, the digest values of the files "# 14" and "# 15" are not shown in the common list J1 of the common definition information Gx. Therefore, the generation unit 147 calculates the hash value of the file data of the files "# 14" and "# 15", and uses the calculated hash value as the "digest value 14," of the files "# 14" and "# 15". It is decided as "15". Then, the generation unit 147 describes "digest values 14, 15" as digests of the files "# 14" and "# 15" in the list B1 of the collation information Rxx. Since the files "# 11" and "# 12" are described in the common list J1 of the common definition information Gx, the generation unit 147 describes "digest values 11 and 12" in the list B1 of the collation information Rxx. To do.

Next, a case where the generation unit 147 creates the list B2 of the collation information Rxx will be described. The generation unit 147 performs the following determination processing with reference to the list Wc2 of the individual definition information Lxx with respect to the file defined in the list B2 of the collation information Rxx in the common list J2 of the common definition information Gx.

Similar to the case of the list B1 of the collation information Rxx, the generation unit 147 sets the individual definition information Lxx for the file in which "F" is added as an essential flag of the element attribute E1 in the common list J2 of the common definition information Gx. Refer to the list Wc2 of the above to determine whether or not to place the device.

For example, since the file "# 22" which is the flag "F" of the common definition information Gx is "arrangement required" in the list Wc2 of the individual definition information Lxx, the generation unit 147 generates the file "# 22". Decide to place it in list B2. On the other hand, for the file "# 23" which is the flag "F" of the common definition information Gx, the generation unit 147 lists the file "# 23" because the individual definition information Wc1 states that "arrangement is unnecessary". Decide not to place in B2.

Then, the generation unit 147 sets the file with the flag "F" and the file with the flag "T" for which the arrangement is determined as the files in the list B2. Specifically, the generation unit 147 determines the file "# 22" of the flag "F" and the file "# 21" of the flag "T" whose arrangement has been determined as the files in the list B2.

Subsequently, the generation unit 147 determines the file path notation that satisfies the file path conditions of the common list J2 of the common definition information Gx for these files. Then, the generation unit 147 describes the file path described according to the determined notation as the file path in the list B2.

That is, for the files "# 21" and "# 22", the generation unit 147 uses the "file path notation (individual element) 21 and 22" of the list Wc2 of the individual definition information Lxx and the "file path condition" of the common definition information Gx. The file path notation "File path 21 and 22" satisfying "21,22" is determined and described in the list B2 of the collation information Rxx.

Next, a case where the generation unit 147 creates the list B3 of the collation information Rxx will be described. The generation unit 147 performs the following determination processing with reference to the list Wc3 of the individual definition information Lxx with respect to the directory defined in the list B3 of the collation information Rxx in the common list J3 of the common definition information Gx.

In this case, the generation unit 147 determines the directory path notation that satisfies the directory path notation of the common list J3 of the common definition information Gx, and sets the directory path described according to the determined notation as the directory path of the list B3 of the collation information Rxx. ..

That is, the generation unit 147 uses the "directory path notation (individual element) 31, 32" of the list Wc3 of the individual definition information Lxx for the directories "# 31" and "# 32" as the "directory path condition" of the common definition information Gx. The directory path notation "directory path 31, 32" that satisfies "31, 32" is determined, and is described in the list B3 of the collation information Rxx.

[Processing of collation part]
Next, the processing of the collating unit 148 will be described. 14 and 15 are diagrams for explaining the processing of the collating unit 148 shown in FIG. As shown in FIG. 14, the collation unit 148 first determines the collation information Rxx to be used for confirmation, and uses the collation information Rxx to output a confirmation result for the confirmation items A1 to A3 as an example. For example, the collation unit 148 confirms whether or not the file to be confirmed arranged in the file management device 3 satisfies all the conditions described in the collation information Rxx.

Here, the arrangement of the file to be confirmed and the directory is as shown in the frame W2 on the right side of FIG. Specifically, the files f1 and f2 are files for data falsification confirmation (confirmation item A1) and for excess / deficiency confirmation (confirmation item A2) directly under the directory d1. File f3 is a file to be checked for excess / deficiency (confirmation item A2) directly under the directory d1. The directory d1 is a directory to be checked for excess or deficiency (confirmation item A3). File f4 is a file that is not subject to file integrity confirmation.

Then, an example of the collation information Rxx set for the file set having such an arrangement is shown in the frame W1 on the left side of FIG. As shown in FIG. 15, in the collation information Rxx, the combination of the file path and the directory value of the files f1 and f2 to be confirmed for data tampering is described in the list B1. In the collation information Rxx, the file path of the file f3 to be confirmed for excess / deficiency is described in the list B2, and the directory path of the directory d1 to be confirmed for excess / deficiency is described in the list B3. Note that the directory d2 in the frame W2 is not listed in the list B3 because the files f4 not listed in the lists B1 and B2 are placed directly under the directory d2. As a result of the normal operation of the application, the number of files directly under the application may increase or decrease. Therefore, the directory in which only the files listed in the lists B1 and B2 are placed is not always listed in the list B3.

The collation unit 148 collates the contents of each list of the collation information Rxx with the file paths, digest values, and directories of the files f1 to f4 (see arrow Y10). Then, the confirmation unit 149 confirms whether or not the file to be confirmed satisfies all of the confirmation items A1 to A3 based on the collation result.

Here, the specific processing of the collating unit 148 will be described. First, the collation unit 148 determines whether or not the collation condition C1 is satisfied for the files f1 and f2 shown in the list B1 among the confirmation targets. In this case, the collation unit 148 confirms whether or not the file path “/ d1 / f1” described in the list B1 of the collation information Rxx is arranged in the file management device 3. In the case of the example of FIG. 15, the collation unit 148 has the file path “/ d1 / f1” shown in the list B1 of the collation information Rxx arranged in the file management device 3. Therefore, the collation unit 148 calculates the hash value of the “/ d1 / f1” file of the file management device 3 and collates it with the digest value “data 1” described in the list B1 of the collation information Rxx.

Subsequently, the collation unit 148 confirms that the file path “/ d1 / f2” described in the list B1 of the collation information Rxx is arranged in the file management device 3, and confirms that the file path “/ d1 / f2” is arranged. The hash value of the "/ d1 / f2 file" of the file management device 3 is calculated and collated with the digest value "data 2" described in the list B1 of the collation information Rxx. If the hash value calculated for each of the collation units 148 and the digest value in the list B1 match, the collation unit 148 determines that the collation condition C1 is satisfied.

Next, the collation unit 148 determines whether or not the collation condition C2 is satisfied for the file f3 listed in the list B2 among the confirmation targets. In this case, the collation unit 148 confirms that the file path “/ d1 / d2 / f3” described in the list B2 of the collation information Rxx is arranged in the file management device 3. In the example of FIG. 15, the collation unit 148 can confirm that the file path “/ d1 / d2 / f3” described in the list B2 of the collation information Rxx is arranged, and therefore determines that the collation condition C2 is satisfied.

Next, the collation unit 148 determines whether or not the collation condition C3 is satisfied with respect to the directory path “/ d1” shown in the list B3. In this case, the collation unit 148 confirms that the directory path “/ d1” described in the list B3 of the collation information Rxx is arranged in the file management device 3. In the example of FIG. 15, it can be confirmed that the directory path “/ d1” described in the list B3 of the collation information Rxx is arranged in the file management device 3.

Then, the collation unit 148 confirms the following with respect to the files {d1 / f1, d1 / f2} directly under "/ d1" on the file management device 3. First, the collation unit 148 determines whether or not the files "/ d1 / f1" and "/ d1 / f2" directly under "/ d1" are the files described in the list B1 or the list B2 of the collation information Rxx. .. In the example of FIG. 15, the files “/ d1 / f1” and “/ d1 / f2” directly under “/ d1” are all the file paths described in the list B1 of the collation information Rxx. Therefore, the collation unit 148 can determine that the files "/ d1 / f1" and "/ d1 / f2" directly under "/ d1" are the files described in the list B1 of the collation information Rxx.

Subsequently, the collation unit 148 confirms that the directory "/ d1 / d2" directly under "/ d1" is a directory path under which the files described in the collation information Rxx list B1 or list B2 are arranged. .. In the case of FIG. 15, since the file f3 shown in the list B2 is placed under the directory "/ d1 / d2", the collation information Rxx is provided for the directory "/ d1 / d2" directly under "/ d1". It can be confirmed that the files listed in List B2 are directory paths to be placed under it. That is, in the example of FIG. 15, since the files directly under the directory "/ d1" all satisfy the directory conditions b31 and b32, the collation unit 148 determines that the collation condition C3 is satisfied. The collation unit 148 outputs the above collation result to the confirmation unit 149.

[Processing of confirmation part]
Next, the processing of the confirmation unit 149 with respect to the case of the example of FIG. 15 will be described. The confirmation unit 149 confirms the confirmation items A1 to A3 based on the collation result of the collation unit 148.

First, the confirmation unit 149 determines that the file arranged in the file management device 3 satisfies the confirmation item A1 when the collation condition C1 is satisfied for all the lists described in the list B1 of the collation information Rxx. That is, the confirmation unit 149 determines that the file to be placed has not been tampered with. On the other hand, the confirmation unit 149 determines that the confirmation item A1 is not satisfied when the file arranged in the file management device 3 does not satisfy the collation condition C1 for all the lists described in the list B1 of the collation information Rxx. To do. That is, the confirmation unit 149 determines that the file to be placed has been tampered with.

Subsequently, in the confirmation unit 149, the files arranged in the file management device 3 satisfy the collation condition C1 for all the lists described in the list B1 of the collation information Rxx, and all the lists described in the list B2 of the collation information Rxx. When the collation condition C2 is satisfied, it is determined that the confirmation item A2 is satisfied. That is, the confirmation unit 149 determines that the file to be placed has not been deleted. On the other hand, in the confirmation unit 149, the file arranged in the file management device 3 does not satisfy the collation condition C1 for all the lists described in the list B1 of the collation information Rxx, or all the files described in the list B2 of the collation information Rxx. If the collation condition C2 is not satisfied for the list, it is determined that the confirmation item A2 is not satisfied. That is, the confirmation unit 149 determines that the file to be placed has been deleted.

Then, the confirmation unit 149 determines that the file arranged in the file management device 3 satisfies the confirmation item A3 when the collation condition C3 is satisfied for all the lists described in the list B3 of the collation information Rxx. That is, the confirmation unit 149 determines that a file that should not be placed has not been added. On the other hand, the confirmation unit 149 determines that the confirmation item A3 is not satisfied when the file arranged in the file management device 3 does not satisfy the verification condition C3 for all the lists described in the list B3 of the verification information Rxx. To do. That is, the confirmation unit 149 determines that a file that should not be placed has been added.

The file management device 3 may register a plurality of collation information Rx1, Rx2, Rx3, and sequentially or simultaneously collate and confirm the plurality of collation information. Further, the file management device 3 may pre-register the order and time of integrity confirmation for one or more collation information in the scheduler function or the like, and automatically perform collation and confirmation. In addition, the file management device 3 may generate a log, an alarm, or the like based on the confirmation result, or may take measures such as prohibiting access to the file in which an error has occurred.

[Processing procedure for collation information generation processing]
Next, the processing procedure of the collation information generation process by the file management device 3 will be described. FIG. 16 is a flowchart of a processing procedure of the collation information generation processing according to the embodiment.

As shown in FIG. 16, first, the common definition information acquisition unit 144 acquires at least a part of the shared common definition information stored in the common definition information DB 2 (step S1). Then, the individual definition item extraction unit 145 extracts an item to be defined as the individual definition information 125 from the common definition information 123 acquired by the common definition information acquisition unit 144 (step S2). The individual definition information input unit 146 presents the items extracted from the common definition information 123 by the individual definition item extraction unit 145 (step S3), and accepts the input of the individual definition information (step S4).

Then, the generation unit 147 refers to the individual definition information 125 based on the common list and the element attributes of the common definition information 123, and performs a generation process for generating the collation information 122 (step S5). The generation unit 147 outputs the generated collation information 122 (step S6).

[Processing procedure for collation information generation processing]
Next, the processing procedure of the collation information generation process (step S5) will be described. FIG. 17 is a flowchart of the processing procedure of the collation information generation process shown in FIG.

As shown in FIG. 17, the generation unit 147 sets the description contents of the list B1 of the collation information 122 based on the common definition information 123 and the individual definition information 125 as the collation information generation process (list B1 setting process). Step S11) is performed. Subsequently, the generation unit 147 performs a list B2 setting process (step S12) for setting the description contents of the list B2 of the collation information 122. Subsequently, the generation unit 147 performs a list B3 setting process (step S13) for setting the description contents of the list B3 of the collation information 122.

[List B1 setting process processing procedure]
Next, the processing procedure of the list B1 setting processing (step S11) will be described. FIG. 18 is a flowchart of the processing procedure of the list B1 setting process shown in FIG.

The generation unit 147 refers to the file defined in the list B1 of the collation information 122 in the common list J1 of the common definition information 123 (step S21). Then, the generation unit 147 determines for each file whether the required flag of the common definition information 123 is either “T” or “F” (step S22).

When the generation unit 147 determines that the required flag of the common definition information 123 of this file is "T" (step S22: T), the generation unit 147 determines to place this file in the list B1 of the collation information 122 (step). S23).

On the other hand, when the generation unit 147 determines that the required flag of the common definition information 123 of this file is "F" (step S22: F), the individual definition information 125 requires the placement of this file in the list B1. It is determined whether it is either "" or "unnecessary" (step S24).

When the generation unit 147 determines in the individual definition information 125 that the placement of this file in the list B1 is "necessary" (step S24: required), the generation unit 147 decides to place this file in the list B1 of the collation information 122. (Step S23). On the other hand, when the generation unit 147 determines in the individual definition information 125 that the arrangement of this file in the list B1 is "unnecessary" (step S24: unnecessary), the generation unit 147 arranges this file in the list B1 of the collation information 122. It is decided not to do so (step S25).

After the end of step S23, the generation unit 147 determines the file path notation that satisfies the file path condition of the common list J1 of the common definition information 123 for the file determined to be arranged in the list B1 (step S26). Then, the generation unit 147 sets the file path described according to the determined notation as the file path of the list B1 of the collation information 122 (step S27).

Then, the generation unit 147 determines whether or not the common definition information 123 defines the digest value for the file to be arranged (step S28). When the generation unit 147 determines that the common definition information 123 defines the digest value (step S28: Yes), for this file, the digest value defined in the common definition information 123 is compared with the list B1 of the collation information 122. It is set to the digest value of (step S29). On the other hand, when the generation unit 147 determines that the common definition information 123 does not define the digest value (step S28: No), the generation unit 147 calculates the hash value of the file data of this file, and collates the calculated hash value with the calculated hash value. It is set to the digest value of the list B1 of 122 (step S30).

[List B2 setting process processing procedure]
Next, the processing procedure of the list B2 setting processing (step S12) will be described. FIG. 19 is a flowchart of the processing procedure of the list B2 setting process shown in FIG.

The generation unit 147 refers to the file defined in the list B2 of the collation information 122 in the common list J2 of the common definition information 123 (step S31). Then, the generation unit 147 determines for each file whether the required flag of the common definition information 123 is either “T” or “F” (step S32).

When the generation unit 147 determines that the required flag of the common definition information 123 of this file is "T" (step S32: T), the generation unit 147 determines to place this file in the list B2 of the collation information 122 (step). S33).

On the other hand, when the generation unit 147 determines that the required flag of the common definition information 123 of this file is "F" (step S32: F), the individual definition information 125 requires the placement of this file in the list B2. It is determined whether it is either "" or "unnecessary" (step S34).

When the generation unit 147 determines in the individual definition information 125 that the placement of this file in the list B2 is "required" (step S34: required), the generation unit 147 decides to place this file in the list B2 of the collation information 122. (Step S33). On the other hand, when the generation unit 147 determines in the individual definition information 125 that the arrangement of this file in the list B2 is "unnecessary" (step S34: unnecessary), the generation unit 147 arranges this file in the list B2 of the collation information 122. It is decided not to do so (step S35).

After the end of step S33, the generation unit 147 determines the file path notation that satisfies the file path condition of the common list J3 of the common definition information 123 for the file determined to be arranged in the list B3 (step S36). Then, the generation unit 147 sets the file path described according to the determined notation as the file path of the collation information 122 list B3 (step S37).

[List B3 setting processing procedure]
Next, the processing procedure of the list B3 setting processing (step S13) will be described. FIG. 20 is a flowchart of the processing procedure of the list B3 setting process shown in FIG.

First, the generation unit 147 refers to the directory defined in the list B3 of the collation information 122 in the common list J3 of the common definition information 123 (step S41). Then, the generation unit 147 determines the directory path notation satisfying the directory path notation of the common list J3 of the common definition information 123 for each of the directories for which the description is defined (step S42). The generation unit 147 sets the directory path described according to the determined notation as the directory path of the list B3 of the collation information 122 (step S43).

[Processing procedure for file confirmation processing]
Next, the processing procedure of the file confirmation process by the file management device 3 will be described. FIG. 21 is a flowchart of the processing procedure of the file confirmation process according to the embodiment.

First, in the file management device 3, the file management unit 141 executes a file management step of identifying the file data of the file to be managed by the file path, classifying the file path by the directory, and identifying the directory by the directory path. To do. Further, the file confirmation unit 143 acquires the collation information 122 used for confirming the file set from the confirmation information storage unit 12 (step S51) and stores it in the confirmation information storage unit 12.

Then, the collation unit 148 determines the collation information 122 to be used for confirmation according to the file set to be confirmed, and performs the collation process (step S52). When the collation process reaches a predetermined confirmation timing, the file path of the arranged file and the file path indicated by the collation information 122, the digest value of the file data of the arranged file and the digest value of the file data indicated by the collation information 122, In addition, it is a process of collating any one of the directory path of the arranged file and the directory path indicated by the collation information 122.

Subsequently, the confirmation unit 149 performs a confirmation process for confirming at least one of the confirmation items A1 to A3 based on the collation result by the collation unit 148 (step S53), and the communication unit 13 or the output unit 16 confirms. The result is output (step S54).

[Collation processing procedure]
Next, the processing procedure of the collation process (step S52) will be described. FIG. 22 is a flowchart showing a processing procedure of the collation process shown in FIG.

As shown in FIG. 22, the collation unit 148 refers to the combination of the file path and the digest value in the list B1 of the collation information 122 (step S61). Then, the collation unit 148 confirms whether or not all the files matching the file paths shown in the list B1 are arranged in the file management device 3 (step S62).

When the collation unit 148 confirms that all the files matching the file paths shown in the list B1 are not arranged in the file management device 3 (step S62: No), the files arranged in the file management device 3 are collation conditions. It is determined that C1 is not satisfied (step S63).

On the other hand, when the collation unit 148 confirms that all the files matching the file paths shown in the list B1 are arranged in the file management device 3 (step S62: Yes), each file arranged in the file management device 3 Calculate the hash value of the file data of (step S64). Then, the collation unit 148 collates the digest value of the list B1 with the calculated hash value for each file (step S65). The collation unit 148 determines whether or not the digest value in the list B1 and the calculated hash value match for all the files (step S66).

When the collation unit 148 determines that the digest value in the list B1 and the calculated hash value do not match for all the files (step S66: No), the collation unit 148 determines that this file does not satisfy the collation condition C1 (step S63). ). On the other hand, when the collation unit 148 determines that the digest value in the list B1 and the calculated hash value match for all the files (step S66: Yes), it determines that this file satisfies the collation condition C1 (step S67). ).

Subsequently, the collation unit 148 refers to the file path in the list B2 of the collation information 122 (step S68). The collation unit 148 determines whether or not all the file paths shown in the list B2 are arranged in the file set to be confirmed in the file management device 3 (step S69). When the collation unit 148 determines that all the file paths shown in the list B2 are not arranged (step S69: No), the collation unit 148 determines that the collation condition C2 is not satisfied (step S70). On the other hand, when the collation unit 148 determines that all the file paths shown in the list B2 are arranged (step S69: Yes), it determines that the collation condition C2 is satisfied (step S71).

Subsequently, the collation unit 148 refers to the directory path in the list B3 of the collation information 122 (step S72). Then, the collation unit 148 determines whether or not all the directory paths in the list B3 of the collation information 122 are arranged in the file management device 3 (step S73). When the collation unit 148 determines that all the directory paths in the list B3 of the collation information 122 are arranged in the file management device 3 (step S73: Yes), the file directly under the directory is the list of the collation information 122. It is determined whether or not the file is described in B1 or list B2 (step S75).

When the collation unit 148 determines that the file directly under the directory is not the file described in list B1 or list B2 of the collation information 122 (step S75: No), the directory directly under the directory is the file described in lists B1 and B2. It is determined whether or not the directory is one or more subordinates (step S76).

When the collation unit 148 determines that all the directory paths in the list B3 of the collation information 122 are not arranged in the file management device 3 (step S73: No), the directories directly under the collation information 122 are the files described in the lists B1 and B2. When it is determined that the directory does not have one or more subordinates (step S76: No), it is determined that the collation condition C3 is not satisfied (step S74).

On the other hand, when the collation unit 148 determines that the file directly under the directory is the file described in the list B1 or the list B2 of the collation information 122 (step S75: Yes), or the directory directly under the directory is a list. When it is determined that the directory is for arranging one or more of the files described in B1 and B2 under it (step S76: Yes), it is determined that the collation condition C3 is satisfied (step S77). The collation unit 148 outputs the collation results for the collation conditions C1 to C3 to the confirmation unit 149 (step S78).

[Confirmation processing procedure]
Next, the processing procedure of the confirmation process (step S53) will be described. FIG. 23 is a flowchart showing a processing procedure of the confirmation process shown in FIG.

As shown in FIG. 23, when the confirmation unit 149 acquires the collation result by the collation unit 148 (step S81), the file arranged in the file management device 3 is displayed for all the lists described in the list B1 of the collation information 122. It is determined whether or not the collation condition C1 is satisfied (step S82). When the confirmation unit 149 determines that the collation condition C1 is satisfied for all the lists described in the list B1 of the collation information 122 (step S82: Yes), the file to be arranged has not been tampered with (confirmation item A1). Is confirmed (step S83). On the other hand, when the confirmation unit 149 determines that all the lists described in the list B1 of the collation information 122 do not satisfy the collation condition C1 (step S82: No), there is no file to be arranged or there is no file to be arranged. Confirm that the file to be placed has been tampered with (step S84).

Subsequently, in the confirmation unit 149, the file arranged in the file management device 3 satisfies the collation condition C1 for all the lists described in the list B1 of the collation information 122, and all the lists described in the list B2 of the collation information 122. It is determined whether or not the collation condition C2 is satisfied (step S85).

When the confirmation unit 149 determines that the collation condition C1 is satisfied for all the lists described in the list B1 of the collation information 122, and the collation condition C2 is satisfied for all the lists described in the list B2 of the collation information 122 (step). S85: Yes), it is determined that the file to be placed has not been deleted (confirmation item A2) (step S86). On the other hand, the confirmation unit 149 determines that the collation condition C1 is satisfied for all the lists described in the list B1 of the collation information 122, and the collation condition C2 is not satisfied for all the lists described in the list B2 of the collation information 122. If so (step S85: No), it is determined that the file to be placed has been deleted (step S87).

Then, the confirmation unit 149 determines whether or not the file arranged in the file management device 3 satisfies the collation condition C3 for all the lists described in the list B3 of the collation information 122 (step S88). When the confirmation unit 149 determines that the collation condition C3 is satisfied for all the lists described in the list B3 of the collation information 122 (step S88: Yes), the files that should not be arranged are not added (confirmation item A3). (Step S89). When the confirmation unit 149 determines that the collation condition C3 is not satisfied for all the lists described in the list B3 of the collation information 122 (step S88: No), it determines that a file that should not be arranged has been added (step S88: No). Step S90).

Subsequently, the confirmation unit 149 creates a confirmation result (step S91), outputs the confirmation result to the communication unit 13 or the output unit 16, and ends the confirmation process.

[Effect of Embodiment]
As described above, the file management device 3 according to the present embodiment generates collation information 122 suitable for the file management device 3 based on at least a part of the shared common definition information 123 created in advance. That is, the file management device 3 according to the present embodiment uses the individual definition information 125, which indicates the conditions to be individually provided according to the file management device 3, in addition to the shared common definition information. Collation information that satisfies both the common definition information 123 is generated.

In other words, the file management device 3 according to the present embodiment generates the collation information 122 by using the individual definition information input by the administrator and at least a part of the shared common definition information 123 acquired from the outside. .. Therefore, according to the file management device 3 according to the present embodiment, the information input by the administrator is only the individual definition information regarding the file or the like in which a part of the file is changed, and the burden on the administrator regarding the creation of the collation information is borne. It can be reduced. Thereby, in the present embodiment, the collation information creation cost by the administrator of the file management device 3 can be reduced.

And, conventionally, when a part of a file belonging to a software package can be changed, the software provider may not be able to provide accurate collation information for such a file. In this case, there is a problem that the system administrator cannot obtain the collation information for the partially changeable file and cannot confirm the integrity of the file.

For example, conventionally, when a part of the file path of a file belonging to a software package can be customized (prefix specification, wildcard specification, etc.), the software provider has specified the file path of the list B1 to B3 of the collation information of these files. Could not be specified in some cases.

On the other hand, in the present embodiment, the software provider creates and provides common definition information G1 to G3 indicating the file path condition in the element attribute E2 for the file path of the collation information lists B1 to B3. .. Then, the administrator of the file management device 3 determines the file path of the file to be managed within the range satisfying the file path condition of the definition D1 of the common definition information. Then, the administrator of the file management device 3 designates the file path determined in this way as the file path of the lists B1 to B3 of the collation information 122. Therefore, in the present embodiment, the file paths of the collation information lists B1 to B3 can be determined without delay.

Further, for example, in the past, when some of the files belonging to the software package can be deleted at the time of installation (manual file, etc.), the software provider lists these files in the collation information lists B2 and B3. I can't decide whether to do it or not.

On the other hand, in the present embodiment, the software provider creates and provides the required flag of the element attribute E2 of the common definition information for the files of the collation information lists B1 and B2. The administrator of the file management device 3 decides whether or not to install the file whose required flag of the definition D2 of the common definition information is "No (F)", and lists the files that are decided not to be installed in the collation information. Delete from B1 and B2. Therefore, in the present embodiment, the determination of the file to be posted in the collation information lists B1 and B2 can be executed without delay.

Further, for example, in the past, when a part of the file data belonging to the software package can be changed at the time of installation (setting file, etc.), the software provider has the file data in the list B1 of the collation information of these files. In some cases, the digest value could not be specified.

On the other hand, in the present embodiment, the software provider creates and provides a fixed value flag which is an element attribute E3 of the common definition information for the file of the list B1 of the collation information. The administrator of the file management device 3 decides whether or not to change the data for the file whose fixed value flag of E3 of the common definition information is "No (F)", and the digest value of the file decided to be changed. Is set to the digest value of the collation information list B1. Therefore, in the present embodiment, the digest value of the file data in the collation information list B1 can be determined without delay.

As described above, in the present embodiment, even if a part of the file belonging to the software package is changed in the file management device 3, the file management device 3 provides accurate collation information for the changed software package. Can be generated. Therefore, according to the present embodiment, even if a part of the file belonging to the software package is changed in the file management device 3, the integrity of the file is determined by using the collation information matching the arranged file. You can check it accurately.

Further, in the present embodiment, the software provider and the administrator of the file management device 3 do not determine all the collation information. According to the present embodiment, it is possible to generate collation information suitable for the file management device 3 only by setting a part of the information that can be handled by the software provider and the administrator of the file management device 3. Therefore, according to the present embodiment, the burden on the software provider in addition to the administrator of the file management device 3 can be reduced.

Further, in the present embodiment, the collation information 122 includes a list B1 indicating a combination of the file path of the file to be arranged and the file data does not change and the digest value of the file data. Use information. Then, in the present embodiment, the file path of the arranged file and the file path indicated by the collation information 122, the digest value of the file data of the arranged file, and the digest value of the file data indicated by the collation information 122 are collated and arranged. Make sure that the file to be done has not been tampered with. Therefore, according to the present embodiment, it is possible to confirm the excess or deficiency of the files without burdening the administrator of the file management device 3.

Then, in the present embodiment, as the collation information 122, a collation condition having a list B2 indicating the file path of the file to be arranged and the file data can be changed is used. Then, in the present embodiment, as the collation information 122, the file directly under the file is the first directory condition that is the file described in the list B1 or the list B2 that belongs to the same collation information, and the directory directly under the directory is the list B1 that belongs to the same collation information. Or, a second directory condition that is a directory in which one or more files listed in List B2 are placed under it, and a third directory that does not place a file or directory that does not meet the first directory condition or the second directory condition directly under it. Collation information having list B3, which indicates the directory path of the directory satisfying the condition, is used.

Then, in the present embodiment, the log file is collated by collating the file path of the arranged file and the file path indicated by the collation information 122, the directory path of the arranged file and the directory path indicated by the collation information 122, and the directory conditions. It is possible to appropriately check the excess / deficiency of files and directories for which digest values such as etc. cannot be defined.

As described above, according to the embodiment, it is possible to reduce the burden on the administrator of the file management device 3 regarding file management, and to accurately confirm the file by using appropriate collation information according to the file to be managed. it can.

[Modification 1 of the embodiment]
As an embodiment, the case where the file management device 3 confirms all of the confirmation items A1 to A3 has been described, but of course, the file management device 3 selects one of the confirmation items A1 to A3 for confirmation. You may. In that case, the combination of the list of collation information to be used differs depending on the confirmation item to be confirmed. In other words, the file management device 3 confirms at least one of the confirmation item A1 and the confirmation items A2 and A3 according to the combination of the lists B1 to B3 possessed by the acquired collation information 122.

FIG. 24 is a diagram showing an example of the data structure of the correspondence information 127 shown in FIG. As shown in FIG. 24, the correspondence information 127 is a list of collation information according to a combination of falsification confirmation (confirmation item A1) and excess / deficiency confirmation (confirmation items A2 and A3), or not. It is associated with whether B1 to B3 are necessary or unnecessary.

As described above, when both the falsification confirmation (confirmation item A1) and the excess / deficiency confirmation (confirmation items A2 and A3) are executed, the list B1 of the collation information 122 is shown as shown in the method 1 on the first line. All of ~ B3 are required. Further, when only the falsification confirmation (confirmation item A1) is executed, only the list B1 is required as shown in the method 2 on the second line. Further, when only the excess / deficiency confirmation (confirmation items A2 and A3) is executed, only the lists B2 and B3 are required as shown in the method 3 on the third line. If neither the falsification confirmation (confirmation item A1) nor the excess / deficiency confirmation (confirmation items A2 and A3) is executed, none of the lists B1 to B3 is required as shown in the fourth line. In this way, the file management device 3 may acquire the necessary lists B1 to B3 according to the combination of the confirmation items (confirmation item determination method 1). On the other hand, there are cases where the collation information that can be acquired, that is, the collation information created / distributed does not include all the lists B1, B2, and B3, and only the list B1 and only the list B2 and B3. There is also a method of confirming the confirmation items that can be carried out in (Confirmation item determination method 2). For example, if the collation information is only the list B1, only the confirmation item A1 is confirmed, and if the collation information is only the lists B2 and B3, only the confirmation items A2 and A3 are confirmed. Since the confirmation item determination method 1 and the confirmation item determination method 2 do not contradict each other, both can be realized by one system, but a system in which only the confirmation item determination method 2 is implemented may be used.

[Modification 2 of the embodiment]
Next, a modification 2 of the embodiment will be described. FIG. 25 is a diagram illustrating a process of generating collation information in the second modification of the embodiment. As shown in FIG. 25, {prefix} is a common value in the lists B1 to B3 of the common definition information Gx, the individual definition information Cx, and the collation information Rxx.

In the common definition information Gx, the file path condition and the directory path condition define the whole or a part of the files or directories described in the collation information list B1, list B2, and list B3 as the prefix range. Then, in the common definition information Gx, the file path condition and the directory path condition allow the prefix range to be arranged under the directory path (prefix) individually determined by the file management device 3. Further, in the common definition information Gx, the file path condition and the directory path condition are not allowed to be individually determined by the file management device 3 except for the directory path (prefix).

For example, the process of creating the file path of the collation information Rxx will be described as an example. The common definition information Gx defines a part of the file path as a prefix (see (1) in FIG. 25). Further, in the individual definition information Lxx, the value of prefix is defined (see (2) in FIG. 25). In the common definition information Gx, the generation unit 147 creates a file path from the definitions of the common definition information Gx and the individual definition information Lxx according to the file path condition. Specifically, for the file "# 11", the common definition information Gx defines the file path of the file "# 11" as "/ [prefix1] / f11". Then, in the individual definition information Lxx, the value of prefix is defined as "dc". The generation unit 147 creates "/ dc / f11" as the file path of the file "# 11" from the definitions of the common definition information Gx and the individual definition information Lxx (see (3) in FIG. 25). It should be noted that a plurality of prefixes can be defined in the collation information Rxx. For example, by defining two prefixes (eg, prefix1 and prefix2), it is possible to define a file set under two directories whose directory paths are individually determined.

FIG. 26 is a diagram illustrating another example of the collation information generation process in the second modification of the embodiment. As shown in FIG. 26, {wildcard} is an arbitrary value in the lists B1 to B3 of the common definition information Gx, the individual definition information Cx, and the collation information Rxx, and does not have to be common.

In the common definition information Gx, the file path condition and the directory path condition define a part of the character strings constituting the file path or the directory path described in the collation information lists B1, B2 and B3 as a wildcard part. Then, in the common definition information Gx, it is permitted to replace the wildcard portion with an arbitrary character string individually determined by the file management device 3. Then, the common definition information Gx does not allow the file management device to individually determine other than the wildcard portion.

For example, the process of creating the file path of the collation information Rxx will be described as an example. The common definition information Gx defines a part of the file path as a wildcard (see (1) in FIG. 26). Further, in the individual definition information Lxx, the value of the wild card is defined (see (2) in FIG. 26). In the common definition information Gx, the generation unit 147 creates a file path from the definitions of the common definition information Gx and the individual definition information Lxx according to the file path condition (see (3) in FIG. 26). Specifically, for the file "# 12", the common definition information Gx defines the file path of the file "# 12" as "/d2/[wildcard12].exe". Then, in the individual definition information Lxx, the file path of the file "# 12" is defined as "[wildcard12] =" fc12 "". The generation unit 147 creates "/d2/fc12.exe" as the file path of the file "# 12" from the definitions of the common definition information Gx and the individual definition information Lxx.

FIG. 27 is a diagram illustrating another example of the collation information generation process in the second modification of the embodiment. As shown in FIG. 27, the regular expression is an arbitrary value in the lists B1 to B3 of the common definition information Gx, the individual definition information Lxx, and the collation information Rxx, and does not have to be common.

In the common definition information Gx, the file path condition and the directory path condition define the character strings constituting the file path or the directory path described in the collation information lists B1, B2, and B3 by regular expressions.

For example, the process of creating the file path of the collation information Rxx will be described as an example. The common definition information Gx defines a part of the file path as a regular expression (see (1) in FIG. 27). Further, in the individual definition information Lxx, the value of the regular expression is defined (see (2) in FIG. 27). In the common definition information Gx, the generation unit 147 creates a file path from the definitions of the common definition information Gx and the individual definition information Lxx according to the file path condition (see (3) in FIG. 27). Specifically, for the file "# 12", the common definition information Gx sets the file path of the file "# 12" to "/d2/f12.*\.exe" and partly uses an arbitrary character string using a regular expression. Defined with ". *". Then, in the individual definition information Lxx, the value of the arbitrary character string is defined as "test" for the file path of the file "# 12". The generation unit 147 creates "/d2/f12test.exe" as the file path of the file "# 12" from the definitions of the common definition information Gx and the individual definition information Lxx.

Here, in the prior art (for example, the functions described in Non-Patent Documents 1 and 2), when a part of the file path of the file belonging to the software package can be customized (prefix specification, wildcard specification, etc.), the software provider Cannot specify the file path for collation information for these files.

On the other hand, in the second modification of the present embodiment, the software provider provides a part of the common definition information in which the prefix definition, the wildcard definition, or the regular expression definition is performed. Then, the administrator of the file management device 3 determines by simply inputting the values of prefix, wildcard, or regular expression within the range that satisfies the file path condition and the directory path condition of the common definition information. Then, the administrator of the file management device 3 designates the file path determined in this way as the file path of the lists B1 to B3 of the collation information 122. Therefore, in the present embodiment, even if a prefix specification or a wildcard specification is specified for a part of the file path of the file belonging to the software package, the file path of the collation information lists B1 to B3 is smoothly entered. Can be decided.

[Modification 3 of the embodiment]
Next, a modification 3 of the embodiment will be described. FIG. 28 is a schematic diagram showing another schematic configuration of the management system having the file management device according to the embodiment. As shown in FIG. 28, the management system according to the modified example of the embodiment has a configuration in which the collation information generation device 202 is provided separately from the file management devices 203X to 203Z. Further, when a plurality of file management devices 203X to 203Z will be described without particular distinction, the file management device 203 will be described.

The collation information generation device 202 acquires shared common definition information from the shared definition information DB2 (see arrow Y21). Then, the collation information generation device 202 acquires individual definition information indicating conditions to be individually provided based on the input information and the like by the administrator of the file management devices 203X to 203Z. Then, the collation information generation device 202 generates collation information corresponding to each file management device 203X to 203Z, and outputs the corresponding collation information to the file management devices 203X to 203Z (see arrows Y22 to Y24). Each of the file management devices 203X to 203Z manages a file by using the collation information generated by the collation information generation device 202. In FIG. 28, one collation information generation device 202 is shown under the common definition information DB2, but in a more general configuration, the common definition information DB2 generates a plurality of collation information belonging to different systems. Common definition information is provided to the device 202.

[Configuration of collation information generator]
FIG. 29 is a schematic diagram showing a schematic configuration of the collation information generation device 202 shown in FIG. 28. As shown in FIG. 29, the collation information generation device 202 has a control unit 214 having a collation information generation unit 142 instead of the control unit 42, as compared with the file management device 2 shown in FIG. Further, the collation information generation device 202 stores the collation information 122, the common definition information 123, the item extraction information 124, and the individual definition information 125 in the confirmation information storage unit 12. The common definition information 123 is acquired from the shared common right definition information DB2. The individual definition information 125 is based on the input information by the administrator of the file management devices 203X to 203Z input via the communication unit 13 and the like.

The collation information generation device 202 generates collation information for each of the file management devices 203X to 203Z for which the collation information is generated by executing the processing procedures of FIGS. 16 to 20, and the target file management devices 203X to 203Z. The generated collation information is output to.

[File management device configuration]
FIG. 30 is a configuration of the file management device 203 shown in FIG. 28. Compared to the file management device 2 shown in FIG. 2, the file management device 203 has a control unit 314 having a file management unit 141 and a file confirmation unit 143 instead of the control unit 42. Further, the collation information generation device 202 stores the confirmation content information 121, the collation information 122, the condition information 126, and the correspondence information 127 used for file management in the confirmation information storage unit 12. The file management device 203 confirms the integrity of the file by executing the processing procedures of FIGS. 21 to 23 using the collation information output from the collation information generation device 202.

In the management system according to the present embodiment, as in the first modification, the collation information generation device 202 is provided separately from the file management device 203, and one collation information generation device 202 collates a plurality of file management devices 203. It may be configured to generate information.

[About the system configuration of the embodiment]
The file management devices 3, 203, the collation information generation device 202, and each component shown in FIG. 1 are functionally conceptual, and do not necessarily have to be physically configured as shown in the drawing. That is, the specific forms of distribution and integration of the functions of the file management devices 3, 203 and the collation information generation device 202 are not limited to those shown in the drawings, and all or part of them may be used according to various loads and usage conditions. It can be functionally or physically distributed or integrated in any unit.

Further, each process performed by the file management devices 3, 203 and the collation information generation device 202 is a program in which all or any part of the processing is analyzed and executed by the CPU, GPU (Graphics Processing Unit), CPU, and GPU. May be realized. Further, each process performed by the file management devices 3 and 203 and the collation information generation device 202 may be realized as hardware by wired logic.

Further, among the processes described in the embodiment, all or a part of the processes described as being automatically performed can be manually performed. Alternatively, all or part of the processing described as being performed manually can be automatically performed by a known method. In addition, the above-mentioned and illustrated processing procedures, control procedures, specific names, and information including various data and parameters can be appropriately changed unless otherwise specified.

[program]
FIG. 31 is a diagram showing an example of a computer in which the file management devices 3, 203 and the collation information generation device 202 are realized by executing the program. The computer 1000 has, for example, a memory 1010 and a CPU 1020. The computer 1000 also has a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. Each of these parts is connected by a bus 1080.

The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores, for example, a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1090. The disk drive interface 1040 is connected to the disk drive 1100. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to, for example, a mouse 1110 and a keyboard 1120. The video adapter 1060 is connected to, for example, the display 1130.

The hard disk drive 1090 stores, for example, the OS 1091, the application program 1092, the program module 1093, and the program data 1094. That is, the program that defines each process of the file management devices 3, 203 and the collation information generation device 202 is implemented as a program module 1093 in which a code that can be executed by the computer 1000 is described. The program module 1093 is stored in, for example, the hard disk drive 1090. For example, the program module 1093 for executing the same processing as the functional configuration in the file management devices 3, 203 and the collation information generation device 202 is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD.

Further, the setting data used in the processing of the above-described embodiment is stored as program data 1094 in, for example, a memory 1010 or a hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1090 into the RAM 1012 and executes them as needed.

The program module 1093 and the program data 1094 are not limited to the case where they are stored in the hard disk drive 1090, and may be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and the program data 1094 may be stored in another computer connected via a network (LAN, WAN (Wide Area Network), etc.). Then, the program module 1093 and the program data 1094 may be read by the CPU 1020 from another computer via the network interface 1070.

Although the embodiment to which the invention made by the present inventor is applied has been described above, the present invention is not limited by the description and the drawings which form a part of the disclosure of the present invention according to the present embodiment. That is, all other embodiments, examples, operational techniques, and the like made by those skilled in the art based on the present embodiment are included in the scope of the present invention.

2 Common definition information database (DB)
3,203 File management device 10 Storage unit 11 File storage unit 12 Confirmation information storage unit 13 Communication unit 14,214,314 Control unit 15 Input unit 16 Output unit 121 Confirmation content information 122 Verification information 123 Common definition information 124 Item extraction information 125 Individual definition information 126 Condition information 127 Correspondence relation information 141 File management unit 142 Collation information generation unit 143 File confirmation unit 144 Common definition information acquisition unit 145 Individual definition item extraction unit 146 Individual definition information input unit 147 Generation unit 148 Verification unit 149 Confirmation Part 202 Collation information generator

Claims (8)

A collation information generating device for generating collation information, the file management apparatus is used to manage the placed file in the file management apparatus,
Regarding the collation information to be collated when confirming file tampering or excess / deficiency in any file management device, the definition of a common list, which is a list of files and directories that may be described in the collation information, and individual files. in the management apparatus, an acquisition unit that acquires at least one common definition information of a plurality of common definition information defining and, sharing indicating file and element attributes is a condition for determining the elements of the list of directories of the verification information,
Based on the definition of the common list and the definition of the element attribute of at least one common definition information acquired by the acquisition unit, the file should be arranged in the file management device as the collation information, and the file data is The first list showing the combination of the file path of the file that does not change and the digest value of the file data, the file path of the file that should be placed in the file management device and the file data can change. The list of 2 and the file directly under it are the first directory conditions that are the files described in the first list or the second list that belong to the same collation information, and the directory directly under is the first that belongs to the same collation information. File or directory that does not correspond to the first directory condition or the second directory condition directly under the second directory condition, which is the directory under which one or more of the files listed in the list or the second list are placed. A generator that generates collation information, with a third list showing the directory paths of directories that satisfy the third directory condition.
A collation information generator characterized by having. The common definition information is not a first flag or essential indicates that the file according to the common list of the first and second lists of the verification information is disposed in said file management apparatus is essential An essential flag that defines the second flag to be shown, a file path condition that is a condition for creating a file path notation of a file described in the first list of the collation information and the common list of the second list, and a first of the collation information. Among the files listed in the common list of the list, the digest value of the file whose file data cannot be changed when it is placed in the file management device, and the conditions for creating the directory path notation of the directory described in the common list of the third list of the collation information. The directory path condition that is is defined as the element attribute,
The generating unit, to the file set to be disposed in the file management apparatus, the verification information which satisfies both and the common definition information and individual definition information indicating a condition to be provided individually in accordance with the file management apparatus The collation information generator according to claim 1, wherein the collation information generator is generated. From the common definition information, the file defined in the first list in the common definition information as an item to be defined as the individual definition information satisfies the file path of the second flag and the file path. A file in which either an element individually determined by the file management device or a file path in which the digest value is not defined is extracted from the file path notation, and the description is defined in the second list in the common definition information. Of the file of the second flag and the file path notation satisfying the file path condition, any of the elements individually determined by the file management device is extracted, and described in the third list in the common definition information. For the defined directory, an individual definition item extraction unit that extracts from the common definition information the elements that are individually determined by the file management device among the directory path notations that satisfy the file path conditions, and
According to the items extracted from the common definition information by the individual definition item extraction unit, the file management device for the file of the second flag is defined for the file defined in the first list of the collation information in the common definition information. whether the arrangement in the file path satisfying file path element value for determining separately in the file management apparatus of the notation, the information of the file data of the file to the digest values are not defined in the common definition information Regarding the files defined in the second list of the collation information, whether or not the file of the second flag is arranged in the file management device, and the file path notation that satisfies the file path conditions, are individually specified in the file management device. The information on the value of the element to be determined and the directory defined in the third list of the collation information in the common definition information are individually determined by the file management device among the directory path notations satisfying the file path conditions. The individual information input unit that accepts the input of the value information of the element to be performed as the individual definition information, and
The collation information generation device according to claim 2, further comprising. The file path condition and the directory path condition define all or a part of the files or directories described in the first list, the second list, and the third list of the collation information as a prefix range, and the prefix range. Is allowed to be placed under the directory path (prefix) individually determined by the file management device, and other than the directory path (prefix) is not allowed to be individually determined by the file management device. The collation information generation device according to claim 2 or 3. In the file path condition and the directory path condition, a part of the character string constituting the file path or the directory path described in the first list, the second list, and the third list of the collation information is defined as a wildcard part. However, it is characterized in that the wildcard part is allowed to be replaced with an arbitrary character string individually determined by the file management device, and the file management device is not allowed to individually determine other than the wildcard part. The collation information generation device according to claim 2 or 3. The file path condition and the directory path condition define a character string constituting the file path or directory path described in the first list, the second list, and the third list of the collation information by a regular expression. The collation information generator according to claim 2 or 3. A management system comprising a said file management apparatus that manages the placed file in the file management apparatus, a verification information generating device for generating collation information, the file management apparatus is used,
The collation information generator is
Regarding the collation information to be collated when confirming file tampering or excess / deficiency in any file management device, the definition of a common list, which is a list of files and directories that may be described in the collation information, and individual files. in the management apparatus, an acquisition unit that acquires at least one common definition information of a plurality of common definition information defining and, sharing indicating file and element attributes is a condition for determining the elements of the list of directories of the verification information,
A file that should be placed in the arbitrary file management device as collation information based on the definition of the common list and the definition of the element attribute of at least one common definition information acquired by the acquisition unit. The first list showing the combination of the file path of the file whose data does not change and the digest value of the file data, the file of the file which should be placed in the arbitrary file management device and whose file data can change. The second list showing the path and the file directly under it belong to the same collation information, the first directory condition is the file described in the first list or the second list, and the directory directly under is the same collation information. Corresponds to the second directory condition, which is a directory under which one or more of the files described in the first list or the files described in the second list belong, and the first directory condition or the second directory condition directly underneath. A generator that generates collation information with a third list of directory paths for directories that satisfy the third directory condition, and a generator that does not place files or directories.
Have,
The file management device is
For files placed in the file management device, a file management unit that identifies file data by file path, classifies file paths by directory, identifies directories by directory path, and manages files.
The file path of the file placed in the file management device, the file path indicated by the collation information, the digest value of the file data of the file placed in the file management device, the digest value of the file data indicated by the collation information, and A collation unit that collates any one of the directory path of the file arranged in the file management device and the directory path indicated by the collation information.
Based on the collation result by the collation unit, the file to be placed in the file management device, which is the first confirmation content, has not been tampered with according to the combination of the lists of the acquired collation information, and the second At least one of the confirmation contents of the file that should not be placed in the file management device has not been deleted and the third confirmation content that the file that should not be placed in the file management device has not been added. A confirmation unit to confirm one and
A management system characterized by having. This is a collation information generation method executed by the collation information generator that generates collation information used when managing files placed in the database.
Regarding the collation information to be collated when confirming file tampering or excess / deficiency in any file management device, the definition of a common list, which is a list of files and directories that may be described in the collation information, and individual files. in the management apparatus, an acquisition step of acquiring at least one common definition information of a plurality of common definition information defining and, sharing indicating file and element attributes is a condition for determining the elements of the list of directories of the verification information,
Based on the definition of the common list and the definition of the element attribute of at least one common definition information acquired in the acquisition process, the file should be arranged in the file management device as the collation information, and the file data. 1st list showing the combination of the file path of the file that does not change and the digest value of the file data, showing the file path of the file that should be placed in the file management device and the file data can change. The second list and the file directly under it belong to the same collation information, the first directory condition is the file described in the first list or the second list, and the directory directly underneath belongs to the same collation information. A second directory condition that is a directory under which one or more of the files listed in the first list or the second list are arranged, a file that does not correspond to the first directory condition or the second directory condition directly under the first list or the file that does not correspond to the second directory condition. A generation step of generating collation information with a third list showing the directory paths of directories that satisfy the third directory condition where no directories are placed, and
A collation information generation method characterized by including.

Images