JP2017010424A - Data management device, data management method and data management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data management device etc., capable of strictly inhibiting user data from being written to a secondary storage device by an operation by a user and more effectively preventing the user data from leaking and so on.SOLUTION: A data management device 1 comprises: a drive device 17 which has a first folder where user data is disable to be written and a second folder where the user data is enabled to be written; a virtual drive D1 set as a storage destination of the user data written to the second folder; and a filter driver 21 which rejects a write request for the first folder of the drive device 17 when the write request is made, and encrypts and saves user data, which is to be written to the second folder at a write request to the second folder of the drive device 17, in the virtual drive D1 without writing the user data to the second folder when the write request is made.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a data management apparatus, a data management method, and a data management program for managing user data.

  Regardless of the type of computer (desktop type, notebook type, tablet type), user data is stored in a secondary storage device such as an HDD (hard disk drive) or SSD (solid state drive) provided in the computer. It is common. Here, user data refers to data created or edited by a user using an application, and is different from application data automatically created by the application. Examples of user data include document data, music data, image data, and moving image data.

  The user data stored in the secondary storage device of the computer may be leaked to a third party or deleted if the computer is stolen or lost. In order to eliminate such a risk, in recent computers, data written in the secondary storage device is not written in the secondary storage device, but a transfer destination designated in advance (for example, connected to a network). (Redirect function) is provided. In a computer in which the redirection function is used, the secondary storage device is controlled by the OS function (for example, group policy) so that the secondary storage device cannot be accessed from a standard file operation program (for example, Explorer) attached to the OS. Often all or a part of is invisible.

  Patent Document 1 below discloses a technique for preventing leakage and loss of confidential data by prohibiting writing to a secondary storage device and automatically collecting confidential data on a server. Specifically, in Patent Document 1 below, for writing to the secondary storage device, the memory of the computer is used as the primary cache, and the cache server connected to the network is used as the secondary cache to redirect the writing. Thereby, the differential data is automatically collected in the cache server without writing to the secondary storage device.

JP 2011-8813 A

  By the way, by making the secondary storage device invisible by the function of the OS described above, the user basically becomes unable to access the secondary storage device. Therefore, user data is saved in the secondary storage device by a user operation. The risk is greatly reduced. However, even if the secondary storage device is made invisible, it is difficult to completely prohibit writing to the secondary storage device, so the risk of leakage or loss of user data cannot be completely eliminated. There is.

  For example, if a file operation program other than the standard file operation program attached to the OS is used, the user can write user data to a secondary storage device that has been made invisible. When the user intentionally writes user data to the secondary storage device using such a file operation program, there is a risk of leakage or loss of user data due to theft or loss of the computer.

  Also, the setting of whether or not to make the secondary storage device invisible is performed by a user having administrator authority. For this reason, the user can freely decide whether or not to make the secondary storage device invisible on a computer in which the administrator authority is granted to a general user or a personally owned computer in which the company cannot restrict the administrator authority. Since it can be set, the user cannot be restricted from writing user data to the secondary storage device. Therefore, when user data is intentionally written in the secondary storage device visualized, there is a risk of leakage or loss of user data due to theft or loss of the computer.

  In addition, when the computer is connected to the network, access to some folders (for example, folders storing setting information for connecting to the network) provided in the secondary storage device may occur. There is sex. Since such a folder is necessary for network connection, it must be provided in the secondary storage device. In order to prevent leakage of information stored in such a folder, it is conceivable to encrypt the folder itself. However, only the user who encrypted the folder can basically decrypt the encrypted folder. Since this is not possible, there is a problem that the operation may be hindered.

  The present invention has been made in view of the above circumstances, and data management that can strictly prevent user data from being leaked by strictly prohibiting user data from being written to a secondary storage device by a user operation. An object is to provide an apparatus, a data management method, and a data management program.

