Data erasure device, data erasure system and data erasure method

The data erasing device and system address the issue of incomplete file deletion by systematically identifying and deleting residual files, thereby reducing security risks and information leakage.

JP7586850B2Active Publication Date: 2024-11-19HITACHI LTD
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2022057546
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-03-30
Publication Date
2024-11-19
Estimated Expiration
2042-03-30

AI Technical Summary

Technical Problem

Existing data erasure systems fail to effectively identify and delete residual files, leading to security risks due to incomplete deletion and potential information leakage, especially when operation logs are insufficient.

Method used

A data erasing device and system that identifies residual files not included in permission or deletion lists, adds them to a deletion target list, and ensures their deletion before device shutdown, with optional administrator evaluation and impact assessment.

Benefits of technology

Prevents omissions in data erasure and reduces information leakage by systematically identifying and deleting residual files, enhancing security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007586850000001
    Figure 0007586850000001
  • Figure 0007586850000002
    Figure 0007586850000002
  • Figure 0007586850000003
    Figure 0007586850000003
Patent Text Reader

Abstract

To prevent failure in erasure to reduce an information leakage risk by recognizing and erasing remaining files by a data eraser.SOLUTION: A list of files stored in a storage device is acquires as a list of remaining files, and files included in neither survival permission list data nor erasure object list data in the list of remaining files are determined as new additional files to be additionally erased, and the files to be additionally erased are added to the erasure object list data to update the erasure object list data, and the files to be erased which are registered in the erasure object list data are erased after the end of the use of an activated application.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a data erasure device, a data erasure system, and a data erasure method. [Background technology]

[0002] Companies and other organizations implement security measures to reduce security risks for business devices, such as terminals used by employees for work, to prevent the business data stored on the business devices from being used illegally in the event of theft or loss.

[0003] One method for reducing security risks is to erase business data stored in business equipment. Patent Document 1 describes that it is possible to recognize the existence of data that has been stored in the information processing terminal since it was stored by acquiring files stored in the information processing terminal and an operation log in the information processing terminal from the information processing terminal, and outputting an alert according to the elapsed time from the storage timing of the acquired file, which is specified based on the acquired operation log. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-92544 A Summary of the Invention [Problem to be solved by the invention]

[0005] Patent Document 1 is premised on the acquisition of operation logs, and there is an issue that if operation logs are not acquired or are insufficient, no alert will be given even if data remains stored, making it difficult to recognize its existence.

[0006] In addition, there is no mention of how to reduce the risk of leakage of remaining files by simply issuing an alert when the existence of remaining files is recognized, which is insufficient to ensure security.

[0007] An object of the present invention is to prevent missing deletions and reduce the risk of information leaks by identifying and erasing remaining files in a data erasure device. [Means for solving the problem]

[0008] A data erasure device according to one aspect of the present invention is a data erasure device for a user device having a processing device for performing a predetermined process and a storage device in which predetermined files are stored, the processing device having a data erasure unit and an application launch unit, the storage device storing remaining permission list data in which remaining permission files are described and erasure target list data in which files to be erased are described, the data erasure unit acquiring a list of the files stored in the storage device as a remaining file list, The method is characterized in that a file that is not included in either the remaining permission list data or the erasure target list data from the obtained remaining file list is determined to be a newly added additional file to be erased, the additional file to be erased is added to the erasure target list data to update the erasure target list data, the application launch unit launches the application after updating of the erasure target list data is completed, and the data erasure unit erases the file to be erased that is listed in the updated erasure target list data after use of the launched application is terminated. Effect of the Invention

[0009] According to one aspect of the present invention, in a data erasure device, remaining files can be identified and erased, thereby preventing omissions in erasure and reducing the risk of information leakage. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of an overall configuration of a data erasure device according to a first embodiment of the present invention. [Diagram 2] FIG. 13 is a diagram illustrating an example of a configuration of remaining permission list data according to the first embodiment of the present invention. [Diagram 3] FIG. 13 is an example of a diagram for explaining a configuration of erasure target list data in the first embodiment of the present invention. [Figure 4] 5 is a flowchart illustrating an example of an operation of the data erasure device according to the first embodiment of the present invention. [Diagram 5] FIG. 11 is a diagram illustrating an example of an overall configuration of a data erasure system according to a second embodiment of the present invention. [Figure 6] FIG. 11 is a diagram illustrating an example of a configuration of a management device according to a second embodiment of the present invention. [Figure 7] FIG. 11 is a diagram illustrating an example of a configuration of a user device according to a second embodiment of the present invention. [Figure 8] FIG. 11 is a diagram illustrating an example of a configuration of remaining permission list data in the second embodiment of the present invention. [Figure 9] FIG. 11 is a diagram illustrating an example of a configuration of erasure target list data according to the second embodiment of the present invention. [Figure 10] FIG. 11 is a diagram illustrating an example of a configuration of user device list data according to the second embodiment of the present invention. [Figure 11] 10 is a flowchart illustrating an example of an operation of a data erasure system according to a second embodiment of the present invention. [Figure 12] FIG. 11 is a diagram illustrating an example of an overall configuration of a data erasure system according to a third embodiment of the present invention. [Figure 13] FIG. 11 is a diagram illustrating an example of a configuration of a management device according to a third embodiment of the present invention. [Figure 14] FIG. 11 is a diagram illustrating an example of a configuration of a user device according to a third embodiment of the present invention. [Figure 15] FIG. 13 is a diagram illustrating an example of a configuration of remaining permission list data in the third embodiment of the present invention. [Figure 16] FIG. 13 is a diagram illustrating an example of a configuration of erasure target list data according to the third embodiment of the present invention. [Figure 17] FIG. 13 is a diagram illustrating an example of a configuration of erasure permission / prohibition determination list data according to the third embodiment of the present invention. [Figure 18] FIG. 13 is a diagram illustrating an example of a configuration of remaining file list data according to the third embodiment of the present invention. [Figure 19] FIG. 13 is a diagram illustrating an example of a configuration of user device list data according to the third embodiment of the present invention. [Figure 20] FIG. 13 is a diagram illustrating an example of a configuration of evaluation request list data according to the third embodiment of the present invention. [Figure 21] 13 is a flowchart illustrating an example of an overall operation of a data erasure system according to a third embodiment of the present invention. [Figure 22] 13 is a flowchart illustrating an example of a part of the operation of a data erasure system according to a third embodiment of the present invention. [Figure 23] FIG. 13 is a diagram illustrating an example of an evaluation start request screen interface according to the third embodiment of the present invention. [Figure 24] FIG. 13 is a diagram illustrating an example of an evaluation input request screen interface according to the third embodiment of the present invention. [Diagram 25] 13 is a flowchart illustrating an example of a part of the operation of a data erasure system according to a third embodiment of the present invention. [Figure 26] 13 is a diagram illustrating an example of an erasure judgment request interface according to the third embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to FIGS. EXAMPLES

