JP4678884B2 - Portable storage media management system - Google Patents

Description

The present invention relates to a management technology of a removable storage medium that can be attached to and detached from a computer (terminal), and in particular, can manage computers and users that can be used for a removable storage medium that can be attached to and detached from a computer. , prevention of information leakage by the portable storage medium is Hakare, and relates to a portable storage medium management system capable of grasping the data and the operation history to be recorded.

  Conventionally, as a technology to prevent information leakage from portable storage media, to use authentication information for reading and writing to portable storage media, to restrict usage by setting passwords, and to make authentication stronger than passwords, There is a technique in which authentication information is stored in another storage medium and used as a hard key.

  Japanese Patent Laid-Open No. 2006-65829 (Patent Document 1) describes a computer in order to limit computers (corresponding to clients in the present invention) that can use simple media (corresponding to portable storage media in the present invention). The authentication key created from the unique information is stored in a simple medium, and when the simple medium is connected to the computer, the authentication key created on the computer is checked against the authentication key stored in the simple medium. A technique for confirming whether the product is acceptable or not is disclosed.

  More specifically, the simple medium use management system disclosed in Patent Document 1 aims to prevent information leakage by permitting the use of only the simple medium confirmed in advance by the client. As shown in FIG. 3, the management server 701 having a mounting portion of a simple medium 703 that is a removable portable data storage medium and a plurality of clients 702, and the simple medium use management for managing the use of the simple medium of the client 702 The management server 701 is a simple medium 703 from a client information storage unit (client management DB 717) for storing client information for identifying the client 702 and a simple medium 703 attached to the attachment unit of the management server 701. Simple medium information collecting means 711 for collecting simple medium information for identifying Client selection means 713 for selecting a client permitted to use the simple medium, client information collection means 712 for collecting client information of the selected client from the client information storage means, the simple medium information and the above-mentioned according to a predetermined rule An authentication key creating unit 714 that creates an authentication key using client information; and a management data writing unit 715 that stores management data including the created authentication key in a predetermined area of the simple medium 702, and includes the client 702. Includes a simple medium information collecting unit 721 for collecting simple medium information of the simple medium from a simple medium 703 attached to the attachment unit of the client, a management data collecting unit 722 for collecting management data from the simple medium, Collect client information for the client Client information collecting means 723, authentication key creating means 724 for creating a client authentication key using the simple medium information and the client information in accordance with rules used by the authentication key creating means 714 of the management server 701, and the client authentication Authentication key verification means for verifying a key and an authentication key included in the management data, and permitting a write process, a read process, or a read / write process to the simple medium when the client authentication key and the authentication key match 725. The management data writing means 715 writes the management data in an area where only data can be read as the area. The medium usage history DB 718 includes information for specifying the simple medium 703 used by the client 702, time information (date / time) when the simple medium is inserted into the mounting unit, time information (date / time) when the simple medium is taken out from the mounting unit, and the like. This is a database for storing medium usage history information.

JP 2006-65829 A

  In companies and schools, a plurality of computers (terminals) are connected via a network to configure a computer system, and an information sharing service or the like is operated to improve work efficiency.

  Since such computer systems may store important information that cannot be disclosed, management for protecting the information is always necessary.

  For example, a portable storage medium (removable medium; for example, a USB memory or a USB hard disk is assumed in the present invention) that can be attached to and detached from the computer system, and the portable storage medium that copies and records information in the computer system is maintained. When it is taken out of the area, there is a possibility that information leakage will occur. In particular, when a portable storage medium storing information is lost or stolen, there is a very high possibility that information leakage will occur.

  In recent years, due to technological development, the amount of information that can be recorded has increased along with the increase in the capacity of portable storage media, and the damage caused by information leakage has also increased significantly. In addition, in the event of an information leakage incident, management systems and responsibilities are being rigorously asked, and the impact is immeasurable. Therefore, information leakage prevention measures are now an extremely important issue among information security measures.

  Conventionally, a portable storage medium is considered as a portable storage device that can read and write data, and has been widely used with attention paid to the convenience of the portable type. However, if there is a means for securely transferring data connected to the network, a portable storage medium with the possibility of information leakage as described above should not be used until the risk of information leakage is taken.

  As described above, the use of portable storage media involves the risk of information leakage as described above. Therefore, it is better not to use portable storage media as much as possible if there are other safe data transfer means. A portable storage medium is an indispensable means for data exchange between computers that are not, and the use of the portable storage medium cannot be completely prohibited.

  As described above, the portable storage medium is required when data is transferred between a computer system and a stand-alone computer that cannot be connected to the network. In this case, the portable storage medium is a secure data storage medium. It must be transportable.

  For this reason, organizations that have to use portable storage media adopt products with security measures, and take measures to prevent information leakage by thoroughly implementing rules and education for authorized users. ing. However, since it is assumed that a user who is allowed to use any of these products with security measures will not be negligent or fraudulent, a portable storage medium can be freely used by an authorized user once. Information leakage may occur. In addition, there is a dependency on the user's morals, and even if rules and education are thoroughly enforced, there are often cases where the morals of authorized users are lacking, and information leakage incidents do not end. Currently.

  Since the portable storage medium is a non-volatile data storage device, the data once stored is kept even without supplying power. Even if the data to be stored is encrypted or a password is set, there is a release key to release it, so a malicious third party can spend a lot of time trying to crack. There is a risk that confidential information will be read out.

  Further, since the complexity of the release key affects the safety, cracking is likely to occur if a simple release key is set. The risk of cracking must be eliminated given that important information is worth seeing even with great effort.

  In order to prevent such information leakage due to portable storage media, not only limit the usable range, but also eliminate dependence on the user's morals and use it under strict management by the manager in charge. There is no choice but to do.

  For example, when a portable storage medium that is not permitted in the computer system is connected to the computer, the use of the portable storage medium must be restricted without being used effectively. In addition, it is necessary to restrict access to portable storage media that are permitted to be connected, even if the user intentionally takes them out of the maintenance area or loses them due to theft or negligence. There is.

  Furthermore, it is necessary to restrict the unauthorized data from being copied without permission, and it is necessary to record all the history of who, what, and what operations were performed, and an information leakage incident occurred. It is also necessary to keep track of the data recorded on the portable storage medium in preparation for the case.

  Furthermore, when the portable storage medium is illegally used, a self-protection measure is provided such as invalidating the portable storage medium so that the portable storage medium cannot be used or erasing the recorded data. There is also a need.

  Since the person in charge of management is also one of the users, it is important to be able to manage using a computer so that omissions, omissions and mistakes can be prevented.

  As a generally known technique, as described in the above [Background Art] section, a password setting is used for reading and writing to a portable storage medium, and a password set on the portable storage medium and a user input it. Some passwords are checked against the password and allowed to be used if they match. In order to further strengthen authentication, authentication information is stored in another storage medium as a hard key, and use permission is determined by comparing the authentication key set in the portable storage medium with the hard key. There is something to do.

  However, with either technology, the portable storage medium can be connected to any computer that can be connected to the portable storage medium, so the user can take the portable storage medium out of the maintenance area and use it. Information leakage when it is lost or lost with another hard key cannot be prevented.

  In the technique disclosed in Patent Document 1, the authentication key created from the unique information of the computer and the unique information of the portable storage medium (simple medium) is stored in the portable storage medium, and the portable storage medium is stored in the computer. When connected, the client authentication key is created from the unique information of the computer and the unique information of the portable storage medium, and the use permission is determined by comparing with the authentication key stored in the portable storage medium in advance. Yes. In addition, in order to grasp the operation history (such as the insertion date and time and date and time of insertion and removal of the portable storage medium) by the authorized user, the operation history is collected through a network connection with the management server.

  However, although the technology disclosed in Patent Document 1 has an information leakage prevention effect by restricting computers that can use portable storage media, it still contains security vulnerabilities and still depends on user morals. The degree is high and it is hard to say that it is a complete information leakage prevention measure.

  The security vulnerability of Patent Document 1 is that only a countermeasure against falsification is performed by writing an authentication key embedded in a portable storage medium (simple medium) in an area where only data can be read.

  In general authentication processing, a password is converted into a character string using a technique such as encryption in advance, and a password entered later is converted into a character string using the same encryption technique. Judgment is made by checking the subsequent character string.

  Since the same authentication method is used in Patent Document 1, the security may be broken by reading the authentication key embedded in the portable storage medium and using the read authentication key as it is for the authentication process. In such an authentication method, the authentication key must be hidden so that it cannot be read.

  In parts that depend on the user's morals, for example, authentication based on a combination of individual computer information and individual information on a portable storage medium can be used by another user on most computers with a multi-user environment. Therefore, the combined use with the encryption function or the security lock function is essential.

  Once authenticated, the user can freely read from and write to a portable storage medium on a computer that is permitted to write data, and can also freely read data on a computer that is permitted to read data. End up.

  In addition, only by monitoring the operation history (such as the insertion date / time and removal date / time of portable storage media), the contents of the written file cannot be confirmed. If a malicious user falsifies the file name, the operation will be performed. Unauthorized use cannot be detected from the history.

  In addition, there is no means to prevent data from being written to a portable storage medium, and even if it can be detected from the operation history, the response must be postponed. Can not.

  In addition, the collection of operation histories is premised on network connection. However, if network communication is possible, there is no need to use a portable storage medium until the risk of information leakage. A suitable data transfer means should be used. Accordingly, unauthorized use cannot be detected in data exchange with a computer that requires a portable storage medium and cannot communicate over a network.

  Also, in the procedure for embedding and deleting the authentication key in the portable storage medium, the operation of registering the authentication key only when using the portable storage medium and deleting the authentication key when not required is strictly performed for each client. It is difficult to implement, and all the work for resetting will be borne by the manager. Therefore, it becomes difficult for the person in charge of management to register all the clients that may use the portable storage medium from the beginning in order to reduce the burden, and to limit the range of use.

  In addition, the person in charge of management must confirm whether or not the portable storage medium is lost. Therefore, there is always a risk of leakage, omission, mistake, and the like. In addition, there is no countermeasure when a portable storage medium is illegally used.

  Speaking of the safety of data transport using portable storage media, data can be taken home after the data is read from a portable storage medium to a computer that is only allowed to read data from the portable storage media. Although the data need not be recorded on the portable storage medium, the danger is increased because the portable storage medium on which the unnecessary data is recorded must be taken home.

  Therefore, from the viewpoint of information leakage prevention measures, the technology of Patent Document 1 is suitable for use as an authentication medium for identifying a usable computer, but is portable for safely transporting data. Not suitable for storage media.

The object of the present invention is to manage everything from the portable storage medium, the usage environment of the portable storage medium, and the data recorded on the portable storage medium in an integrated manner, and to depend on the user's morality. It is an object of the present invention to provide a portable storage medium management system that can be eliminated and prevent information leakage from the portable storage medium.