In order to solve the above problems, a data management device according to the present invention includes a first folder (F1) in which user data cannot be written in a data management device (1, 2) that manages user data, and a user A non-volatile first storage device (17) having a second folder (F2) in which data can be written, and a first virtual drive (set as a storage destination of user data written in the second folder) D1) and when there is a write request for the first folder of the first storage device, the write request is rejected and there is a write request for the second folder of the first storage device In this case, a data processing unit (2) that encrypts user data written to the second folder in response to the write request and saves it in the first virtual drive without writing to the second folder. ) Is characterized by comprising a.
In the data management apparatus of the present invention, the second folder includes a third folder (F3) in which a destination for storing user data to be written is set in an external storage device (ND) provided in the network. The data processing unit transfers user data to be written to the third folder to the external storage device without writing to the third folder.
In the data management device of the present invention, the data processing unit is a driver that controls writing to the first storage device in response to the write request from a user process managed by an operating system (22). It is characterized by that.
The data management device of the present invention is characterized in that the data processing unit suspends writing to the first storage device from the start of the operating system until the mounting of the first virtual drive is completed. Yes.
Further, the data management device of the present invention, when switching from a first user who is not allowed to access the external storage device to a second user who is allowed access to the external storage device, A volatile second storage device (D3) in which a second virtual drive (D2) in which user data of the first user or user data of the second user stored in the external storage device is stored is created. It is characterized by providing.
The data management method of the present invention is a data management method for managing user data, and includes a first folder (F1) in which user data cannot be written and a second folder in which user data can be written. When there is a write request for the first folder of the nonvolatile storage device (17) having (F2), the write request is rejected (S22), and the second folder of the storage device is rejected. When there is a write request, the user data written to the second folder in response to the write request is encrypted and set as the storage destination of the user data written to the second folder without writing to the second folder The stored virtual drive (D1) is stored (S23).
A data management program according to the present invention is a data management program that causes a computer to function as a data management device (1, 2) that manages user data. When there is a write request to the first folder of the nonvolatile storage device (17) having the folder (F1) and the second folder (F2) in which user data can be written, When the write request is rejected and there is a write request to the second folder of the storage device, the user data written to the second folder by the write request is encrypted and written to the second folder Data processing means (21) for storing in the virtual drive (D1) set as the storage destination of user data written in the second folder It is characterized in that to function as a.

  According to the present invention, when there is a write request for the first folder in which user data cannot be written, the data processing unit rejects the write request and the user data can be written. When there is a write request for the second folder, the data processing unit encrypts the user data written to the second folder by the write request and writes it to the second folder without writing to the second folder. To save. For this reason, it is possible to strictly prohibit the writing of user data to the first storage device by the user's operation, and there is an effect that leakage of user data and the like can be more effectively prevented.

It is a block diagram which shows the hardware constitutions of the data management apparatus by 1st Embodiment of this invention. It is a figure which shows an example of the folder structure in the data management apparatus by 1st Embodiment of this invention. It is a block diagram which shows the software structure of the data management apparatus by 1st Embodiment of this invention. It is a flowchart which shows the operation | movement at the time of starting of the data management apparatus by 1st Embodiment of this invention. It is a flowchart which shows the operation | movement at the time of the writing of the user data of the data management apparatus by 1st Embodiment of this invention. It is a block diagram which shows the software structure of the data management apparatus by 2nd Embodiment of this invention.

  Hereinafter, a data management device, a data management method, and a data management program according to embodiments of the present invention will be described in detail with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram showing a hardware configuration of a data management apparatus according to the first embodiment of the present invention. As shown in FIG. 1, the data management apparatus 1 of this embodiment includes an input device 11, a display device 12, a communication device 13, a CPU (central processing unit) 14, an optical drive device 15, a memory 16, and a drive device 17 (first device). 1 storage device, storage device), connected to the network N1, and manages data (user data) created or edited by a user using an application. Such a data management device 1 is realized by, for example, a desktop or notebook personal computer. The network N1 is, for example, a LAN (Local Area Network) laid in a company.

  The input device 11 includes, for example, a keyboard, a pointing device, and the like, and inputs an instruction according to a user operation using the data management device 1 to the CPU 14. The display device 12 includes a liquid crystal display device and the like, and displays various information output from the CPU 14. The communication device 13 is connected to the network N1, and communicates with the network drive ND (external storage device) via the network N1.

  The CPU 14 controls each of the blocks shown in FIG. 1 to control the operation of the data management apparatus 1 in an integrated manner. The optical drive device 15 reads data recorded on a computer-readable recording medium M such as a CD-ROM or a DVD (registered trademark) -ROM. The functions of the data management device 1 (details will be described later) are realized by software by reading and installing a program (data management program) recorded on the recording medium M by the optical drive device 15.

  The memory 16 is a volatile semiconductor memory such as a RAM (Random Access Memory). Various data (including user data) stored in the memory 16 are deleted when the data management apparatus 1 is shut down (power is cut off), restarted, or logged off. The drive device 17 is a non-volatile secondary storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

  FIG. 2 is a diagram showing an example of a folder configuration in the data management apparatus according to the first embodiment of the present invention. The folder shown in FIG. 2 is formed in the drive device 17 included in the data management device 1. As shown in FIG. 2, the folder structure formed in the drive device 17 has a hierarchical structure (tree structure) with “C: ¥” as a root folder. In the example shown in FIG. 2, a plurality of folders such as “Users”, “ProgramData”, and “Program Files” are formed in the root folder.

  The folder “Users” is a folder in which user data created or edited by a user who uses the data management apparatus 1, setting data for each user, and other various data for each user are stored. In this folder “Users”, as shown in FIG. 2, folders “UserA”, “UserB”, “UserC” and the like for each user and a folder “Public” common to the users are formed. In addition, folders “Desktop”, “Documents”, and the like are formed in a folder for each user. The folder “Desktop” is a folder in which setting data relating to the desktop screen is stored, and the folder “Documents” is a folder in which user data is stored.

  The folder “Program Files” is a file that stores various programs used in the data management apparatus 1, and the folder “ProgramData” stores application data that is shared by all users who use the data management apparatus 1. It is a file. In addition to the folders “Users”, “ProgramData”, and “Program Files” shown in FIG. 2, the root folder is provided with a folder for storing a program for realizing the operating system OS and other folders.