[0012] First, a data erasing device according to a first embodiment of the present invention will be described with reference to Figures 1 to 4. In the first embodiment, a list of files remaining in a user device used by a user after the user device is started is obtained, and a list of files to be erased is generated by combining the list of files permitted to remain, and the files to be erased are erased before the user device is shut down, thereby ensuring that no files not included in the list of files permitted to remain remain after the user device is shut down.

[0013] First, the configuration of a data erasure device according to a first embodiment of the present invention will be described with reference to FIGS.

[0014] FIG. 1 is a schematic diagram showing the overall configuration of the first embodiment. The user device 10 is a device used by a user 11. The user device 10 is composed of a processor 12, a memory 13, an input / output device 14, a storage device 15, an internal signal line 16, a monitor 17, a keyboard 18, and a mouse 19. The processor 12 is a device that processes programs. The storage device 15 is a hard disk or a non-volatile memory, and is a device that stores programs and data. The memory 13 is a storage device for storing programs to be executed and temporarily storing data. The input / output device 14 is a device that controls output to the monitor 17 and input from the keyboard 18 and the mouse 19. The storage device 15 stores programs and data for realizing the data erasure device in the first embodiment.

[0015] As programs, an OS (Operating System) program 100, an erasure program 101, and an application program 104 are stored. As data, remaining permission list data 102 and erasure target list data 103 are stored. The OS program 100 on the storage device 15 is loaded into the memory 13 and executed. The OS program 100 controls the input / output device 14, loads data from the storage device 15 into the memory 13, and so on. The OS program 100 also loads the erasure program 101 and the application program 104 from the storage device 15 into the memory 13 and executes them. The application program 104 stores application data in an application data area 105.

[0016] The processor 12, which is a processing device, functions as a "data erasure unit" by loading an erasure program 101 from the storage device 15 via the OS program 100 into the memory 13 and executing it. The processor 12, which is a processing device, also functions as an "application startup unit" by loading an application program 104 from the storage device 15 via the OS program 100 into the memory 13 and executing it.

[0017] 2 is a diagram for explaining the configuration of the remaining permission list data 102 shown in FIG. 1. The remaining permission list data 102 is composed of fields of a remaining permission ID 201 and a remaining permission target path 202. The remaining permission ID 201 is a field in which a unique identifier is written for the path of a file or folder that is a remaining permission target. The remaining permission target path 202 is a field in which a path of a file or folder that is a remaining permission target corresponding to the remaining permission ID 201 is written. In the organization, a remaining permission path is registered in the remaining permission list data 102 before the user 11 starts using the user device 10.

[0018] Fig. 3 is a diagram for explaining the configuration of the erasure target list data 103 shown in Fig. 1. The erasure target list data 103 is composed of fields of an erasure target ID 301 and an erasure target path 302. The erasure target ID 301 is a field in which an identifier that is unique to the path of a file or folder to be erased is written.

[0019] The erasure target path 302 is a field for describing the path of a file or folder to be erased corresponding to the erasure target ID 301. When the user 11 starts using the user device 10, the contents of the erasure target list data 103 are updated by the erasure program 101. In the organization, the initial value of the path to be erased may be registered in the erasure target list data 103 before the user 11 starts using the user device 10.

[0020] Next, the operation of the data erasure device according to the first embodiment of the present invention will be described with reference to FIG. 4 is a flowchart explaining the operation from when the user 11 starts up the user device 10, performs a task using an application, to when the user shuts down the user device 10. During this operation, remaining files are identified and erased before shutting down the user device 10. First, the user 11 turns on the power of the user device 10 (S401). In the user device 10, the OS program 100 starts up. The OS program 100 starts up the erasing program 101 (S402).

[0021] The erasure program 101 acquires a list of files stored in the storage device 15 of the user device 10 as a remaining file list (S403). Then, from the acquired remaining file list, it determines files that are not included in either the remaining permission list data 102 or the erasure target list data 103 as new erasure targets to be added (S404), adds the new erasure targets to the erasure target list data 103 (S405), and notifies the OS program 100 of the completion of the update (S406).

[0022] The OS program 100 controls the order of programs to be started after the user device 10 is started, and prevents the application program 104 from starting until the erasure program 101 has completed updating the erasure target list data 103. After that, the user performs an operation to start an application (S407), and starts the application program 104 (S408). The user performs a task using the application program 104 (S409), and then performs an operation to shut down the user device 10 (S410).

[0023] The OS program 100, which has received the shutdown operation of the user device 10, issues a shutdown instruction to the erasure program 101 (S411). The erasure program 101 erases all files to be erased that are listed in the erasure target list data 103 (S412), and responds to the OS program 100 that the erasure has been completed (S413). After that, the OS program 100 turns off the power of the user device 10 (S414).

[0024] As described above, according to the first embodiment of the present invention, when the user device 10 is started up, remaining files are checked, and any remaining files that are not included in either the remaining permission list data 102 or the erasure target list data 103 are added to the erasure target list data 103 and can be erased before the user device 10 is shut down, thereby reducing security risks due to remaining data in the user device 10. EXAMPLES

