JP2019148953A - File status confirmation device, file status confirmation method, and file status confirmation program - Google Patents

Abstract

To provide a file status confirmation device, a file status confirmation method, and a file status confirmation program capable of confirming the management status of a file.SOLUTION: A file status confirmation device (a management server 200) comprises a communication unit 201 and a processing unit 202. The communication unit 201 acquires, from management terminals 110, file identification information collected from a non-management terminal 120 by each of the management terminals 110 when an access to the non-management terminal 120 that is attempted based on an IP address generated by each of the different management terminals 110 is successful. The processing unit 202 estimates the confidentiality of files having the identification information in common on the basis of the number of identification information in common among the management terminals 110.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a file status confirmation device, a file status confirmation method, and a file status confirmation program.

  In view of the importance of appropriately managing documents including confidential information, various techniques relating to document management have been proposed. For example, a corporate document management system including at least one terminal and a server is known (see, for example, Patent Document 1). This corporate document management system manages documents in the corporate network and prevents leakage of confidential information.

JP 2008-541273 A

  By the way, an administrator who manages the corporate document management system may manage the terminal described above together with the corporate document management system. When an employee who uses a terminal leaves the manager, the administrator may perform an operation to return the terminal to its initial state so that an electronic file containing confidential information (hereinafter simply referred to as a file) does not remain in the terminal. .

  However, if the administrator forgets to perform the above operation and forgets to manage the terminal and leaves it, the file remains in the unmanaged terminal, and if the access to the file is not restricted, any terminal May be open to view the file. As described above, there is a problem that it is difficult to find a file that exists in an unmanaged terminal and is unintentionally opened to the public.

  Therefore, an object of one aspect is to provide a file status confirmation device, a file status confirmation method, and a file status confirmation program that can confirm the management status of a file.

  In one embodiment, the file status confirmation device is configured such that each of the first terminal devices has a successful access to the second terminal device attempted based on an IP address generated by each of a plurality of different first terminal devices. Based on the number of identification information that is common between the first terminal device and the acquisition unit that acquires the identification information of the file collected from the second terminal device from the first terminal device, the file having the common identification information And a processing unit for estimating confidentiality.

  You can check the management status of files.

FIG. 1 is a diagram for explaining an example of a management system. FIG. 2 shows an example of the hardware configuration of the management server. FIG. 3 is an example of a block diagram of the management terminal and the management server. FIG. 4 is a flowchart showing an example of the operation of the management terminal. FIG. 5 is a flowchart showing an example of the operation of the management server. FIG. 6 is an example of processing target information. FIG. 7 is a flowchart showing an example of the operation of the first estimation process. FIG. 8 shows an example of a security leak confirmation screen. FIG. 9A is a flowchart illustrating a part of the operation of the management server. FIG. 9B is a flowchart illustrating an example of the second estimation process. FIG. 10 is an example of an access restriction estimation screen. FIG. 11A is a flowchart illustrating a part of the operation of the management server. FIG. 11B is a flowchart illustrating an example of the distribution determination process. FIG. 12 shows an example of the confidential file distribution screen.

  Hereinafter, an embodiment for carrying out this case will be described with reference to the drawings.

