JP2007334577A - File management device and file management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To much more accurately and efficiently execute processing to an object file in automatically executing prescribed processing to an arbitrary file. <P>SOLUTION: In a file management device 100, an event acquisition part 111 acquires an event which occurs when the status of a file stored in a file server or the like changes, and a file determination part 112 determines whether or not a file corresponding to the event is a plane sentence, and when it is determined that the file is a plane sentence, an information writing part 113 writes object file information for designating the file as the object of encryption processing in a storage device 101, and when the object file information is written in the storage device 101, a processing execution part 114 executes encryption processing to the file designated by the object file information. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a file management apparatus and a file management program. The present invention particularly relates to a mechanism for detecting a file operation event.

  Prevents information leakage in a file management system that encrypts files (also referred to as “documents”) and saves them on a file server, etc., and manages usage rights such as viewing, editing, copying, saving, printing availability, and viewing deadlines. In order to do this, there is one that always encrypts a file on the disk even during use of the file (for example, see Patent Document 1). In this file management system, for example, when monitoring a plurality of folders (also referred to as “directories”) on a file server, the target folder is periodically searched. Specifically, all target folders are periodically searched, and if a file different from the previous one is created, the target file is automatically encrypted.

Some backup systems that perform file backup processing not only periodically perform backup processing, but also automatically perform backup processing according to the occurrence status of jobs and operations on files (for example, Patent Document 2 and 3).
JP 2006-99348 A JP-A-9-160818 JP 2005-346219 A

  As described above, in the conventional file management system, since it is necessary to periodically search all target folders, the load on the server side to be searched increases if the target includes subfolders (also referred to as “subdirectories”). There was a problem that the performance decreased. In addition, there is a problem that necessary processing is delayed from necessary timing. Therefore, it was not possible to target a large number of unspecified folders. For example, it is not possible to designate all subfolders of an arbitrary folder as a target of encryption processing, and it is necessary to designate subfolders one by one.

  In the conventional backup system, it is necessary to always store the occurrence status of jobs and operations. Therefore, there is a problem that the performance decreases when the number of occurrences of jobs and operations is large. Further, in order to perform backup processing more efficiently, it is necessary to store the generation status of jobs and operations in more detail, and there is a problem that a large storage area must be secured.

  An object of the present invention is, for example, to perform a process more reliably and efficiently on a target file when a predetermined process is automatically performed on an arbitrary file. To do.

The file management apparatus according to the present invention is:
An event acquisition unit that acquires an event that occurs when the state of the file changes as an event corresponding to the file by the processing device;
When an event is acquired by the event acquisition unit, the processing device determines whether a predetermined process is being performed on a file corresponding to the event, and designates the file as a target of the predetermined process A file determination unit for determining whether the target file information exists in the storage device;
When the file determination unit determines that the predetermined process has not been performed on the file, and the file determination unit determines that the target file information does not exist in the storage device, Writing the target file information into the storage device, and when the file determination unit determines that the target file information exists in the storage device, an information writing unit that overwrites the target file information;
An information confirmation unit for confirming whether or not the target file information exists in the storage device every predetermined period;
A processing execution unit that, when the information confirmation unit confirms that the target file information exists in the storage device, performs the predetermined processing on the file specified by the target file information by the processing device; It is characterized by.

The file management device further includes:
When the predetermined processing is performed on the file by the processing execution unit, an information deletion unit is provided that deletes target file information specifying the file from the storage device.

The file determination unit determines whether the type of file corresponding to the event is a predetermined type when the event is acquired by the event acquisition unit,
When the file determination unit determines that the file type is the predetermined type, the information writing unit stores target file information for specifying the file as a target of the predetermined process in the storage device. It is characterized by writing.

When the event is acquired by the event acquisition unit, the file determination unit determines whether the file corresponding to the event is plain text,
The information writing unit writes, in the storage device, target file information that designates the file as a target of the predetermined process when the file determination unit determines that the file is plain text,
When the target file information is written by the information writing unit, the processing execution unit performs an encryption process on a file specified by the target file information.

  The event acquisition unit acquires an event corresponding to each of a plurality of files stored in an arbitrary folder and all subfolders of the folder.