[0025] Next, a data erasure system according to a second embodiment of the present invention will be described with reference to Fig. 5 to Fig. 11. In the second embodiment, a list of files remaining in a user device used by a user after the user device is started is obtained, a list of files to be erased is generated by combining with a list of files permitted to remain, the list of files to be erased is collected from one or more user devices to a management device, merged to generate data on the list of files to be erased, and applied to one or more user devices to erase files remaining before the user device is shut down, thereby making it possible to use the data on the list of files to be erased generated from one or more user devices to make it possible ...

[0026] First, the configuration of a data erasure system according to a second embodiment of the present invention will be described with reference to FIGS.

[0027] 5 is a schematic diagram for explaining the overall configuration of a data erasure system in Example 2. A management device 50 is connected to a network 52. A user device 51 is connected to the network 52 and communicates with the management device 50. An administrator 53 can view and edit data in the management device 50. A user 54 is a user of the user device 51.

[0028] 6 is a configuration diagram explaining the configuration of the management device 50. The management device 50 is composed of a processor 61, a memory 62, a communication device 63, an input / output device 64, a storage device 65, an internal signal line 66, a monitor 67, a keyboard 68, and a mouse 69. The processor 61 is a device that processes programs. The storage device 65 is a hard disk or non-volatile memory, etc., and is a device that stores programs and data. The memory 62 is a storage device for storing programs to be executed and temporary data.

[0029] The input / output device 64 is a device that controls output to the monitor 67 and input from the keyboard 68 and mouse 69. The communication device 63 is a device that performs network communication with other devices. The storage device 65 stores programs and data for implementing the data erasure system in the second embodiment. As programs, an OS program 600 and a management program 601 are stored. As data, remaining permission list data 602, erasure target list data 603, and user device list data 604 are stored. The OS program 600 on the storage device 65 is loaded into the memory 62 and executed. The OS program 600 controls the input / output device 64 and loads data from the storage device 65 into the memory 62. The OS program 600 also loads the management program 601 from the storage device 65 into the memory 62 and executes it.

[0030] The processor 61, which is a processing device, functions as a "management unit" by loading a management program 601 from the storage device 65 into the memory 62 via the OS program 600 and executing the program.

[0031] 7 is a diagram illustrating the configuration of the user device 51. The user device 51 is composed of a processor 71, a memory 72, a communication device 73, an input / output device 74, a storage device 75, an internal signal line 76, a monitor 77, a keyboard 78, and a mouse 79. The storage device 75 stores programs and data for implementing the data erasure system in the second embodiment. As programs, an OS program 700, an erasure program 701, and an application program 402 are stored.

[0032] As data, remaining permission list data 602 and erasure target list data 603 are stored. An OS program 700 on the storage device 75 is loaded into the memory 72 and executed. The OS program 700 loads an erasure program 701 and an application program 702 from the storage device 75 into the memory 72 and executes them. The application program 702 stores application data in an application data area 703.

[0033] The processor 71, which is a processing device, functions as a "data erasure unit" by loading an erasure program 701 from the storage device 75 into the memory 72 via the OS program 700 and executing the program. The processor 71, which is a processing device, also functions as an "application startup unit" by loading an application program 702 from the storage device 75 into the memory 72 via the OS program 700 and executing the program.

[0034] Fig. 8 is a diagram for explaining the configuration of the remaining permission list data 602 shown in Fig. 6. The remaining permission list data 602 is composed of fields of a remaining permission ID 801 and a remaining permission target path 802. The remaining permission ID 801 is a field in which a unique identifier is written for the path of a file or folder that is a remaining permission target. The remaining permission target path 802 is a field in which the path of a file or folder that is a remaining permission target corresponding to the remaining permission ID 801 is written.

[0035] Before the data erasure system starts operation, the administrator 53 operates the management device 50 to register a list of files that are permitted to remain in the remaining permission list data 602. Furthermore, when the list of files that are permitted to remain is added, deleted, or changed after the data erasure system starts operation, the administrator 53 operates the management device 50 to change the contents of the remaining permission list data 602. The contents of the remaining permission list data 602 are transmitted to the user device 51 by the management program 601 and applied.

[0036] Fig. 9 is a diagram for explaining the configuration of the erasure target list data 603 shown in Fig. 6. The erasure target list data 603 is composed of fields of an erasure target ID 601 and an erasure target path 602. The erasure target ID 601 is a field in which an identifier that is unique to the path of a file or folder to be erased is written. The erasure target path 602 is a field in which the path of a file or folder to be erased corresponding to the erasure target ID 601 is written.

[0037] Before the data erasure system starts operation, the administrator 53 may operate the management device 50 and register an initial value of a list of files to be erased in the erasure target list data 603. The contents of the erasure target list data 603 are updated by the management program 601. The contents of the erasure target list data 603 are also transmitted by the management program 601 to the user device 51 and applied.

[0038] FIG. 10 is a diagram for explaining the configuration of the user device list data 604 shown in FIG. 6. The user device list data 604 is composed of fields of a user device ID 1001 and a user device name 1002. The user device ID 1001 is a field in which an identifier that is unique to the user device of an organization is described. The user device name 1002 is a field in which the name of the user device corresponding to the user device ID 1001 is described. Before the data erasure system starts operation, the administrator 53 operates the management device 50 to register a list of user devices in the user device list data 604. In addition, when a user device is added, deleted, or changed after the data erasure system starts operation, the administrator 53 operates the management device 50 to change the contents of the user device list data 604.

[0039] Next, the operation of the data erasure system according to the second embodiment of the present invention will be described with reference to FIG. 11 is a flowchart explaining the operation from when the user 54 starts up the user device 51, performs a task using an application, to when the user shuts down the user device 51. During this operation, remaining files are identified and transmitted to the management program, the list of files to be deleted is updated, and the remaining files are deleted before shutting down the user device 51. First, the user 54 turns on the power of the user device 51 (S1101).

[0040] In the user device 51, the OS program 700 is started. The OS program 700 starts the erasure program 701 (S1102). The erasure program 701 acquires a list of files stored in the storage device 75 of the user device 51 as a remaining file list (S1103). Then, from the acquired remaining file list, it determines files that are not included in either the remaining permission list data 602 or the erasure target list data 603 as new erasure targets to be added (S1104), and transmits the new erasure targets to be added to the management program 601 (S1105).