(First embodiment)
FIG. 1 is a diagram for explaining an example of the management system S. The management system S includes a plurality of terminal devices 110 and 120 and a management server 200 as a file status confirmation device. The plurality of terminal devices 110 and 120 and the management server 200 are connected to each other by a communication network NW. An example of the communication network NW is a local area network (LAN). The communication format of the communication network NW is not particularly limited, and may be wired communication or wireless communication. The plurality of terminal devices 110 and 120 are divided into several departments. In the present embodiment, a plurality of terminal devices 110 and 120 are divided and installed in four departments: a sales department, a development department, a research department, and a general affairs department. For example, one terminal device 110 and one terminal device 120 are installed in the sales department. Two terminal devices 110 are installed in the general affairs department. For example, a personal computer (PC) is used for the terminal devices 110 and 120.

  The terminal device 110 is managed by an administrator. Hereinafter, the terminal device 110 is referred to as a management terminal 110. On the other hand, the terminal device 120 is left unmanaged by the administrator. Hereinafter, the terminal device 120 is referred to as an unmanaged terminal 120. Note that the manager corresponds to, for example, a person who manages the management system S.

  Since the management terminal 110 is managed by an administrator, maintenance work is performed regularly or irregularly by the administrator. As a result, various application programs (hereinafter simply referred to as applications) are installed in the management terminal 110. For example, an application (hereinafter referred to as an agent) that performs file sharing access such as Server Message Block (SMB) is installed in the management terminal 110. Details of the agent will be described later. On the other hand, since the non-management terminal 120 is not managed by the administrator, maintenance work is not performed. As a result, no agent is installed in the unmanaged terminal 120.

  As described above, the management system S includes a management terminal 110 in which an agent is installed and a non-management terminal 120 in which no agent is installed. In FIG. 1, in order to easily distinguish between the management terminal 110 and the non-management terminal 120, the management terminal 110 is marked with a mark “◯”, and the non-management terminal 120 is marked with a mark “X”.

  Each management terminal 110 installed with an agent accesses another management terminal 110 or a non-management terminal 120 installed in the same department via the communication network NW. In addition, each management terminal 110 in which an agent is installed accesses a management terminal 110 or a non-management terminal 120 installed in another department via the communication network NW. The management terminal 110 collects file identification information (hereinafter referred to as file identification information) held by the non-management terminal 120 or the like that has been successfully accessed by the agent. In particular, the management terminal 110 collects at least one of the file name, hash value, and fuzzy hash value of the file including confidential information as identification information by the agent. The fuzzy hash value is a value that identifies a file when the contents of the two files are greatly different, and identifies that the files are the same when the contents are not so different. Each management terminal 110 transmits the collected file identification information to the management server 200 as processing target information together with information related to the management terminal 110 itself, an Internet Protocol (IP) address in which file sharing access has succeeded, and the like.

  The management terminal 110 determines whether or not the file includes confidential information using a known technique. As this known technique, for example, there is a technique in which a confidential display character string (for example, “confidential”, “external secret”, etc.) is embedded in a file, and this confidential display character string is read by optical character recognition (OCR). For example, a technique for embedding data indicating confidential information in a header portion of a file and detecting the data may be used. As a result, not only files containing confidential information but also files containing no confidential information are mixed in the management terminal 110 and the non-management terminal 120, a file containing confidential information can be identified.

  The management server 200 receives the processing target information transmitted from each management terminal 110. Thereby, the management server 200 acquires the processing target information. When the management server 200 receives the processing target information, the management server 200 determines the department in which the management terminal 110 and the non-management terminal 120 are installed based on the IP address where the file sharing access is successful, and determines the determined department (hereinafter referred to as an access successful department). ) Is stored. When the processing information is stored, the management server 200 executes various processes regularly or irregularly. For example, the management server 200 estimates the possibility of leakage of confidential information based on the processing target information. In addition, the management server 200 determines the distribution of files including confidential information based on the processing target information, and estimates the access restriction status for the files. Details of processing executed by the management server 200 will be described later.

  Next, details of the management server 200 will be described with reference to FIG.

  FIG. 2 shows an example of the hardware configuration of the management server 200. Note that the management terminal 110 and the non-management terminal 120 described above have basically the same hardware configuration as that of the management server 200, and a description thereof will be omitted. As shown in FIG. 2, the management server 200 includes at least a central processing unit (CPU) 200A as a hardware processor, a random access memory (RAM) 200B, a read only memory (ROM) 200C, and a network I / F (interface) 200D. Is included. The management server 200 may include at least one of a hard disk drive (HDD) 200E, an input I / F 200F, an output I / F 200G, an input / output I / F 200H, and a drive device 200I as necessary. The CPU 200A to the drive device 200I are connected to each other by an internal bus 200J. That is, the management server 200 can be realized by a computer. Note that a micro processing unit (MPU) may be used as a hardware processor instead of the CPU 200A.

  An input device 710 is connected to the input I / F 200F. Examples of the input device 710 include a keyboard and a mouse. A display device 720 is connected to the output I / F 200G. An example of the display device 720 is a liquid crystal display. A semiconductor memory 730 is connected to the input / output I / F 200H. Examples of the semiconductor memory 730 include a universal serial bus (USB) memory and a flash memory. The input / output I / F 200 </ b> H reads programs and data stored in the semiconductor memory 730. The input I / F 200F and the input / output I / F 200H include, for example, a USB port. The output I / F 200G includes a display port, for example.

  A portable recording medium 740 is inserted into the drive device 200I. Examples of the portable recording medium 740 include a removable disk such as a Compact Disc (CD) -ROM and a Digital Versatile Disc (DVD). The drive device 200I reads a program and data recorded on the portable recording medium 740. The network I / F 200D includes, for example, a LAN port. The network I / F 200D is connected to the communication network NW described above.

  In the above-described RAM 200B, a program stored in the ROM 200C or the HDD 200E is stored by the CPU 200A. In the RAM 200B, the program recorded on the portable recording medium 740 is stored by the CPU 200A. When the stored program is executed by the CPU 200A, the CPU 200A realizes various functions described later and executes various processes described later. In addition, what is necessary is just to make a program according to the flowchart mentioned later.

  Next, functions of the management terminal 110, the non-management terminal 120, and the management server 200 will be described with reference to FIG.

  FIG. 3 is an example of a block diagram of the management terminal 110 and the management server 200. In particular, in FIG. 3, the main part of the function with which the management terminal 110 and the management server 200 are provided is shown. Since the non-management terminal 120 basically has the same function as the management terminal 110, the description thereof is omitted.

  First, the management terminal 110 will be described. The management terminal 110 includes a storage unit 101, an input unit 102, a display unit 103, a communication unit 104, and a control unit 105. The storage unit 101 can be realized by the HDD 200E described above, for example. The input unit 102 can be realized by, for example, the keyboard described above. The display unit 103 can be realized by the above-described liquid crystal display, for example. The communication unit 104 can be realized by the network I / F 200D described above, for example. The control unit 105 can be realized by the above-described CPU 200A and RAM 200B, for example.

  The storage unit 101 stores various programs and files. Examples of the program include an operating system (OS) in addition to the agent described above. Examples of the file include a file including confidential information and a file not including confidential information. The input unit 102 receives an input corresponding to an operation performed by a user of the management terminal 110 and outputs the input to the control unit 105. The display unit 103 displays various screens corresponding to the video signal based on the video signal output from the control unit 105. The communication unit 104 receives file identification information of a file held by the non-management terminal 120 and transmits processing target information output from the control unit 105. The control unit 105 controls the overall operation of the management terminal 110. For example, the control unit 105 generates various video signals based on the input output from the input unit 102 and outputs them to the display unit 103. Also, the control unit 105 periodically acquires an agent from the storage unit 101 and executes it. In addition, although the control part 105 performs various processes, the detail of a process is mentioned later.

  The management server 200 includes a communication unit 201, a processing unit 202, and an information storage unit 203. Note that the communication unit 201 can be realized by the network I / F 200D described above, for example. The processing unit 202 can be realized by the above-described CPU 200A and RAM 200B, for example. The information storage unit 203 can be realized by the HDD 200E described above, for example.

  The communication unit 201 receives processing target information including file identification information transmitted from the management terminal 110 as an example of an acquisition unit. The communication unit 201 outputs the received processing target information to the processing unit 202. The processing unit 202 receives the processing target information output from the communication unit 201, and registers the received processing target information in the information storage unit 203 including the successful access department. Further, the processing unit 202 acquires processing target information from the information storage unit 203 and executes various processes. Details of processing executed by the processing unit 202 will be described later.

  Subsequently, the operation of the management system S will be described with reference to FIGS. 4 to 6. FIG. 4 is a flowchart showing an example of the operation of the management terminal 110. More specifically, it is a flowchart showing an operation when the control unit 105 executes an agent stored in the storage unit 101. FIG. 5 is a flowchart showing an example of the operation of the management server 200. More specifically, it is a flowchart showing an operation when the processing unit 202 executes a program stored in the information storage unit 203. FIG. 6 is an example of processing target information.

  In addition, the control part 105 performs the process of the flowchart shown in FIG. 4 regularly. For example, the control unit 105 executes processing based on a predetermined set date or set time. Further, the processing unit 202 periodically executes the processing of the flowchart shown in FIG. For example, the processing unit 202 executes processing based on a predetermined set date or set time.

  First, the operation of the management terminal 110 will be described. For example, when the control unit 105 of the management terminal 110 detects a match between the current time and the set time, the IP address is randomly generated as shown in FIG. 4 (step S101). More specifically, the control unit 105 randomly generates one IP address from among a plurality of IP addresses respectively assigned to the management terminal 110 and the non-management terminal 120 included in the management system S. In addition, when generating the IP address, the control unit 105 desirably generates one IP address at random from the remaining IP addresses excluding the IP address assigned to the management terminal 110. Thereby, the IP address assigned to the non-management terminal 120 can be specified.

  When the process of step S101 is completed, the control unit 105 performs file sharing access to the generated IP address (step S102), and determines whether the file sharing access is successful (step S103). When the file sharing access fails (step S103: NO), the control unit 105 returns to the process of step S101. Therefore, the control unit 105 generates another IP address at random and executes file sharing access. Since the IP address has a fixed segment for each department, the IP address of the access destination department can be efficiently generated by randomly generating the remaining segments excluding the fixed segment based on a random number or the like.

  On the other hand, when the file sharing access is successful (step S103: YES), the control unit 105 collects file identification information (step S104). More specifically, the control unit 105 collects file identification information of files stored in the management terminal 110 or the non-management terminal 120 of the IP address (hereinafter referred to as file sharing access IP address) where the file sharing access has been successful. In particular, the control unit 105 collects file identification information of files including confidential information using the above-described known technology. When the process of step S104 is completed, the control unit 105 outputs processing target information to the communication unit 104 (step S105). Thereby, the communication unit 104 transmits the processing target information to the management server 200.

  Here, in addition to the file identification information collected in step S104, the processing target information is assigned to the file sharing access IP address, the department to which the management terminal 110 belongs (hereinafter referred to as the agent department), and the management terminal 110. Included IP address (hereinafter referred to as agent IP address). That is, the control unit 105 transmits processing target information including the agent department, agent IP address, file sharing access IP address, and file identification information to the management server 200. As described above, every management terminal 110 periodically transmits the processing target information to the management server 200.

  Next, the operation of the management server 200 will be described. When the communication unit 201 of the management server 200 receives the processing target information transmitted from the management terminal 110, the communication unit 201 outputs the received processing target information to the processing unit 202. Thereby, as shown in FIG. 5, the process part 202 receives process target information (step S201). When the process of step S201 is completed, the processing unit 202 determines the department to which the management terminal 110 or the non-management terminal 120 that stores the file to which the file identification information is assigned is based on the processing target information (step S202).

  Here, as illustrated in FIG. 6, the processing unit 202 receives the processing target information excluding the successful access department, and thus determines the department to which the file sharing access success IP address included in the processing target information is used, for example. More specifically, since the segment “10”, the segment “20”, and the like that can determine the department appear in the second segment in the file sharing access success IP address, the processing unit 202 uses the second segment to determine the belonging department. To do. Here, referring to the correspondence relationship between the department to which the agent belongs and the agent IP address, the sales department is associated with the segment “10”. The development department, research department, and general affairs department are associated with segments “20”, “30”, and “40”, respectively. Therefore, the processing unit 202 determines the department specified by the second segment using such a correspondence. In FIG. 6, the file sharing access success IP address “123.20.0.5” represents the IP address of the non-management terminal 120 installed in the development department. The file sharing access success IP address “123.10.0.8” represents the IP address of the non-management terminal 120 installed in the sales department. The file sharing access success IP address “123.30.0.9” represents the IP address of the non-management terminal 120 installed in the research department.

  When the processing in step S202 is completed, the processing unit 202 then registers processing target information including a successful access department in the information storage unit 203 (step S203). That is, the processing unit 202 registers the processing target information described with reference to FIG. When the process of step S203 is completed, the processing unit 202 executes a first estimation process (step S204). The first estimation process is a process for estimating the possibility that a file is in an unpublished state unintentionally released. In particular, the first estimation process is a process for estimating a possibility that confidential information is leaked from a file when the file is disclosed. The first estimation process will be described in detail below.

  FIG. 7 is a flowchart showing an example of the operation of the first estimation process. FIG. 8 shows an example of a security leak confirmation screen. When the process of step S203 described above is completed, the processing unit 202 acquires file identification information from the information storage unit 203 (step S301). More specifically, the processing unit 202 designates any one of the agent departments, and acquires file identification information associated with the designated agent department. Next, the processing unit 202 designates any one different from the previously designated agent affiliation, and acquires file identification information associated with the designated other agent affiliation. For example, in the processing target information shown in FIG. 6, when the processing unit 202 first designates “development unit” as the agent department, the processing unit 202 includes four pieces of file identification information “product design drawing” and “development progress management”. , “Product planning document” and “Research report” are acquired. Next, when the processing unit 202 designates “general affairs department” as a department to which the agent belongs, the processing unit 202 includes five file identification information “product design drawing”, “development progress management”, “product plan document”, “customer list”. ”And“ Claim handling cases ”.