In order to achieve the above object, the present invention employs the following configuration.
(A) <Overall configuration of portable storage medium management system>
In order to achieve the above object, the portable storage medium management system according to the present invention has a portable storage medium (removable medium such as a USB memory or a USB hard disk) 2 that can be attached to and detached from a computer (terminal), and its portable storage. A management console 4, a management terminal 5, a use terminal 6, and a management server 3 that integrates management of the portable storage medium 2 can be attached to and removed from the medium 2 (reference numerals are given to aid understanding, The same reference numerals are used in FIGS.

  The portable storage medium 2, the management server 3, the management console 4, the management terminal 5, and the use terminal 6 have the following internal configurations (processing means, database). Hereinafter, each internal structure is demonstrated using drawing.

(B) <Portable storage medium>
As shown in FIG. 2, the portable storage medium 2 is
(B1) Authentication key collating unit 211 that collects terminal information including terminal specific information for identifying a computer, inputs a terminal user name and password from a user, activates and transmits a medium control unit 221 described later, and , The authentication key collating unit 211 includes an authentication utility storage area 21 including an area access unit 212 for accessing the management utility storage area 22 described later,
(B2) The authentication information received from the authentication key collating unit 211 is collated with the terminal authentication information previously set in the terminal authentication information DB 222 in the portable storage medium 2, and the use permission / inhibition is determined according to the use condition and authority. The medium control unit 221 that performs processing when the use condition is not satisfied, records the medium operation history, and controls the operation to the stored data, the terminal authentication information DB 222 that stores the terminal authentication information, and the medium control unit 221 The data access means 223 for accessing the data storage area 23 described later, the data encryption means 224 for encrypting the data stored in the data storage area 23 of the portable storage medium 2, and the data storage of the portable storage medium 2 A management utility storage area 22 comprising data decryption means 225 for decrypting the encrypted data stored in the area 23;
(B3) A data storage area including a use condition DB 231 for storing use conditions, a data attribute DB 232 for storing data attributes, a medium operation history DB 233 for storing medium operation history information, and encrypted data 234 (plural). 23.

(C) <Management server>
As shown in FIG. 1, the management server 3
(C1) server information collecting means 302 for generating server specific information of the management server 3;
(C2) medium lending management means 303 for managing a medium lending procedure for lending by making the portable storage medium 2 usable;
(C3) medium return management means 304 for managing a medium return procedure for returning the portable storage medium 2 and making it unusable;
(C4) Medium inventory management means 309 for periodically connecting the portable storage medium 2 to the management console 4 or the management terminal 5 to confirm the actual product and managing the use conditions relating to the inventory set in the portable storage medium 2; ,
(C5) A medium that periodically connects the portable storage medium 2 to the management console 4 or the management terminal 5 to collect a medium operation history, and manages usage conditions related to the medium operation history set in the portable storage medium 2 Operation history management means 308;
(C6) terminal operation history management means 307 for collecting and storing terminal operation histories for the management server 3, the management console 4 and the management terminal 5,
(C7) In order to identify a computer that can use the portable storage medium 2, the terminal-specific information collected from the computer, the terminal user name and password when the portable storage medium 2 is used by the computer, and the portable Terminal authentication key generation means 305 for generating a terminal authentication key from the medium specific information collected from the storage medium 2,
(C8) data transmission / reception means 310 for communicating with the management console 4 and the management terminal 5;
(C9) Management server control means 301 that manages a management database 306 that stores management information of the portable storage medium management system and controls the means (c1) to (c8).

(D) <Management console>
As shown in FIG. 1, the management console 4
(D1) terminal information collection means 402 for collecting terminal specific information of the management console 4;
(D2) a non-managed medium exclusion unit 409 that prohibits connection as a non-managed medium when a portable storage medium of a different type from the portable storage medium is connected;
(D3) medium lending means 403 for operating a medium lending procedure for lending the portable storage medium 2 to be usable;
(D4) medium return means 404 for operating a medium return procedure for returning the portable storage medium 2 and making it unusable;
(D5) medium information collecting means 405 for connecting the portable storage medium 2 and collecting medium specific information from the portable storage medium 2;
(D6) A terminal authentication key that approves the setting of authentication information including the terminal authentication key to the portable storage medium 2 and the setting application of authentication information including the terminal authentication key to the portable storage medium 2 from the management terminal 5 Registration means 406;
(D7) data writing means 407 for performing data writing to the portable storage medium 2 and approving an application for writing data to the portable storage medium 2 from the management terminal 5;
(D8) a medium inventory unit 413 that periodically connects the portable storage medium 2 to the management console 4 to confirm the actual product, and resets the use conditions relating to the inventory set in the portable storage medium 2;
(D9) terminal operation history uploading means 410 for uploading a terminal operation history for the management console 4 to the management server 3;
(D10) Medium operation history uploading means 411 for connecting the portable storage medium 2 and uploading the medium operation history in the portable storage medium 2 to the management server 3;
(D11) Medium operation history browsing means 412 for extracting, tabulating, and displaying the analysis results of the portable storage medium 2 stored in the management server 3,
(D12) data transmission / reception means 414 for communicating with the management server 3 and the management terminal 5;
(D13) medium access means 408 having a device driver function for using the portable storage medium 2;
(D14) Management that displays an operation screen for the portable storage medium 2, reads and writes data stored in communication with the program in the portable storage medium 2, and controls the respective means from (d1) to (d13). Console control means 401.

(E) <Management terminal>
As shown in FIG. 1, the management terminal 5
(E1) terminal information collection means 502 for collecting terminal specific information of the management terminal 5;
(E2) a non-managed medium exclusion unit 505 that prohibits connection as a non-managed medium when a portable storage medium of a different type from the portable storage medium is connected;
(E3) a terminal authentication key registration application unit 503 that performs an application for setting authentication information including a terminal authentication key to the portable storage medium 2 and performs registration upon approval of the management console 4;
(E4) a data write application means 504 that makes a data write application to the portable storage medium 2 and writes the data with the approval of the management console 4;
(E5) a medium inventory unit 509 that periodically connects the portable storage medium 2 to the management console 4 to perform physical confirmation, and resets the use conditions relating to the inventory set in the portable storage medium 2;
(E6) terminal operation history uploading means 507 for uploading the terminal operation history for the management terminal 5 to the management server 3;
(E7) medium operation history uploading means 508 for connecting the portable storage medium 2 and uploading the medium operation history in the portable storage medium 3 to the management server 3;
(E8) data transmission / reception means 510 for communicating with the management server 3 and the management console 4;
(E9) medium access means 505 having a device driver function for using the portable storage medium 2;
(E10) Management that displays an operation screen for the portable storage medium 2, reads and writes data stored in communication with a program in the portable storage medium 2, and supervises each means from (e1) to (e9). Terminal control means 501.

(F) <Used terminal>
As shown in FIG.
(F1) terminal information collection means 602 that collects terminal-specific information of the used terminal 6;
(F2) a non-managed medium exclusion unit 604 that prohibits connection as a non-managed medium when a portable storage medium of a different type from the target portable storage medium is connected;
(F3) medium access means 603 having a device driver function for using the portable storage medium 2;
(F4) Use terminal that displays an operation screen for the portable storage medium 2, reads data stored in communication with the program in the portable storage medium 2, and supervises the means (f 1) to (f 3). And a control means 601.

  The management server 3 constituting the present invention stores and manages information necessary for managing the portable storage medium 2 in the management database 306 and executes processing related to the management of the portable storage medium 2.

  However, it is assumed that the management server 3 is installed in an isolated room and operated for 24 hours, and all operations on the management server 3 are executed from the management console 4 or the management terminal 5.

  Therefore, the management server 3 must be able to communicate with the management console 4 and the management terminal 5 via the network 1.

  The use terminal 6 constituting the present invention is assumed to be a non-communicable computer managed by another organization and does not require a network connection with the management server 3. In addition, since data managed by another organization is stored in the portable storage medium 2 and is not taken away, it is possible to read only data from the portable storage medium 2.

  If there is information to be taken back from another organization, it is desirable to write it in another portable storage medium in accordance with the security policy of the other organization, receiving approval for taking out by the other organization.

  The management console 4 constituting the present invention operates the management server 3 to manage the portable storage medium 2 by the management server 3. Data writing to the portable storage medium 2 is also executed.

  The management terminal 5 constituting the present invention executes means for continuing to use the portable storage medium 2 among the means included in the management console 4 and writes data to the portable storage medium 2 with the approval of the management console 4 Also execute.

  The portable storage medium 2 constituting the present invention is divided into an authentication utility storage area 21, a management utility storage area 22, and a data storage area 23 as shown in FIG. 2 (and as described above). The storage area 21 includes an authentication key verification unit 211 and an area access unit 212, and the management utility storage area 22 includes a medium control unit 221, a terminal authentication information DB 222, a data access unit 223, a data encryption unit 224, and a data decryption unit. The data storage area 23 includes a use condition DB 231, a data attribute DB 232, a medium operation history DB 233, and data (encryption) 234 (plural).

  These are authentication information for determining whether or not the portable storage medium 2 can be used, a program for determining whether or not to use the portable storage medium 2 based on the authentication information, use conditions of the portable storage medium 2, and use of the portable storage medium 2 depending on the use conditions. Control program, medium operation history, program for encrypting or decrypting data, and encrypted data.

  The operation on the portable storage medium 2 is performed by executing a program stored in the portable storage medium 2 from a computer.

  In the present invention, a program, authentication information, and the like are stored inside the portable storage medium. However, it is not preferable that these are read unnecessarily, and it is desirable that the information stored inside be hidden.

  Therefore, the authentication utility storage area 21, the management utility storage area 22, and the data storage area 23 that constitute the interior of the portable storage medium are in a unique format that cannot be used by normal access means that are standard on computers. It is desirable to be.

  In addition, the medium access means installed in each computer is equipped with a device driver for using the authentication utility only by reading, and the area access means 212 of the authentication utility storage area 21 is only read the management utility storage area 22. A device driver for use in the management utility storage area 22 is provided with a device driver for reading and writing the data storage area 23, so that a program instruction for actually reading and writing data is provided. And authentication information can be hidden.

  The medium access means 408, 505, and 603 installed in each computer are dedicated device drivers for reading data from the portable storage medium 2. When writing data to the portable storage medium 2, it is possible to download and execute a dedicated device driver from the management server 3 so that it is not necessary to store program instructions for writing data in each computer. can do.

  Further, only the necessary file information is displayed on the file operation screen for reading / writing data to / from the portable storage medium 2, and information such as each program, terminal authentication information DB 222, use condition DB 231, data attribute DB 232, etc. By hiding it from the file operation screen, the internal structure can be hidden.

  In the present invention, in order to identify a computer and a user who can use a portable storage medium, terminal-specific information for identifying the computer, medium-specific information for identifying the portable storage medium, and portable by the computer A terminal authentication key can be created by combining a terminal user name and a password for identifying a user who can use the storage medium.

  Each time the user connects the portable storage medium 2 to the computer, the terminal specific information for identifying the connected computer and the medium specific information for identifying the connected portable storage medium 2 are collected. Enter the terminal user name and password for identification, and create a terminal authentication key for authentication.

  This terminal authentication key for authentication is collated with a terminal authentication key stored in advance in the portable storage medium, and can be set to the portable storage medium only when the collation result matches, read / write Yes, allow only read-only operations.

  On the other hand, when the portable storage medium is connected to a computer that is not permitted to use the portable storage medium, the terminal specific information for identifying the connected computer is different, so the terminal specific information, the medium specific information, and the terminal Different character strings are created for the terminal authentication key created from the combination of the user name and the password, and the verification with the terminal authentication key stored inside the portable storage medium does not match. For this reason, operations on the portable storage medium 2 are prohibited and use is not permitted.

  In addition, even when the terminal authentication key stored in the portable storage medium is illegally copied to another portable storage medium, the medium-specific information for identifying another portable storage medium is different. , A different terminal authentication key is created, the matching does not match, and use is not allowed.

  Similarly, when a different character string is input to the terminal user name or password, a different terminal authentication key is created, the verification does not match, and use is not permitted.

  Thus, the terminal authentication key stored inside the portable storage medium only when the combination of the computer, the portable storage medium, and the user permitted to use the portable storage medium in advance matches. Since they agree with each other and can be used, it is possible to eliminate the risk of illegally connecting to an unauthorized computer and causing information leakage.

  In order to set the terminal authentication key to the portable storage medium, the administrator can set it in the medium lending procedure when starting to use the portable storage medium, and also set it in the terminal authentication key registration procedure even during lending of the portable storage medium Can be added.

  In addition, it is possible to reduce the burden on the manager in charge by enabling registration by the user applying for registration from the management terminal and the manager responsible approving from the management console. Furthermore, by setting a registration deadline for each terminal authentication key, a terminal authentication key that has passed the registration deadline can be automatically invalidated.

  As a result, the procedure for setting the terminal authentication key in the portable storage medium can be operated strictly by registering only the computer to be used and deleting it when it is no longer needed, and the security level can be further increased.

  In the present invention, the use conditions for managing the portable storage medium and the data attributes for managing the data stored in the portable storage medium are stored in the portable storage medium, and these are managed. Stores the program.

<Usage conditions>
The usage conditions for managing portable storage media are evaluated each time the portable storage medium is operated. If the usage conditions are not met, the prescribed operation is restricted and information leakage prevention measures are taken. Or run.

  As an information leakage prevention measure, it is possible to execute processing such as deleting all data stored in the portable storage medium or rewriting the use conditions so that the portable storage medium cannot be used.

The usage conditions for managing portable storage media include:
1) When the authentication process for using the portable storage medium fails, it is determined that the access is unauthorized and information leakage prevention measures can be taken.