[0041] The management program 601 adds the received erasure target to be added to the erasure target list data 603 and updates it (S1106). The addition excludes those included in the erasure target paths already registered, thereby eliminating duplicate additions. The management program 601 sends the remaining permission list data 602 and the updated erasure target list data 603 to the erasure program 701 (S1107).

[0042] The erasure program 701 stores the received remaining permission list data 602 and erasure target list data 603 in the storage device 75 (S1108), and notifies the OS program 700 of the completion of the updates (S1109). The OS program 700 controls the order of programs to be started after the user device 51 is started, and prevents the application program 702 from starting until the erasure program 701 has completed updating the remaining permission list data 602 and the erasure target list data 603. Thereafter, the user 54 performs an operation to start an application (S1110), and starts the application program 702 (S1111).

[0043] The user 54 performs a task using the application program 702 (S1112), and then performs an operation to shut down the user device 51 (S1113). The OS program 700, which has received the shutdown operation from the user device 51, issues a shutdown instruction to the erasure program 701 (S1114). The erasure program 701 erases all files to be erased that are listed in the erasure target list data 603 (S1115), and responds to the OS program 700 that the erasure has been completed (S1116). The OS program 700 then turns off the power to the user device 51 (S1117).

[0044] As described above, according to the second embodiment of the present invention, when the user device 51 is started up, the remaining files are checked, and a list of remaining files that are not included in either the remaining permission list data 602 or the erasure target list data 603 is transmitted to the management server and updated to include files from other user devices. Then, the erasure target list data 603 updated to reflect the list of remaining files from one or more devices is applied to the user device 51, making it possible to erase the files before the user device 51 is shut down, thereby further reducing the security risk due to remaining data in the user device 51. EXAMPLES

[0045] Next, a data erasure system according to a third embodiment of the present invention will be described with reference to Figs. 12 to 26. In the third embodiment, a list of files remaining in a user device used by a user after the user device is started is grasped, a list of files to be erased is generated by combining with a list of files permitted to remain, the list of files to be erased is collected from one or more user devices to a management device, merged to generate erasure target list data, and applied to one or more user devices to erase files remaining before the user device is terminated, thereby making it possible to use the erasure target list data generated from one or more user devices to make it possible to make a state in which no files remain after the user device is terminated. Among these, before adding the erasure target to the erasure target list data, the user is asked to confirm whether there is an impact by applying erasure to some user devices, and it is determined whether to add the erasure target to the erasure target list data based on the result of the impact confirmation and the judgment of the administrator.

[0046] Third Embodiment First, the configuration of a data erasure system according to a third embodiment of the present invention will be described with reference to FIGS.

[0047] 12 is a schematic diagram illustrating the overall configuration of the data erasure system. A management device 120 is connected to a network 122. A user device 121 is connected to the network 122 and communicates with the management device 120. An administrator 123 can view and edit data in the management device 120. A user 124 is a user of the user device 121.

[0048] 13 is a configuration diagram explaining the configuration of the management device 120. The management device 120 is composed of a processor 131, a memory 132, a communication device 133, an input / output device 134, a storage device 135, an internal signal line 136, a monitor 137, a keyboard 138, and a mouse 139. The processor 131 is a device that processes programs.

[0049] The storage device 135 is a hard disk or non-volatile memory, and is a device for storing programs and data. The memory 132 is a storage device for storing programs to be executed and temporary data. The input / output device 134 is a device for controlling output to the monitor 137 and input from the keyboard 138 and mouse 139. The communication device 133 is a device for performing network communication with other devices. The storage device 135 stores programs and data for implementing the data erasure system in the third embodiment.

[0050] As programs, an OS program 1300 and a management program 1301 are stored. As data, remaining permission list data 1302, erasure target list data 1303, erasure permission / prohibition judgment list data 1304, remaining file list data 1305, and user device list data 1306 are stored. The OS program 1300 on the storage device 135 is loaded into the memory 132 and executed. The OS program 1300 controls the input / output device 134, loads data from the storage device 135 into the memory 132, and so on. The OS program 1300 also loads the management program 1301 from the storage device 135 into the memory 132 and executes it.

[0051] The processor 131, which is a processing device, functions as a "management unit" by loading a management program 1301 from the storage device 135 into the memory 132 via an OS program 1300 and executing the program.

[0052] 14 is a diagram illustrating the configuration of the user device 121. The user device 121 is composed of a processor 141, a memory 142, a communication device 143, an input / output device 144, a storage device 145, an internal signal line 146, a monitor 147, a keyboard 148, and a mouse 149. The storage device 145 stores programs and data for implementing the data erasure system in the third embodiment. As programs, an OS program 1400, an erasure program 1401, and an application program 1404 are stored.

[0053] The data stored are remaining permission list data 1302, erasure target list data 1303, and evaluation request list data 1402. An OS program 1400 on the storage device 145 is loaded into the memory 142 and executed. The OS program 1400 loads an erasure program 1401 and an application program 1402 from the storage device 145 into the memory 142 and executes them. The application program 1402 stores application data in an application data area 1403. The OS program 1400 also monitors the creation of files in the storage device 145, generates a log of file creation, and stores it in a file creation log data area 1405.

[0054] The processor 141, which is a processing device, functions as a "data erasure unit" by loading an erasure program 1401 from the storage device 145 via the OS program 1400 into the memory 142 and executing it. The processor 141, which is a processing device, also functions as an "application startup unit" by loading an application program 1403 from the storage device 145 via the OS program 1400 into the memory 142 and executing it.

[0055] Fig. 15 is a diagram for explaining the configuration of the remaining permission list data 1302 shown in Fig. 13. The remaining permission list data 1302 is composed of fields of a remaining permission ID 1501 and a remaining permission target path 1502. The remaining permission ID 1501 is a field in which a unique identifier is written for the path of a file or folder that is a remaining permission target. The remaining permission target path 1502 is a field in which the path of a file or folder that is a remaining permission target corresponding to the remaining permission ID 1501 is written.