When the processing in step S301 is completed, the processing unit 202 then counts the number of common file identification information types CNT _AB (step S302). Here, A represents the previously assigned agent affiliation, and B represents another agent affiliation. As described above, the processing unit 202 has four file identification information “product design drawing”, “development progress management”, “product plan”, and “research report” based on different agent departments and five file identification information “ When the product design drawing, “development progress management”, “product plan”, “customer list”, and “complaint handling case” are acquired, the number of types CNT _AB as the number of types of common file identification information CNT _AB “3” Is counted. That is, the processing unit 202 determines the file sharing status based on the number of types CNT _AB .

When the process of step S302 is completed, then the processing unit 202 the number of kinds _{CNT AB} is determined whether a first determination threshold value theta ₁ or more (step S303). When the processing unit 202 determines that the number of types CNT _AB is equal to or greater than the first determination threshold θ ₁ (step S303: YES), the processing unit 202 estimates that the risk of confidential leakage is low (step S304). For example, when θ ₁ “3” is set as the first determination threshold, if the processing unit 202 counts the number of types CNT _AB “3” in the process of step S302, the development unit and the general affairs unit regularly file. The possibility that unintentional disclosure has occurred is low, and it is estimated that there is a low risk that confidential information will be leaked only between departments.

On the other hand, if the processing unit 202 which is the number of kinds _{CNT AB} is determined that the first determination threshold value theta less than ₁ (step S303: NO), then the processing unit 202 is the number of kinds _{CNT AB} smaller than the first determination threshold value theta ₁ determining whether a second determination threshold value theta ₂ or more (step S305). If the processing unit 202 which is the number of kinds _{CNT AB} was determined to be the second determination threshold value theta ₂ or more (step S305: YES), estimates that there is a leakage of confidential information risk (step S306).

