JP4662722B2 - Document protection management system and method - Google Patents

Description

  The present invention relates to a document protection management system and method, and more particularly to a document protection management system and method for encrypting and storing a document with an encryption key generated using employee attribute information (affiliated department, position, etc.).

When a document (especially confidential document) created by an employee using a terminal (such as a personal computer) is stored in a common database, employees other than those who have the authority to refer to and update this document may view it. To prevent this, the document is encrypted and stored using a common key (see, for example, Patent Document 1 shown below), or the document is encrypted using an electronic certificate, and the document is referenced and updated. There are restrictions. Further, when an employee who has the authority to refer to and update a document views a document encrypted and stored in the database, the employee decrypts the document using a common key or an electronic certificate.
JP 2000-267939 A

However, in the method of encrypting a document using a common key or electronic certificate, if the scope of employees who have authority to view and update the document changes due to personnel changes, etc., the common key or electronic certificate is changed and changed. It becomes necessary to encrypt and save the document again with a later common key or electronic certificate.
In addition, even if a document is created by the same employee, for example, it is a document that can be viewed only within a department, or a document that can be viewed only by employees of a predetermined post in the department. Since the range of employees is not necessarily the same, employees need to manage a plurality of common keys according to the number of documents.
Furthermore, in order to prevent employees other than those authorized to view and update the document from browsing, it is necessary for the employee not to know the common key.

An object of the present invention is to allow a document creator and a document viewer to enter their predetermined personal information so that the document creator and the document viewer manage a key for encrypting and decrypting the document. An object is to provide a document protection management system and method capable of encrypting and decrypting a document.

The document protection management system of the present invention includes a terminal (11) used by a document creator, another terminal (13) used by a document viewer, and these terminals (11, 13), which are interconnected with each other, and A document protection management system comprising a server (20, 30) in which attribute information relating to a department and job title of a document creator and a document viewer is stored, and a database (40) for storing an encrypted document, The terminal (11) includes personal information reading means (12) for reading the personal information of the document creator input by the document creator to encrypt the document, and the personal information of the document creator as the server ( and transmits to the 20, 30), means for receiving the attribute information of the document creator retrieved based from said server (20, 30) in the personal information of the document creator, said server (20 Upon receiving the attribute information of the document creator 30), to display the inquiry screen for inquiring a document reference and update permissions range based on the received the document creator attribute information, the document reference and update the document to be encrypted A means for inputting an authority range, and an encryption key for the document creator and an encryption key for the document viewer are generated based on the received attribute information of the document creator and the inputted document reference / update authority range. , and means for storing the documents to the use of an encryption key thus generated to the database by creating a document encrypted by encrypting (40), said other terminal (13), wherein said other personal information reading means for a document viewer reads the personal information of the document viewer entered to decrypt the encrypted document (14), the personal information of the document viewer server ( 0, 30), and means for receiving attribute information of the document viewer retrieved from the server (20, 30) based on the personal information of the document viewer; and the server (20, 30) When the attribute information of the document viewer is received from the document viewer, a decryption key for the document viewer is generated based on the received attribute information of the document viewer, and the database (40) is generated using the generated decryption key. and means for decoding the stored the encrypted document, the said server (20, 30) includes means for storing the personal information and the attribute information of the document creator and the document viewer, the Based on the personal information of the document creator or the document viewer received from the terminal (11) or the other terminal (13) , the stored attribute information of the document creator or the document viewer is searched. And means for transmitting the searched attribute information of the document creator or the document viewer to the terminal (11) or the other terminal (13).
In addition, the personal information reading means (12) and the other personal information reading means (14) are connected to the document creator from an IC card storing the employee code of the document creator and the employee code of the document viewer. It may be an IC card reader for reading the employee code and the employee code of the document viewer.