[0056] Before the data erasure system starts operation, the administrator 123 operates the management device 120 to register a list of files permitted to remain in the remaining permission list data 1302. Furthermore, when the list of files permitted to remain is added, deleted or changed after the data erasure system starts operation, the administrator 123 operates the management device 120 to change the contents of the remaining permission list data 1302. The contents of the remaining permission list data 1302 are updated by the management program 1301. Furthermore, the contents of the remaining permission list data 1302 are transmitted by the management program 1301 to the user device 121 and applied.

[0057] Fig. 16 is a diagram for explaining the configuration of the erasure target list data 1303 shown in Fig. 13. The erasure target list data 1303 is composed of fields of an erasure target ID 1601 and an erasure target path 1602. The erasure target ID 1601 is a field in which an identifier that is unique to the path of a file or folder to be erased is described. The erasure target path 1602 is a field in which the path of a file or folder to be erased corresponding to the erasure target ID 1601 is described.

[0058] Before the data erasure system starts operation, the administrator 123 may operate the management device 120 and register an initial value of a list of files to be erased in the erasure target list data 1303. The contents of the erasure target list data 1303 are updated by the management program 1301. The contents of the erasure target list data 1303 are also transmitted by the management program 1301 to the user device 121 and applied.

[0059] Fig. 17 is a diagram for explaining the configuration of the erasure propriety judgment list data 1304 shown in Fig. 13. The erasure target list data 1304 is composed of fields of an erasure candidate ID 1701, an erasure candidate path 1702, a creating application name 1703, an evaluated user device (1) ID 1704, an evaluation result (1) 1705, an evaluated user device (2) ID 1706, and an evaluation result (2) 1707. The erasure candidate ID 1701 is a field in which a unique identifier is entered for the path of a file or folder that is a candidate for erasure.

[0060] The erasure candidate path 1702 is a field for describing the path of a file or folder that is a candidate for erasure corresponding to the erasure candidate ID 1701. The creating application name 1703 is a field for describing the name of the application that created the file or folder that is a candidate for erasure corresponding to the erasure candidate ID 1701. The evaluation user device (1) ID 1704 is a field for describing the user device ID of a user device that has requested or is currently requesting evaluation corresponding to the erasure candidate ID 1701.

[0061] The evaluation result (1) 1705 is a field in which the result of the evaluation requested to the user device 121 described in the evaluated user device (1) ID 1704 corresponding to the erasure candidate ID 1701 is described. In the third embodiment, in order to make it possible to request evaluation from two user devices 121, there are fields for an evaluated user device (2) ID 1706 and an evaluation result (2) 1707 as the second device in the combination of the evaluated user device ID and evaluation result. The contents of the erasure feasibility determination list data 1304 are updated by the management program 1301.

[0062] Fig. 18 is a diagram for explaining the configuration of the remaining file list data 1305 shown in Fig. 13. The remaining file list data 1305 is composed of fields of an erasure candidate ID 1801 and a storage path in management device 1802. The erasure candidate ID 1801 is a field in which an identifier that is unique to the path of a file or folder to be erased is described. The storage path in management device 1802 is a field in which a path in the management device in which a copy of a file or folder to be erased is stored in correspondence with the erasure candidate ID 1801 is described. The contents of the remaining file list data 1305 are updated by the management program 1301.

[0063] Fig. 19 is a diagram for explaining the configuration of the user device list data 1306 shown in Fig. 13. The user device list data 1306 is composed of fields of a user device ID 1901 and a user device name 1902. The user device ID 1901 is a field in which an identifier that is unique to the user device of an organization is described. The user device name 1902 is a field in which the name of the user device corresponding to the user device ID 1901 is described.

[0064] Before the data erasure system starts operation, the administrator 123 operates the management device 120 to register a list of user devices in the user device list data 1306. Furthermore, when a user device is added, deleted, or changed after the data erasure system starts operation, the administrator 123 operates the management device 120 to change the contents of the user device list data 1306.

[0065] Fig. 20 is a diagram for explaining the configuration of the evaluation request list data 1402 shown in Fig. 14. The evaluation request list data 1402 is composed of fields: erasure candidate ID 2001, erasure candidate path 2002, creating application name 2003, evaluation end date 2004, and evaluation status 2005. The erasure candidate ID 2001 is a field in which a unique identifier for the path of a file or folder that is a candidate for erasure is entered.

[0066] The erasure candidate path 2002 is a field for describing the path of a file or folder that is a candidate for erasure corresponding to the erasure candidate ID 2001. The creating application name 2003 is a field for describing the name of the application that created the file or folder that is a candidate for erasure corresponding to the erasure candidate ID 2001. The evaluation end date 2004 is a field for describing the date when the evaluation ends corresponding to the erasure candidate ID 2001. The evaluation status 2005 is a field for describing the evaluation status of the erasure candidate in the user device corresponding to the erasure candidate ID 2001. The contents of the evaluation request list data 1402 are updated by the erasure program 1401.

[0067] Next, the operation of the data erasure system according to the third embodiment of the present invention will be described with reference to FIGS.

[0068] 21 is a flowchart explaining the operation from when the user 124 starts up the user device 121, performs a task using an application, and shuts down the user device 121. During this operation, remaining files are identified and transmitted to the management program, a list of files to be deleted is updated, and the remaining files are deleted before shutting down the user device 121. First, the user 124 turns on the power of the user device 121 (S2101).

[0069] In the user device 121, the OS program 1400 is started. The OS program 1400 starts the erasure program 1401 (S2102). The erasure program 1401 acquires a list of files stored in the storage device 145 of the user device 121 as a remaining file list (S2103). Then, from the acquired remaining file list, it determines a file that is not included in either the remaining permission list data 1302 or the erasure target list data 1303 as a new file to be erased (S2104), acquires the path and file of the file to be added to be erased, and the name of the application that created the file to be erased from the log stored in the file creation log data area 1405, and transmits them to the management program 1301 (S2105).