For example, when the processing unit 202 designates the sales department and the general affairs department in the process of step S301, since the file identification information “customer list” and “claim complaint case” are common, the processing part 202 is processed in step S302. counting the number of types _{CNT AB} "2" as the number of types _{CNT AB} of common file identification information. Therefore, when θ ₂ “2” is set as the second determination threshold, if the processing unit 202 counts the number of types CNT _AB “2” in the process of step S302, the sales department and the general affairs department share the file. It is judged that this is a relatively rare case, and there is a possibility that unintended disclosure may have occurred, and it is estimated that there is a risk that confidential information will be leaked outside the departments.

On the other hand, if the processing unit 202 which is the number of kinds _{CNT AB} is determined that the second determination threshold value θ less than ₂ (step S305: NO), estimates that there is a high security breaches risk (step S307). For example, when the processing unit 202 designates the research unit and the development unit in the process of step S301, the file identification information “research report” is common, and therefore, in the process of step S302, the processing unit 202 uses the common file identification information. counting the number of types of _{CNT AB} "1" as the number of types of _{CNT AB.} Therefore, when θ ₂ “2” is set as the second determination threshold, if the processing unit 202 counts the number of types CNT _AB “1” in the process of step S302, the research unit and the development unit share the file. It is judged that there is rarely, and it is highly probable that an unintended disclosure has occurred, and it is estimated that there is a high risk that confidential information will leak outside the department.

  When the processing unit 202 repeats the processing from step S301 to S307 and estimates the possibility of the security risk of the files held by the management terminal 110 and the non-management terminal 120 of each department, as shown in FIG. A confirmation screen is displayed (step S308). On the security leak confirmation screen, it is possible to visually check the relationship between the risk of security leak, the department name sharing the file, and the file identification information. Note that the processing unit 202 does not need to execute the process of step S308 until the process from steps S301 to S307 is performed to classify the risk of leakage of confidential information contained in the file.

  As described above, according to the first embodiment, the management server 200 includes the communication unit 201 and the processing unit 202. The communication unit 201 stores the file identification information collected from the non-management terminal 120 by each of the management terminals 110 when the access to the non-management terminal 120 tried based on the IP address generated by each of the plurality of different management terminals 110 is successful. Obtained from the management terminal 110. Then, the processing unit 202 estimates the confidentiality of files having common identification information based on the number of types of identification information common to the management terminals 110. Thereby, the management state of the file can be confirmed. In particular, even when a confidential information file exists in the non-management terminal 120 that is not under the management of an administrator or the like, the file can be found and the public status of the file can be confirmed.