2) By setting the expiration date, you can perform the procedure for lending and returning portable storage media. If the expiration date is reached and the computer is connected to the computer, it will be judged as unauthorized use and information leakage prevention measures will be taken can do. Moreover, since the portable storage medium in storage which has not been lent out is in an unusable state, it cannot be used without permission from the manager.

3) By setting the inventory cycle, you can periodically connect to the management server and check the actual product. If the inventory expires and is connected to the computer within the inventory cycle, it is determined to be unauthorized use. Information leakage prevention measures can be implemented.

4) When the media operation history upload cycle is set, the media operation history can be uploaded by periodically connecting to the management server. If the media operation history upload cycle does not upload and the computer is expired and connected to the computer Can be determined to be unauthorized use and information leakage prevention measures can be implemented.

5) By setting the storage capacity upper limit of the medium operation history, when a medium operation history exceeding the capacity is stored, it is determined that the use cannot be continued, and information leakage prevention measures can be taken. However, in practice, as long as there is free space, keep accumulating and record the trace of unauthorized access.
Etc. can be implemented.

<Data attribute>
The data attribute for managing the data stored in the portable storage medium is evaluated every time the data stored in the portable storage medium is operated, and information leakage prevention measures are executed according to the data attribute.

  As an information leakage prevention measure, a process of deleting target data stored in the portable storage medium is executed.

Data attributes for managing data stored in portable storage media include:
1) By setting the number of remaining data copies, the number of data read times can be set to prevent unnecessarily reading data, and invalid data when the remaining number of data copies becomes zero. Information leakage prevention measures can be implemented. Thereby, for example, by setting the remaining number of times of replication as 1 time, the data can be deleted immediately after the data is read out, and data can be conveyed in one direction.

2) By setting the storage period, it is possible to set a period during which data is stored in the portable storage medium, and it is possible to implement information leakage prevention measures such as deleting data that has passed the storage period.

3) By setting a computer that can be read for each data, data to be copied to different computers can be carried in a single portable storage medium, and duplication errors when reading data can be prevented. it can,
Etc. can be implemented.

  As a result, even if the computer is not connected to a network and cannot communicate, when using the portable storage medium, the usage conditions for managing the portable storage medium and the data stored in the portable storage medium are stored. Data attributes for management can be evaluated, and predetermined operations can be restricted and information leakage prevention measures can be taken.

  Further, even when connected to a computer that is not permitted to be used, it is possible to take information leakage prevention measures by determining that the access is unauthorized due to the failure of authentication.

  In the present invention, some of the use conditions for managing the portable storage medium and the data attribute for managing the data stored in the portable storage medium use the system time. Measures to prevent information leakage are being implemented.

  Although the system time can be obtained from a computer, it is desirable to incorporate a clock function in the portable storage medium because it may be camouflaged. Therefore, it is assumed that the clock function automatically synchronizes the time when connected to the management server so that the user cannot correct it without permission.

  Further, since it is necessary to incorporate a power source in order to drive the clock function, it is possible to forcibly erase data when the expiration date has passed by using the clock function and the power source.

  In the present invention, the operation can be restricted by an authentication process for using the portable storage medium, so that data writing to the portable storage medium is restricted to only a management console and a management terminal that can communicate with the management server. can do.

  In addition, before the data is written to the portable storage medium, the manager can check the contents of the data, and only the data approved by the manager can be written to the portable storage medium.

  In order for a user using a management terminal to write data to a portable storage medium, specify the data to be written and the attributes of the data in the specified input field displayed on the file operation screen of the portable storage medium management system. Apply for writing to the manager in charge of using the management console.

  The manager in charge confirms the contents and attributes of the data submitted for writing, approves the writing application if there is no problem, and rejects the writing application if there is a problem. The management terminal stores only the data permitted to be written by the management console in the portable storage medium.

  On the other hand, in order for the manager responsible for using the management console to write data to the portable storage medium, the data to be written and the data to be written are entered in a predetermined input field displayed on the file operation screen of the portable storage medium management system. Data can be stored in a portable storage medium by specifying attributes.

  In the approval procedure when writing data to the portable storage medium and writing the data to the portable storage medium, the file stored in the portable storage medium is grasped by recording the information of the file to be written on the management server. It becomes possible to do.

  As a result, before the data is written to the portable storage medium, it becomes possible for the manager in charge to check the contents of the data to be written from the management console, and it is possible to prevent the data from being illegally written. It is also possible to set the attribute of data to be written to the portable storage medium, and it is possible to take information leakage prevention measures such as limiting the computer to which data is read and specifying the storage period.

  Furthermore, it becomes possible to grasp all data stored in the portable storage medium, and even if the portable storage medium is lost, an appropriate response can be supported.

  In the present invention, a computer for managing a portable storage medium and a medium operation history DB for recording a medium operation history are stored inside the portable storage medium. The medium operation history can be acquired even if used in.

  Even when connected to a computer that is not permitted to use, if the program in the portable storage medium is executed, the result of the authentication process and information on the computer that is not permitted to use can be acquired.

  The medium operation history recorded in the portable storage medium can be collected by uploading it to the management server when the portable storage medium is connected to the management console or the management terminal.

  In order to periodically upload the medium operation history to the management server, use conditions for managing the portable storage medium are used, and an inventory cycle for checking the actual thing and an operation history upload cycle are used. Under these usage conditions, it is possible to automatically prohibit the use of portable storage media after a certain period of time without uploading to the management server. it can.

  Use conditions for managing portable storage media set in portable storage media and data attributes for managing data stored in portable storage media are also retained in the management database in the management server. Thus, the portable storage medium can be managed by the management server.

  As a result, the person in charge of management can grasp the status of the portable storage medium. For example, when the expiration date has passed, the management server can automatically prompt the person in charge of management and the user to return. Become.

  In the present invention, inside the portable storage medium, authentication information for determining whether or not the portable storage medium can be used, a program for determining whether or not to use the portable storage medium based on the authentication information, use conditions and usage conditions of the portable storage medium A program for controlling use of a portable storage medium, a medium operation history, a program for encrypting or decrypting data, and the like are stored, and by executing these, data is written to and read from the portable storage medium.

  The present invention relates to terminal-specific information for identifying a connected computer, medium-specific information for identifying a connected portable storage medium, and user identification each time a portable storage medium is connected to a computer. Create a terminal authentication key from the terminal user name and password, compare it with the terminal authentication key stored in advance in the portable storage medium, and set the portable storage medium only if the verification result matches, Predetermined operations such as writing and reading are permitted.

  When connecting to a computer that is not permitted to use, a different terminal authentication key is created because the terminal-specific information of the computer is different, and the verification of the terminal authentication key fails and the use is not permitted.

  In this way, since the use permission is given only to the combination of the computer, the portable storage medium, and the user who are permitted to use the portable storage medium in advance, the use on the computer that is not permitted to use can be prohibited. Information leakage can be prevented.

  In addition, by setting a registration time limit in the terminal authentication key stored in the portable storage medium, it is automatically invalidated and cannot be used after the registration time limit. In addition, the user can apply for registration of the terminal authentication key from the management terminal to the portable storage medium and can be registered if the management manager approves it from the management console, thereby reducing the workload of the management manager.

  As a result, the procedure for setting the terminal authentication key in the portable storage medium can be operated strictly by registering only the computer to be used and deleting it when it is no longer needed, and the security level can be further increased.

  Even when connected to a computer system that is not connected to the network, a stand-alone computer, or a third computer that does not permit the use of portable storage media, measures to prevent information leakage are implemented depending on the authentication result. It is also possible to acquire the result of the authentication process and information on computers that are not permitted to be used.

  In the present invention, the use conditions for managing the portable storage medium and the data attributes for managing the data stored in the portable storage medium are stored in the portable storage medium, and these are managed. A program is also stored.

  In addition, every time an operation is performed on a portable storage medium, when the usage conditions for managing the portable storage medium and the data attributes for managing the data are evaluated in combination, the usage conditions are not satisfied. Can execute information leakage prevention measures such as limiting a predetermined operation or deleting all data.

<Usage conditions>
As usage conditions for managing portable storage media, for example,
1) When authentication processing for using a portable storage medium fails, it is determined that the access is unauthorized and the stored data is deleted.

2) By setting the expiration date, the portable storage medium can be lent and returned, and when the expiration date has passed, the use can be stopped or the stored data can be deleted.

3) By setting the inventory cycle, it is possible to periodically connect to the management server and confirm the actual product, and it is possible to detect the loss of the portable storage medium at an early stage and take measures.

4) By setting the medium operation history upload cycle, the medium operation history accumulated in the portable storage medium can be periodically collected, and the trace of unauthorized use can be found at an early stage.

<Data attribute>
Moreover, as a data attribute for managing the data stored in the portable storage medium, for example,
1) By setting the number of remaining copies of data, the number of remaining copies can be set to 1 so that data can be automatically deleted immediately after reading, and the risk of information leakage can be reduced by making data transport in one direction. Can do.