[0070] The management program 1301 checks whether the path to be added and received as an erase target is already included in the erase feasibility judgment list data 1304. If the path is included, the contents of the evaluation user device (2) ID 1706 of the erase feasibility judgment list data 1304 are further checked, and if it is not registered, the user device ID of the user device 121 that sent the path is registered in the evaluation user device (2) ID 1706 of the erase feasibility judgment list data 1304, and "not started" is registered in the evaluation result (2) 1707. If the path is not included, a new row is added to the erase feasibility judgment list data 1304, a new erase candidate ID is assigned and registered in the erase candidate ID 1701, the transmitted path is registered in the erase candidate path 1702, the transmitted application name is registered in the creation application name 1703, the user device ID of the user device 121 that sent the path is registered in the evaluation user device (1) ID 1704, and "not started" is registered in the evaluation result (1) 1705 (S2106).

[0071] The management program 1301 transmits the remaining permission list data 1302 and the erasure target list data 1303 to the erasure program 701. Also, when adding to the evaluated user device (1) or (2) in S2106, the erasure candidate ID described in the erasure candidate ID 1701, the erasure candidate path described in the erasure candidate path 1702, and the creating application name described in the creating application name 1703 for the added erasure candidate are returned to the erasure program 701 as an evaluation request (S2107).

[0072] The erasure program 1401 saves the received remaining permission list data 1302 and erasure target list data 1303 in the storage device 145 (S2108), and when an evaluation request is received, adds a new row to the evaluation request list data 1402, enters the received erasure candidate ID, erasure candidate path, and creating application name, and updates the evaluation status to not yet started. After that, the erasure program 1401 performs evaluation processing (S2109). A flowchart of the evaluation processing S2109 is shown in Fig. 22.

[0073] Fig. 22 is a flowchart explaining the operation of the erasure program 1401 in cooperation with the management program 1301, from the start of evaluation of an erasure candidate that has not yet been started to the evaluation of an erasure candidate that has expired. In this operation, the operation of inquiring the user about the evaluation of an erasure candidate that has not yet been started and starting the evaluation after confirming it, and the operation of inquiring the user about the erasure impact for an erasure candidate whose evaluation period has expired, receiving the evaluation response, and registering it in the management program are performed. First, the erasure program 1401 checks the contents of the evaluation request list data 1402 (S2201) and checks whether there is an erasure candidate whose evaluation status 2005 is not started (S2202). If there is an erasure candidate that has not yet been started, the corresponding erasure candidate is presented to the user 124 on the evaluation request screen interface shown in Fig. 23 (S2203).

[0074] 23 is a diagram showing an evaluation start request screen interface that presents a request to the user to start evaluation of the erasure impact of an erasure candidate. The evaluation start request screen interface is composed of a title display area 2301 and an operation content display area 2302. The operation content display area 2302 displays the path of the erasure candidate, the name of the creating application, the evaluation expiration date, and a button for the user 124 to respond whether or not to cooperate. The evaluation end date is set to a date after the elapse of a period specified by the data erasure system or administrator, such as one week from now. The user 124 responds by pressing the button (S2204).

[0075] If the response to the evaluation start request is cooperation, the erasure program 1401 changes the evaluation status 2005 for the corresponding erasure candidate in the evaluation request list data 1402 to "under evaluation" and transmits the corresponding erasure candidate ID as an evaluation start notification to the management program 1301 (S2206). For the received erasure candidate ID, the management program 1301 updates the evaluation result of the corresponding user device ID in the erasure feasibility determination list data 1304 to "under evaluation" (S2207) and returns a notification of update completion to the erasure program 1401 (S2208).

[0076] Next, the erasure program 1401 checks the evaluation request list data 1402 to see if the date written in the evaluation expiration date 2004 has passed, thereby confirming whether there are any erasure candidates whose expiration date has passed (S2209), and if there are any erasure candidates whose expiration date has passed, the erasure program 1401 presents the corresponding erasure candidates to the user 124 in the evaluation input screen interface shown in FIG. 24 (S2210).

[0077] 24 is a diagram showing an evaluation input request screen interface that presents a request to the user to input an evaluation of the erasure impact of an erasure candidate. The evaluation input request screen interface is composed of a title display area 2401 and an operation content display area 2402. The operation content display area 2402 displays the path of the erasure candidate, the creating application name, and the evaluation expiration date, as well as radio buttons for inputting whether there is an impact and a text input area for the user 124 to evaluate and input the impact of the erasure. The user 124 answers by pressing a button or entering text (S2211).

[0078] After the user 124 inputs an evaluation, the erasure program 1401 deletes the corresponding erasure candidate from the evaluation request list data 1402, and then transmits the corresponding erasure candidate ID and the evaluation input content to the management program 1301 as the evaluation result (S2212). The management program 1301 updates the content of the erasure feasibility judgment list data 1304 corresponding to the received erasure candidate ID. If the sending user device 121 is one listed in the evaluated user device (1) ID 1704, it registers the received evaluation input content in evaluation result (1) 1705, and if it is one listed in the evaluated user device (2) ID 1706, it registers the received evaluation input content in evaluation result (2) 1707 (S2213).

[0079] Furthermore, when both evaluation result (1) 1705 and evaluation result (2) 1707 are registered rather than not started or being evaluated, list update processing is performed on the remaining permission data list 1302 and the erasure target data list 1303 for the corresponding erasure candidate (S2214). The flowchart of the list update processing S2214 is shown in FIG.

[0080] Fig. 25 is a flowchart explaining the operation of the management program 1301 in cooperation with the administrator 123 to update the remaining permission list data 1302 and the erasure target list data 1303 based on the evaluation result of the impact of erasure and the judgment result by the administrator. First, the management program 1301 checks the contents of the evaluation result (1) 1705 and evaluation result (2) 1707 in the erasure feasibility judgment list data 1304 for the relevant erasure candidate, and if neither has an impact, it adds the relevant erasure candidate to the erasure target list data 1303 (S2506). If either one has an impact, it presents the relevant erasure candidate to the administrator 123 on the erasure judgment request screen interface shown in Fig. 26 (S2502).

[0081] 26 is a diagram showing an erasure judgment request interface that presents the evaluation results of the erasure impact of erasure candidates and requests the administrator 123 to judge whether to erase them. The erasure judgment request interface is made up of a title display area 2601 and an operation content display area 2602. The operation content display area 2602 displays the path of the erasure candidate, the name of the creating application, the evaluation results, the storage path in the management device of the file of the erasure candidate, and a button with which the administrator 123 responds whether to erase them or not.