The document protection management method of the present invention includes a terminal (11) used by a document creator, another terminal (13) used by a document viewer, and these terminals (11, 13), and A document protection management method using a server (20, 30) storing attribute information of a document creator and a document viewer and a database (40) for storing an encrypted document, the server ( 20, 30) storing the personal information of the document creator and the document viewer, and attribute information regarding the department and position , and the document creator encrypts the document using the terminal (11). The personal information of the document creator input to the server is read, the personal information of the document creator is transmitted to the server (20, 30), and based on the personal information of the document creator from the server (20, 30). The When the retrieved attribute information of the document creator is received and the attribute information of the document creator is received from the server (20, 30), the document reference / update authority is received based on the received attribute information of the document creator. An inquiry screen for inquiring the range is displayed, the document to be encrypted and the document reference / update authority range are input, and the document is created based on the received attribute information of the document creator and the input document reference / update authority range. stored in the database (40) to create a generates an encryption key for encryption and document viewer for creator encrypted by encrypt a document the use of an encryption key thus generated document and, on the other hand, using the other terminal (13), reads the personal information of the document viewer entered to decrypt a document the document viewer is the encrypted personal of the document viewer Information is transmitted to the server (20, 30), the attribute information of the document viewer retrieved based on the personal information of the document viewer is received from the server (20, 30), and the server (20 When receiving the attribute information of the document viewer 30), to generate a decryption key for the document viewer based on the received the document viewer attribute information, said database using a decryption key thus generated ( decoding the stored the encrypted document 40), characterized in that.
Further, the predetermined personal information of the document creator and the predetermined personal information of the document viewer may be the employee code of the document creator and the employee code of the document viewer.