2) Data that has passed the storage period can be deleted by setting the storage period.
3) By setting a computer that can be read for each data, data to be copied to different computers can be carried in a single portable storage medium, and duplication errors when reading data can be prevented. it can.

  In the present invention, the operation can be restricted by an authentication process for using the portable storage medium, so that data writing to the portable storage medium is restricted to only a management console and a management terminal that can communicate with the management server. can do.

  In addition, before the data is written to the portable storage medium, the manager can check the contents of the data, and only the data approved by the manager can be written to the portable storage medium.

  As a result, before the data is written to the portable storage medium, it becomes possible for the manager in charge to check the contents of the data to be written from the management console, and it is possible to prevent the data from being illegally written. It is also possible to set the attribute of data to be written to the portable storage medium, and it is possible to take information leakage prevention measures such as limiting the computer to which data is read and specifying the storage period.

  Furthermore, it becomes possible to grasp all data stored in the portable storage medium, and even if the portable storage medium is lost, an appropriate response can be supported.

  In the present invention, the portable storage medium stores the program for managing the portable storage medium and the medium operation history DB for recording the medium operation history. Even if it is used with a simple computer, the medium operation history can be acquired.

  This makes it possible to record the media operation history in all situations where the portable storage medium is used, check the operation status by the authorized user by analyzing the media operation history, check the trace of unauthorized use, etc. It is possible to prevent information leakage due to unauthorized use.

  Further, by holding the use conditions and data attributes set in the portable storage medium in the management server, the portable storage medium can be managed by the management server. As a result, the person in charge of management can grasp the status of the portable storage medium and can prevent omissions, omissions and mistakes in the management of the portable storage medium.

  As described above, the portable storage medium management system according to the present invention has been described in the sections “Means for Solving the Problems” and “Effects of the Invention”. The following is the description of the best mode for carrying out the present invention. Examples will be described in more detail with reference to the drawings.

<Overall configuration>
FIG. 1 is a diagram showing an example of the overall configuration of a portable storage medium management system according to the present invention, and FIG. 2 is a diagram showing an example of the internal configuration of a portable storage medium 2 according to the present invention.

  As shown in FIG. 1, the portable storage medium management system according to the present invention includes a management server 3, a management console 4 (generally plural) and a management terminal 5 that can transmit / receive data to / from the management server 3 via the network 1. (Generally plural), use terminals 6 (generally plural) not connected to the network, and portable storage medium 2 (generally plural).

  The management server 3 and the management console 4 according to the present invention can be mounted on the same computer, and only one of the management terminal 5 and the use terminal 6 may be provided. Further, a plurality of management consoles 4 may be prepared to perform the duties of the manager in charge.

  The processes according to the present invention in the management server 3, the management console 4, and the management terminal 5 are executed in cooperation with each other, and the portable storage medium 2, the management console 4, the portable storage medium 2, the management terminal 5, and the portable storage. The processing of the medium 2 and the use terminal 6 is also executed in cooperation.

  The management server 3 includes a management server control unit 301, a server information collection unit 302, a medium lending management unit 303, a medium return management unit 304, a terminal authentication key generation unit 305, a management database 306, a terminal operation history management unit 307, a medium operation history. A management unit 308, a medium inventory management unit 309, and a data transmission / reception unit 310 are provided.

  The management console 4 includes a management console control unit 401, a terminal information collection unit 402, a medium lending unit 403, a medium return unit 404, a medium information collection unit 405, a terminal authentication key registration unit 406, a data writing unit 407, and a medium access unit 408. , An unmanaged medium exclusion unit 409, a terminal operation history upload unit 410, a medium operation history upload unit 411, a medium operation history browsing unit 412, a medium inventory unit 413, and a data transmission / reception unit 414.

  The management terminal 5 includes a management terminal control unit 501, a terminal information collection unit 502, a terminal authentication key registration application unit 503, a data write application unit 504, a medium access unit 505, an unmanaged medium exclusion unit 506, and a terminal operation history upload unit 507. , Medium operation history upload means 508, medium inventory means 509, and data transmission / reception means 510.

  The use terminal 6 includes use terminal control means 601, terminal information collection means 602, medium access means 603, and unmanaged medium exclusion means 604.

  As shown in FIG. 2, the portable storage medium 2 is divided into an authentication utility storage area 21, a management utility storage area 22, and a data storage area 23. The authentication utility storage area 21 includes an authentication key verification unit 211, area access The management utility storage area 22 includes a medium control means 221, a terminal authentication information DB 222, a data access means 223, a data encryption means 224, and a data decryption means 225. The data storage area 23 includes usage conditions. A DB 231, a data attribute DB 232, a medium operation history DB 233, and a plurality of data (encrypted) 234 are provided.

  The authentication utility storage area 21 is an area that can be read and cannot be written, and the management utility storage area 22 is an area that can be read only via the area access means 212 and cannot be written, and stores data. The area 23 is an area that can be read and written only through the data access means 223.

  The management server 3 is a server that includes a management database 306 that accumulates management information of the portable storage medium 2 and executes processing related to the management of the portable storage medium 2.

  Further, it is assumed that the management server 3 is installed in an isolated room and operated for 24 hours, and the operation to the management server 3 is executed from the management console 4 or the management terminal 5. Therefore, the management console 4 and the management terminal 5 must be able to communicate with the management server 3 via the network 1.

  The management console 4 includes a connection device (not shown) for the portable storage medium 2, operates the management server 3 to execute processing related to the management of the portable storage medium 2, and writes data to the portable storage medium 2. It is a computer that can read data. It is assumed that the highest management person (administrator) of the portable storage medium 2 uses it.

  The management terminal 5 includes a connection device (not shown) for the portable storage medium 2, executes processing for maintaining the use of the portable storage medium 2, and writes data to and reads data from the portable storage medium 2. It is a computer that can.

  However, writing from the management terminal 5 to the portable storage medium 2 requires the approval of the manager in charge of data. It is assumed that it is used by a quasi-manager following the person in charge of management of the portable storage medium 2 or a user authorized to write data to the portable storage medium 2.

  The use terminal 6 is a computer that includes a connection device (not shown) for the portable storage medium 2 and can only read data from the portable storage medium 2.

  Since it is assumed that the use terminal 6 includes a computer managed by another organization, the use terminal 6 may not be connected to the network 1 and may be a computer incapable of network communication.

  The portable storage medium 2 is a portable data storage device that can be attached to and detached from a computer, such as a USB memory, a memory card, and a removable disk.

  The portable storage medium 2 contains therein authentication information for using the portable storage medium 2, usage condition information for managing the portable storage medium 2, and data stored in the portable storage medium 2. This is a portable data storage device incorporating data attribute information for management, a plurality of programs for managing use of these, and medium operation history information.

  In the present invention, since programs, authentication information, and the like are stored inside the portable storage medium 2, it is not preferable to read them easily, and it is desirable that the information stored inside be hidden.

  Therefore, each area of the authentication utility storage area 21, the management utility storage area 22, and the data storage area 23 constituting the inside of the portable storage medium 2 is a unique format that cannot be used by the access means that is standardly installed in the computer. It is desirable.

  In addition, the authentication utility storage area 21 is used only for reading in each of the medium access means 408, medium access means 505, and medium access means 603 installed in each computer (management console 4, management terminal 5, use terminal 6). A device driver for use in the management utility storage area 22 is provided in the area access means 212 of the authentication utility storage area 21 and the data access means 223 in the management utility storage area 22 is used. By installing a device driver for reading and writing the data storage area 23, a program instruction for actually reading and writing data is concealed.

  The medium access means 408, medium access means 505, and medium access means 603 installed in each computer (management console 4, management terminal 5, use terminal 6) are device drivers dedicated to reading data from the portable storage medium 2. When writing data to the portable storage medium 2, downloading a dedicated device driver from the management server 3 and executing it eliminates the need to store program instructions for writing data in the computer.

  Further, only necessary file information is displayed on a file operation screen (not shown) for reading and writing data to / from the portable storage medium 2, and information such as each program, terminal authentication information, use conditions, and data attributes is displayed. Hides the internal structure by not displaying it on the file operation screen (not shown).

[Description of data stored in the management database 306 of the management server 3]
Next, terminal management information, medium management information, data attributes, medium operation history, and terminal operation history data stored in the management database 306 inside the management server 3 will be described.

  3A to 3E are diagrams illustrating data examples of terminal management information, medium management information, data attributes, medium operation history, and terminal operation history stored in the management database 306 inside the management server 3, respectively.

<Terminal management information DB stored in the management database>
In the terminal management information DB of the management database 306, as shown in FIG. 3A, all terminals related to the management server 3, the management console 4, the management terminal 5, and the used terminals 6 that are managed by the portable storage medium management system. Management information is stored.

  Further, the terminal authentication key set inside the portable storage medium 2 is also stored for each portable storage medium 2.

  FIG. 3A is an example of the terminal management information DB, which includes groups (servers, consoles, management terminals, “which group they belong to” used terminals), terminal display names, terminal identifiers, terminal authentication keys, terminal user names, and the like. An example having items is shown.

<Media management information DB stored in the management database>
In the medium management information DB of the management database 306, as shown in FIG. 3B, all medium management information of the portable storage medium 2 that is a management target in the portable storage medium management system is stored.

  FIG. 3B is an example of a medium management information DB, which includes a medium identifier, a status (in use, in storage, waiting for actual confirmation, etc.), start of use (how many months, what day, what hour, how many minutes, and what second). The example has items such as a time limit (year, month, date, hour, minute, and second), an inventory cycle, and a user.

<Data attribute DB stored in management database>
In the data attribute DB of the management database 306, as shown in FIG. 3C, the attributes and storage conditions of all data stored in the portable storage medium are stored.

  FIG. 3C is an example of the data attribute DB, and shows an example having items such as a data identifier, a file name, a remaining copy count, a storage deadline, and a copyable terminal identifier.

<Media Operation History DB Stored in Management Database>
In the medium operation history DB of the management database 306, as shown in FIG. 3D, medium operation histories uploaded from the inside of all portable storage media 2 to be managed are accumulated.

  FIG. 3D is an example of the medium operation history DB, which includes a time stamp (year, month, day, hour, minute, and second), medium identifier, terminal identifier, terminal user name, operation (what operation ( The example includes items such as connection / authentication, writing, reading, and disconnection).

<Terminal operation history DB stored in the management database>
In the terminal operation history DB of the management database 306, terminal operation histories uploaded from the management server 3, the management console 4, and the management terminal 5 are accumulated.

  FIG. 3E is an example of the terminal operation history DB, which includes a time stamp (year, month, day, hour, minute, and second), terminal identifier, terminal user name, operation (what operation (connection / authentication) , Data write application, data write, medium inventory check, etc.)), objects (objects to be operated) are shown.

  In addition, there may be configuration information for operating the portable storage medium management system, operation information, user information, schedule information, workflow information related to data write application and terminal authentication key registration application, and the like.

  The terminal identifier, medium identifier, and data identifier used in the management database 306 are character strings for uniquely identifying each in the portable storage medium management system of the present application. Each of these identifiers is a character string arbitrarily assigned by the portable storage medium management system for internal processing, and is assumed to be a character string that is not related to terminal specific information or medium specific information.

  The terminal authentication key in the management database 306 (see “terminal management information DB” in FIG. 3A) is an authentication key used to identify a computer that can use the portable storage medium 2 and a user. Terminal unique information for identifying the portable storage medium 2, medium unique information for identifying the portable storage medium 2, and a terminal user name and password for identifying a user who can use the portable storage medium 2 on a computer A uniquely identifiable character string converted by a technique such as multiple encryption.

  As a result, if any one of the terminal unique information of the computer that is the conversion source, the medium unique information of the portable storage medium 2, the terminal user name, or the password is different, it is converted into a completely different character string. Thus, it is possible to reliably identify a computer and a user who can use the portable storage medium 2.