[0082] The administrator 123 opens the file indicated in the storage path in the managed device, checks the contents, and then performs a determination and responds (S2503).

[0083] If the answer to S2503 is "no deletion", the corresponding deletion candidate is added to the remaining permission list data 1302 (S2505), and the row of the corresponding deletion candidate is deleted from the deletion permission judgment list (S2507). If the answer to S2503 is "delete", the corresponding deletion candidate is added to the deletion target list data 1303 (S2506), and the row of the corresponding deletion candidate is deleted from the deletion permission judgment list (S2507).

[0084] When the list update process (S2214) is completed, the management program 1301 returns registration completion to the erasure program 1401 (S2215). The above is the operation from starting evaluation of unstarted erasure candidates to evaluating expired erasure candidates, as shown in Fig. 22. The updated remaining permission list data 1302 and erasure target list data 1303 are sent to and applied to all user devices.

[0085] As described above, according to the third embodiment of the present invention, when the user device 121 is started, the remaining files are checked, and the list of remaining files that are not included in either the remaining permission list data 1302 or the deletion target list data 1303 is transmitted to the management server and is updated by adding files including those from other user devices. When adding files, the effect of deletion is evaluated by one or more user devices, and it is determined whether to add files according to the evaluation results and the judgment of the administrator.

[0086] That is, if it is evaluated that there is no impact from erasure, it is added to the list of data to be erased, and if there is an impact from erasure, it is added to the list of data to be erased or the list of data permitted to remain, depending on the result of the administrator's judgment. Then, the list of data to be erased 1303 updated to reflect the list of one or more remaining files and taking into account the impact of erasure is applied to the user device 121, making it possible to erase the data before the user device 121 is shut down, and the security risk due to the remaining data in the user device 121 can be further reduced.

[0087] The above embodiment is a data erasure device that erases data stored in a device, and has a means for acquiring a list of data remaining in the device after the device is started as a remaining data list, a means for erasing data before the device is shut down using the remaining data list, and a means for inhibiting the start of an application until the acquisition of the list of data remaining in the device after the device is started is completed.

[0088] Also, a data erasure system for erasing data stored in a device includes a means for acquiring a list of data remaining in the device after the device is started as a remaining data list, a means for collecting the remaining data lists acquired by one or more devices in a management device, a means for creating an aggregated remaining data list by aggregating the collected remaining data lists and distributing the aggregated remaining data list to the devices, and a means for erasing data before the device is shut down using the aggregated remaining data list. Also includes a means for inhibiting the start of an application until acquisition of the list of data remaining in the device after the device is started is completed.

[0089] The data erasure system further comprises a means for evaluating the impact of erasing the remaining data and then determining whether to add the remaining data to the aggregated remaining data.The data erasure system further comprises a means for a user of the device to evaluate the impact of erasing the remaining data.The data erasure system further comprises a means for an administrator to determine whether to erase the remaining data.

[0090] According to the above embodiment, the data erasure device can identify and erase remaining files, thereby preventing omissions in erasure and reducing the risk of information leakage.

[0091] The present invention is not limited to the above-mentioned embodiment, and various modifications are possible within the scope of the gist. For example, in the third embodiment, the impact was evaluated using two user devices, but the number of devices may be increased to one or three or more. In the third embodiment, the administrator determines whether to erase the file, but the administrator may mechanically determine whether the remaining file contains a keyword. Furthermore, in the third embodiment, the end of the evaluation of the user is determined by the date, but the end of the evaluation of the user may be determined by other methods, such as the number of times the user device is started or the number of times an application is started from the start of the evaluation, or the time the application is used.

[0092] It is also possible to define a policy for determining what to erase that reflects the security policies of the organization. For example, if two or more people responded that the data erasure had no impact, then it can be added to the list of items to be erased, or even if there was an impact, all items can be added to the list of items to be erased, or the paths to be erased can be limited.

[0093] When evaluating the deletion, a backup may be made so that data can be restored immediately if there is an effect of data deletion. Furthermore, since the remaining file names and folder names on the user device may contain character strings that differ for each user device, such as the user name, the user device name, and the file creation time, it is possible to confirm and delete the remaining files after normalizing and matching the file names and folder names, assuming that files for the same purpose may have different file names and folder names between multiple user devices. In addition, in the system configuration diagrams of Figures 1, 6, 13, and 14, some or all of the programs and data may be stored in advance in storage device 15, storage device 65, storage device 135, and storage device 145, or may be introduced from a non-transitory storage medium or from an information processing device equipped with an external non-transitory storage device via a network. [Explanation of symbols]

[0094] 10 User Equipment 12 processors 15 Storage device 100 OS Programs 101 Erase Program 102 Remaining permit list data 103 List of data to be deleted 104 Application Programs 105 Application Data Area 50 Management equipment 51 User Equipment 61 processors 65 Storage device 600 OS Programs 601 Management Program 602 Remaining Permit List Data 603 List of data to be deleted 604 User device list data 71 Processor 75 Storage device 700 OS Program 701 Erase Program 702 Application Program 703 Application Data Area 120 Management equipment 121 User Equipment 131 processors 135 Storage device 1300 OS Program 1301 Management Program 1302 Remaining permit list data 1303 List of data to be deleted 1304 List of data for determining whether or not it can be deleted 1305 Remaining File List Data 1306 User device list data 1307 Remaining file data area 141 processors 145 Storage device 1400 OS Program 1401 Erasing Program 1402 Evaluation request list data 1403 Application Program 1404 Application Data Area 1405 File Creation Log Data Area

Claims

1. A data erasure device for a user device having a processing device that performs a predetermined process and a storage device in which a predetermined file is stored, The processing device includes: It has a data erasing unit and an application launching unit, The storage device includes: storing remaining permission list data in which remaining permission files are described and deletion target list data in which files to be deleted are described; The data erasure unit includes: Obtaining a list of the files stored in the storage device as a remaining file list; determining, from the obtained remaining file list, a file that is not included in either the remaining permission list data or the deletion target list data as a newly added additional deletion target file; adding the additional file to be deleted to the deletion target list data to update the deletion target list data; The application launch unit After the updating of the data list of the data to be erased is completed, an application is started, The data erasure unit includes: a data erasure device that erases the files to be erased that are listed in the updated list of files to be erased after the use of the launched application is terminated.