(Second Embodiment)
Subsequently, a second embodiment of the present case will be described with reference to FIGS. 9 and 10. FIG. 9A is a flowchart illustrating a part of the operation of the management server 200. FIG. 9B is a flowchart illustrating an example of the second estimation process. FIG. 10 is an example of an access restriction estimation screen. In the first embodiment, as described with reference to FIG. 5, the processing unit 202 executes the first estimation process after executing the process of step S <b> 203, but in the second embodiment, FIG. ), The second estimation process is executed instead of the first estimation process (step S205). The second estimation process is a process for estimating access restrictions on files. More specifically, it is processing for estimating which department can access the file and which department cannot access the file. For example, the second estimation process may be paraphrased as a process for estimating the setting state of access control information for a file. The second estimation process will be described in detail below.

  When the processing in step S203 described above is completed, the processing unit 202 acquires the agent department and file identification information from the information storage unit 203 (step S311). When the processing of step S311 is completed, the processing unit 202 then classifies the agent department to each file identification information (step S312), and displays an access restriction estimation screen as shown in FIG. 10 (step S313). With the access restriction estimation screen, it is possible to visually recognize the relationship between the file identification information and the department that can access the file to which the file identification information is assigned.

  In particular, as described with reference to FIG. 6, the non-management terminal 120 installed in the development department has the first file with the file identification information “product design drawing”, the file identification information “development progress management”. The second file assigned and the third file assigned the file identification information “product plan” are stored. As shown in FIG. 10, the second file and the third file can be accessed by the management terminal 110 installed in the development department and the management terminal 110 installed in the general affairs department, but the first file has the development department. In addition to the general affairs department, the management terminal 110 installed in the sales department and the management terminal 110 installed in the research department can also be accessed. For this reason, it can be estimated that the access restriction for the sales department and the research department is not set in the first file.

  As described above, according to the second embodiment, the processing unit 202 can estimate access restrictions on files stored in the non-management terminal 120 using the processing target information stored in the information storage unit 203. Note that the processing unit 202 does not need to execute the process of step S313 until the processes of steps S311 and S312 are executed.