[Description of data stored in each DB in the portable storage medium 2]
Next, data stored in the terminal authentication information DB 222, the use condition DB 231, the data attribute DB 232, and the medium operation history DB 233 in the portable storage medium 2 will be described.

  4A to 4D respectively show terminal authentication information, usage conditions, data attributes stored in the terminal authentication information DB 222, usage condition DB 231, data attribute DB 232, and medium operation history DB 233 in the portable storage medium 2, respectively. FIG. 6 is a diagram illustrating a data example of medium operation history.

<Terminal authentication information DB stored in portable storage medium>
In the terminal authentication information DB 222, as shown in FIG. 4A, the management server information of the management server 3 that manages the portable storage medium, the management console 4, the management terminal 5, and the terminals of the use terminal 6 that are permitted to be used. Stores authentication information.

  A registration deadline can also be set for each computer that is allowed to be used. Since the “terminal unique information”, “medium unique information”, “terminal user name”, and “password” used for authentication are converted into “terminal authentication keys” by a technique such as multiple encryption, the internal structure Even if the concealment countermeasures are broken and read, the original information cannot be viewed.

  FIG. 4A is an example of the terminal authentication information DB 222 and shows an example having items such as “terminal identifier”, “terminal authentication key”, “authority”, and “registration deadline”.

<Use condition DB stored in portable storage medium>
The use condition DB 231 stores use conditions for using the portable storage medium 2. As usage conditions, “expiration date”, “allowable upper limit number of unauthorized access”, “inventory cycle”, “media operation history upload cycle”, and the like can be set.

  FIG. 4B is an example of the use condition DB 231, which includes “usability flag”, “expiration flag”, “use start time”, “use deadline”, “unauthorized access counter”, “unauthorized access allowable upper limit”, “inventory completed flag” ”,“ Inventory deadline ”,“ Inventory cycle ”,“ Last inventory timestamp ”,“ History record availability flag ”,“ Operation history DB capacity ”,“ Operation history upload deadline ”,“ Operation deadline upload cycle ”,“ Final An example having items such as “upload time stamp” is shown.

  The “expiration date” is managed by “use start time”, “expiration date”, and “expiration flag”, and only the lending period from the lending procedure to the returning procedure of the portable storage medium 2 can be used.

  “Maximum number of allowable unauthorized access” is managed by “Unauthorized access counter” and “Unauthorized access limit”, and when you connect to a computer that is not permitted to use or input the terminal user name and password incorrectly. It is for prohibiting use.

  “Inventory cycle” is managed by “Last inventory time stamp”, “Inventory cycle” and “Inventory completed flag”, and the physical inventory is regularly confirmed to detect the loss of the portable storage medium 2 at an early stage. When it is not possible, it is for prohibiting use.

  “Upload cycle of media operation history” is managed by “last upload timestamp”, “operation history upload cycle”, and “history record enable / disable flag”, and manages the media operation history recorded in the portable storage medium 2 It prompts the procedure for collection to the server.

  In addition, a flag is set in each use condition to prevent unauthorized use by returning the system time by some means after use is prohibited.

<Data attribute DB stored in portable storage medium>
The data attribute DB 232 stores data attributes and storage conditions stored in the portable storage medium 2. As the storage condition, “remaining copy count”, “storage expiration”, a plurality of “duplicatable terminal identifiers”, and the like can be set.

  FIG. 4C is an example of the data attribute DB 232 and shows an example having items such as “data identifier”, “file name”, “remaining copy count”, “retention period”, and “replicable terminal identifier”.

  The “remaining copy count” manages the number of times the stored data can be read out to another computer, and deletes the data when the “remaining copy count” becomes zero.

  “Storage deadline” manages the storage deadline stored in the portable storage medium 2 and deletes data that has passed the “storage deadline”.

  The “duplicatable terminal identifier” is for restricting the reading destination of stored data so that a plurality of data can be stored in one portable storage medium 2.

<Media operation history DB stored in a portable storage medium>
In the medium operation history DB 233, operations on the portable storage medium 2 and operations on data stored in the portable storage medium 2 are accumulated as a medium operation history.

  FIG. 4D is an example of the medium operation history DB 233, “time stamp” (how many months, what days, hours, minutes, and seconds), “operations” (connection / authentication, data write application, data write, disconnect) Etc.), “object” (object to be operated), “value” (normal or abnormal when the object is a function, or data identifier when the object is a data operation).

<Registration processing of terminal specific information to the management server>
FIG. 5 is a diagram showing a flow of processing for collecting terminal specific information and registering it in the management server 3.

  Terminal information collection means 402, terminal information collection means 502, and terminal information collection means 602 of each computer (management console 4, management terminal 5, and use terminal 6) receive terminal information including terminal specific information and management data on the computer. Collect (step S101).

  The terminal-specific information collected from each computer is information that can uniquely identify the computer, such as the device ID of the CPU, the system ID of the installed operating system, and the MAC address of the LAN board, and can easily be counterfeited by other computers. Information that cannot be desirable.

  In the case of the management server 3, the server specific information is generated by the server information collecting unit 302 instead of collecting the terminal specific information. The management server 3 considers the migration (change) of the hardware constituting the management server 3 and uses an arbitrary character string that can be uniquely identified, not information obtained from the hardware.

  Collected terminal information is managed using data transfer means via the network 1 when connected to the network 1, and using removable media when the terminal is not connected to the network 1. It is sent to the console 4 (S102).

  Next, the terminal information is sent from the management console 4 to the management server 3 and stored in the management database 306 of the management server 3 (step S103).

<Registration processing of media specific information to management server>
FIG. 6 is a diagram showing a flow of processing for collecting medium specific information and registering it in the management server 3.

  The medium information collection unit 405 of the management console 4 collects medium information including medium specific information and management data from the portable storage medium 2 connected to the management console 4 (step S201).

  The medium-specific information collected from the portable storage medium 2 uniquely identifies the portable storage medium 2 that is a combination of “maker name”, “model number”, “single unit identification ID”, etc. set for each portable storage medium. It is a possible character string.

  Next, the collected media information is sent to the management server 3 and stored in the management database 306 (step S202).

<Verification of terminal authentication key and usage conditions>
7A to 7D are diagrams showing a flow of processing for collating the terminal authentication key with the use conditions.

  The management console control means 401, the management terminal control means 501, and the use terminal control means 601 of each computer (management console 4, management terminal 5, and use terminal 6) are connected to the portable storage medium 2 by the processing shown in FIGS. 7A to 7D. Each time an operation request is issued, the authentication key collating unit 211 inside the portable storage medium 2 is activated to collate the terminal authentication key with the use condition.

  In the first authentication process after the portable storage medium 2 is connected to a computer connection device (not shown), the authentication key verification unit 211 in the portable storage medium 2 is activated and the terminal user name and password are activated. However, if the user continues to connect to the computer and keep using the authentication key collating unit 211, the terminal user name and password can be omitted in the second and subsequent authentication processes. .

  When the verification of the terminal authentication key and the use condition is successful, processing such as data writing and data reading is executed by a program inside the portable storage medium 2 and a response is returned.

  In these authentication processes, measures such as expiration of use are evaluated by checking the use conditions, the use condition DB 231 is updated according to the evaluation result, and the use is invalidated.

  By checking the usage conditions every time an operation request is generated and evaluating the usage conditions at that time, there is no omission in evaluation even if the usage is left connected for a long time, and counterfeiting becomes difficult.

  Since the medium inventory means for the purpose of confirming the actual object is only required to confirm that the portable storage medium 2 is connected to the management console 4 or the management terminal 5, if the authentication of the portable storage medium 2 is successful, It may be automatically executed at regular intervals.

  The medium inventory management unit 309 of the management server 3 communicates with the medium inventory unit 413 of the management console 4 or the medium inventory unit 509 of the management terminal 5 in the background while the portable storage medium 2 is connected. The setting relating to the inventory cycle stored in the use condition DB 231 of the portable storage medium 2 is updated.

  If the portable storage medium 2 is not connected, the setting related to the inventory cycle stored in the management database 306 of the management server 3 is confirmed, and the management console 4 and the user are prompted to confirm the actual item.

  Next, according to the flowcharts of FIGS. 7A to 7D, the flow of processing for collating the terminal authentication key with the use conditions will be described in detail.

  First, every time an operation request to the portable storage medium 2 is generated, the authentication key verification unit 211 inside the portable storage medium 2 is activated (step S301).

  The authentication key collating unit 211 confirms the activated management console control unit 401, the management terminal control unit 501, or the used terminal control unit 601, and collates the activated terminal (step S302).

  If it is one of the terminals (step S303: Y), then the authentication key collating unit 211 collects the terminal specific information of the connected terminal and the medium specific information of the portable storage medium, and uses the terminal from the user. The user name and password are input (step S304).

  Next, the authentication key collating unit 211 activates the medium control unit 221 and transmits the collected terminal unique information and medium unique information, and the inputted terminal user name and password to the medium control unit 221 ( Step S305).

  The medium control means 221 generates a terminal authentication key from the terminal unique information, medium unique information, terminal user name, and password received from the authentication key collating means 211 (step S306).

  Next, the medium control unit 221 collates the generated terminal authentication key with a valid terminal authentication key in the terminal authentication information DB 222 (step S307).

  If there is a matching entry as a result of the collation in step S307 (step S308: Y), terminal authentication information including authority is read for the matched entry in the terminal authentication information DB 222 (step S309).

  Next, the “usability flag” in the use condition DB 231 is verified (step S310), and the process proceeds to the flowchart of FIG. 7B. If the “usability flag” is “possible” (step S311: Y), the use condition is next. The “expiration flag” in the DB 231 is verified (step S 313). If the “expiration flag” is “within expiration” (step S 314: Y), the system time is acquired, and the “expiration date” in the system time and use condition DB 231 is acquired. "Is collated (step S316).

  If the result of collation in step S316 is within the expiration date (step S317: Y), the “inventory completed flag” in the usage condition DB 231 is verified (step S320), and if the “inventory completed flag” is “completed” ( Step S321: Y), the system time is acquired, and the system time is compared with the “inventory expiration date” in the use condition DB 231 (Step S323).

  If the result of the collation in step S323 is within the inventory deadline (step S324: Y), the process proceeds to the flowchart of FIG. 7C, and the “history record enable / disable flag” in the use condition DB 231 is verified (step S327).

  As a result of the collation in step S327, if the “history record availability flag” is “possible” (step S328: Y), the capacity of the medium operation history DB is acquired, and the “operation history DB capacity” of the capacity and use condition DB 231 is acquired. (Step S330), and if the acquired capacity is equal to or smaller than the “operation history DB capacity” in the use condition DB 231 (step S331: Y), the system time is acquired, and the system time and the use condition The “operation history upload time limit” in the DB 231 is collated (step S334).

  As a result of the collation in step S334, if it is within the upload deadline (step S335: Y), it is determined whether the terminal that requested the operation to the portable storage medium 2 is the management console 4, the management terminal 5 or the use terminal 6, and the management console 4 (Step S338: Y), the process proceeds to step S341 in the flowchart of FIG. 7D. In the case of the management terminal 5 (step S339: Y), the process proceeds to step S342 in the flowchart of FIG. Step S340: Y), the process proceeds to Step S343 in the flowchart of FIG. 7D.

  In the case of the management console 4, the collation result of the held use condition is examined (step S 341), and if it is in a usable state (step S 344: Y), it is normal and the medium use is “set” and “write”. "Read" and "Read" (step S347), the process proceeds to step S353, and if it is not in the usable state (step S344: N), it is normal (maintenance required) and the use of the medium is permitted by "setting" ( Step S348), the process proceeds to Step S353.

  In the case of the management terminal 5, the collation result of the held use condition is examined (step S 342), and if it is in the usable state (step S 345: Y), it is normal and the use of the medium is “written” and “read”. "" (Step S349), the process proceeds to step S353, and if it is not in an available state (step S345: N), it is abnormal and the use of the medium is not permitted (step S350), and the process proceeds to step S353.

  In the case of the terminal 6 in use, the collation result of the held use condition is examined (step S343). If it is in the usable state (step S346: Y), it is normal and the use of the medium is permitted by “reading”. (Step S351), the process proceeds to Step S353, and if it is not in the usable state (Step S346: N), it is abnormal and the use of the medium is not permitted (Step S352), and the process proceeds to Step S353.

  In step S353, it is determined whether or not the use is permitted as normal. If the use is permitted as normal (step S353: Y), the “illegal access counter” in the use condition DB 231 is cleared to zero (step S354). Then, the operation history is recorded in the portable storage medium 2 (step S356, see FIG. 8 for details), and the authentication key collating means 211 is made resident (this is a terminal authentication process to be carried out later and used by the terminal) (This is a process for omitting the input of the user name and password.)

  In FIG. 7B, in the case of (step S311: N), the fact that the “usability flag” in the use condition DB 231 is “impossible” proceeds to step S313 (step S312), and (step S314: N). ) Holds that the “expiration date” in the use condition DB 231 is “expired” and proceeds to step S316 (step S315), and in the case of (step S317: N), the “expiration flag” in the use condition DB 231 "Expired" is set to "Expired" (Step S318), the expiration date is held to be "Expired", and the process proceeds to Step S320 (Step S319). In the case of (Step S321: N), "Inventory" is " In step S 322, the process proceeds to step S 323 (N in step S 324: N). Set the "not yet" to "Inventories flag" of the matter DB231 (step S325), the process proceeds to step S327 of FIG. 7C holds that the inventory is "Not" (step S326).

  Further, in FIG. 7C, in the case of (Step S328: N), the history recording permission / inhibition is held to be “impossible”, and the process proceeds to Step S330 (Step S329), and in the case of (Step S331: N), it is used. The “history recording flag” in the condition DB 231 is set to “impossible” (step S332), the fact that the history recording propriety is “impossible” is held, the process proceeds to step S334 (step S333), and (step S335: N) In this case, the “history record enable / disable flag” in the use condition DB 231 is set to “impossible” (step S336), and the history storage enable / disable is held as “impossible”, and the process proceeds to step S338 (step S337).

  In the case of (Step S303: N), (Step S308: N), or (Step S340: N), the “illegal access counter” in the use condition DB 231 is incremented by “+1” in FIG. 7D (Step S358). The “illegal access counter” and the “unauthorized access allowable upper limit” in the use condition DB 231 are collated (step S359), and if the “unauthorized access counter” is less than the “unauthorized access allowable upper limit” (step S360: Y), the operation history Is recorded in the portable storage medium 2 (step S362, see FIG. 8 for details), and the processes of the authentication key verification unit 211 and the medium control unit 221 are terminated (step S363).