A file management program according to the present invention includes:
An event acquisition procedure provided by the computer, an event acquisition procedure for acquiring an event that occurs when the state of the file changes by the processing device as an event corresponding to the file,
When a file determination unit included in the computer acquires an event by the event acquisition procedure, the file determination unit determines whether or not a predetermined process is being performed on a file corresponding to the event, and the file is A file determination procedure for determining whether or not target file information to be specified as a target for a predetermined process exists in the storage device;
The information writing unit included in the computer determines that the predetermined processing has not been performed on the file by the file determination procedure, and the target file information exists in the storage device by the file determination procedure. If it is determined that the target file information does not exist, the target file information is written into the storage device, and if it is determined by the file determination procedure that the target file information exists in the storage device, the target file information is overwritten. Information writing procedure;
An information confirmation unit provided in the computer, an information confirmation procedure for confirming whether the target file information exists in the storage device for each predetermined period;
When the processing execution unit included in the computer confirms that the target file information exists in the storage device by the information confirmation procedure, the processing device performs the predetermined processing on the file specified by the target file information. The processing execution procedure is executed by a computer.

  In the present invention, in the file management apparatus, when the event is acquired by the event acquisition unit, the file determination unit determines whether the predetermined process is performed on the file corresponding to the event, It is determined whether target file information to be specified as a target exists in the storage device. The information writing unit writes the target file information in the storage device when the file determination unit determines that the predetermined process has not been performed on the file and the target file information does not exist in the storage device. When the file determination unit determines that the target file information exists in the storage device, the target file information is overwritten. The information confirmation unit confirms whether the target file information exists in the storage device every predetermined period. When the processing execution unit confirms that the target file information exists in the storage device by the information confirmation unit, the processing execution unit performs a predetermined process on the file specified by the target file information. As a result, it is possible to carry out the processing more reliably and efficiently for the files that are subject to the predetermined processing while keeping the storage area used for event monitoring and management small. Become.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