The folder formed in the drive device 17 is set so that user data can be written to the folder F1 (first folder) in which user data cannot be written in order to prevent leakage or loss of user data. And F2 (second folder). Specifically, the folder shown below is a folder F2 in which user data can be written, and folders other than the following folder are folders F1 in which user data cannot be written.
C: \ Users \ <Folder for each user>
C: \ Users \ Public
C: \ ProgramData

Although details will be described later, the user data is not stored in the above folder of the drive device 17 but is encrypted and stored in the virtual drive D1 (see FIG. 3) in order to prevent leakage and disappearance. Or transferred to the network drive ND and stored. For example, user data written in the following folder F3 (third folder) formed in the lower layer of the folder F2 is actually transferred to the network drive ND and stored without being written in the following folder. .
C: \ Users \ <folder for each user> \ Desktop
C: \ Users \ <folder for each user> \ Documents

  FIG. 3 is a block diagram showing a software configuration of the data management apparatus according to the first embodiment of the present invention. As shown in FIG. 3, the data management apparatus 1 includes a virtual drive D1 (first virtual drive), a filter driver 21 (data processing unit, data processing means, driver), an operating system (OS) 22, and an application 23. The filter driver 21 is realized by the CPU 14 executing a program (data management program) installed in the data management apparatus 1.

  The virtual drive D1 is a virtual secondary storage device created in the drive device 17 provided in the data management device 1. In FIG. 3, the entity of the virtual drive D1 created in the drive device 17 is illustrated as “VHD” for easy understanding. The virtual drive D1 is set as a storage destination of user data (for example, user data created by the application 23) written in the folder F2 described above.

  The filter driver 21 performs user data writing control. Specifically, when there is a write request from the operating system 22 (more precisely, a write request from a user process managed by the operating system 22), the filter driver 21 is specified by the write request. Folder F1 (folder in which user data writing is disabled), folder F2 (folder in which user data writing is enabled), and folder F3 (storage destination is network drive ND). And the user data write control is performed.

  For example, if the write request from the operating system 22 is a write request for the folder F1, the filter driver 21 rejects the write request. Further, when the write request from the operating system 22 is a write request for the folder F2, the filter driver 21 encrypts user data written in the folder F2 by this write request and does not write it in the folder F2. Save to virtual drive D1. An arbitrary method can be used as the user data encryption method, but a practical method is used in consideration of the time required for encryption processing (encryption and decryption), encryption strength, and the like.

  When the write request from the operating system 22 is a write request for the folder F3, the filter driver 21 does not write the user data written in the folder F3 by this write request to the network drive without writing to the folder F3. Transfer (redirect) to ND. Such write control is performed in order to more effectively prevent user data leakage and the like by strictly prohibiting writing of user data to the drive device 17.

  The operating system 22 is software that provides the application 23 with an interface that abstracts the hardware shown in FIG. Although not shown in FIG. 3, the operating system 22 is provided with a file system that handles various data including user data as files and handles folders shown in FIG. The operating system 22 performs various processes such as a user data write request created by the application 23 (write requests to the folders F1 to F3 described above).

  The application 23 is software that operates on the operating system 22 and is used for creating or editing user data. Examples of the application 23 include word processor software that creates and edits document data, and paint software and draw software that create and edit image data. In addition, browsing software called a browser is also included in the application 23.

  Next, the operation of the data management apparatus 1 having the above configuration will be described. In the following, first, an operation at the time of starting the data management device 1 (operation at the time of startup) will be described, and then an operation at the time of writing user data (operation at the time of writing) of the data management device 1 will be described.