<Recording process of medium operation history>
FIG. 8 is a diagram showing a flow of processing for recording an operation history in the portable storage medium 2.

  The medium operation history recording process is a process of recording the processing result in the medium operation history DB 233 every time each program in the portable storage medium 2 executes the process, and indicates a single program. is not.

  The medium operation history DB 233 for recording the medium operation history is managed by the “operation history DB capacity”, “last upload timestamp”, “operation history upload cycle”, and “history record enable / disable flag” set in the use condition DB 231. ing. However, since the operation history of unauthorized use is recorded even after the use of the portable storage medium 2 is invalidated, the storage is continued as long as there is a recordable free space in the area.

  The flow of processing for recording the operation history in the portable storage medium 2 will be described in detail with reference to the flowchart of FIG.

  First, the “history record enable / disable flag” in the use condition DB 231 is verified (step S401). If the “history record enable / disable flag” is “enable” (step S402: Y), the capacity of the medium operation history DB 233 is acquired and acquired. The capacity of the medium operation history DB 233 and the “operation history DB capacity” of the use condition DB 231 are collated (step S403).

  As a result of the collation, when the capacity of the acquired medium operation history DB 233 is equal to or smaller than the “operation history DB capacity” of the use condition DB 231 (step S404: Y), the system time is acquired and the system time and the “operation history” of the use condition DB 231 are acquired. The “upload deadline” is collated (step S406).

  If the system time is within the “operation history upload time limit” in the use condition DB 231 (step S407: Y), the free space in the area storing the medium operation history DB 233 is acquired (step S409), and there is free space. (Step S410: Y), after writing the operation history (time stamp, operation, object, value, etc.) in the medium operation history DB 233 (step S411), and when there is no free space (step S410: N), After executing information leakage prevention measures such as deleting all stored data (step S412), the process is terminated.

  If the “history record enable / disable flag” in the use condition DB 231 is not “permitted” (step S402: N), the process proceeds to step S409. Further, when the acquired capacity of the medium operation history DB 233 is not less than or equal to the “operation history DB capacity” of the use condition DB 231 (step S404: N), and when the system time is not within the “operation history upload deadline” of the use condition DB 231 ( In step S407: N), after the “history record enable / disable flag” in the use condition DB 231 is set to “impossible” (step S405, step S408), the process proceeds to step S409.

<Lending process for portable storage media>
FIG. 9A and FIG. 9B are diagrams showing the flow of the lending process for the portable storage medium 2.

  In the management of the portable storage medium 2, when the portable storage medium 2 is needed, it is lent out by the manager, and when it is no longer needed after use, it is returned to the manager. It is desirable to invalidate the usage and store it in a safe. Therefore, the lending process of the portable storage medium 2 is a procedure for making the portable storage medium 2 usable by the manager in charge.

  The portable storage medium 2 is connected to a connection device (not shown) of the management console 4 and a process (FIGS. 7A to 7D) for collating the terminal authentication key with the use conditions is executed.

  The medium lending unit 403 of the management console 4 initializes each use condition of the use condition DB 231 of the portable storage medium 2 so that the portable storage medium 2 can be used. As described above, the usage conditions include “usability flag”, “expiration flag”, “use start date / time”, “expiration date / time”, “unauthorized access counter”, “unauthorized access allowable upper limit”, “inventory flag” , “Inventory deadline”, “Inventory cycle”, “Last inventory time stamp”, “History record availability flag”, “Operation history DB capacity”, “Operation history upload deadline”, “Operation history upload cycle”, “Last upload time” There are items such as “stamp”.

  When the initial setting in the use condition DB 231 is completed, the medium lending unit 403 transmits setting information to the management server 3, and the medium lending management unit 303 of the management server 3 records it as information on the portable storage medium 2 in the management database 306. .

  The flow of the lending process of the portable storage medium 2 will be described in detail along the flowcharts of FIGS. 9A to 9B.

  First, in FIG. 9A, it is determined whether or not the initialization of the portable storage medium has been executed (step S501). If the initialization has been executed (step S501: Y), the terminal described in FIGS. 7A to 7D above. Processing for collating the authentication key is performed (step S503). In the case of a portable recording medium to be managed (step S504: Y), the type of the terminal and the authority of the entry that matches the terminal in the terminal authentication information DB 222 Information is read (step S505).

  If the authority of the read authority information is “setting” and the terminal type is the management console (step S506: Y), the “usability flag” in the use condition DB 231 is read (step S507), and the usability flag is “impossible”. "" (Step S508: Y), the “usability flag” in the use condition DB 231 is changed to “permitted” (step S509), and the “expired flag” in the use condition DB 231 is changed to “within the deadline”. A deadline is set (step S511), "unauthorized access allowable upper limit" of the use condition DB 231 is set, "unauthorized access counter" is set to 0 (step S512), and "inventory flag" of the use condition DB 231 is set to "done" "Inventory deadline" and "Inventory cycle" are set, and the current time is set in "Last inventory time stamp" (step S5). 3) “History record availability flag” in use condition DB 231 is changed to “Yes”, “Operation history DB capacity”, “Operation history upload deadline” and “Operation history upload cycle” are set, and “Last upload time stamp” ”Is set (step S514), and the operation history described in FIG. 8 is recorded in the portable recording medium 2 (step S515).

  In FIG. 9A, in the case of (step S501: N), that is, when the initialization of the portable storage medium has not been executed, the portable storage medium is initialized so that only the management console 4 can be used. (Step S502), the process proceeds to Step S503, and in the case of (Step S504: N) or (Step S506: N), the process proceeds to Step S515 in FIG. 9B to perform processing for recording the operation history in the portable recording medium. .

  In the case of (Step S508: N), a warning is given that the portable storage medium is in use, and in the case of resetting, a warning is given to execute the “return processing” first (Step S510). Proceeding to step S515 in FIG. 9B, a process of recording the operation history in the portable recording medium is performed.

<Return processing of portable storage media>
FIG. 10 is a diagram showing the flow of return processing of the portable storage medium 2.

  In the management of the portable storage medium 2, when the portable storage medium 2 is needed, it is lent out by the manager, and when it is no longer needed after use, it is returned to the manager. It is desirable to invalidate the usage and store it in a safe. For this reason, the process of returning the portable storage medium 2 is a procedure for making the portable storage medium 2 unusable by a manager.

  The medium return means 404 of the management console 4 deletes all data (encryption) 234 remaining in the portable storage medium 2 and uploads the medium operation history in order to make the portable storage medium 2 unusable. The terminal authentication information in the terminal authentication information DB 222 and the use conditions in the use condition DB 231 are set.

  The terminal authentication information DB 222 leaves the terminal authentication information of the management server 3 and the management console 4 and deletes all others. The use condition DB 231 is changed so that various flags cannot be used, and other conditions are deleted.

  When the settings in the terminal authentication information DB 222 and the use condition DB 231 are completed, the medium return unit 404 transmits the setting information to the management server 3, and the medium return management unit 304 of the management server 3 stores the portable storage medium 2 in the management database 306. Record as information.

  The flow of the return process of the portable storage medium 2 will be described in detail along the flowchart of FIG.

First, a process for collating terminal authentication keys as described with reference to FIGS. 7A to 7D is performed (step S601).
As a result of the collation, in the case of a portable storage medium to be managed (step S6021: Y), the type of the terminal and the authority information of the entry matching the terminal in the terminal authentication information DB are read (step S603). When “Authority” is “Setting” and the terminal type is the management console (step S604: Y), the “usability flag” in the use condition DB 231 is read (step S605).

  If the “usability flag” is “available” (step S606: Y), the contents of the medium operation history DB 233 are uploaded to the management server 3 (step S607), the portable storage medium 2 is initialized, and only the management console 4 is used. (Step S609), the “usability flag” in the use condition DB 231 is changed to “impossible” (step S610), and the operation history as described in FIG. 8 is recorded in the portable storage medium. Is performed (step S611).

  If (step S602: N) or (step S604: N), the process proceeds to step S611. If (step S606: N), the portable storage medium is warned that it is being stored and can be used. If so, after warning that the "lending process" is performed first (step S608), the process proceeds to step S611.