(Third embodiment)
Subsequently, a third embodiment of the present case will be described with reference to FIGS. 11 and 12. FIG. 11A is a flowchart illustrating a part of the operation of the management server 200. FIG. 11B is a flowchart illustrating an example of the distribution determination process. FIG. 12 shows an example of the confidential file distribution screen. In the first embodiment, as described with reference to FIG. 5, the processing unit 202 executes the first estimation process after executing the process of step S <b> 203, but in the third embodiment, FIG. ), A distribution determination process is executed instead of the first estimation process (step S206). The distribution determination process is a process for determining the distribution status of files distributed in the management system S. The distribution determination process will be described in detail below.

  When the processing in step S203 described above is completed, the processing unit 202 acquires a successful access department and file identification information from the information storage unit 203 (step S321). When the processing in step S321 is completed, the processing unit 202 then classifies successful access departments by file identification information (step S322), and displays a confidential file distribution screen as shown in FIG. 12 (step S323). With the confidential file distribution screen, the relationship between the file identification information and the department representing the location of the file to which the file identification information is assigned can be visually recognized.

  As described above, according to the third embodiment, the processing unit 202 can determine the distribution status of the files stored in the non-management terminal 120 using the processing target information stored in the information storage unit 203. Note that the processing unit 202 does not need to execute the process of step S323, but only executes the processes of steps S321 and S322.

The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to the specific embodiments according to the present invention, and various modifications are possible within the scope of the gist of the present invention described in the claims.・ Change is possible. For example, when a fuzzy hash value is used as the file identification information, in order to utilize the advantage of the fuzzy hash value, it is desirable to expand the compressed file and then acquire the fuzzy hash value for the contents of the file. In the first embodiment described above, the number of types CNT _AB is used, but the number of file identification information acquired instead of the number of types may be used. Furthermore, the processing unit 202 may execute the first estimation process, the second estimation process, and the distribution determination process described above in parallel without executing them independently.