<Operation at startup>
FIG. 4 is a flowchart showing an operation at the time of starting the data management apparatus according to the first embodiment of the present invention. 4 is performed when, for example, the data management apparatus 1 is turned on, various programs stored in the drive apparatus 17 shown in FIG. 1 are loaded by the CPU 14, and the operating system 22 is started. To begin.

  When the process is started, the operating system 22 performs a process for reading a program for realizing the filter driver 21 from the drive device 17 (step S11) and a process for starting the mounting of the virtual drive D1 (step S12). In FIG. 2, for the sake of convenience, the process of starting mounting the virtual drive D1 after the process of reading the program that implements the filter driver 21 from the drive device 17 is illustrated, but these processes are performed in parallel. .

  When the reading of the program that realizes the filter driver 21 is completed and the filter driver 21 shown in FIG. 3 is activated, the process of holding the writing to the virtual drive D1 by holding all writing to the drive device 17 is filtered. This is performed by the driver 21 (step S13). Such a process is performed in order to complete the mounting of the virtual drive D1 before the logon screen to the operating system 22 is displayed without hindering the operation of the data management apparatus 1.

  In other words, the virtual drive D1 may store various data necessary for logon processing (for example, setting data related to the desktop screen). For this reason, if the mounting of the virtual drive D1 is not completed before the logon screen is displayed, there is a possibility that the activation of the operating system 22 or the logon process may fail. In order to avoid such a situation, the filter driver 21 performs processing to suspend writing to the drive device 17 and the virtual drive D1. Even if the filter driver 21 performs a process of suspending the writing to the drive device 17 and the virtual drive D1, the operating system 22 recognizes the drive device 17 and the virtual drive D1 as a low-speed drive. The operation of the management apparatus 1 is not hindered.

  Next, the filter driver 21 determines whether or not the mounting of the virtual drive D1 is completed (step S14). Since the mounting of the virtual drive D1 is performed by the operating system 22, the filter driver 21 makes an inquiry to the operating system 22 as to whether or not the mounting of the virtual drive D1 is completed, and makes the above determination. .

  If the filter driver 21 determines that the mounting of the virtual drive D1 has not been completed, the process of step S14 is repeated. On the other hand, when it is determined that the mounting of the virtual drive D1 is completed, the filter driver 21 performs a process of starting writing to the drive device 17 and the virtual drive D1 (step S15). When the above processing is completed, processing for displaying a logon screen (logon screen to the operating system 22) is performed by the operating system 22 (step S16).