Embodiment 1 FIG.
FIG. 1 is a block diagram showing a configuration of a file management apparatus 100 according to the present embodiment.

  1, the file management apparatus 100 includes an event acquisition unit 111, a file determination unit 112, an information writing unit 113, a processing execution unit 114, an information confirmation unit 115, and an information deletion unit 116. The event acquisition unit 111, the file determination unit 112, and the information writing unit 113 provide an event monitoring service 201 described later. The processing execution unit 114, the information confirmation unit 115, and the information deletion unit 116 provide a periodic protection service 202 described later. In addition, the file management apparatus 100 includes hardware devices such as a storage device 101, a processing device 102, an input device 103, and an output device 104 (or these hardware devices are connected to the file management device 100). The hardware device is used by each unit of the file management device 100. For example, the processing device 102 is used for each unit of the file management device 100 to perform calculation, processing, reading, writing, and the like of data and information. The storage device 101 is used to store the data and information. The input device 103 is used to input the data and information, and the output device 104 is used to output the data and information.

  The event acquisition unit 111 acquires, by the processing device 102, an event that occurs when the state of a file stored in a file server or the like changes as an event corresponding to the file. By specifying an arbitrary folder, the user can set a file stored in the folder as a target from which the event acquisition unit 111 acquires an event. That is, the user can designate an arbitrary folder and set the folder as a target folder for encryption processing, as will be described later. Further, the user can specify not only an arbitrary folder as a target folder but also a subfolder of the specified folder as a target folder. That is, the user can make each of the plurality of files stored in an arbitrary folder and all the subfolders of the folder the event acquisition unit 111 acquires events. For this purpose, the event acquisition unit 111 inputs the folder designation information indicating whether the user designates a folder and whether the user includes a subfolder of the folder with the input device 103. Then, the event acquisition unit 111 selects an event that occurs when there is a file whose state has changed among a plurality of files stored in the folder indicated by the folder designation information and all subfolders of the folder, Acquired as an event corresponding to the file.

  When an event is acquired by the event acquisition unit 111, the file determination unit 112 performs a predetermined process on a file corresponding to the event (a file having a state change that has triggered the event). It is determined by the processing device 102 whether or not it exists. In the present embodiment, the file determination unit 112 determines whether or not an encryption process is performed on the file as a predetermined process. That is, the file determination unit 112 determines whether or not the file is plain text. If the file is plain text, the file has not been encrypted. If the file is not plain text, the file has been encrypted. Here, the encryption process is an example of a predetermined process, and the file determination unit 112 may determine whether another process (for example, a process of adding an electronic signature) is performed on the file. In addition, when an event is acquired by the event acquisition unit 111, the file determination unit 112 determines whether target file information specifying a file corresponding to the event exists in the storage device 101. The target file information will be described later. In addition, when an event is acquired by the event acquisition unit 111, the file determination unit 112 determines whether the type of file corresponding to the event is a predetermined type. As will be described later, the file type is, for example, a Microsoft (registered trademark) / Office document (a file such as Word, Excel, PowerPoint (registered trademark)) (hereinafter referred to as an “Office document”). The user can designate an arbitrary file type as a target file for encryption processing or the like. For this purpose, the file determination unit 112 inputs file designation information indicating the type of file designated by the user through the input device 103. Then, the file determination unit 112 determines whether the file type corresponding to the event acquired by the event acquisition unit 111 is the file type indicated by the file designation information.

  When the file determination unit 112 determines that the predetermined process has not been performed on the file corresponding to the event acquired by the event acquisition unit 111, the information writing unit 113 sets the file as a target for the predetermined process. The target file information to be specified is written into the storage device 101. In the present embodiment, when the file determination unit 112 determines that the file is plain text, the information writing unit 113 stores target file information for designating the file as a target for encryption processing in the storage device 101. Write. In addition, the information writing unit 113, when the file determination unit 112 determines that the target file information specifying the file corresponding to the event acquired by the event acquisition unit 111 does not exist in the storage device 101, the target The file information is written in the storage device 101. When the file determination unit 112 determines that the target file information exists in the storage device 101, the target file information is overwritten. For example, when the target file information is stored in one table of the database as an example of the storage device 101, the target file information can be stored as one record for each file. In this example, when the record of the target file information of a certain file is not stored in the database, the information writing unit 113 newly adds the record, and when the record is stored in the database , That record will be updated. In addition, when the file determination unit 112 determines that the file type corresponding to the event acquired by the event acquisition unit 111 is a predetermined type, the information writing unit 113 processes the file with a predetermined process (main book). In the embodiment, target file information designated as a target of encryption processing is written in the storage device 101.

  The information confirmation unit 115 confirms whether or not the target file information exists in the storage device 101 at regular intervals. The user can specify this period. For this purpose, the information confirmation unit 115 inputs period designation information indicating a period designated by the user through the input device 103. Then, the information confirmation unit 115 confirms whether the target file information exists in the storage device 101 for each period indicated by the period designation information.

  When the target file information is written in the storage device 101 by the information writing unit 113, the processing execution unit 114 performs predetermined processing (in this embodiment, encryption on the file specified by the target file information). Processing) is performed by the processing device 102. In addition, when the information confirmation unit 115 confirms that the target file information exists in the storage device 101, the processing execution unit 114 performs predetermined processing (in the present embodiment, on the file specified by the target file information). Encryption processing) is performed by the processing device 102.

  The information deletion unit 116 deletes the target file information specifying the file from the storage device 101 when a predetermined process (encryption process in the present embodiment) is performed on the file by the processing execution unit 114. To do. For example, as described above, when the target file information is stored as one record for each file, the information deletion unit 116 deletes the record of the target file information specifying the encrypted file, or records history information (log). Move to another table (may be another database table).

  In the present embodiment, the event acquisition unit 111 detects a change in the state of an Office document for each file as an example of a file. An Office document is an example of a file type, and other types of files (for example, text files, PDF files, image files, video files) may be targeted, and multiple types of files may be targeted. May be. When processing (predetermined processing) according to the state change is performed on the Office document on the file server, it is necessary to accurately detect the state change for each file. Therefore, the event acquisition unit 111 detects an event related to a change in the state of a file at an OS level using an API (Application, Program, Interface) provided from the OS (operating system). However, depending on the API used, the event acquisition unit 111 may acquire a plurality of events (recognize that a plurality of events have occurred) in response to a change in one state. For example, when an API provided from a Windows (registered trademark) OS is used, an event for a change in the state of an Office document differs depending on the type of file and the operation that is the basis of the change in the state of the file. On the other hand, a plurality of events may be acquired (occurred) or different events may be acquired (occurred). For example, as shown in FIG. 2, on the Office application, the acquisition form (event generation form) by which the event acquisition unit 111 acquires an event is different for each operation. In FIG. 2, “X file” indicates an Excel file, “W file” indicates a Word file, and “P file” indicates a PowerPoint (registered trademark) file. Acquire “change” event depending on the type and operation of file (application) when “Open”, “Close”, “Overwrite”, and “Save As” are performed for each Office document. The number of times (number of occurrences) is different as shown in FIG. Further, for example, as shown in FIG. 3, even when an Office document is operated by an explorer (“E application”) or a DOS command (“D application”), the “change” event is changed depending on the type and operation of the application. The number of acquisitions (number of occurrences) is different.

  File state changes (save, copy, move, etc.) can be monitored at the driver layer. However, since such a method is monitoring at the same level as the OS, maintenance after the method is once introduced is not easy. Basically, all files are targeted, and it is difficult to target only a specific state change of an Office document as in the present embodiment. Therefore, it is possible to detect an event associated with a change in the state of the file and process the file using the acquired event itself. However, in such a system, as described above, it is impossible to appropriately cope with the fact that the number of event occurrences varies depending on the type and operation of the file (application). For example, when the state of the file changes, the same event occurs multiple times (as shown in FIG. 2, if “P file” is “save as” (save as), “change” In this method, the target file is processed a plurality of times, resulting in unnecessary processing being executed.

  Therefore, in the present embodiment, the file management apparatus 100 organizes events having different generation forms according to file types and states for each file and each state, manages them on a database, and executes them according to states (predetermined The processing is performed at a necessary timing based on information on the database (target file information). For example, when an Office document on a file server is automatically encrypted at the time of file creation, the present embodiment accurately detects a state change of “file creation” and creates a target file. Only when it is necessary, encryption can be performed. Therefore, even when there are a plurality of folders and subfolders such as a file server, encryption processing can be performed only on necessary files at a necessary timing. As a result, it becomes possible to cope with the operation of a file server in which subfolders normally exist without lowering the performance, and it is possible to realize a system that improves user convenience. Furthermore, by adopting the method as described above, it is possible to realize an application that realizes state change monitoring in the application layer on the server, and the introduction and maintenance can be facilitated.

  FIG. 4 is a conceptual diagram showing processing of the file management system 200 according to the present embodiment.

  In the file management system 200, the event monitoring service 201 is provided by the event acquisition unit 111, the file determination unit 112, and the information writing unit 113 of the file management apparatus 100. The event monitoring service 201 is an application (part of a file management program) that organizes and manages events by file and state described above using the protected document information table 203 (an example of the storage device 101) of the database. This application can be implemented as a service on Windows (registered trademark) Server, for example. The periodic protection service 202 is provided by the processing execution unit 114, the information confirmation unit 115, and the information deletion unit 116 of the file management apparatus 100. The periodic protection service 202 periodically acquires information for each file and each state (target file information 204) registered in the protected document information table 203 of the database by the event monitoring service 201, and encrypts the target file. Application (part of the file management program). This application can also be implemented as a service on Windows (registered trademark) Server, for example.

The file management apparatus 100 first starts the event monitoring service 201 and the periodic protection service 202, respectively. In the event monitoring service 201, event monitoring of the target folder is started. Thereafter, the following processing is executed.
(1) The user creates (saves or copies) the file “file A1” in the monitoring target folder “folder A” on the file server 300. In addition, “file A11” and “file A12” are created in the subfolders “folder A-1” and “folder A-2” of the monitoring target folder, respectively.
(2) In the event monitoring service 201, the event acquisition unit 111 detects the event (1). At this time, the events of the target folders “Folder A”, “Folder A-1”, and “Folder A-2” are monitored events for both file generation and overwrite copy.
(3) When the file determination unit 112 determines that the target documents “file A1”, “file A11”, and “file A12” are not encrypted, the information writing unit 113 indicates the target document (full path) and the state ( New creation), the target file information 204 is newly registered in the protection target document information table 203 of the database. At this time, when a plurality of events occur for one file, the target file information 204 related to the same file in the protection target document information table 203 of the database is overwritten (updated). During this process or while the user is operating the file, the target record of the database is locked so that it cannot be accessed from the periodic protection service 202. After the process is completed, the event waits again.
(4) In the periodic protection service 202, the information confirmation unit 115 searches for an encryption target file in the protection target document information table 203 on the database, and the processing execution unit 114 encrypts the target file (“encrypt”). This is also called "protecting"). At this time, if the target file is being operated and encryption cannot be performed, the record on the protection target document information table 203 is locked, so the target file is excluded from the encryption target of the periodic protection service 202 and next time. After confirming that the record is not locked after the periodic operation of, encryption is performed.
(5) In the periodic protection service 202, after completing the encryption processing in (4), the information deletion unit 116 stores the record (target file information 204) for the target file on the protection target document information table 203 in the storage device 101. After being stored in the history information table (not shown), the record for the target file on the protection target document information table 203 is deleted. A history information table (not shown) has the same file structure as that of the protection target document information table 203, and can be used as a history of confirmation of the normal end of the encryption process.

  After the above (5), when the user performs “overwrite saving” on the same file again, the event acquisition unit 111 acquires the event in the event monitoring service 201, but the file determination unit 112 has already Since it is determined that the file is an encrypted file, the information writing unit 113 does not register it in the protected document information table 203. On the other hand, when the user creates a new file and saves it with the same path and the same file name as (1) by “overwrite”, an event is acquired as in (2), and (3) to (5) The process is implemented.

  In the above (1), when the state of the file changes, the event may not occur at all (as shown in FIG. 2, even if “W file” is “overwritten”, the “change” event is Does not occur). In this case, in the above (2), another type of event is also acquired (when the “W file” is “overwritten”, a “create” event occurs).

  FIG. 5 is a flowchart showing processing of the file management system 200.

  First, in the file management apparatus 100, the event monitoring service 201 and the periodic protection service 202 are started (steps S101 and S201). In the event monitoring service 201, the event acquisition unit 111 transitions to an event occurrence waiting state (step S102).

  The user copies a plain text file to the folder monitoring target folder (step S301). When the file is copied, a “change” event is generated (step S302).

  The event acquisition unit 111 acquires a “change” event (step S103: event acquisition procedure). The file determination unit 112 determines whether the target document (the file copied in step S301) is plain text (step S104: part of the file determination procedure). If the target document is not plain text, the target document has already been encrypted, and the process returns to step S102. On the other hand, if the target document is plain text, the target document has not been encrypted yet, and the process proceeds to step S105. Then, the file determination unit 112 determines whether the target document is an Office document (an example of a predetermined type) based on, for example, the extension of the target document (step S105: part of the file determination procedure). As a precondition, here, files other than the Office document are not subject to encryption processing. Therefore, if the target document is not an Office document, the process returns to step S102. On the other hand, if the target document is an Office document, the process proceeds to step S106. Then, the file determination unit 112 determines whether or not the record (target file information 204) related to the target document exists in the protection target document information table 203 stored in the storage device 101 (step S106: one of the file determination procedures). Part). When the record related to the target document does not exist in the protection target document information table 203, the information writing unit 113 writes the record related to the target document as new information in the protection target document information table 203 (step S107: information writing). procedure). On the other hand, when the record related to the target document exists in the protection target document information table 203, the information writing unit 113 overwrites the record related to the target document (existing information in the protection target document information table 203) (step S107). : Information writing procedure).

  The information confirmation unit 115 periodically confirms whether or not a record (new information) relating to the target document exists in the protection target document information table 203 (step S202: information confirmation procedure). When the information confirmation unit 115 confirms that the record related to the target document exists in the protection target document information table 203, the processing execution unit 114 encrypts the target document (step S203: processing execution procedure). . The information deletion unit 116 writes the record (existing information) related to the encrypted target document in a history information table (not shown) stored in the storage device 101, and then stores the target document on the protection target document information table 203. Is deleted (step S204: information deletion procedure).

  Here, as an example of the target file information 204, the configuration of the protection target document information table 203 is shown in FIG.

  In FIG. 6, the “protection file number” is a unique number of the protection target file, that is, an identifier for uniquely identifying the target file. “File name” is the file name of the file to which the event corresponds. The “protected file name” is the file name of the encrypted file (in this example, when the file is encrypted, the encrypted file is saved with a different file name). “Error file name” is a file name of a file created when an error occurs during execution of the encryption process. In this example, “file name”, “protection file name”, and “error file name” are all represented by full paths. The “event” is information indicating the type of event (“change”, “create”, “rename”, etc.). “Initial event occurrence date and time” is the date and time when the event corresponding to the target file first occurred. “Last event occurrence date and time” is the date and time when the event corresponding to the target file last occurred. The “last protection execution date” is the date when the target file was last encrypted. In this example, “initial event occurrence date / time”, “last event occurrence date / time”, and “last protection execution date / time” are all recorded using the time of the file server 300. The “final protection execution result” is a flag registered so that the next encryption process can be performed when an error occurs during the execution of the encryption process. In this example, it is set to 0 when the encryption processing has not been performed (default), and is set to 1 when an error occurs during encryption. The “number of times protection is performed” is information indicating the number of times encryption processing has been performed (the number of retries), and is counted up only when an error occurs.

  In the example shown in FIG. 6, the items “file name”, “event”, “initial event occurrence date / time”, and “last event occurrence date / time” are recorded in the protected document information table 203 by the event monitoring service 201. The Specifically, the information writing unit 113 creates these items based on the information included in the event acquired by the event acquisition unit 111 and records them in the protected document information table 203. The other items are recorded in the protection target document information table 203 by the periodic protection service 202. Specifically, the processing execution unit 114 creates each item and records it in the protection target document information table 203 when the encryption process is executed or when an error occurs. Further, as described above, the information stored in the protection target document information table 203 is saved as a history information table (not shown), so that it can be used as a history such as confirmation of normal termination of the encryption process.

  In FIG. 5, as in step S302, for example, when the second and third events occur (steps S303 and S304) (as shown in FIG. 3, the file is copied by “E application”. ”Occurs, the“ change ”event occurs three times), and the file management apparatus 100 executes the processes after step S103. When the target document is encrypted by the periodic protection service 202 when the first event occurs, it is determined in step S104 that the target document is not plain text when the second and third events occur, and the event monitoring service 201 Will return to the event waiting state. On the other hand, when the second and third events occur due to the periodic activation timing of the periodic protection service 202, the target document is not encrypted by the periodic protection service 202, and the target document is stored in plain text. Sometimes. At this time, if the target file information 204 is stored in the protection target document information table 203 by an amount corresponding to the event occurrence, useless encryption processing is generated by the periodic protection service 202. Therefore, it is checked whether or not the corresponding target file information 204 exists in the protection target document information table 203 in the process of step S106, and if it does not exist, it is written as new information (step S107), and if it exists, the existing information is overwritten. By operating as described above (step S108), it is possible to efficiently perform processing without causing unnecessary processing.

  Similarly to step S301, for example, when the user starts Excel, edits the file, and then saves the file with a different name, a second event occurs (as shown in FIG. 2). When the “X file” is “saved and saved”, the “change” event occurs twice).

  FIG. 7 is a diagram illustrating an example of hardware resources of the file management apparatus 100.

  In FIG. 7, the file management apparatus 100 is composed of a computer and other hardware resources. The file management apparatus 100 includes a display device 901 having a display screen of a CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display), a keyboard 902 (K / B), a mouse 903, an FDD 904 (Flexible Disk Drive), and a CDD 905. (Compact / Disc / Drive) and hardware resources such as a printer device 906 are provided, and these are connected by a cable or a signal line.

  The file management apparatus 100 also includes a CPU 911 (Central Processing Unit) (also called “central processing unit”, “arithmetic unit”, “microprocessor”, “microcomputer”, “processor”) that executes a program. ing. The CPU 911 is an example of the processing device 102. The CPU 911 includes a ROM 913 (Read / Only / Memory), a RAM 914 (Random / Access / Memory), a communication board 915, a display device 901, a keyboard 902, a mouse 903, an FDD 904, a CDD 905, a printer device 906, and a magnetic disk. It is connected to the device 920 and controls these hardware devices. Instead of the magnetic disk device 920, a storage medium such as an optical disk device or a memory card reader / writer may be used.

  The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device 101. The communication board 915, the keyboard 902, the FDD 904, and the like are examples of the input device 103. The communication board 915, the display device 901, the printer device 906, and the like are examples of the output device 104.

  The communication board 915 is connected to a LAN or the like. The communication board 915 is not limited to the LAN, and may be connected to the Internet, a WAN (wide area network) such as ISDN (Integrated Services, Digital, Network).

  The magnetic disk device 920 stores an operating system 921, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922. The program group 923 stores programs that execute functions described as “˜unit” and “˜means” in the description of the present embodiment. The program is read and executed by the CPU 911. The file group 924 includes data and information described as “˜data”, “˜information”, “˜ID (IDentifier)”, “˜flag”, “˜result” in the description of this embodiment. Signal values, variable values, and parameters are stored as items of “˜file”, “˜database”, and “˜table”. The “˜file”, “˜database”, and “˜table” are stored in a storage medium such as a disk or a memory. Data, information, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for processing (operation) of the CPU 911 such as calculation / control / output / printing / display. Data, information, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during processing of the CPU 911 such as extraction, search, reference, comparison, calculation, control, output, printing, and display. Is remembered.

  In the block diagrams and flowcharts described in the description of this embodiment, the arrows indicate mainly input and output of data and signals. Data and signals are stored in a memory such as a RAM 914, a flexible disk (FD) of the FDD 904, and a CDD 905. Recording is performed on a recording medium such as a compact disk (CD), a magnetic disk of the magnetic disk device 920, other optical disks, a mini disk (MD), and a DVD (Digital Versatile Disc). Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In the description of the present embodiment, what is described as “to part” and “to means” may be “to circuit”, “to device”, and “to device”, and “to step”. , “˜step”, “˜procedure”, and “˜treatment”. That is, what is described as “˜unit” and “˜means” may be realized by firmware stored in the ROM 913. Alternatively, it may be realized only by software, or only by hardware such as an element, a device, a board, and wiring, or a combination of software and hardware, and further by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, flexible disk, optical disk, compact disk, minidisk, or DVD. This program is read by the CPU 911 and executed by the CPU 911. In other words, the program causes the computer to function as “to part” and “to means” described in the description of the present embodiment. Alternatively, the procedure or method of “˜unit” and “˜means” described in the description of the present embodiment is executed by a computer.

  Further, in the configuration diagram of the file management system 200 according to the present embodiment shown in FIG. 4, one file management device 100 and one file server 300 are shown, but the file management device 100 and the file server 300 are In addition to each being configured as a single computer, the file management apparatus 100 and the file server 300 may be configured as a single computer (that is, the file management system 200 is implemented as a single computer). . Further, one (one) file management apparatus 100 is configured to manage file information of two or more (plurality) of file servers 300 (that is, the file management system 200 includes one file management apparatus 100 and one file management apparatus 100). It is also possible to include a plurality of file servers 300).

  As described above, in the present embodiment, in the file management apparatus 100, when the file determination unit 112 acquires an event by the event acquisition unit 111, a predetermined process is performed on the file corresponding to the event. If the information writing unit 113 determines that the predetermined process is not performed on the file by the file determination unit 112, target file information that designates the file as a target of the predetermined process 204 is written in the storage device 101, and when the target file information 204 is written by the information writing unit 113, the processing execution unit 114 performs a predetermined process on the file specified by the target file information 204. As a result, it is possible to more reliably and efficiently process files that are subject to predetermined processing. It is possible to carry out.

  In the present embodiment, when an event is acquired by the event acquisition unit 111, the file determination unit 112 determines whether the target file information 204 that designates a file corresponding to the event exists in the storage device 101. When the information writing unit 113 determines that the target file information 204 does not exist in the storage device 101 by the file determination unit 112, the information writing unit 113 writes the target file information 204 to the storage device 101, and the file determination unit 112 When it is determined that the target file information 204 exists in the storage device 101, the storage area used for event monitoring and management can be reduced by overwriting the target file information 204. .

  In addition, as described above, depending on the application, the event acquisition unit 111 may acquire the corresponding event multiple times for a single user operation (change in one state) (the corresponding event occurs multiple times). However, there is a problem in that the same process occurs unnecessarily a plurality of times in a method of simply acquiring an event and performing a predetermined process according to the event. In order to solve the problem, when it is determined that the target file information 204 exists in the storage device 101, the target file information 204 is overwritten, and the information confirmation unit 115 confirms the target file information 204 and performs processing. The execution unit 114 is configured to execute one predetermined process (encryption process in the present embodiment) for one event by executing the process.

  In the present embodiment, the information confirmation unit 115 confirms whether the target file information 204 exists in the storage device 101 for each predetermined period, and the processing execution unit 114 applies the target to the storage device 101 by the information confirmation unit 115. When it is confirmed that the file information 204 exists, a predetermined process is performed on the file specified by the target file information 204 by the processing device 102, whereby a plurality of files that are targets of the predetermined process are processed. The processing can be performed collectively.

  In the present embodiment, the information deletion unit 116 deletes the target file information 204 specifying the file from the storage device 101 when a predetermined process is performed on the file by the processing execution unit 114. It is possible to further reduce the storage area used for event monitoring and management.

  In addition, as described in the present embodiment using an example, the periodic protection service 202 including the processing execution unit 114, the information confirmation unit 115, and the information deletion unit 116, the event acquisition unit 111, the file determination unit 112, the information By configuring the event monitoring service 201 including the writing unit 113 as a separate service, each service can be operated asynchronously in a predetermined period. Further, by configuring as a separate service, there is an advantage that the maintainability of each service program is improved. In addition, the information writing unit 113 writes a record (target file information 204) for the target file on the protection target document information table 203 stored in the storage device 101, the processing execution unit 114 overwrites it, and the information deletion unit 116 When deleting the record from the protected document information table 203, the record such as the normal end confirmation of the encryption process can be confirmed or utilized by writing the record into the history information table stored in the storage device 101. It becomes possible to do.

  In the present embodiment, when an event is acquired by the event acquisition unit 111, the file determination unit 112 determines whether the type of file corresponding to the event is a predetermined type, and the information writing unit 113 However, when the file determination unit 112 determines that the file type is the predetermined type, the target file information 204 that designates the file as a target for the predetermined process is written in the storage device 101, thereby The types can be limited.

  In the present embodiment, when an event is acquired by the event acquisition unit 111, the file determination unit 112 determines whether the file corresponding to the event is plain text, and the information writing unit 113 determines whether the file is When the unit 112 determines that the file is plain text, the target file information 204 that designates the file as a target for the predetermined process is written in the storage device 101, and the processing execution unit 114 is used by the information writing unit 113. When the target file information 204 is written, the information specified by the target file information 204 is encrypted, so that information leakage can be prevented more reliably.

  In the present embodiment, the event acquisition unit 111 acquires an event corresponding to each of a plurality of files stored in an arbitrary folder and all subfolders of the folder, thereby providing a highly convenient and flexible service. Can be provided.