In addition, the following additional notes are disclosed regarding the above description.
(Appendix 1) Files collected by each of the first terminal devices from the second terminal device when the access to the second terminal device attempted based on the IP address generated by each of a plurality of different first terminal devices is successful. An acquisition unit that acquires the identification information from the first terminal device, and a processing unit that estimates the confidentiality of the file having the common identification information based on the number of identification information common to the first terminal devices; A file status confirmation device.
(Additional remark 2) The said process part determines the sharing condition of the file which has the said common identification information based on the number of the identification information common between the said 1st terminal devices, Based on the determined sharing condition, The file status confirmation apparatus according to appendix 1, characterized by estimating a possibility that confidentiality of files having common identification information is not secured.
(Additional remark 3) When the number of the identification information common between the said 1st terminal devices is more than a 1st determination threshold value, the said process part may not ensure the confidentiality of the file which has the said common identification information The file status confirmation apparatus according to appendix 1 or 2, wherein the file status confirmation apparatus is estimated to be low.
(Additional remark 4) The said process part is the confidentiality of the file which has the said common identification information, when the number of the common identification information between said 1st terminal devices is less than the 2nd determination threshold value smaller than the said 1st determination threshold value The file status confirmation apparatus according to appendix 3, wherein it is estimated that there is a high possibility that the file is not secured.
(Supplementary Note 5) Files collected by each of the first terminal devices from the second terminal device when the access to the second terminal device attempted based on the IP address generated by each of the plurality of different first terminal devices is successful The computer executes the process of obtaining the identification information of the file from the first terminal device and estimating the confidentiality of the file having the common identification information based on the number of identification information common to the first terminal devices. To check file status.
(Additional remark 6) The process which estimates the confidentiality determines the sharing situation of the file which has the said common identification information based on the number of the identification information common between said 1st terminal devices, and uses the judged sharing situation. 6. The file status confirmation method according to appendix 5, wherein the possibility that the confidentiality of the file having the common identification information is not secured is estimated based on the file.
(Additional remark 7) The process which estimates the said confidentiality ensures the confidentiality of the file which has the said common identification information, when the number of the identification information common between said 1st terminal devices is more than a 1st determination threshold value. The file status confirmation method according to appendix 5 or 6, wherein it is estimated that there is a low possibility that the file has not been created.
(Supplementary Note 8) The process for estimating the confidentiality includes the common identification information when the number of identification information common to the first terminal devices is less than a second determination threshold smaller than the first determination threshold. The file status confirmation method according to appendix 7, wherein it is estimated that there is a high possibility that the confidentiality of the file is not secured.
(Supplementary Note 9) Files collected by each of the first terminal devices from the second terminal device when the access to the second terminal device attempted based on the IP address generated by each of the plurality of different first terminal devices is successful Is obtained from the first terminal device, and based on the number of common identification information among the first terminal devices, the confidentiality of the file having the common identification information is estimated, and processing is executed on the computer File status check program.

S management system 110 management terminal 120 non-management terminal 200 management server 201 communication unit 202 processing unit 203 information storage unit

Claims (6)

The identification information of the file collected from the second terminal device by each of the first terminal devices when the access to the second terminal device tried based on the IP address generated by each of the plurality of different first terminal devices is successful. An obtaining unit for obtaining from the first terminal device;
A processing unit that estimates the confidentiality of a file having the common identification information based on the number of common identification information between the first terminal devices;
A file status confirmation device. The processing unit determines a sharing status of a file having the common identification information based on the number of identification information common to the first terminal devices, and the common identification information based on the determined sharing status Estimate the possibility that the confidentiality of files with
The file status confirmation apparatus according to claim 1, wherein: When the number of pieces of identification information common to the first terminal devices is equal to or greater than a first determination threshold, the processing unit estimates that it is unlikely that confidentiality of the file having the common identification information is not ensured. To
The file status confirmation apparatus according to claim 1 or 2, characterized by the above. When the number of pieces of identification information common to the first terminal devices is less than a second determination threshold smaller than the first determination threshold, the processing unit ensures the confidentiality of the file having the common identification information. Presumably not,
The file status confirmation apparatus according to claim 3, wherein: The identification information of the file collected from the second terminal device by each of the first terminal devices when the access to the second terminal device tried based on the IP address generated by each of the plurality of different first terminal devices is successful. Obtained from the first terminal device,
Estimating the confidentiality of a file having the common identification information based on the number of identification information common to the first terminal devices;
A file status check method in which the computer executes the process. The identification information of the file collected from the second terminal device by each of the first terminal devices when the access to the second terminal device tried based on the IP address generated by each of the plurality of different first terminal devices is successful. Obtained from the first terminal device,
Estimating the confidentiality of a file having the common identification information based on the number of identification information common to the first terminal devices;
A file status check program that causes a computer to execute processing.

Images