<Terminal authentication key registration process>
11A to 11B are diagrams showing a flow of processing for registering a terminal authentication key in the portable storage medium 2.

  The main registration process is a process of registering a terminal authentication key of a computer that can use the portable storage medium 2 in the terminal authentication information DB 222 inside the portable storage medium 2.

  Since the process of registering a computer that can be used in the portable storage medium 2 is an action of setting a range in which data can be carried, judgment and approval by the manager in charge are necessary. For this reason, registration of the terminal authentication key in the portable storage medium 2 is limited only to the management console 4 and the management terminal 5, and the management terminal 5 requires approval by the management console 4.

When registering from the management terminal 5, the following application procedure and approval procedure are performed.
The terminal authentication key registration application unit 503 of the management terminal 5 causes the user to select a computer to apply for registration from the list of computers displayed on the terminal authentication key registration application screen (not shown) of the management terminal 5 and register the computer. The user enters the time limit and the terminal user name and password used for authentication to use the portable storage medium 2 on the computer.

  The computer displayed on the terminal authentication key registration application screen (not shown) needs to be registered in advance in the management server 3 by the process of FIG. Further, the terminal user name and password are arbitrary character strings and are not related to authentication information used for actual login to the computer or the like.

  After inputting the terminal user name and password, the management terminal 5 applies to the management console 4 for registration. The management console 4 examines the contents of the registration application from the management terminal 5 to determine permission or disapproval, and performs approval or return.

  When approved by the management console 4, the terminal authentication key generation unit 305 of the management server 3 uses the terminal specific information of the computer for which registration has been applied, the medium specific information of the portable storage medium 2, and the terminal usage input from the management terminal 5. A terminal authentication key is generated by combining the user name and password.

  Next, the management server 3 transmits terminal authentication information including the generated terminal authentication key and a dedicated device driver for registration in the portable storage medium 2 to the management terminal 5. At this time, the management server 3 registers the registration application information in the management database 306.

  The management terminal 5 registers terminal authentication information including a terminal authentication key in the terminal authentication information DB 222 of the portable storage medium 2 using a dedicated device driver received from the management server 3.

  When registering from the management console 4, since the person in charge of management who uses the management console 4 has the authorization authority, the terminal authentication key registration unit 406 does not require an application procedure or an approval procedure, and includes a terminal authentication key. The terminal authentication information can be registered in the terminal authentication information DB 222 of the portable storage medium 2.

  Next, the flow of processing for registering the terminal authentication key in the portable storage medium 2 will be described in detail with reference to the flowcharts of FIGS. 11A to 11B.

  First, a process for collating terminal authentication keys as described with reference to FIGS. 7A to 7D is performed (step S701).

  As a result of the collation, when the usage condition is satisfied and usable (step S702: Y), the type of the terminal and the authority information of the entry matching the terminal in the terminal authentication information DB 222 are read (step S703).

  When the authority is “write” (step S704: Y) and the terminal type is the management console 4 (step S705: Y), the management console 4 can be set from the terminal information registered in the management server 3. Terminal information is extracted (step S707).

  A list of the extracted terminal information is displayed on the terminal authentication key registration screen (step S708), a terminal to be set and a type of terminal are selected from the displayed terminal information list (step S709), and used on the selected terminal. A terminal user name and a password (non-display) for identifying the user are input (step S710).

  Proceeding to FIG. 11B, the management console 4 records the selected terminal information, medium information connected to the management console 4, input terminal user name, and password information in the management database 306 of the management server 3. (Step S718).

  The management server 3 generates a terminal authentication key from the terminal information, medium information, terminal user name, and password (step S719), stores the generated terminal authentication key in the management database 306, and transmits it to the management console 4 ( Step S720).

  The management console 4 stores the received terminal authentication key in the terminal authentication information DB 222 of the portable storage medium 2 (step S724), and then performs a process of recording the operation history as shown in FIG. 8 in the portable storage medium. (Step S728).

  If the terminal type is not the management console (step S705: N) and the terminal is a management terminal (step S706: Y), the management terminal 5 can be set from the terminal information registered in the management server 3. Terminal information is extracted (step S711).

  The extracted list of terminals is displayed on the terminal authentication key registration screen (step S712), the terminal to be set and the type of terminal are selected from the displayed terminal list (step S713), and the user is selected on the selected terminal. A terminal user name and a password (not displayed) for identification are input (step S714), and a terminal authentication key registration application is transmitted to the management console (step S715).

  Proceeding to FIG. 11B, the management console 4 confirms the use range and authority of the portable storage medium based on the content of the terminal authentication key registration application, and corrects the authority as necessary (step S716).

  When the management console 4 permits registration (step S717: Y), the management console 4 displays the selected terminal information, the medium information connected to the management terminal, and the input terminal user name and password information. The information is recorded in the management database 306 of the management server 3 (step S721).

  The management server 3 generates a terminal authentication key from the terminal information, medium information, terminal user name, and password (step S722), stores the generated terminal authentication key in the management database 306, and transmits it to the management terminal 5 ( Step S723).

  After storing the received terminal authentication key in the terminal authentication information DB 222 of the portable storage medium 2 (step S725), the management terminal 5 performs a process of recording the operation history as shown in FIG. 8 in the portable storage medium. (Step S728).

  In the case of (Step S702: N), (Step S704: N), or (Step S706: N), it is determined that there is no terminal authentication key registration authority (Step S727), and the operation history as shown in FIG. Is recorded in the portable storage medium (step S728).

  In the case of (Step S717: N), the management terminal 5 receives the fact that the terminal authentication key registration application has been rejected (Step S726), and then stores the operation history as shown in FIG. The recording process is performed (step S728).

<Data writing process>
12A to 12B are diagrams illustrating a flow of data writing processing to the portable storage medium 2.

  The process of writing data in the portable storage medium 2 may be leaked when the data is taken out or the portable storage medium 2 is lost. is necessary. Therefore, data writing to the portable storage medium 2 is limited to only the management console 4 and the management terminal 5, and the management terminal 5 needs to be approved by the management console 4.

  When data is written from the management terminal 5, the following application procedure and approval procedure are performed.

  The data writing application unit 504 of the management terminal 5 causes the user to select a file to be written from a file operation screen (not shown) of the management terminal 5 and to input a data attribute and an encryption password set in the file.