1 is a block diagram illustrating a configuration of a file management apparatus according to a first embodiment. It is a table | surface which shows an example of the kind of file and the event acquisition frequency (occurrence frequency) for every operation. It is a table | surface which shows an example of the kind of application and the event acquisition frequency (occurrence frequency) for every operation. FIG. 3 is a conceptual diagram illustrating processing of the file management system according to the first embodiment. 4 is a flowchart showing processing of the file management system according to the first embodiment. It is a table | surface which shows an example of object file information. 3 is a diagram illustrating an example of hardware resources of a file management apparatus according to Embodiment 1. FIG.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 File management apparatus, 101 Storage apparatus, 102 Processing apparatus, 103 Input apparatus, 104 Output apparatus, 111 Event acquisition part, 112 File determination part, 113 Information writing part, 114 Processing execution part, 115 Information confirmation part, 116 Information deletion Part, 200 file management system, 201 event monitoring service, 202 periodic protection service, 203 protection target document information table, 204 target file information, 300 file server, 901 display device, 902 keyboard, 903 mouse, 904 FDD, 905 CDD, 906 Printer device, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 magnetic disk device, 921 operating system, 923 program group, 924 file group.

Claims (6)

An event acquisition unit that acquires an event that occurs when the state of the file changes as an event corresponding to the file by the processing device;
When an event is acquired by the event acquisition unit, the processing device determines whether a predetermined process is being performed on a file corresponding to the event, and designates the file as a target of the predetermined process A file determination unit for determining whether the target file information exists in the storage device;
When the file determination unit determines that the predetermined process has not been performed on the file, and the file determination unit determines that the target file information does not exist in the storage device, Writing the target file information into the storage device, and when the file determination unit determines that the target file information exists in the storage device, an information writing unit that overwrites the target file information;
An information confirmation unit for confirming whether or not the target file information exists in the storage device every predetermined period;
A processing execution unit that, when the information confirmation unit confirms that the target file information exists in the storage device, performs the predetermined processing on the file specified by the target file information by the processing device; A file management device characterized by the above. The file management device further includes:
2. The information deletion unit according to claim 1, further comprising: an information deletion unit that deletes target file information specifying the file from the storage device when the predetermined processing is performed on the file by the processing execution unit. File management device. The file determination unit determines whether the type of file corresponding to the event is a predetermined type when the event is acquired by the event acquisition unit,
When the file determination unit determines that the file type is the predetermined type, the information writing unit stores target file information for specifying the file as a target of the predetermined process in the storage device. The file management apparatus according to claim 1, wherein writing is performed. When the event is acquired by the event acquisition unit, the file determination unit determines whether the file corresponding to the event is plain text,
The information writing unit writes, in the storage device, target file information that designates the file as a target of the predetermined process when the file determination unit determines that the file is plain text,
The said process execution part implements an encryption process with respect to the file which the said target file information designates, when the target file information is written by the said information writing part. File management device.   The file management apparatus according to claim 1, wherein the event acquisition unit acquires an event corresponding to each of a plurality of files stored in an arbitrary folder and all subfolders of the folder. An event acquisition procedure provided by the computer, an event acquisition procedure for acquiring an event that occurs when the state of the file changes by the processing device as an event corresponding to the file,
When a file determination unit included in the computer acquires an event by the event acquisition procedure, the file determination unit determines whether or not a predetermined process is being performed on a file corresponding to the event, and the file is A file determination procedure for determining whether or not target file information to be specified as a target for a predetermined process exists in the storage device;
The information writing unit included in the computer determines that the predetermined processing has not been performed on the file by the file determination procedure, and the target file information exists in the storage device by the file determination procedure. If it is determined that the target file information does not exist, the target file information is written into the storage device, and if it is determined by the file determination procedure that the target file information exists in the storage device, the target file information is overwritten. Information writing procedure;
An information confirmation unit provided in the computer, an information confirmation procedure for confirming whether the target file information exists in the storage device for each predetermined period;
When the processing execution unit included in the computer confirms that the target file information exists in the storage device by the information confirmation procedure, the processing device performs the predetermined processing on the file specified by the target file information. A file management program for causing a computer to execute a processing execution procedure.

Images