2. The data erasure unit includes:

2. The data erasure device according to claim 1, further comprising: a data erasure unit configured to erase the files to be erased that are listed in the updated list of files to be erased before the user device is powered off after the use of the launched application is terminated.

3. The remaining permission list data is The remaining permission identifier and the remaining permission target path corresponding to the remaining permission identifier are included, 2. The data erasure device according to claim 1, wherein the remaining permission target path describes a path of a file that is a remaining permission target corresponding to the remaining permission identifier.

4. The data to be erased is The data is composed of an erasure target identifier and an erasure target path corresponding to the erasure target identifier, 2. The data erasure device according to claim 1, wherein the erasure target path includes a path of a file to be erased corresponding to the erasure target identifier.

5. A data erasure system in which at least one user device and a management device are connected via a network, The user equipment, A computer system including a first processor for performing a predetermined process and a first storage device in which a predetermined file is stored, The management device includes: A second processing device that performs a predetermined process and a second storage device that stores a predetermined file, The first processing device of the user equipment, It has a data erasing unit and an application launching unit, The second processing device of the management device It has an administrative department. The first storage device of the user equipment includes: storing remaining permission list data in which remaining permission files are described and deletion target list data in which files to be deleted are described; The second storage device of the management device storing the remaining permission list data and the deletion target list data; The data erasure unit includes: Obtaining a list of the files stored in the first storage device as a remaining file list; determining, from the obtained remaining file list, a file that is not included in either the remaining permission list data or the deletion target list data as a newly added additional deletion target file, and transmitting the additional deletion target file to the management unit; The management unit adding the received additionally deleted file to the deletion target list data stored in the second storage device, updating the deletion target list data, and sending the updated deletion target list data to the data erasure unit; The data erasure unit includes: updating the erasure target list data stored in the first storage device based on the received erasure target list data; The application launch unit After the updating of the data list of the data to be erased is completed, an application is started, The data erasure unit includes: a data erasure system for erasing the files to be erased that are listed in the updated list of files to be erased after the use of the launched application is terminated.

6. The second storage device of the management device, Further storing user device list data in which the name of at least one of the user devices is described; The management unit aggregating the additional files to be deleted received for at least one of the user devices and adding them to the list of files to be deleted, thereby updating the list; The data erasure unit includes: updating the erasure target list data stored in the first storage device based on the erasure target list data received for each of the user devices; 6. The data erasure system according to claim 5, further comprising: erasing the files to be erased that are listed in the list of files to be erased that has been updated for each user device after the use of the application has ended.

7. The management unit 6. The data erasure system according to claim 5, wherein when the additional file to be erased is added to the data list of files to be erased, it is evaluated whether there is any adverse effect if the additional file to be erased is erased.

8. The management unit As a result of evaluating whether there is any impact if the additional files to be deleted are deleted, if it is determined that there will be no adverse effect even if the additional file to be deleted is deleted, the additional file to be deleted is added to the deletion target list data, and the deletion target list data is updated; The data erasure system according to claim 7, characterized in that if it is determined that erasing the additional file to be erased will have an impact, the additional file to be erased is added to the remaining permission list data and the remaining permission list data is updated.

9. The user equipment, further comprising an input / output device for displaying a predetermined evaluation screen; The management unit 8. The method according to claim 7, wherein the evaluation as to whether or not there is any adverse effect caused by erasing the additional files to be erased is performed based on an evaluation result input by a user via the evaluation screen. Data erasure system.

10. The management device includes: further comprising an input / output device for displaying a predetermined evaluation screen; The management unit 8. The data erasure system according to claim 7, wherein the evaluation as to whether there is no adverse effect caused by erasing the additional files to be erased is performed based on an evaluation result input by an administrator via the evaluation screen.

11. The data erasure unit, for each of the at least one user equipment, The data erasure system according to claim 5, further comprising: erasing the files to be erased that are listed in the updated list of files to be erased before the user device is powered off after the use of the launched application is terminated.

12. The remaining permission list data is The remaining permission identifier and the remaining permission target path corresponding to the remaining permission identifier are included, 6. The data erasure system according to claim 5, wherein the remaining permission target path describes a path of a file that is a remaining permission target corresponding to the remaining permission identifier.

13. The data to be erased is The data is composed of an erasure target identifier and an erasure target path corresponding to the erasure target identifier, 6. The data erasure system according to claim 5, wherein the erasure target path includes a path of a file to be erased corresponding to the erasure target identifier.

14. A data erasure method for a user device having a processing device that performs a predetermined process and a storage device in which a predetermined file is stored, comprising the steps of: The processing device includes: Execute a storing step, a data erasing step, and an application starting step; The storing step includes: storing in the storage device remaining permission list data in which remaining permission files are described and erasure target list data in which files to be erased are described; The data erasing step includes: acquiring a list of the files stored in the storage device as a remaining file list, determining from the acquired remaining file list that a file not included in either the remaining permission list data or the deletion target list data as an additional deletion target file to be newly added, and adding the additional deletion target file to the deletion target list data to update the deletion target list data; The application launch step includes: After the updating of the data list of the data to be erased is completed, an application is started, The data erasing step includes: a data erasure method for erasing data, the data being erased being stored in the updated list of files to be erased after the started application has been terminated;

15. The data erasing step includes: The data erasure method according to claim 14, characterized in that after use of the launched application is terminated, the files to be erased that are listed in the updated list data to be erased are erased before the user device is powered off.

Citation Information

Patent Citations

  • Imaging apparatus

    JP2003326777A

  • Recording and reproducing device, recording management method, recording medium, and program

    JP2007257648A

  • Server device, information sharing system, program, and recording medium

    JP2007293619A

  • Data management system, information processor and computer program

    JP2008250574A

  • Media player

    JP2009104709A