The document protection management system and method of the present invention have the following effects.
(1) The document creator and the document viewer can encrypt and decrypt the document by inputting their own personal information (for example, employee code and fingerprint). The viewer does not need to manage a key for encrypting and decrypting the document.
(2) Since the document can be encrypted simply by inputting the predetermined personal information (and document reference / update authority range) of the document creator, the document creator can encrypt the document even if the number of documents increases. There is no need to manage a plurality of keys.
(3) The document creator and the document viewer input their own personal information (for example, employee code, fingerprint, etc.) using a dedicated personal information reading means, so that the personal information of others (for example, other people's personal information) It is possible to prevent a document from being created or viewed using the employee code.
(4) For example, when an employee code is used as predetermined personal information, if the employee changes the department due to a personnel change, a decryption key is generated based on the attribute information of the employee after the personnel change. However, it is possible to make it impossible to view documents that can be viewed before the personnel change after the personnel change.

  The purpose of the document creator and the document viewer to be able to encrypt and decrypt the document by inputting his / her predetermined personal information is the purpose of the document creator's own personal information and the document viewer's own This is realized by obtaining the attribute information of the document creator and the attribute information of the document viewer from predetermined personal information, and generating an encryption key and a decryption key based on the acquired attribute information.

Embodiments of a document protection management system and method according to the present invention will be described below with reference to the drawings.
As shown in FIG. 1, a document protection management system 1 according to an embodiment of the present invention is connected to a first terminal 11 used by an employee who creates a document (document creator) and the first terminal 11. Connected to the first IC card reader 12 (personal information reading means), the second terminal 13 (other terminal) used by the employee browsing the document (document reader), and the second terminal 13 A second IC card reader 14 (another personal information reading means), an authentication server 20 interconnected with the first and second terminals 11 and 13 via an in-house LAN, and the first and second terminals 11 , 13 and an OA server 30 interconnected by an in-house LAN, and a database 40 interconnected by first and second terminals 11 and 13 by an in-house LAN.

The authentication server 20 stores an affiliation code / position code table indicating the department and position, which is attribute information of each employee, as shown in Table 1. In addition, when the employee changes, the authentication server 20 has the personnel server so that an affiliation code / posture code table reflecting the department and job title of the employee after the personnel change is immediately stored in the authentication server 20. It is linked with an information management server (not shown).

  Here, the employee code is one piece of personal information assigned to each employee and is stored in an IC card owned by each employee.

As shown in Table 2, the affiliation code indicates the department to which each employee belongs, and also indicates the working group if there is a working group across the departments in the company. The affiliation code consists of 3 digits, the most significant digit indicates the department name, and the lower 2 digits indicate the section name. That is, in the example shown in Table 2, the most significant digit “1” of the affiliation code “100” indicates “information system part”, and the lower two digits “00” indicates “entire information system part”. The most significant digit “1” of the affiliation code “110” indicates “information system section”, and the lower two digits “10” indicate “section a”. The most significant digit “1” of the affiliation code “120” indicates “information system section”, and the lower two digits “20” indicate “section b”. The most significant digit “4” of the affiliation code “400” indicates “general affairs department”, and the lower two digits “00” indicates “entire general affairs department”. In the affiliation code “410”, the most significant digit “4” indicates “general affairs department”, and the lower two digits “10” indicate “section c”. The most significant digit “9” of the affiliation code “900” indicates “dd working group”, and the lower two digits “00” indicates “the entire dd working group”.

As shown in Table 3, the position code indicates the position of each employee in the department to which the employee belongs, and also indicates the position in the working group when a working group is established across the departments in the company.

The OA server 30 stores an affiliation code list indicating the affiliation department as attribute information of each employee as shown in Table 4 as an example. In this example, the heads of employee code “111111” and job title “1” (see Table 1) belong to “information system department” and “dd working group”, and employee code “222222” and job title “2” (See Table 1)
Indicates that the person in charge of employee code “333333” and post code “3” (see Table 1) belongs to “general affairs department c section”. Note that the OA server 30 manages the personnel information management described above so that when the employee changes, the affiliation code list reflecting the employee's department after the personnel change is immediately stored in the OA server 30. Linked with the server.

  The database 40 stores the encrypted document as a document file. Further, when an employee views an encrypted document, the employee needs to read the corresponding document file from the database 40 and decrypt the encrypted document in the read document file.

Next, the operation of the document protection management system 1 when encrypting a document will be described with reference to the flowchart shown in FIG.
When the department manager A of the employee code “111111” belonging to the department “information system department” creates a document and saves it in the database 40, the department manager A is connected to the first terminal 11 being used. The IC card is inserted into the first IC card reader 12 to read the employee code “111111” stored in the IC card. The employee code “111111” read by the first IC card reader 12 is sent to the first terminal 11 (step S1).

Subsequently, the employee code “111111” is transmitted from the first terminal 11 to the authentication server 20. The authentication server 20 searches the affiliation code / position code table (see Table 1) based on the received employee code “111111”, and acquires the affiliation code “100” and the position code “1” of the general manager A. The authentication server 20 transmits the affiliation code “100” and job title code “1” of the general manager A to the first terminal 11 (step S2).
The first terminal 11 also transmits the employee code “111111” to the OA server 30. The OA server 30 searches the affiliation code list (see Table 4) based on the received employee code “111111”, and acquires the affiliation code lists “100” and “900” of the general manager A. The OA server 30 transmits the acquired department A's belonging code list “100” and “900” to the first terminal 11 (step S3).

The first terminal 11 belongs to two departments “information system department” and “dd working group” according to the affiliated code list “100” and “900” of the department manager A received from the OA server 30. (See Table 2), whether the range having the authority to refer to and update the document to be encrypted (hereinafter referred to as “document reference / update authority range”) is “the entire information system section” or “information An inquiry screen for inquiring the department manager A whether it is “system department a section”, “information system department b section” or “dd working group” is displayed (step S4).
Further, according to the position code “1” of the department manager A received from the authentication server 30, the first terminal 11 has the department manager A's department as “department manager” (see Table 3). An inquiry screen for inquiring the department manager A as to which position is over is displayed (step S4).

  The department manager A looks at the inquiry screen displayed on the first terminal 11 and inputs the document reference / update authority range (step S5).

The first terminal 11 encrypts the document by generating an encryption key based on the received attribute information of the general manager A and the input document reference / update authority range. The operation of the first terminal 11 at this time The following description will be divided into first to fourth cases having different document reference / update authority ranges. (First case)
When the department manager A inputs the department “information system department a section” and the title “section manager or higher” as the document reference / update authority range, the first terminal 11 can allow the section manager of the information system department a section or higher to view the document. In order to do this, a 4-digit code “1001” using “100” indicating “information system section” in the affiliation code and “1” indicating “department manager” in the position code and “information system section” in the affiliation code Two encryption keys are generated using “110” indicating “section a” and a four-digit code “1102” using “2” indicating “section manager” among the position codes, respectively (step S6). The document is encrypted with each of the two encryption keys (step S7). Documents encrypted with the two encryption keys are combined into one document file and stored in the database 40 (step S8).

(Second case)
When the department manager A inputs the department “entire information system department” and the title “section manager or higher” as the document reference / update authority range, the first terminal 11 is configured so that the section manager and above of the information system department can browse the document. The four-digit code “1001” using “100” indicating “Information System Department” in the affiliation code and “1” indicating “Department Manager” in the position code and “Information System Department a Section” in the affiliation code In addition, encryption is performed using “110” and “120” indicating “information system section b section” and four-digit codes “1102” and “1202” using “2” indicating “section manager” among the position codes. After generating three keys (step S6), the document is encrypted with each of the three generated encryption keys (step S7). Documents encrypted with the three encryption keys are combined into one document file and stored in the database 40 (step S8).

(Third case)
When the department manager A inputs the department “whole information system department” and the title “in charge or higher” as the document reference / update authority range, the first terminal 11 enables the person in charge of the information system department or higher to view the document. The four-digit code “1001” using “100” indicating “Information System Department” in the affiliation code and “1” indicating “Department Manager” in the position code and “Information System Department a Section” in the affiliation code And “110” and “120” indicating “information system section b section” and “2” and “3” indicating “section manager” and “person in charge” of the position codes, respectively, “4” code “1102”, After generating five encryption keys using “1103”, “1202”, and “1203” (step S6), each of the documents is encrypted using the generated five encryption keys (step S6). Step S7). The documents encrypted with the five encryption keys are collected into one document file and stored in the database 40 (step S8).