<Operation during writing>
FIG. 5 is a flowchart showing an operation at the time of writing user data of the data management apparatus according to the first embodiment of the present invention. In the process of the flowchart shown in FIG. 5, the user operating the data management device 1 gives an instruction to write user data to the drive device 17, and the operating system 22 issues a write request to the filter driver 21. It starts when it is made.

  When the processing is started, first, the filter driver 21 determines whether or not the folder specified by the write request from the operating system 22 is the unwritable folder F1 (step S21). When it is determined that the folder specified by the write request is the folder F1 (when the determination result of step S21 is “YES”), a process of rejecting the user's write by the write request is performed. This is performed by the filter driver 21 (step S22).

  On the other hand, when it is determined that the folder specified by the above write request is not the folder F1 (when the determination result of step S21 is “NO”), the folder specified by the above write request. Is a folder that needs to be redirected, the filter driver 21 determines (step S23). That is, the filter driver 21 determines whether or not the folder specified by the write request is the folder F3.

  When it is determined that the folder specified by the above write request is not the folder F3 (when the determination result of step S23 is “NO”), user data written in the above write request (in the folder F2). The filter driver 21 performs processing for encrypting user data to be written. Then, the filter driver 21 performs processing for storing the encrypted user data in the virtual drive D1 without writing it in the folder F2 (step S24).

  On the other hand, when it is determined that the folder specified by the above write request is the folder F3 (when the determination result of step S23 is “YES”), the write request is written into the folder F3. The filter driver 21 performs a process of transferring the user data to be transmitted to the network drive ND without writing it in the folder F3 (step S25).

  As described above, in the present embodiment, when there is a write request for the folder F1 in which user data cannot be written, the filter driver 21 rejects the write request. When there is a write request for the folder F2 in which user data can be written, the filter driver 21 encrypts the user data written in the folder F2 by the write request and writes it in the folder F2. Instead, it is stored in the virtual drive D1. For this reason, writing of user data to the drive device 17 by a user operation can be strictly prohibited, and leakage of user data and the like can be more effectively prevented.

  Further, when there is a write request to the folder F3 whose user data storage destination is set to the network drive ND, the filter driver 21 transfers the user data written to the folder F3 by the write request to the folder F3. The data is transferred to the network drive ND without writing. As a result, user data originally written to the folder F3 is not written to the folder F3, so that leakage of user data and the like can be effectively prevented.

  In the present embodiment, the user data writing control is performed by the filter driver 21, so that the user data writing is performed regardless of whether the user has administrator authority. Control can be performed. The filter driver 21 encrypts user data stored in the virtual drive D1 with system authority. For example, even if the user at the time of user data encryption and the user at the time of decryption are different, data management is performed. There is no problem in the operation of the device 1.

[Second Embodiment]
FIG. 6 is a block diagram showing a software configuration of the data management apparatus according to the second embodiment of the present invention. Note that the hardware configuration of the data management apparatus 2 of the present embodiment is the same as the hardware configuration of the data management apparatus 1 shown in FIG. In FIG. 6, the same reference numerals are given to the same components as those shown in FIG. 3.

  The data management apparatus 2 according to the present embodiment replaces the virtual drive D1 of the data management apparatus 1 shown in FIG. 3 with the virtual drive D2, adds a RAM disk D3, and accesses the network drive ND via the network N2 such as the Internet. Is limited to specific users. In other words, the data management apparatus 2 according to the present embodiment logs on as a user who is not permitted to access the network drive ND (non-permitted user: first user) unless accessing the network drive ND. The device 2 can be used. However, when accessing the network drive ND, it is necessary to switch the logged-on user from the non-permitted user to a user permitted to access the network drive ND (permitted user: second user). is there.

  It is assumed that such a data management device 2 is realized by a personally owned computer that is not managed by a company, for example. In the data management apparatus 2 realized by a personally owned computer, the operation cannot always be limited. For this reason, only when access to the network drive ND is performed, by restricting the operation of an authorized user permitted to access the network drive ND (user data write control is performed), user data leakage, etc. It is intended to prevent.

  The RAM disk D3 is a volatile secondary storage device that is realized using a memory (a memory corresponding to the memory 16 in FIG. 1) provided in the data management device 2. That is, various data stored in the RAM disk D3 are deleted when the data management device 2 is shut down, restarted, logged off, or the like. A virtual drive D2 is created in the RAM disk D3. In FIG. 6, in order to facilitate understanding, the entity of the virtual drive D2 created in the RAM disk D3 is illustrated as “VHD”. The virtual drive D2 stores user data of authorized users.

  The reason why the virtual drive D2 is created in the RAM disk D3 is to prevent leakage of user data and the like. That is, when the authorized user's user data necessary for accessing the network drive ND is stored in the RAM disk D3, and the access to the network drive ND ends and the authorized user logs off, the RAM disk The user data stored in D3 is automatically deleted, thereby preventing the leakage of user data.

  Here, the user data of the unauthorized user or the user data of the authorized user stored in advance in the network drive ND is stored in the RAM disk D3 when switching from the unauthorized user to the authorized user is performed. When the user data of the unauthorized user is stored in the RAM disk D3, the data management device is provided with almost no change in the environment such as the desktop screen despite the user switching from the unauthorized user to the authorized user. 2 can be used. Further, when the user data of the authorized user stored in advance in the network drive ND is stored in the RAM disk D3, the data management device 2 can be used in the environment when the network drive ND was previously accessed.

  Next, the operation of the data management apparatus 2 having the above configuration will be briefly described. When access to the network drive ND is required according to an instruction from the unauthorized user while the unauthorized user is logged on, the logged-on user is switched from the unauthorized user to the authorized user. When such user switching is performed, a virtual drive D2 is created and mounted in the RAM disk D3. When the mounting of the virtual drive D2 is completed, for example, user data of an authorized user stored in advance in the network drive ND (user data necessary for accessing the network drive ND) is stored in the mounted virtual drive D2. The Thereby, an authorized user can access the network drive ND.

  Here, when the power of the data management apparatus 2 is shut off while the authorized user is logged in, various data stored in the RAM disk D3 are erased, so the data management apparatus 2 is formed in the RAM disk D3. User data stored in the virtual drive D2 is also automatically deleted. Further, even when switching from an authorized user to an unauthorized user is performed, the authorized user is logged off, so that the user data stored in the virtual drive D2 is automatically deleted. In this way, leakage of user data is prevented.

  As described above, in this embodiment, access to the network drive ND is limited to a specific user (authorized user), and when access to the network drive ND is performed, the user is switched to the authorized user, The operation of the authorized user is restricted (user data write control is performed). For this reason, the writing of user data to the drive device 17 by the operation of the authorized user can be strictly prohibited as in the first embodiment, and leakage of user data and the like can be more effectively prevented.

  As described above, the data management apparatus, the data management method, and the data management program according to the embodiment of the present invention have been described. However, the present invention is not limited to the above embodiment, and can be freely changed within the scope of the present invention. It is. For example, in the above embodiment, the case where the functions of the data management devices 1 and 2 are realized by software by reading and installing the program recorded on the recording medium M by the optical drive device 15 will be described as an example. did. However, the functions of the data management apparatuses 1 and 2 may be realized by installing a program downloaded through a network such as the Internet (a program similar to the program recorded in the recording medium M) in a computer.

  In the above-described embodiment, the example in which the data management devices 1 and 2 are realized by a desktop or notebook personal computer has been described. However, the data management device 1 can also be realized by a tablet computer. When the present invention is also realized by a tablet computer, the optical drive device 15 shown in FIG. 1 is omitted, and a program downloaded via a network such as the Internet (a program similar to the program recorded on the recording medium M). Is installed in the computer, the functions of the data management devices 1 and 2 are realized.