After the input, the management terminal 5 applies for data writing to the management console 4.
The management console 4 examines the contents and data attributes of the file for which data application has been applied from the management terminal 5, determines permission / rejection, and performs approval or return.

  If approved by the management console 4, the management server 3 registers the data write application information in the management database 306.

  The management terminal 5 encrypts and stores the write-permitted file in the portable storage medium 2 by the data encryption unit 224.

  When registering from the management console 4, the person in charge of management who uses the management console 4 has the approval authority, so the data writing means 407 does not require an application procedure or an approval procedure, and a file for which writing has been permitted is not required. Data can be encrypted and stored in the portable storage medium 2 by the data encryption unit 224.

  Next, the flow of data writing processing to the portable storage medium 2 will be described in detail with reference to the flowcharts of FIGS. 12A to 12B.

  First, a process for collating terminal authentication keys as described with reference to FIGS. 7A to 7D is performed (step S801).

  As a result of the collation, if the usage condition is satisfied and usable (step S802: Y), the type of the terminal and the authority information of the entry matching the terminal in the terminal authentication information DB are read (step S803).

  When the “authority” is “write” (step S804: Y) and the terminal type is the management console 4 (step S805: Y), the management console 4 designates the data file to be written, the data attribute and the encrypted password ( (Not displayed) is input (step S807).

  Proceeding to FIG. 12B, the management console 4 records the data file and data attribute information in the management database 306 of the management server 3 (step S812), encrypts the data file with the encryption password, and stores the data file along with the data attribute in a portable manner. After storing in the medium 2 (step S813), the operation history as shown in FIG. 8 is recorded in the portable storage medium 2 (step S818).

  If the terminal type is not the management console 4 (step S805: N) and the management terminal 5 is (step S806: Y), the management terminal 5 designates the data file to be written, the data attribute and the encrypted password ( (Not displayed) is input (step S808), and a write permission application is transmitted to the management console 4 (step S809).

  The management console 4 confirms the content and data attribute of the write data file based on the content of the write permission application, and corrects the data attribute as necessary (step S810).

  When the management console 4 permits the writing (step S811: Y), the process proceeds to FIG. 12B, and the management console 4 records the data file and the data attribute information that are permitted to be written in the management database 306 of the management server 3. (Step S814).

  The management terminal 5 encrypts the permitted data file with the encryption password and stores it in the portable storage medium 2 together with the data attribute (step S815), and then stores the operation history as shown in FIG. The recording process is performed (step S818).

  Further, in the case of (step S811: N), the management terminal 5 receives that the write permission application has been rejected (step S816), and stores the operation history as shown in FIG. 8 into the portable storage medium 2. A recording process is performed (step S818).

  In the case of (Step S802: N), (Step S804: N), or (Step S806: N), it is determined that there is no writing authority, and the operation history as shown in FIG. The recording process is performed (step S818).

<Data read processing>
FIG. 13A to FIG. 13B are diagrams showing the flow of data read processing from the portable storage medium 2.

  The data stored in the portable storage medium 2 is a computer (terminal) set in advance in the terminal authentication information DB 222 of the portable storage medium 2 and a computer (terminal) set in the duplicatable terminal identifier of the data attribute DB 232. The password cannot be read without knowing the password for decryption by the data decryption means 225.

  Furthermore, in order to continue storing data in the portable storage medium 2, it is necessary to appropriately manage the portable storage medium 2 and satisfy the conditions set in the use condition DB 231 and the data attribute DB 232. .

  Next, the flow of data read processing from the portable storage medium 2 will be described in detail with reference to the flowcharts of FIGS. 13A to 13B.

  First, a process for collating terminal authentication keys as described with reference to FIGS. 7A to 7D is performed (step S901).

  As a result of the collation, if the usage condition is satisfied and usable (step S902: Y), the type of the terminal and the authority information of the entry matching the terminal in the terminal authentication information DB are read (step S903).

  If the “authority” is “read” (step S904: Y), the “remaining copy count” in the data attribute DB 232 is collated with respect to all data stored in the data storage area 23, and the “remaining copy count” is checked. Is deleted (step S905), the system time is compared with the “storage expiration” in the data attribute DB 232, and the data file whose storage expiration has expired is deleted (step S906).

  The “replicatable terminal identifier” in the data attribute DB 232 is compared with the terminal identifier of the terminal, a matching data file and an unspecified data file are extracted (step S907), and a list of the extracted data files is displayed. The data file is displayed on the file operation screen (step S908), the data file to be read is selected from the displayed data file list (step S909), and the decryption password (non-display) of the data file is input (step S910).

  Proceeding to FIG. 13B, the decrypted data file is stored in the terminal (step S 911), the “remaining copy count” in the data attribute DB 232 is decremented (−1) (step S 912), and stored in the data storage area 233. For all the data, the “remaining copy count” in the data attribute DB 232 is collated, the data file whose “replication remaining count” is 0 is deleted (step S913), and the system time and “ After checking the storage expiration date and deleting the data file whose storage expiration date has expired (step S914), a process of recording the operation history as shown in FIG. 8 in the portable storage medium is performed (step S916).

  In the case of (Step S902: N) or (Step S904: N), it is determined that there is no read authority (Step S915), and the operation history as shown in FIG. 8 is recorded in the portable storage medium. Is performed (step S916).

  It should be noted that the non-managed medium removing unit 409, the non-managed medium removing unit 506, and the non-managed medium removing unit 604 installed in each computer (management console 4, management terminal 5, use terminal 6) are equipped with the computer (terminal). Some types of portable storage medium connecting devices that allow the use of another type of portable storage medium while the portable storage medium 2 is usable can be used for another type of portable storage medium. This is means for prohibiting connection of a storage medium as an unmanaged medium.

  Further, the data transmission / reception means 310, the data transmission / reception means 414, and the data transmission / reception means 510 mounted on each computer (management server 3, management console 4, management terminal 5) are connected to the management server 3, management console 4, and management terminal 5. Means for communicating with each other via the network 1.

  The terminal operation history uploading means 410 of the management console 4 and the terminal operation history uploading means 507 of the management terminal 5 upload the operation history of the portable storage medium management system in each computer to the management server 3 via the network 1. The operation history management unit 307 is a unit for accumulating and managing in the management database 306.

  If the portable storage medium 2 is connected to the management console 4 or the management terminal 5 and authentication of the portable storage medium 2 is successful, the medium operation history accumulated in the portable storage medium 2 is set at regular intervals. It is also possible to execute automatically. By automatically uploading the media operation history, it is possible to reduce the burden on the user and to prevent omission of upload.

  The medium operation history management unit 308 of the management server 3 and the medium operation history upload unit 508 of the management console 4 or the medium operation history upload unit 508 of the management terminal 5 while the portable storage medium 2 is connected. It communicates in the ground, uploads the medium operation history stored in the medium operation history DB 233 of the portable storage medium 2, and deletes the uploaded medium operation history.

  When the portable storage medium 2 is not connected, the setting regarding the medium operation history upload cycle stored in the management database 306 of the management server 3 is confirmed, and the upload operation of the medium operation history to the management console 4 or the user is performed. Prompt.

  The medium operation history browsing means 412 of the management console 4 is a means for extracting, summing up, and analyzing the medium operation history accumulated in the management database 306 of the management server 3.

  The medium control unit 221 of the portable storage medium 2 accepts an operation request for the portable storage medium 2, compares it with a terminal authentication key and use conditions, performs access control according to the authority given by the authentication result, and performs unauthorized use and use conditions. It has a role of overseeing each means mounted on the portable storage medium 2 such as invalidation of the portable storage medium 2 when it does not match, recording of a medium operation history, operation on stored data, and the like.

  The management server control unit 301 of the management server 3 manages the management database 306 that stores management information of the portable storage medium management system, and has a role of supervising each unit installed in the management server 3.

  The management console control unit 401 of the management console 4 displays an operation screen related to the management of the portable storage medium, communicates with a program inside the portable storage medium 2 and performs an operation on the portable storage medium 2. It has a role to supervise each means that is installed.

  The management terminal control unit 501 of the management terminal 5 displays an operation screen related to the use of the portable storage medium, communicates with a program inside the portable storage medium 2, performs an operation on the portable storage medium 2, and manages the management terminal 5. It has a role to supervise each means that is installed.

  The use terminal control means 601 of the use terminal 6 displays an operation screen for reading data from the portable storage medium 2, communicates with a program inside the portable storage medium 2, and operates the portable storage medium 2. And has a role of supervising each means mounted on the use terminal 5.

  In the present invention, some of the use conditions for managing the portable storage medium 2 and the data attribute for managing the data stored in the portable storage medium 2 use the system time, which is compared with the system time. As a result, information leakage prevention measures are implemented.

  Although the system time can be obtained from a computer, it is desirable to incorporate a clock function in the portable storage medium 2 because it may be camouflaged. Therefore, it is assumed that the clock function automatically synchronizes the time when connected to the management server 3 so that the user cannot correct the clock function without permission.

  Further, since it is necessary to incorporate a power source in order to drive the clock function, it is possible to forcibly erase data when the expiration date has passed by using the clock function and the power source.

The present invention has been described with the embodiment.
All of these embodiments of the present invention are not essential and can be modified according to the situation of the organization to be used. Various modifications are possible within the scope of the present invention.

  The functions (see the flowcharts in FIGS. 5 to 13B) of each means mounted on each computer (management server 3, management console 4, management terminal 5, and use terminal 6) shown in FIG. It is realized by reading a corresponding program (read from an external storage device such as an HDD) into the main storage device and executing it using hardware such as a CPU and memory that are components of the computer. These programs can be distributed via a network such as the Internet or a computer-readable recording medium such as ROM, FD, or DVD.

It is a figure which shows the structural example of the whole system of this invention. It is a figure which shows the structural example in the portable storage medium of this invention. It is a figure which shows the example of terminal management information DB stored in the management database in a management server. It is a figure which shows the example of medium management information DB stored in the management database in a management server. It is a figure which shows the example of data attribute DB stored in the management database in a management server. It is a figure which shows the example of medium operation log | history DB stored in the management database in a management server. It is a figure which shows the example of terminal operation log | history DB stored in the management database in a management server. It is a figure which shows the example of terminal authentication information DB stored in a portable storage medium. It is a figure which shows the example of usage condition DB stored in a portable storage medium. It is a figure which shows the example of data attribute DB stored in a portable storage medium. It is a figure which shows the example of medium operation log | history DB stored in a portable storage medium. It is a figure which shows the flow of a process which collects terminal specific information and registers with a management server. It is a figure which shows the flow of a process which collects medium specific information and registers with a management server. It is a figure which shows the flow of a process which collates a terminal authentication key and use conditions (the 1). It is a figure which shows the flow of a process which collates a terminal authentication key and use conditions (the 2). It is a figure which shows the flow of a process which collates a terminal authentication key and use conditions (the 3). It is a figure which shows the flow of a process which collates a terminal authentication key and use conditions (the 4). It is a figure which shows the flow of a process which records operation history in a portable storage medium. It is a figure which shows the flow of a lending process of a portable storage medium (the 1). It is a figure which shows the flow of a lending process of a portable storage medium (the 2). It is a figure which shows the flow of a return process of a portable storage medium. It is a figure which shows the flow of a process which registers a terminal authentication key into a portable storage medium (the 1). It is a figure which shows the flow of a process which registers a terminal authentication key into a portable storage medium (the 2). It is a figure which shows the flow of the write-in process of the data to a portable storage medium (the 1). It is a figure which shows the flow of the write-in process of the data to a portable storage medium (the 2). It is a figure which shows the flow of the read-out process of the data from a portable storage medium (the 1). It is a figure which shows the flow of the read-out process of the data from a portable storage medium (the 2). It is a figure which shows the conventional simple medium use management system.

Explanation of symbols

1: Network 2: Portable storage medium 21: Authentication utility storage area 211: Authentication key verification means 212: Area access means 22: Management utility storage area 221: Medium control means 222: Terminal authentication information DB
223: Data access means 224: Data encryption means 225: Data decryption means 23: Data storage area 231: Usage condition DB
232: Data attribute DB
233: Medium operation history DB
234: Data (encryption)
3: management server 301: management server control means 302: server information collection means 303: medium lending management means 304: medium return management means 305: terminal authentication key generation means 306: management database 307: terminal operation history management means 308: medium operation History management means 309: Medium inventory management means 310: Data transmission / reception means 4: Management console 401: Management console control means 402: Terminal information collection means 403: Medium lending means 404: Medium return means 405: Medium information collection means 406: Terminal authentication Key registration means 407: Data writing means 408: Medium access means 409: Unmanaged medium exclusion means 410: Terminal operation history upload means 411: Medium operation history upload means 412: Medium operation history browsing means 413: Medium inventory means 414: Data Sender and receiver 5: Management terminal 501: Management terminal control means 502: Terminal information collection means 503: Terminal authentication key registration application means 504: Data write application means 505: Medium access means 506: Unmanaged medium exclusion means 507: Terminal operation history upload means 508: Medium operation history upload means 509: Medium inventory means 510: Data transmission / reception means 6: Use terminal 601: Use terminal control means 602: Terminal information collection means 603: Medium access means 604: Unmanaged medium exclusion means 701: Management server 702 : Client 703: Simple medium 711: Simple medium information collection means 712: Client information collection means 713: Client selection means 714: Authentication key creation means 715: Management data writing means 716: Simple medium management DB (simple medium information storage means)
717: Client management DB (client information storage means)
718: Medium usage history DB
721: Simple medium information collection means 722: Management data collection means 723: Client information collection means 724: Authentication key creation means 725: Authentication key collation means 810: Input means 811: Display device

Claims (9)

A portable storage medium, a management server having a management database for storing management information of the portable storage medium, executing a process related to management of the portable storage medium, and operating the management server to operate the portable storage medium A management console capable of writing and reading data to and from the portable storage medium, a process for maintaining the use of the portable storage medium, and the portable storage medium A portable storage medium management system comprising a management terminal capable of writing data to and reading data from, and a use terminal capable of only reading data from a portable storage medium,
The portable storage medium includes a terminal authentication information DB that stores terminal authentication information including a terminal authentication key and access authority information, a use condition DB that stores use conditions regarding availability, and a data attribute that stores data attributes DB, when the management console or the management terminal or the use terminal is connected, terminal-specific information acquired from the connected management console, management terminal or use terminal, and medium-specific information of the portable storage medium Terminal authentication key generating means for generating a terminal authentication key from the terminal user name and password input by the user, terminal authentication key generated by the terminal authentication key generating means, and terminal authentication stored in the terminal authentication information DB The key is verified, and if the corresponding terminal authentication key exists, the authority information is read and stored in the use condition DB Medium control means for referring to the use condition and the data attribute stored in the data attribute DB, and controlling data writing or data reading from the management console or management terminal or use terminal based on the result. A portable storage medium management system.   As the access authority information, “authentication” for the management server, “read”, “write” and “setting” for the management console, “read” and “write” for the management terminal, use 2. The portable storage medium management system according to claim 1, wherein "reading" is set for the terminal.   The usage conditions include: availability flag, expiration flag, usage start time, usage expiration date, unauthorized access counter, unauthorized access allowable upper limit, inventory completed flag, inventory expiration date, inventory cycle, final inventory timestamp, history record availability flag, operation history 3. The portable storage medium management system according to claim 1, further comprising information on DB capacity, operation history upload time limit, operation history upload cycle, or last upload time stamp.   The portable storage medium management system according to any one of claims 1 to 3, wherein the attribute of the data includes information related to the remaining number of times of copying or a storage time limit for each data.   The portable storage medium further includes a medium operation history DB for storing an operation history for the medium, and each time an operation is performed, the operation contents and the time stamp at which the operation is performed and an object (operation target) are displayed as an operation history. The portable storage medium management system according to any one of claims 1 to 4, further comprising means for storing as a storage medium.   6. The portable storage medium management system according to claim 1, wherein the data writing is performed by encrypting data and the data reading is performed by decrypting the data.   The portable storage medium includes the use condition DB, the data attribute DB, the medium operation history DB, a data storage area including encrypted data, and a data access means for accessing the medium control means and the data storage area. An authentication utility area including a utility area and an area access means for accessing the management utility area, wherein the authentication utility area is a readable and non-writable area, and the management utility area includes the area access means. 7. The area according to claim 1, wherein the data storage area is an area that can be read and written only through the data access means. The portable storage medium management system described in 1.   The portable storage medium management system according to any one of claims 1 to 7, wherein the management server and the management console are mounted on the same computer. The portable storage medium management system according to claim 1, comprising only one of the management terminal and the use terminal .

Images