(Fourth case)
When the department manager A inputs the department “dd working group” as the document reference / update authority range, the first terminal 11 includes “ After generating an encryption key using a four-digit code “9000” using “900” indicating “dd working group” (step S6), the document is encrypted with the generated encryption key (step S7). The encrypted document is stored in the database 40 as a document file (step S8).

Next, the operation of the document protection management system 1 when decrypting a document encrypted in this way will be described with reference to the flowchart of FIG.
For manager B (document reader) of employee code “222222” belonging to department “information system department a section” to make department “information system department a section” and title “section manager or higher” within the document reference / update authority range When browsing a document (first case document) encrypted with two encryption keys generated using the four-digit codes “1001” and “1102”, the section manager B uses The document file of this document is read from the database 40 to the second terminal 13 and the IC card is inserted into the second IC card reader 14 connected to the second terminal 13, and the IC card is inserted. The stored employee code “222222” is read. The employee code “222222” read by the second IC card reader 14 is sent to the second terminal 13 (step S11).

Subsequently, the employee code “222222” is transmitted from the second terminal 13 to the authentication server 20. The authentication server 20 searches the department code / posture code table (see Table 1) based on the received employee code “222222”, and acquires the department code “110” and post code “2” of the section manager B. The authentication server 20 transmits the acquired department code “110” and post code “2” of the section manager B to the second terminal 13 (step S12).
The second terminal 13 also transmits the employee code “222222” to the OA server 30. The OA server 30 searches the affiliation code list (see Table 4) based on the received employee code “222222” and acquires the affiliation code list “110” of the section manager B. The OA server 30 transmits the acquired section code “110” of the section manager B to the second terminal 13 (step S13).