1, 2 Data management device 17 Drive device 21 Filter driver 22 Operating system D1, D2 Virtual drive D3 RAM disk F1-F3 Folder ND Network drive

Claims (7)

In a data management device that manages user data,
A non-volatile first storage device having a first folder in which user data cannot be written and a second folder in which user data can be written;
A first virtual drive set as a storage destination of user data written to the second folder;
When there is a write request for the first folder of the first storage device, the write request is rejected, and when there is a write request for the second folder of the first storage device, A data management device comprising: a data processing unit that encrypts user data written to the second folder in response to the write request and stores the encrypted user data in the first virtual drive without writing to the second folder. The second folder includes a third folder in which user data to be written is stored in an external storage device provided in the network,
The data management device according to claim 1, wherein the data processing unit transfers user data written to the third folder to the external storage device without writing to the third folder.   The data processing unit is a driver that controls writing to the first storage device in response to the write request from a user process managed by an operating system. Data management device.   4. The data management apparatus according to claim 3, wherein the data processing unit suspends writing to the first storage device from the start of the operating system until the mounting of the first virtual drive is completed.   When switching from a first user not permitted to access the external storage device to a second user permitted to access the external storage device, the user data of the first user, or the 3. The data management apparatus according to claim 2, further comprising a volatile second storage device in which a second virtual drive in which user data of the second user stored in an external storage device is stored is created. A data management method for managing user data,
When there is a write request for the first folder of the non-volatile storage device having the first folder in which user data writing is disabled and the second folder in which user data writing is enabled, When the write request is rejected and there is a write request to the second folder of the storage device, user data written to the second folder by the write request is encrypted and stored in the second folder. A data management method comprising: saving in a virtual drive set as a storage destination of user data to be written in the second folder without writing. A data management program for causing a computer to function as a data management device for managing user data,
There has been a write request to the first folder of the non-volatile storage device having the computer having a first folder in which user data cannot be written and a second folder in which user data can be written. In this case, the write request is rejected, and when there is a write request for the second folder of the storage device, the user data written to the second folder by the write request is encrypted to A data management program that functions as a data processing unit that stores data in a virtual drive set as a storage destination of user data to be written to the second folder without writing to the second folder.

Images