The second terminal 13 uses a four-digit code “1102” using the section code “110” of the section manager B received from the OA server 30 and the post code “2” of the section manager B received from the authentication server 20. After the decryption key is generated (step S14), the encrypted document in the document file is decrypted with the generated decryption key “1102” (step S15).
At this time, the document encrypted with the encryption key generated using the 4-digit code “1001” cannot be decrypted with the decryption key “1102”, but the encryption generated using the 4-digit code “1102”. Since the document encrypted with the key can be decrypted with the decryption key “1102”, the second terminal 13 displays the decrypted document on the screen (step S16). Thereby, the section manager B can browse the document created by the section manager A.

  Similarly, the section manager B uses the four-digit codes “1001”, “1102”, and “1202” to set the department “entire information system section” and the title “section manager or higher” as the document reference / update authority range. In order to make the document reference / update authority range the document encrypted with the three generated encryption keys (document of the second case), the department “whole information system department”, and the post “in charge” or more Browsing a document (third case document) encrypted with five encryption keys generated using the codes “1001”, “1102”, “1103”, “1202”, and “1203” it can.

  On the other hand, the section manager B creates a document (fourth case) encrypted with an encryption key generated using the four-digit code “9000” in order to set the department “dd working group” as the document reference / update authority range. Even if an attempt is made to browse the document), the document cannot be decrypted with the decryption key “1102”. Thereby, it is possible to prevent the section manager B from browsing the document created by the section manager A for the dd working group.

  In addition, when the section manager B updates the contents of the encrypted document, the second terminal 13 encrypts the updated document with the decryption key used when decrypting the encrypted document. After that, the document file of the encrypted document may be overwritten and saved.

The document protection management system 1 according to one embodiment of the present invention has been described above, and modifications thereof will be described below.
(1) Although the employee protection code is used as the predetermined personal information in the document protection management system 1, other personal information (for example, fingerprint, iris, etc.) that can identify an individual may be used.
(2) In the document protection management system 1, the employee code “111111” of the department manager A (document creator) and the employee code “222222” of the section manager B (document viewer) are sent to the first and second IC card readers 12 and 14. Although it was read by (personal information reading means), the manager A and the manager B may instead input their own employee codes on the keyboard. At this time, a password may be entered at the same time in order to confirm whether or not the user is the person himself / herself.
(3) In the document protection management system 1, the encryption key is created using the document reference / update authority range, but when there is no need to limit the document reference / update authority range, only the attribute information of the document creator is used. An encryption key may be created (for example, in the example described above, using the 4-digit code “1001” using the department A's belonging code “100” and post code “1”).
(4) Although the authentication server 20 and the OA server 30 are separate servers in the document protection management system 1, the authentication server 20 and the OA server 30 may be a single server.

(5) Although the document protection management system 1 encrypts the document with a plurality of encryption keys depending on the document reference / update authority range (see the first to third cases), for example, as shown in Table 5, To reduce the number of encryption keys by creating a correspondence table of codes indicating update authority ranges (encryption key creation codes in the document protection management system 1) and encryption keys (encryption key creation codes in the modification) Thus, the number of documents to be encrypted may be reduced. In this case, when the section manager B views the document in the first case, the second terminal 12 uses the section code list “110” of the section manager B and the post code “2” 4. Three decryption keys are created using the encryption key creation codes “AAAA”, “BBBB” and “CCCC” in the modified example including the digit code “1102”, and the section manager B uses the created three decryption keys. When the document to be browsed is decrypted and decrypted with any one of the three decryption keys, the decrypted document is displayed on the screen.

  As described above, the document protection management system and method of the present invention can be used, for example, for encrypting and storing documents in a company common database.

1 is a block diagram illustrating a document protection management system according to an embodiment of the present invention. FIG. Example 1 4 is a flowchart for explaining an operation when the document protection management system 1 shown in FIG. 1 encrypts a document. Example 1 6 is a flowchart for explaining an operation when the document protection management system 1 shown in FIG. 1 decrypts a document. Example 1

1 Document Protection Management System 11, 13 Terminal 12, 14 IC Card Reader 20 Authentication Server 30 OA Server 40 Database S1-S8, S11-S16 Steps

Claims (4)

A terminal (11) used by the document creator, another terminal (13) used by the document viewer, and these terminals (11, 13) are interconnected with each other, and to which the document creator and the document viewer belong A document protection management system comprising servers (20, 30) in which attribute information relating to departments and positions is stored, and a database (40) for storing encrypted documents,
It said terminal (11),
Personal information reading means (12) for reading the personal information of the document creator inputted by the document creator to encrypt the document ;
The personal information of the document creator is transmitted to the server (20, 30), and the attribute information of the document creator retrieved from the server (20, 30) based on the personal information of the document creator is received. Means to
When the attribute information of the document creator is received from the server (20, 30), an inquiry screen for inquiring a document reference / update authority range is displayed based on the received attribute information of the document creator, and the document to be encrypted Means for inputting the document reference / update authority range;
Based on the received attribute information of the document creator and the inputted document reference / update authority range, the encryption key for the document creator and the encryption key for the document viewer are generated, and the generated encryption key is used. and means for storing the documents to the encrypted database to create a document that has been encrypted by encrypting (40) Te,
The second terminal (13),
Other personal information reading means (14) for reading the personal information of the document viewer input by the document viewer to decrypt the encrypted document;
The personal information of the document viewer is transmitted to the server (20, 30) and the attribute information of the document viewer retrieved from the server (20, 30) based on the personal information of the document viewer is received. Means to
When the attribute information of the document viewer is received from the server (20, 30), a decryption key for the document viewer is generated based on the received attribute information of the document viewer, and the generated decryption key is used. And means for decrypting the encrypted document stored in the database (40),
The server (20, 30) is,
Means for storing personal information and attribute information of the document creator and the document viewer;
Based on the personal information of the document creator or the document viewer received from the terminal (11) or the other terminal (13) , the stored attribute information of the document creator or the document viewer is searched. And means for transmitting the searched attribute information of the document creator or the document viewer to the terminal (11) or the other terminal (13). system.   The personal information reading means (12) and the other personal information reading means (14) are connected to the document creator's employee code from an IC card storing the document creator's employee code and the document viewer's employee code. 2. The document protection management system according to claim 1, wherein the document protection management system is an IC card reader for reading the employee code of the document viewer. The terminal (11) used by the document creator, the other terminal (13) used by the document viewer, and the attributes of the document creator and the document viewer that are interconnected with these terminals (11, 13) A document protection management method using a server (20, 30) storing information and a database (40) for storing an encrypted document,
In the server (20, 30), the personal information of the document creator and the document viewer, and attribute information related to the department and position,
Using the terminal (11) ,
Reading the personal information of the document creator entered by the document creator to encrypt the document;
The personal information of the document creator is transmitted to the server (20, 30), and the attribute information of the document creator retrieved from the server (20, 30) based on the personal information of the document creator is received. And
When the attribute information of the document creator is received from the server (20, 30), an inquiry screen for inquiring a document reference / update authority range is displayed based on the received attribute information of the document creator, and the document to be encrypted Enter the document reference / update authority range ,
Based on the received attribute information of the document creator and the inputted document reference / update authority range, the encryption key for the document creator and the encryption key for the document viewer are generated , and the generated encryption key is used. And encrypting the document to be encrypted to create an encrypted document and storing it in the database (40),
On the other hand, using the other terminal (13) ,
Reading the personal information of the document viewer entered by the document viewer to decrypt the encrypted document;
The personal information of the document viewer is transmitted to the server (20, 30) and the attribute information of the document viewer retrieved from the server (20, 30) based on the personal information of the document viewer is received. And
When the attribute information of the document viewer is received from the server (20, 30), a decryption key for the document viewer is generated based on the received attribute information of the document viewer , and the generated decryption key is used. said decrypting said encrypted document stored in the database (40), the document protection management method characterized by Te.   4. The document creator's own personal information and the document viewer's own personal information are the document creator's employee code and the document viewer's employee code, respectively. Document protection management method.

Images