JP2010016465A - Authority verification apparatus, user terminal device, key generating apparatus, access control system, computer program, authority verification method, operation request notifying method, key generating method and access control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To verify the operation authority of a user even when throughput and communicability are limited. <P>SOLUTION: By using user identification data generated by an identification generation part 123 as a public key in an ID base cipher system, a communication key ciphering part 133 ciphers a common key generated by a communication key generation part 131 and a ciphered communication key transmission part 142 transmits the ciphered common key. By using the common key generated by the identification generation part 123 as a decipher key, an operation request deciphering part 152 deciphers a ciphered operation request received by a ciphered operation request reception part 151, and when it is correctly deciphered, an operation request verification part 162 determines that the user has the operation authority. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technique for determining whether a user of a user terminal device has authority to operate a target device and controlling access to the target device.

  There is a technique for verifying a user and controlling access using encrypted communication.

The encryption communication method includes a symmetric encryption method and an asymmetric encryption method.
The symmetric encryption method is an encryption method in which an encryption key used for encryption and a decryption key used for decryption are the same. The sending device and the receiving device share the same common key, the sending device encrypts using the shared common key as an encryption key, and the receiving device shares Decryption is performed using the common key as a decryption key. In symmetric cryptography, the issue is how to share a common key without being known by a third party.
An asymmetric encryption method is an encryption method in which an encryption key and a decryption key are different. In particular, even if one of the encryption key and the decryption key is disclosed and known to a third party, the third party A method that cannot infer the other is called a public key cryptosystem. In public key cryptography, the key that may be known to a third party is called a public key, and the key that must be kept secretly is called a secret key. For example, when the encryption key is disclosed, the transmitting device encrypts using the disclosed public key as the encryption key, and the receiving device uses the secret key held in the secret key as the decryption key. Use as a decryptor. This eliminates the need for the transmitting device to share a secret with the receiving device. When the decryption key is disclosed, the transmitting device encrypts the secret key held in the secret key as the encryption key, and the receiving device uses the disclosed public key as the decryption key. Use to decrypt. As a result, anyone can decrypt it, but since a third party cannot falsify it, it is used for signatures and the like. In the public key cryptosystem, there is a problem of means for verifying that a public key disclosed corresponds to a secret key held by a transmission destination or transmission source device. This is because spoofing and the like cannot be prevented unless the correspondence between the public key and the device holding the secret key can be verified.
One method for verifying the correspondence between a public key and a device that holds a secret key is a method that uses a public key infrastructure (PKI). In a public key infrastructure, data representing the correspondence between a public key and a device that holds a private key corresponding to the public key is used as a public key certificate, and the public key certificate is verified. And the device holding the private key are verified. In order to prevent the public key certificate from being falsified by a third party, the public key certificate is signed with a private key of a certification authority (CA) that issued the public key certificate. In order to verify the signature attached to the public key certificate, the public key of the certification authority is required. The public key of the certification authority can be obtained from the public key certificate of the certification authority. In the method using the public key infrastructure, the correspondence between the public key and the device holding the private key is verified by tracing the public key certificate in this way.
As another method, there is a method using an ID-based encryption method. The ID-based encryption method is a public key encryption method in which an apparatus ID (manufacturing number, apparatus number, MAC address, IP address, mac address, and other data for identifying the apparatus) is used as it is as a public key of the apparatus. . Since the ID of the device is used as a public key, it is not necessary to verify the correspondence between the public key and the device holding the secret key.
JP 2006-325072 A JP 2004-112538 A Japanese Patent Laid-Open No. 10-30367 JP 2002-290394 A JP 2006-208967 A JP 2003-32235 A JP 2005-198189 A JP 2006-319457 A William Sterlings "Cryptography and Network Security Theory and Practice" Pearson Education, 618-619, ISBN 4-89471-367-5, 2001.

When performing access control using encrypted communication, the issue is how to verify the user's authority.
In particular, an embedded device or the like may have a low processing capability or communication capability, and it is desired to reduce the processing load for verifying the authority of the user.
The present invention has been made to solve the above-described problems, for example, and enables verification of a user's operation authority even when processing capability and communication capability are limited. Objective.

The authority verification device according to the present invention is:
In the authority verification device that verifies whether the user has the authority to operate the target device,
A processing device that processes data, a transmitting device that transmits data, a receiving device that receives data, an identification acquisition unit, a communication key generation unit, a communication key encryption unit, an encrypted communication key transmission unit, An encryption operation request reception unit, an operation request decryption unit, an operation request verification unit, and an operation request notification unit,
The identification acquisition unit acquires user identification data for identifying a user using the processing device,
The communication key generation unit generates an encryption key and a decryption key corresponding to the encryption key using the processing device,
The communication key encryption unit encrypts the encryption key generated by the communication key generation unit using the user identification data acquired by the identification acquisition unit using an ID-based encryption method using the processing device. Into an encrypted communication key,
The encrypted communication key transmission unit transmits the encrypted communication key encrypted by the communication key encryption unit using the transmission device,
The encrypted operation request receiving unit receives an encrypted operation request obtained by encrypting an operation request message representing an operation on the target device, using the receiving device,
The operation request decryption unit decrypts the encryption operation request received by the encryption operation request reception unit using the decryption key generated by the communication key generation unit using the processing device, and performs a decryption operation As a request,
The operation request verification unit determines whether or not the decryption operation request decrypted by the operation request decryption unit is correctly decrypted using the processing device. Judge that there is,
When the operation request verification unit determines that the operation authority has the operation authority using the processing device, the operation request notification unit sends the decryption operation request decrypted by the operation request decryption unit to the target device as an operation request message. It is characterized by notifying.

  According to the authority verification device according to the present invention, since the encryption key (common key) is encrypted by the ID-based encryption method, there is no need to verify the validity / validity of the public key using PKI. Even when the authority verification device 100 is provided in an apparatus such as an embedded device that has limited processing capability and communication capability, the operation authority of the user can be verified.

Embodiment 1 FIG.
The first embodiment will be described with reference to FIGS.

FIG. 1 is a system configuration diagram showing an example of the overall configuration of an access control system 800 in this embodiment.
The access control system 800 includes a key generation device 400 and a plurality of user terminal devices 300a to 300d (hereinafter referred to as “user terminal device 300” when there is no need to distinguish between the plurality of user terminal devices 300a to 300d). And a plurality of execution devices 200a to 200c (also referred to as “execution device 200”).

  The key generation device 400 is a device that generates a secret key in the ID-based encryption method. The key generation device 400 receives data for identifying a user (hereinafter referred to as “user identification data”) from the user terminal device 300, generates a secret key corresponding to the received user identification data, and generates the secret key. The private key is returned to the user terminal device 300.

  The user terminal device 300 inputs an operation request for the execution device 200 by the user, and passes the input operation request to the execution device 200.

  The execution device 200 receives an operation request from the user terminal device 300, confirms whether the user has the authority to perform the operation, and executes the process based on the operation if there is the authority.

There are a plurality of users having authority to operate the execution apparatus 200. Each user has one user terminal device 300 and operates the execution device 200 via his user terminal device 300.
Each execution device 200 has a different user who has the authority to perform the operation, and the range of the authorized operation varies depending on the user.
For example, a user who has authority to operate the execution device 200a includes a user of the user terminal device 300a (hereinafter referred to as “user a”) and a user of the user terminal device 300b (hereinafter referred to as “user b”). The user of the user terminal device 300c and the user of the user terminal device 300d are not authorized to operate the execution device 200a. The user a has administrator authority of the execution apparatus 200a and has authority to perform all operations on the execution apparatus 200a, but the user b has only general user authority of the execution apparatus 200a. The user has the authority to monitor the state of the execution apparatus 200a, but does not have the authority to perform the operation to change the state of the execution apparatus 200a.

The key generation device 400 manages user authority.
The execution device 200 encrypts data for verifying whether the user of the user terminal device 300 has authority by using an ID-based encryption method and passes the data to the user terminal device 300.
The key generation device 400 determines whether the user of the user terminal device 300 has authority, and when determining that the user has authority, passes the secret key in the ID-based encryption method to the user terminal device 300.
The user terminal device 300 decrypts the data received from the execution device 200 using the secret key received from the key generation device 400 by the ID-based encryption method.
The execution device 200 recognizes that the user of the user terminal device 300 is authorized when the user terminal device 300 can correctly decrypt the data passed to the user terminal device 300.

FIG. 2 is a diagram illustrating an example of hardware resources of the key generation device 400, the user terminal device 300, and the execution device 200 according to this embodiment.
The key generation device 400, the user terminal device 300, and the execution device 200 include a CPU 911 (also referred to as a central processing unit, a central processing device, a processing device, an arithmetic device, a microprocessor, a microcomputer, or a processor) that executes a program. ing. The CPU 911 is connected to the ROM 913, the RAM 914, the communication device 915, the display device 901, the keyboard 902, the mouse 903, the FDD 904, the CDD 905, the printer device 906, the scanner device 907, and the magnetic disk device 920 via the bus 912, and the hardware. Control the device. Instead of the magnetic disk device 920, a storage device such as an optical disk device or a memory card read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of a storage device or a storage unit.
A communication device 915, a keyboard 902, a scanner device 907, an FDD 904, and the like are examples of an input unit and an input device.
Further, the communication device 915, the display device 901, the printer device 906, and the like are examples of an output unit and an output device.

The communication device 915 is connected to a facsimile machine 932, a telephone 931, a LAN 942, and the like. The communication device 915 is not limited to the LAN 942, and may be connected to the Internet 940, a WAN (wide area network) such as ISDN, or the like. When connected to a WAN such as the Internet 940 or ISDN, the gateway 941 is unnecessary.
The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922.

The program group 923 stores a program for executing a function described as “˜unit” in the description of the embodiment described below. The program is read and executed by the CPU 911.
The file group 924 includes information, data, signal values, variable values, and parameters that are described as “determination results of”, “calculation results of”, and “processing results of” in the description of the embodiments described below. Are stored as items of “˜file” and “˜database”. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, Used for CPU operations such as calculation, calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.
In addition, the arrows in the flowcharts described in the following description of the embodiments mainly indicate input / output of data and signals. The data and signal values are the RAM 914 memory, the FDD 904 flexible disk, the CDD 905 compact disk, and the magnetic field. The data is recorded on a recording medium such as a magnetic disk of the disk device 920, another optical disk, a mini disk, or a DVD (Digital Versatile Disk). Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In the description of the embodiments described below, what is described as “to part” may be “to circuit”, “to device”, and “to device”, and “to step” and “to”. “Procedure” and “˜Process” may be used. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” described below. Alternatively, the procedure or method of “to part” described below is executed by a computer.

FIG. 3 is a block configuration diagram showing an example of a functional block configuration of the key generation device 400 in this embodiment.
The key generation device 400 includes a generation user identification reception unit 411, a signature reception unit 412, a public key certificate storage unit 421, a generation individual identification acquisition unit 422, a signature verification unit 423, a role storage unit 431, a generation role acquisition unit 432, A generation target identification acquisition unit 433, an authority determination unit 434, a secret key generation unit 441, a secret key encryption unit 442, and an encrypted secret key transmission unit 451 are included.

  The generated user identification reception unit 411 uses the communication device 915 to receive the user identification data transmitted by the user terminal device 300. Using the CPU 911, the generated user identification receiving unit 411 outputs the received user identification data.

The signature receiving unit 412 receives the signature data transmitted by the user terminal device 300 using the communication device 915. The signature data is data generated from the user identification data by the user terminal device 300. By verifying the signature data, it can be confirmed that the user identification data transmitted by the user terminal device 300 has not been altered in the middle. The signature method includes a public key signature method based on a normal public key encryption method, an ID-based signature method based on an ID-based encryption method, and the like. Any signature method may be used. In this example, a public key signature method based on a normal public key encryption method is used as the signature method.
Using the CPU 911, the signature receiving unit 412 outputs the received signature data.

  The public key certificate storage unit 421 stores a public key certificate for each user using the magnetic disk device 920. The public key certificate is data that proves that the user's public key corresponds to the user's private key.

The generated individual identification acquisition unit 422 uses the CPU 911 to input the user identification data output by the generated user identification receiving unit 411.
The generated individual identification acquisition unit 422 uses the CPU 911 to identify the user of the user terminal device 300 that has transmitted the input user identification data to the key generation device 400. The generated individual identification acquisition unit 422 uses the CPU 911 to acquire data that individually identifies the identified user (hereinafter referred to as “individual identification data”). For example, the user identification data received by the generated user identification receiving unit 411 includes individual identification data, and the generated individual identification acquisition unit 422 uses the CPU 911 to extract the individual identification data included in the user identification data. Thus, the individual identification data is acquired.
Using the CPU 911, the generated individual identification acquisition unit 422 outputs the acquired individual identification data.

  The individual identification data identifies the individual user (or the user terminal device 300 of the user), and the correspondence between the user (or the user terminal device 300) and the individual identification data is as follows. In principle, it does not change. On the other hand, the user identification data identifies the user in the current operation on the execution device 200. Therefore, the correspondence between the user and the user identification data may not change or may change. When the correspondence between users and user identification data changes, different user identification data may correspond to a certain user depending on the situation, or the same user identification data may correspond to different users depending on the situation. Also good.

Using the CPU 911, the signature verification unit 423 uses the CPU 911 to output user identification data output from the generated user identification reception unit 411, signature data output from the signature reception unit 412, and individual identification data output from the generated individual identification acquisition unit 422. Enter.
Using the CPU 911, the signature verification unit 423 acquires a public key certificate for the user identified by the input individual identification data from the public key certificate stored in the public key certificate storage unit 421.
Using the CPU 911, the signature verification unit 423 acquires the user's public key from the acquired public key certificate.
Using the CPU 911, the signature verification unit 423 uses the public key signature method to decrypt the input signature data using the acquired public key as a decryption key. Hereinafter, data obtained by decrypting the signature data by the signature verification unit 423 is referred to as “decrypted signature data”.
Using the CPU 911, the signature verification unit 423 compares the decrypted decrypted signature data with the input user identification data to determine whether the user identification data has been altered.
If it is determined that the user identification data has not been altered, the signature verification unit 423 uses the CPU 911 to output the input individual identification data.

  The role storage unit 431 uses the magnetic disk device 920 to represent data indicating the correspondence between the user of the user terminal device 300, the execution device 200, and the role that the user has for the execution device 200 ( Hereinafter referred to as “role correspondence data”). The role of the user means, for example, a classification such as “administrator” or “general user”, and there is a difference in authority to operate the execution apparatus 200 depending on the role.

FIG. 4 is a diagram schematically showing an example of role correspondence data 510 stored in the role storage unit 431 in this embodiment.
The role correspondence data 510 is data composed of a plurality of records, for example, with the individual identification data 511, the target identification data 512, and the role data 513 as a set of data (records).
In this figure, the individual identification data 511 is arranged in the left column, the object identification data 512 is arranged in the middle column, the role data 513 is arranged in the right column, and the individual identification data 511 arranged side by side and the object identification The data 512 and the role data 513 represent one record.
Individual identification data 511 is data for individually identifying a user.
The target identification data 512 is data for identifying the execution device 200.
The role data 513 is data for identifying a role.

In the role correspondence data 510 shown in this example, for example, the top record indicates that the user identified by the individual identification data 511 “a” (for example, the user of the user terminal device 300a) is subject identification data. This indicates that the execution device 200 (for example, the execution device 200a) identified by 512 “A” has a role (for example, a role as an administrator) identified by the role data “ADMIN”.
Note that the format of the role correspondence data 510 shown in this figure is an example, and any format can be used to indicate what role each user has for each execution device 200. The format of the role correspondence data may be another format.

  Returning to FIG. 3, the description of the functional blocks of the key generation device 400 will be continued.

The generation role acquisition unit 432 uses the CPU 911 to input the user identification data output by the generation user identification reception unit 411.
The generation role acquisition unit 432 uses the CPU 911 and based on the input user identification data, the role data indicating what role the user intends to operate the execution device 200 is based on. To get. For example, the user identification data received by the generated user identification receiving unit 411 includes role data, and the generated role acquisition unit 432 uses the CPU 911 to extract the role data included in the user identification data, thereby Get the data.
Using the CPU 911, the generation role acquisition unit 432 outputs the acquired role data.

The generation target identification acquisition unit 433 uses the CPU 911 to input the user identification data output from the generation user identification reception unit 411.
Using the CPU 911, the generation target identification acquisition unit 433 acquires target identification data representing the execution device 200 that the user is trying to operate based on the input user identification data. For example, the user identification data received by the generated user identification reception unit 411 includes target identification data, and the generation target identification acquisition unit 433 uses the CPU 911 to extract the target identification data included in the user identification data. Thus, the object identification data is acquired.
Using the CPU 911, the generation target identification acquisition unit 433 outputs the acquired target identification data.

The authority determination unit 434 uses the CPU 911 to input the individual identification data output from the signature verification unit 423, the role data output from the generation role acquisition unit 432, and the target identification data output from the generation target identification acquisition unit 433. To do.
The authority determining unit 434 uses the CPU 911 to identify the user identified by the input individual identification data based on the role-corresponding data stored in the role storage unit 431 by the input target identification data. On the other hand, it is determined whether or not it has a role identified by the input role data.
The authority determination unit 434 uses the CPU 911 to output data representing the determination result.

Using the CPU 911, the secret key generation unit 441 inputs the data output from the authority determination unit 434.
The secret key generation unit 441 uses the CPU 911 to output the generated user identification reception unit 411 when the user has the role of the execution device 200 based on the determination result represented by the input data. Enter the user identification data.
Using the CPU 911, the secret key generation unit 441 uses the input user identification data as a public key in the ID-based encryption method, and generates a secret key corresponding to the public key.
Using the CPU 911, the secret key generation unit 441 outputs the generated secret key.

Using the CPU 911, the secret key encryption unit 442 inputs the secret key output from the secret key generation unit 441 and the individual identification data output from the signature verification unit 423.
Using the CPU 911, the private key encryption unit 442 obtains a public key certificate for the user identified by the input individual identification data from the public key certificate stored in the public key certificate storage unit 421. To do.
Using the CPU 911, the secret key encryption unit 442 acquires the user's public key from the acquired public key certificate.
Using the CPU 911, the secret key encryption unit 442 encrypts the input secret key using the acquired public key as an encryption key by a public key cryptosystem. Hereinafter, data (encrypted text) obtained by encrypting the secret key by the secret key encryption unit 442 is referred to as “encrypted secret key”.
Using the CPU 911, the secret key encryption unit 442 outputs the encrypted encrypted secret key.

Using the CPU 911, the encrypted secret key transmission unit 451 inputs the encrypted secret key output from the secret key encryption unit 442.
The encrypted secret key transmission unit 451 uses the communication device 915 to send the user identification data received by the generated user identification reception unit 411 and the user terminal device 300 that has transmitted the signature data received by the signature reception unit 412. On the other hand, the input encryption private key is transmitted.

  In this example, the private key encryption unit 442 uses a normal public key encryption method as the encryption method for encrypting the secret key. However, the encryption is performed by an ID-based encryption method or other encryption methods. May be. In addition, any scheme other than encryption may be used as long as the secret key can be safely delivered to the user terminal device 300 without being known to the third party or altered by the third party. It is good.

FIG. 5 is a block configuration diagram showing an example of a functional block configuration of the user terminal device 300 in this embodiment.
The user terminal device 300 includes a target input unit 311, a role input unit 312, an operation input unit 313, an authority request generation unit 321, an authority request transmission unit 322, a terminal user identification reception unit 331, a terminal user identification storage unit 341, User private key storage unit 342, signature generation unit 343, terminal user identification transmission unit 351, signature transmission unit 352, encrypted private key reception unit 361, private key decryption unit 362, communication key decryption unit 371, decryption communication key storage A unit 372, an operation request generation unit 381, an operation request encryption unit 382, an encryption operation request transmission unit 383, an operation result reception unit 391, and a result output unit 392.

The target input unit 311 uses an input device such as a keyboard 902 to input which execution device 200 the user is trying to operate.
The target input unit 311 uses the CPU 911 to acquire target identification data for identifying the execution device 200 that the user is trying to operate based on the input content.
Using the CPU 911, the target input unit 311 outputs the acquired target identification data.

The role input unit 312 uses an input device such as a keyboard 902 to input what role the user is trying to operate the execution device 200 based on.
The role input unit 312 uses the CPU 911 to acquire role data for identifying the role of the user based on the input content.
The role input unit 312 uses the CPU 911 to output the acquired role data.

The operation input unit 313 uses an input device such as a keyboard 902 to input what operation the user is trying to perform on the execution device 200.
The operation input unit 313 uses the CPU 911 to acquire data representing the content of the operation (hereinafter referred to as “operation content data”) based on the input content.
The operation input unit 313 uses the CPU 911 to output the acquired operation content data.

The authority request generation unit 321 uses the CPU 911 to input the role data output from the role input unit 312.
The authority request generation unit 321 uses the CPU 911 to request the execution apparatus 200 an authority to perform an operation according to the role represented by the role data (hereinafter referred to as “authorization request message”) based on the input role data. .) Is generated.
Using the CPU 911, the authority request generation unit 321 outputs the generated authority request message.

Using the CPU 911, the authority request transmission unit 322 inputs the target identification data output from the target input unit 311 and the authority request message output from the authority request generation unit 321.
Using the communication device 915, the authority request transmission unit 322 transmits the input authority request message to the execution apparatus 200 identified by the input target identification data.

  The execution device 200 transmits the user identification data and the encrypted communication key as a response to the authority request message transmitted by the authority request transmitter 322. The encrypted communication key is obtained by encrypting a common key using user identification data as an encryption key by an ID-based encryption method. The common key is data temporarily shared between the user terminal device 300 and the execution device 200. The user terminal device 300 uses the shared common key and the execution device 200 using the common key encryption method. Encrypt communication between. If the user identification data is the public key in the ID-based encryption method and the user terminal device 300 knows the secret key corresponding to the public key, the secret communication key is correctly used as the decryption key. Since decryption is possible, the execution apparatus 200 can share a common key.

The terminal user identification receiving unit 331 receives the user identification data transmitted by the execution device 200 using the communication device 915.
Using the CPU 911, the terminal user identification receiving unit 331 outputs the received user identification data.

Using the communication device 915, the encrypted communication key receiving unit 332 receives the encrypted communication key transmitted by the execution device 200.
Using the CPU 911, the encrypted communication key receiving unit 332 outputs the received encrypted communication key.

The terminal user identification storage unit 341 uses the CPU 911 to input the user identification data output by the terminal user identification reception unit 331.
The terminal user identification storage unit 341 uses the RAM 914 to store the input user identification data.

  The user secret key storage unit 342 stores a user secret key in the public key cryptosystem using a tamper-resistant storage device.

Using the CPU 911, the signature generation unit 343 inputs the user identification data stored in the terminal user identification storage unit 341 and the secret key stored in the user secret key storage unit 342.
Using the CPU 911, the signature generation unit 343 generates the signature data by encrypting the input user identification data by using the input secret key as an encryption key (signature key) by the public key cryptosystem. .
Using the CPU 911, the signature generation unit 343 outputs the generated signature data.

Using the CPU 911, the terminal user identification transmission unit 351 inputs the user identification data stored in the terminal user identification storage unit 341.
The terminal user identification transmission unit 351 transmits the input user identification data to the key generation apparatus 400 using the communication device 915.

Using the CPU 911, the signature transmission unit 352 inputs the signature data output from the signature generation unit 343.
The signature transmission unit 352 transmits the input signature data to the key generation device 400 using the communication device 915.

The encrypted secret key receiving unit 361 uses the communication device 915 to receive the encrypted secret key transmitted by the key generation device 400. When the key generation device 400 transmits the encrypted secret key, it means that the key generation device 400 determines that the user of the user terminal device 300 has a role for the execution device 200.
Using the CPU 911, the encrypted secret key receiving unit 361 outputs the received encrypted secret key.

Using the CPU 911, the secret key decryption unit 362 inputs the encrypted secret key output from the encrypted secret key reception unit 361 and the secret key stored in the user secret key storage unit 342.
Using the CPU 911, the secret key decryption unit 362 decrypts the input encrypted secret key using the input secret key as a decryption key by the public key cryptosystem. Hereinafter, data obtained by the secret key decryption unit 362 decrypting the encrypted secret key is referred to as a “decryption secret key”.
Using the CPU 911, the secret key decryption unit 362 outputs the decrypted decryption secret key.

Using the CPU 911, the communication key decryption unit 371 inputs the encrypted communication key output from the encrypted communication key reception unit 332 and the decryption secret key output from the secret key decryption unit 362.
The communication key decryption unit 371 uses the CPU 911 to decrypt the input encrypted communication key using the input decryption secret key as a decryption key by the ID-based encryption method. Hereinafter, data obtained by the communication key decryption unit 371 decrypting the encrypted communication key is referred to as a “decryption communication key”.
Using the CPU 911, the communication key decryption unit 371 outputs the decrypted decryption communication key.

Using the CPU 911, the decryption communication key storage unit 372 inputs the decryption communication key output from the communication key decryption unit 371.
The decryption communication key storage unit 372 uses the RAM 914 to store the input decryption communication key.

The operation request generation unit 381 uses the CPU 911 to input the operation content data output from the operation input unit 313.
The operation request generator 381 uses the CPU 911 to send a message (hereinafter referred to as “operation request message”) requesting the execution device 200 to perform an operation represented by the operation content data based on the input operation content data. Generate.
The operation request generation unit 381 uses the CPU 911 to output the generated operation request message.

The operation request encryption unit 382 uses the CPU 911 to input the operation request message output from the operation request generation unit 381 and the decryption communication key stored in the decryption communication key storage unit 372.
Using the CPU 911, the operation request encryption unit 382 encrypts the input operation request message using the input decryption communication key as an encryption key by a common key encryption method. Hereinafter, data obtained by the operation request encryption unit 382 encrypting the operation request message is referred to as an “encryption operation request”.
Using the CPU 911, the operation request encryption unit 382 outputs an encrypted encryption operation request.

Using the CPU 911, the encryption operation request transmission unit 383 inputs the encryption operation request output from the operation request encryption unit 382 and the target identification data output from the target input unit 311.
Using the communication device 915, the encryption operation request transmission unit 383 transmits the input encryption operation request to the execution device 200 identified by the input target identification data.

  The execution apparatus 200 transmits a message indicating the result of the operation (hereinafter referred to as “operation result message”) as a response to the encryption operation request transmitted by the encryption operation request transmission unit 383.

The operation result reception unit 391 uses the communication device 915 to receive the operation result message transmitted by the execution device 200.
Using the CPU 911, the operation result receiving unit 391 outputs the received operation result message.

Using the CPU 911, the result output unit 392 inputs the operation result message output from the operation result receiving unit 391.
The result output unit 392 uses the CPU 911 to acquire the operation result represented by the operation result message based on the input operation result message.
The result output unit 392 outputs the acquired operation result using an output device such as the display device 901.

FIG. 6 is a block configuration diagram showing an example of a functional block configuration of execution device 200 in this embodiment.
The execution device 200 includes an authority verification device 100 and a target device 210.
The authority verification device 100 is a device that determines a user's operation authority.
The target device 210 is a device that actually executes processing in accordance with a user operation.

  The authority verification device 100 includes an authority request reception unit 111, a role acquisition unit 121, a random number generation unit 122, an identification generation unit 123, an identification storage unit 124, a communication key generation unit 131, a communication key storage unit 132, and a communication key encryption unit 133. An identification transmission unit 141, an encrypted communication key transmission unit 142, an encryption operation request reception unit 151, an operation request decryption unit 152, an authority storage unit 161, an operation request verification unit 162, and an operation request notification unit 163.

The authority request receiving unit 111 receives the authority request message transmitted by the user terminal device 300 using the communication device 915.
Using the CPU 911, the authority request receiving unit 111 outputs the received authority request message.

The role acquisition unit 121 uses the CPU 911 to input the authority request message output from the authority request reception unit 111.
The role acquisition unit 121 uses the CPU 911 to determine the role requested by the authority request message based on the input authority request message.
The role acquisition unit 121 uses the CPU 911 to acquire role data for identifying the determined role.
The role acquisition unit 121 uses the CPU 911 to output the acquired role data.

The random number generator 122 uses the CPU 911 to generate a random number.
Using the CPU 911, the random number generation unit 122 outputs the generated random number.

The identification generation unit 123 uses the CPU 911 to input the role data output from the role acquisition unit 121 and the random number output from the random number generation unit 122.
The identification generating unit 123 uses the CPU 911 to generate user identification data based on the input role data and random numbers. For example, the identification generation unit 123 uses the CPU 911 to combine the target identification data for identifying the execution device 200 itself, the input role data, and the character string data representing the input random number, and use the combined data. The person identification data. Alternatively, the identification generation unit 123 uses the CPU 911 to further input the individual identification data for identifying the user of the user terminal device 300 that has transmitted the authority request message received by the authority request receiving unit 111 and input the individual identification data. The identification data may be further combined to form user identification data.
The identification generation unit 123 uses the CPU 911 to output the generated user identification data.

The identification storage unit 124 uses the CPU 911 to input the user identification data output from the identification generation unit 123.
The identification storage unit 124 stores the input user identification data using the magnetic disk device 920.

The communication key generation unit 131 uses the CPU 911 to generate a common key. For example, the communication key generation unit 131 uses the CPU 911 to generate a random number, and uses the generated data representing the random number as a common key.
The communication key generation unit 131 uses the CPU 911 to output the generated common key.

The communication key storage unit 132 uses the CPU 911 to input the common key output from the communication key generation unit 131.
The communication key storage unit 132 stores the input common key using the magnetic disk device 920.

Using the CPU 911, the communication key encryption unit 133 inputs the user identification data stored in the identification storage unit 124 and the common key stored in the communication key storage unit 132.
Using the CPU 911, the communication key encryption unit 133 uses the input user identification data as a public key in the ID-based encryption method, and uses the input user identification data as an encryption key by the ID-based encryption method. Encrypt the entered common key. Hereinafter, data acquired by encrypting the common key by the communication key encryption unit 133 is referred to as an encrypted communication key.
Using the CPU 911, the communication key encryption unit 133 outputs the acquired encrypted communication key.

The identification transmission unit 141 uses the CPU 911 to input the user identification data stored in the identification storage unit 124.
Using the communication device 915, the identification transmission unit 141 transmits the input user identification data to the user terminal device 300 that has transmitted the authority request message received by the authority request reception unit 111.

Using the CPU 911, the encrypted communication key transmission unit 142 inputs the encrypted communication key output from the communication key encryption unit 133.
Using the communication device 915, the encrypted communication key transmission unit 142 transmits the input encrypted communication key to the user terminal device 300 that has transmitted the authority request message received by the authority request reception unit 111.

The encryption operation request reception unit 151 uses the communication device 915 to receive the encryption operation request transmitted from the user terminal device 300.
Using the CPU 911, the encryption operation request reception unit 151 outputs the received encryption operation request.

Using the CPU 911, the operation request decryption unit 152 inputs the encryption operation request output from the encryption operation request reception unit 151 and the common key stored in the communication key storage unit 132.
The operation request decryption unit 152 uses the CPU 911 to decrypt the input encryption operation request using the input common key as a decryption key by the common key encryption method. Hereinafter, data obtained by the operation request decryption unit 152 decrypting the encryption operation request is referred to as a “decryption operation request”.
Using the CPU 911, the operation request decryption unit 152 outputs the decrypted decryption operation request.

  Using the magnetic disk device 920, the authority storage unit 161 uses the magnetic disk device 920 to represent data (hereinafter referred to as “authority-corresponding data”) representing the correspondence between the role of the user and the operation for which the user having that role has authority. It is memorized beforehand.

FIG. 7 is a diagram schematically illustrating an example of authority correspondence data 520 stored in the authority storage unit 161 according to this embodiment.
The authority correspondence data 520 is data composed of a plurality of records, for example, with the role data 521 and the operation content data 522 as a set of data (records).
In this figure, the role data 521 is arranged in the left column, the operation content data 522 in the right column is vertically arranged, and the role data 521 and the operation content data 522 arranged in the horizontal direction are one record. Represents.
The role data 521 is data for identifying a role.
The operation content data 522 is data representing the content of the operation.

In the authority correspondence data 520 shown in this example, for example, the top record indicates that the user having the role (for example, the role as an administrator) identified by the role data 521 “ADMIN” is the operation content data 522. This indicates that the user has an authority to perform an operation (for example, a start operation) represented by “BOOT”.
It should be noted that the format of the authority correspondence data 520 shown in this figure is an example, and if it is a format that can express what kind of operation the user having each role has, the authority correspondence The data format may be other formats.

  Returning to FIG. 6, the description of the functional blocks of the execution apparatus 200 will be continued.

The operation request verification unit 162 uses the CPU 911 to input the decryption operation request output from the operation request decryption unit 152.
The operation request verification unit 162 uses the CPU 911 to verify the input decryption operation request.
There are two stages in the verification of the decryption operation request.
The first stage is verification of whether or not the decryption operation request is correctly decrypted. The operation request message has a predetermined format (format). If the decryption operation request is correctly decrypted, the decryption operation request should satisfy the format as the operation request message. The operation request verification unit 162 uses the CPU 911 to determine whether or not the decryption operation request is correctly decrypted by determining whether or not the decryption operation request satisfies the format of the operation request message.

  If the decryption operation request is correctly decrypted, the encryption operation request is encrypted by the common key encryption method using the same common key as the common key stored in the communication key storage unit 132 as the encryption key. Therefore, it means that the user terminal device 300 was able to correctly decrypt the encrypted communication key. That is, it can be seen that the user identification data generated by the identification generation unit 123 is used as the public key in the ID-based encryption method, and the user terminal device 300 knows the secret key corresponding to the public key in the ID-based encryption method. This is because the key generation device 400 determines that the user terminal device 300 has the authority to operate the execution device 200 based on its role, and the secret key in the ID-based encryption method corresponding to the user identification data is Since the key generation device 400 has taught the user terminal device 300, it is assumed that the operation request verification unit 162 has the authority for the user terminal device 300 to operate the execution device 200 based on its role. The first stage of verification is a success.

  The second stage of verification is verification of whether the role has the authority to perform the operation. The authority of the user is different for each role, and when it is verified that the user has the role with respect to the execution apparatus 200 in the first stage of verification, the user having the role is operated. If the authority can be verified, the user has the authority to perform the operation. The operation request verification unit 162 uses the CPU 911, based on the authority correspondence data 520 stored in the authority storage unit 161, whether the user having the role has the authority to perform the operation requested by the input decryption operation request. Determine whether or not. If it can be determined that it is authorized, the second stage of verification is successful.

Using the CPU 911, the operation request verification unit 162 determines that the operation authority is present when the two-step verification is successful, and otherwise determines that there is no operation authority.
The operation request verification unit 162 outputs the input decryption operation request when it is determined by the CPU 911 that there is an operation authority.

Using the CPU 911, the operation request notification unit 163 inputs the decryption operation request output from the operation request verification unit 162.
Using the CPU 911, the operation request notification unit 163 notifies the target device 210 of the input decryption operation request as an operation request message.

  The target device 210 includes an operation request acquisition unit 211, a process execution unit 212, an operation result generation unit 213, and an operation result transmission unit 214.

The operation request acquisition unit 211 uses the CPU 911 to acquire the operation request message notified by the operation request notification unit 163.
Using the CPU 911, the operation request acquisition unit 211 outputs the acquired operation request message.

The process execution unit 212 uses the CPU 911 to input the operation request message output from the operation request acquisition unit 211.
The process execution unit 212 uses the CPU 911 to execute a process corresponding to the operation requested by the operation request message based on the input operation request message.
The process execution unit 212 uses the CPU 911 to output data representing the result of executing the process (hereinafter referred to as “result data”).

The operation result generation unit 213 uses the CPU 911 to input result data output from the process execution unit 212.
The operation result generation unit 213 uses the CPU 911 to, based on the input result data, a message (hereinafter referred to as “operation result message”) that notifies the user terminal device 300 of the result of the process execution unit 212 executing the process. To generate).
Using the CPU 911, the operation result generation unit 213 outputs the generated operation result message.

The operation result transmission unit 214 uses the CPU 911 to input the operation result message output from the operation result generation unit 213.
The operation result transmission unit 214 uses the communication device 915 to transmit the input operation result message to the user terminal device 300 that has transmitted the encryption operation request received by the encryption operation request reception unit 151.

  Instead of transmitting the operation result message as it is, a configuration may be adopted in which the common key stored in the communication key storage unit 132 is used as an encryption key and is encrypted and transmitted by a common key encryption method.

  FIG. 8 is a flowchart showing an example of the flow of access control processing in which the access control system 800 according to this embodiment controls the operation of the execution device 200 by the user.

  In the operation input process S610, in the user terminal device 300, the target input unit 311 inputs which execution device 200 the user is going to operate using the keyboard 902 or the like. The role input unit 312 uses the keyboard 902 or the like to input what role the user is trying to operate the execution apparatus 200 based on. The operation input unit 313 uses the keyboard 902 or the like to input what operation the user is trying to perform on the execution apparatus 200.

  In the authority request process S615, in the user terminal device 300, the authority request generation unit 321 uses the CPU 911 to generate an authority request message based on the role input by the role input unit 312 in the operation input process S610. The authority request transmission unit 322 transmits the operation request message generated by the authority request generation unit 321 to the execution device 200 input by the target input unit 311 in the operation input process S610 using the communication device 915.

In the communication key issuing process S620, in the execution apparatus 200, the authority request receiving unit 111 receives the operation request message transmitted from the user terminal apparatus 300 in the authority request process S615 using the communication apparatus 915. The role acquisition unit 121 uses the CPU 911 to acquire role data based on the operation request message received by the authority request reception unit 111. The random number generator 122 uses the CPU 911 to generate a random number. The identification generation unit 123 uses the CPU 911 to generate user identification data based on the role data acquired by the role acquisition unit 121 and the random number generated by the random number generation unit 122. The identification storage unit 124 stores the user identification data generated by the identification generation unit 123 using the magnetic disk device 920.
The communication key generation unit 131 uses the CPU 911 to generate a common key in the common key encryption method. The communication key storage unit 132 stores the common key generated by the communication key generation unit 131 using the magnetic disk device 920. The communication key encryption unit 133 encrypts the common key stored in the communication key storage unit 132 by using the user identification data stored in the identification storage unit 124 as a public key in the ID base encryption method by the ID base encryption method. Turn into.
The identification transmission unit 141 transmits the user identification data stored in the identification storage unit 124 to the user terminal device 300 using the communication device 915. Using the communication device 915, the encrypted communication key transmission unit 142 transmits the encrypted communication key encrypted by the communication key encryption unit 133 to the user terminal device 300.

In the secret key request processing S630, in the user terminal device 300, the terminal user identification receiving unit 331 receives the user identification data transmitted by the execution device 200 using the communication device 915. Using the communication device 915, the encrypted communication key receiving unit 332 receives the encrypted communication key transmitted by the execution device 200. The terminal user identification storage unit 341 uses the RAM 914 to store user identification data received by the terminal user identification reception unit 331.
The signature generation unit 343 uses the secret key in the public key encryption method stored in the user secret key storage unit 342 by the public key encryption method using the CPU 911, and the use stored in the terminal user identification storage unit 341. User identification data is encrypted.
The terminal user identification transmission unit 351 transmits the user identification data stored in the terminal user identification storage unit 341 to the key generation device 400 using the communication device 915. Using the communication device 915, the signature transmission unit 352 transmits the signature data generated by the signature generation unit 343 to the key generation device 400.

In the authority determination process S640, in the key generation device 400, the generated user identification receiving unit 411 receives the user identification data transmitted from the user terminal device 300 using the communication device 915. The signature receiving unit 412 receives the signature data transmitted by the user terminal device 300 using the communication device 915.
Using the CPU 911, the signature verification unit 423 verifies the signature data received by the signature reception unit 412 based on the public key certificate stored in the public key certificate storage unit 421.
When the signature verification unit 423 successfully verifies the signature data, the generation role acquisition unit 432 uses the CPU 911 to acquire role data based on the user identification data received by the generation user identification reception unit 411. The generation target identification acquisition unit 433 uses the CPU 911 to acquire target identification data based on the user identification data received by the generation user identification reception unit 411. The authority determination unit 434 uses the CPU 911 to use the user terminal device 300 that has transmitted the user identification data received by the generated user identification reception unit 411 based on the role correspondence data stored in the role storage unit 431. It is determined whether the person has a role identified by the role data acquired by the generation role acquisition unit 432 with respect to the execution device 200 identified by the target identification data acquired by the generation target identification acquisition unit 433.
When the authority determining unit 434 determines that the user has the role of the execution apparatus 200, the key generation apparatus 400 proceeds to the secret key notification process S645.
When the authority determination unit 434 determines that the user does not have the role for the execution device 200 or when the signature verification unit 423 fails to verify the signature data, the key generation device 400 performs processing. finish.

  In the secret key notification processing S645, in the key generation device 400, the secret key generation unit 441 uses the CPU 911 and the user identification data received by the generation user identification reception unit 411 in the authority determination processing S640 by the ID-based encryption method. A secret key corresponding to is generated. Using the CPU 911, the secret key encryption unit 442 uses the public key of the user of the user terminal device 300 based on the public key certificate stored in the public key certificate storage unit 421 by the public key cryptosystem. Then, the secret key in the ID-based encryption method generated by the secret key generation unit 441 is encrypted. Using the communication device 915, the encrypted secret key transmission unit 451 transmits the encrypted secret key encrypted by the secret key encryption unit 442 to the user terminal device 300.

In the communication key decryption process S650, in the user terminal device 300, the encrypted secret key reception unit 361 receives the encrypted secret key transmitted from the key generation device 400 using the communication device 915. Using the CPU 911, the secret key decryption unit 362 decrypts the received encrypted secret key by using the secret key in the public key encryption method stored in the user secret key storage unit 342 by the public key encryption method.
The communication key decryption unit 371 uses the CPU 911 to decrypt the encrypted communication key received by the encrypted communication key reception unit 332 using the decryption secret key decrypted by the secret key decryption unit 362 by the ID-based encryption method. To do. Using the RAM 914, the decryption communication key storage unit 372 stores the decryption communication key decrypted by the communication key decryption unit 371.

  In the operation request process S655, in the user terminal device 300, the operation request generation unit 381 uses the CPU 911 to generate an operation request message based on the operation input by the operation input unit 313 in the operation input process S610. The operation request encryption unit 382 is generated by the operation request generation unit 381 using the decryption communication key stored in the decryption communication key storage unit 372 in the communication key decryption process S650 by the common key encryption method using the CPU 911. Encrypt the operation request message. Using the communication device 915, the encryption operation request transmission unit 383 transmits the encryption operation request encrypted by the operation request encryption unit 382 to the execution device 200.

In the operation request verification process S <b> 660, in the execution device 200, the encryption operation request reception unit 151 receives the encryption operation request transmitted from the user terminal device 300 using the communication device 915. The operation request decryption unit 152 uses the CPU 911 to decrypt the encryption operation request received by the encryption operation request reception unit 151 using the common key stored in the communication key storage unit 132 by the common key encryption method. . The operation request verification unit 162 uses the CPU 911 to determine whether or not the decryption operation request decrypted by the operation request decryption unit 152 has been correctly decrypted.
When it is determined that the decryption operation request is correctly decrypted, the operation request verification unit 162 has the role acquired by the role acquisition unit 121 based on the authority correspondence data stored in the authority storage unit 161 using the CPU 911. It is determined whether the user has the authority to perform the operation requested by the decryption operation request decrypted by the operation request decryption unit 152.
When the operation request verification unit 162 determines that there is an authority, the execution device 200 proceeds to the process execution process S670.
When the operation request verifying unit 162 determines that there is no authority, or when the operation request verifying unit 162 determines that the decryption operation request is not correctly decrypted, the execution device 200 ends the process.

  In the process execution processing S670, in the execution device 200, the operation request notification unit 163 notifies the operation request acquisition unit 211 of the decryption operation request decrypted by the operation request decryption unit 152 as an operation request message using the CPU 911. To do. The operation request acquisition unit 211 uses the CPU 911 to acquire the operation request message notified by the operation request notification unit 163. The process execution unit 212 uses the CPU 911 to execute a process based on the operation request message acquired by the operation request acquisition unit 211. The operation result generation unit 213 uses the CPU 911 to generate an operation result message based on the result of the process executed by the process execution unit 212. The operation result transmission unit 214 transmits the operation result message generated by the operation result generation unit 213 to the user terminal device 300 using the communication device 915.

  In the operation result output process S680, in the user terminal device 300, the operation result receiving unit 391 receives the operation result message transmitted from the execution device 200 using the communication device 915. The result output unit 392 outputs an operation result based on the operation result message received by the operation result receiving unit 391 using the display device 901 or the like.

  When a plurality of operations are continuously performed on the same execution device 200, the processes of the operation input process S610 to the operation result output process S680 are repeated. In the second and subsequent times, the same common key may be used, and the processing of authority request processing S615 to communication key decryption processing S650 may be omitted.

The authority verification apparatus 100 in this embodiment is an apparatus that verifies whether or not the user has the authority to operate the target apparatus 210, and a processing apparatus (CPU 911) that processes data and a transmission that transmits data. Device (communication device 915), receiving device (communication device 915) for receiving data, identification acquisition unit (identification generation unit 123), communication key generation unit 131, communication key encryption unit 133, and encrypted communication The key transmission unit 142 includes an encryption operation request reception unit 151, an operation request decryption unit 152, an operation request verification unit 162, and an operation request notification unit 163.
The identification acquisition unit (identification generation unit 123) uses the processing device (CPU 911) to acquire user identification data for identifying a user.
The communication key generation unit 131 generates an encryption key (common key) and a decryption key (common key) corresponding to the encryption key using the processing device (CPU 911).
The communication key encryption unit 133 uses the user identification data acquired by the identification acquisition unit (identification generation unit 123) by the ID-based encryption method using the processing device (CPU 911) and uses the communication key. The encryption key (common key) generated by the generation unit 131 is encrypted and used as an encrypted communication key.
The encrypted communication key transmission unit 142 transmits the encrypted communication key encrypted by the communication key encryption unit 133 using the transmission device (communication device 915).
The encryption operation request reception unit 151 receives an encryption operation request obtained by encrypting an operation request message representing an operation on the target device 210 using the reception device (communication device 915).
The operation request decryption unit 152 uses the processing device (CPU 911) and uses the decryption key (common key) generated by the communication key generation unit 131 to perform the encryption received by the encryption operation request reception unit 151. The decryption operation request is decrypted to be a decryption operation request.
The operation request verification unit 162 determines whether or not the decryption operation request decrypted by the operation request decryption unit 152 is correctly decrypted using the processing device (CPU 911), and determines that the decryption is correctly performed. In this case, it is determined that there is an operation authority.
The operation request notifying unit 163 uses the processing device (CPU 911) to send the decryption operation request decrypted by the operation request decrypting unit 152 to the operation request when the operation request verifying unit 162 determines that the operation authority exists. The target device 210 is notified as a message.

According to the authority verification device 100 in this embodiment, the encryption operation request received by the encryption operation request reception unit 151 is correctly decrypted using the decryption key (common key) generated by the communication key generation unit 131. When it is possible, it is determined that the user has the operation authority for the target device 210. The fact that the encryption operation request can be correctly decrypted with the decryption key (common key) generated by the communication key generation unit 131 means that the user knows the encryption key (common key) generated by the communication key generation unit 131. This means that the user can correctly decrypt the encrypted communication key encrypted by the communication key encryption unit 133 using the ID-based encryption method. In other words, the encryption operation request receiving unit 151 notifies the user when the user knows the secret key in the ID-based encryption method corresponding to the user identification data acquired by the identification acquisition unit (identification generation unit 123). It is determined that there is an operation authority for the target device 210.
A configuration in which the encryption key (common key) is encrypted not by an ID-based encryption method but by a normal public key encryption method is also conceivable, but in this case, the validity and validity of the user's public key is guaranteed. Need to be. For example, the authority verification device 100 verifies the validity / validity of the public key by using PKI, such as verifying the CA certificate by tracing the public key certificate or confirming the revocation of the public key certificate. There is a need to.
On the other hand, since the authority verification device 100 in this embodiment encrypts the encryption key (common key) by the ID-based encryption method, it is necessary to verify the validity / validity of the public key using PKI. For example, even when the authority verification device 100 is provided in an apparatus with limited processing capability and communication capability such as an embedded device, the operation authority of the user can be verified.

In this example, the user terminal device 300 encrypts the operation request message using a common key encryption method to generate an encryption operation request, and the authority verification device 100 decrypts the encryption operation request using the common key encryption method. However, the encryption method for encrypting the operation request message is not limited to the common key encryption method, and may be an asymmetric encryption method.
In that case, the communication key generation unit 131 uses the CPU 911 to generate a pair of an encryption key and a decryption key in the asymmetric encryption method, and the communication key storage unit 132 uses the magnetic disk device 920 to generate a communication key. The decryption key generated by the unit 131 is stored. Using the CPU 911, the communication key encryption unit 133 uses the user identification data generated by the identification generation unit 123 as a public key by the ID-based encryption method, and uses the encryption key generated by the communication key generation unit 131. Encrypt to obtain an encrypted communication key.
If the user terminal device 300 knows the secret key in the ID-based encryption method corresponding to the user identification data generated by the identification generation unit 123, the encrypted communication key transmitted by the authority verification device 100 can be correctly decrypted. The decryption communication key decrypted by the communication key decryption unit 371 is the same as the encryption key generated by the identification generation unit 123. Accordingly, the decryption communication key decrypted by the communication key decryption unit 371 is used as an encryption key, the operation request encryption unit 382 encrypts the operation request message, and the decryption key stored by the communication key storage unit 132 is used. When the operation request decryption unit 152 decrypts the encrypted operation request, the same effect as the configuration using the common key cryptosystem can be obtained.

The authority verification device 100 in this embodiment further includes a role acquisition unit 121.
The role acquisition unit 121 acquires role data representing the role of the user using the processing device (CPU 911).
The identification acquisition unit (identification generation unit 123) uses the processing device (CPU 911) to generate user identification data based on the role data acquired by the role acquisition unit 121, thereby the user identification. Get the data.
The operation request verification unit 162 determines whether or not the decryption operation request decrypted by the operation request decryption unit 152 is correctly decrypted using the processing device (CPU 911), and determines that the decryption is correctly performed. In this case, it is determined whether or not the role represented by the role data acquired by the role acquisition unit 121 has the authority to perform the operation represented by the decryption operation request, and determines that the role has the authority to perform the operation. In this case, it is determined that there is an operation authority.

  According to the authority verification device 100 in this embodiment, the secret in the ID-based encryption method corresponding to the user identification data generated by the identification acquisition unit (identification generation unit 123) based on the role data acquired by the role acquisition unit 121 Since the operation request verification unit 162 determines whether or not the user knows the key, it can be determined whether or not the user has the role represented by the role data acquired by the role acquisition unit 121. In addition, since the operation request verification unit 162 determines whether or not the role is authorized to perform the operation requested by the user, groups of users with different privileges can be managed by the role. .

The authority verification device 100 according to this embodiment further includes an identification transmission unit 141.
The identification transmission unit 141 transmits the user identification data acquired by the identification acquisition unit (identification generation unit 123) using the transmission device (communication device 915).

According to the authority verification device 100 in this embodiment, since the identification transmitting unit 141 transmits the user identification data acquired by the identification acquiring unit (identification generating unit 123), the authority request receiving unit 111 receives the authority request message. Different user identification data can be used each time.
Even if the user has the authority to operate the target device 210 at a certain point in time and knows the secret key corresponding to the user identification data transmitted by the privilege verification device 100 at that point, the user's authority has expired. Later, if the secret key corresponding to the user identification data transmitted by the authority verification device 100 is not known, the operation request verification unit 162 determines that the user has no operation authority, and after the user's authority has expired The user cannot operate the target device 210. That is, it is possible to cope with a change in the operation authority of the user without changing the setting of the authority verification apparatus 100.

The authority verification device 100 in this embodiment further includes a random number generation unit 122.
The random number generation unit 122 generates a random number using the processing device (CPU 911).
The identification acquisition unit (identification generation unit 123) uses the processing device (CPU 911) to generate user identification data based on the random number generated by the random number generation unit 122, thereby the user identification data. To get.

According to the authority verification device 100 in this embodiment, since the identification acquisition unit generates user identification data based on the random number generated by the random number generation unit 122, every time the authority request reception unit 111 receives an authority request message. Furthermore, user identification data that cannot be predicted in advance can be used.
Since a user having the operation authority cannot predict the user identification data in advance in preparation for the expiration of the operation authority and cannot obtain the secret key in the ID-based encryption method corresponding to the predicted user identification data. The user's operation authority can be revoked without fail.

  The execution device 200 in this embodiment is a device that executes processing based on an operation request from a user having an operation authority, and the operation verification message notified by the authority verification device 100 and the authority verification device 100. And a target device 210 that executes processing based on the above.

  According to the execution device 200 in this embodiment, since the encryption key (common key) is encrypted by the ID-based encryption method, it is not necessary to verify the validity / validity of the public key using PKI, For example, even if the execution device 200 has limited processing capability and communication capability, such as an embedded device, the operation authority of the user can be verified and the process can be executed only when there is the operation authority.

The user terminal device 300 in this embodiment sends an operation request to the target device 210 by the user to the authority verification device 100 that verifies whether the user has the authority to operate the target device 210. A notification device, a processing device (CPU 911) for processing data, a receiving device (communication device 915) for receiving data, a transmitting device (communication device 915) for transmitting data, and a terminal user identification acquisition unit (Terminal user identification reception unit 331), secret key acquisition unit (secret key decryption unit 362), encrypted communication key reception unit 332, communication key decryption unit 371, operation request encryption unit 382, encryption An operation request transmission unit 383.
The terminal user identification acquisition unit (terminal user identification reception unit 331) acquires user identification data for identifying a user, using the processing device (CPU 911).
The secret key acquisition unit (encrypted secret key reception unit 361 and secret key decryption unit 362) uses the processing device (CPU 911) to perform the terminal user identification acquisition unit (terminal user identification reception) in the ID-based encryption method. Unit 331) obtains a secret key corresponding to the user identification data obtained.
The encrypted communication key receiving unit 332 uses the receiving device (communication device 915) to generate an encrypted communication key obtained by encrypting an encryption key (common key) used for encryption by an ID-based encryption method. Received from the authority verification device 100.
The communication key decryption unit 371 uses the processing device (CPU 911) to obtain the secret key acquired by the secret key acquisition unit (encrypted secret key reception unit 361 / secret key decryption unit 362) by an ID-based encryption method. The encrypted communication key received by the encrypted communication key receiving unit 332 is decrypted and used as a decryption communication key.
The operation request encryption unit 382 uses the processing device (CPU 911) to use the decryption communication key decrypted by the communication key decryption unit 371 to indicate an operation request message indicating an operation on the target device 210 by the user. Is encrypted as an encryption operation request.
The encryption operation request transmission unit 383 transmits the encryption operation request encrypted by the operation request encryption unit 382 to the authority verification device 100 using the transmission device (communication device 915).

  According to the user terminal device 300 in this embodiment, in the ID-based encryption method, the secret key corresponding to the user identification data acquired by the terminal user identification acquisition unit (terminal user identification reception unit 331) is secretly stored. The encrypted communication acquired by the key acquisition unit (encrypted secret key receiving unit 361 and secret key decrypting unit 362) and received by the encrypted communication key receiving unit 332 by the ID-based encryption method using the acquired secret key. Since the key is decrypted, the encrypted communication key can be correctly decrypted only when the secret key acquisition unit (secret key decryption unit 362) acquires the correct secret key. If the configuration is such that the secret key acquisition unit (secret key decryption unit 362) can acquire the correct secret key only when the user has the operation authority for the target device 210, the encryption is performed only when the user has the operation authority. Since the communication key can be correctly decrypted, this can be used to prove to the authority verification device 100 that the user has the operation authority.

The user terminal device 300 in this embodiment further includes a terminal user identification transmission unit 351.
The terminal user identification transmission unit 351 uses the transmission device (communication device 915) to transmit the terminal user identification acquisition unit (terminal use) to the key generation device 400 that generates a secret key in the ID-based encryption method. The user identification receiving unit 331) transmits the acquired user identification data.
The secret key acquisition unit (encrypted secret key reception unit 361 and secret key decryption unit 362) receives the secret key generated by the key generation device 400 by using the reception device (communication device 915). Obtain the secret key.

  According to the user terminal device 300 in this embodiment, the terminal user identification transmission unit 351 uses the key generation device 400 as the user identification data acquired by the terminal user identification acquisition unit (terminal user identification reception unit 331). Since the secret key acquisition unit (encrypted secret key reception unit 361 and secret key decryption unit 362) acquires the secret key generated by the key generation device 400, the user has the authority to operate the execution device 200. If it is configured so as to generate a secret key corresponding to the user identification data received by the key generation device 400 only when it has, it can be proved to the authority verification device 100 that the user has the operation authority. .

The key generation device 400 in this embodiment is a device that generates a secret key in the ID-based encryption method, and includes a processing device (CPU 911) that processes data, a receiving device (communication device 915) that receives data, Transmission device (communication device 915) for transmitting data, generation user identification reception unit 411, authority determination unit 434, secret key generation unit 441, secret key transmission unit (secret key encryption unit 442 / encrypted secret) Key transmission unit 451).
The generated user identification receiving unit 411 receives user identification data for identifying a user using the receiving device (communication device 915).
The authority determination unit 434 determines whether the user has the authority to operate the target device 210 using the processing device (CPU 911).
The secret key generation unit 441 uses the processing device (CPU 911) to generate the secret key generation method in the ID-based encryption method when the authority determination unit 434 determines that the user has the authority to operate the target device 210. The user identification receiving unit 411 generates a secret key corresponding to the user identification data received.
The secret key transmission unit (secret key encryption unit 442 / encrypted secret key transmission unit 451) transmits the secret key generated by the secret key generation unit 441 using the transmission device (communication device 915).

  According to the key generation device 400 in this embodiment, when the authority determination unit 434 determines that the user has the authority to operate the target device 210, the generation user identification reception unit 411 uses the ID-based encryption method. Since the secret key generation unit 441 generates a secret key corresponding to the received user identification data, by verifying whether data encrypted using the user identification data in the ID-based encryption method can be correctly decrypted, It is possible to determine whether the user has operation authority.

The key generation device 400 further includes a generation role acquisition unit 432.
The generated user identification receiving unit 411 receives user identification data including role data representing the role of the user, using the receiving device (communication device 915).
The generation role acquisition unit 432 acquires the role data based on the user identification data received by the generation user identification reception unit 411 using the processing device (CPU 911).
The authority determining unit 434 uses the processing device (CPU 911) to determine whether or not the user has a role represented by the role data with respect to the target device 210, and the user performs the target device. When it is determined that the role represented by the role data with respect to 210, it is determined that the user has the authority to operate the target device 210.

  According to the key generation device 400 in this embodiment, the generation role acquisition unit 432 acquires role data included in the user identification data received by the generation user identification reception unit 411, and the role represented by the acquired role data is displayed. Since the authority determination unit 434 determines that the user has the operation authority when the user has the target apparatus 210, the user has a different operation authority for the target apparatus 210. Can be classified and managed by role.

The key generation device 400 in this embodiment further includes a generation individual identification acquisition unit 422.
The generated user identification receiving unit 411 receives user identification data including individual identification data for individually identifying the user, using the receiving device (communication device 915).
The generated individual identification acquisition unit 422 uses the processing device (CPU 911) to acquire the individual identification data based on the user identification data received by the generated user identification receiving unit 411.
Whether the authority determination unit 434 has the authority to operate the target device 210 by a user individually identified by the individual identification data acquired by the generated individual identification acquisition unit 422, using the processing device (CPU 911). Determine whether or not.

  According to the key generation device 400 in this embodiment, the generated individual identification acquisition unit 422 acquires the individual identification data included in the user identification data received by the generated user identification receiving unit 411, and uses the acquired individual identification data. Since the authority determining unit 434 determines whether or not the identified user has an operation authority for the target device 210, a plurality of users having different operation authorities can be managed.

The key generation device 400 in this embodiment further includes a generation target identification acquisition unit 433.
The generated user identification receiving unit 411 receives user identification data including target identification data for identifying the target device 210 using the receiving device (communication device 915).
The generation target identification acquisition unit 433 acquires the target identification data based on the user identification data received by the generation user identification reception unit 411 using the processing device (CPU 911).
The authority determination unit 434 uses the processing device (CPU 911) to determine whether the user has the authority to operate the target device 210 identified by the target identification data acquired by the generation target identification acquisition unit 433. Determine.

  According to the key generation device 400 in this embodiment, the generation target identification acquisition unit 433 acquires the target identification data included in the user identification data received by the generation user identification reception unit 411, and uses the acquired target identification data. When the user has the operation authority for the identified target device 210, the authority determination unit 434 determines that the user has the operation authority. Different cases can be managed.

  The access control system 800 in this embodiment is a system that controls the operation of the target device 210 by a user, and includes the authority verification device 100 and the user terminal device 300.

  According to the access control system 800 in this embodiment, the authority verification device 100 encrypts the encryption key (common key) by the ID-based encryption method using the user identification data, and the user terminal device 300 is correctly Since the operation authority of the user is verified depending on whether it can be decrypted, it is not necessary to verify the validity / validity of the public key using PKI. For example, the processing capability and communication capability of an embedded device are limited. Even when the authority verification apparatus 100 is provided in the apparatus, the user's operation authority can be verified.

  The access control system 800 in this embodiment further includes the key generation device 400.

  According to the access control system 800 in this embodiment, when the authority determining unit 434 determines that the user has the authority to operate the target device 210, the generated user identification receiving unit 411 uses the ID-based encryption method. Since the secret key generation unit 441 generates a secret key corresponding to the received user identification data, there is no need to verify the validity / validity of the public key using PKI. Even when the authority verification device 100 is provided in an apparatus with limited communication capability, the user's operation authority can be verified.

  The authority verification device 100, execution device 200, user terminal device 300, and key generation device 400 in this embodiment all have a processing device (CPU 911) for processing data, a transmission device for transmitting data (a communication device 915). ), A computer program for causing a computer having a receiving device (communication device 915) to receive data to function as the authority verification device 100, the execution device 200, the user terminal device 300, and the key generation device 400. It can be realized by executing.

  According to the computer program in this embodiment, the authority verification device 100, the execution device 200, the user terminal device 300, and the key generation device 400 that achieve the above-described effects can be realized.

  The access control system 800 in this embodiment includes a plurality of processing devices (CPU 911) for processing data, a transmitting device (communication device 915) for transmitting data, and a receiving device (communication device 915) for receiving data. This computer can be realized by executing a computer program that causes the computer to function as the access control system 800.

  According to the computer program in this embodiment, it is possible to realize the access control system 800 having the above-described effects.

The authority verification method in which the authority verification apparatus 100 according to this embodiment verifies whether or not the user has the authority to operate the target apparatus 210 includes the following steps.
The processing device (CPU 911) acquires user identification data for identifying a user.
The processing device (CPU 911) generates an encryption key (common key) and a decryption key (common key) corresponding to the encryption key.
The processing device (CPU 911) encrypts the generated encryption key (common key) by using the acquired user identification data by the ID-based encryption method to obtain an encrypted communication key.
The transmission device (communication device 915) transmits the encrypted encrypted communication key.
The receiving device (communication device 915) receives an encrypted operation request obtained by encrypting an operation request message representing an operation on the target device 210.
The processing device (CPU 911) decrypts the received encryption operation request using the generated decryption key (common key) to obtain a decryption operation request.
The processing device (CPU 911) determines whether or not the decrypted decryption operation request is correctly decrypted, and when it is determined that the decryption operation request is correctly decrypted, it is determined that there is an operation authority.
When the processing device (CPU 911) determines that there is an operation authority, the processing device (CPU 911) notifies the target device 210 of the decrypted operation request as an operation request message.

  According to the authority verification method in this embodiment, since the processing device (CPU 911) encrypts the encryption key (common key) by the ID-based encryption method using the user identification data, it is made public using PKI. It is not necessary to verify the validity / validity of the key. For example, even if a device with limited processing and communication capabilities, such as an embedded device, uses the authority verification method, it verifies the user's operation authority. can do.

The user terminal device 300 in this embodiment sends an operation request to the target device 210 by the user to the authority verification device 100 that verifies whether the user has the authority to operate the target device 210. The operation request notification method to be notified includes the following steps.
The processing device (CPU 911) acquires user identification data for identifying a user.
The processing device (CPU 911) acquires a secret key corresponding to the acquired user identification data in the ID-based encryption method.
The receiving device (communication device 915) receives from the authority verification device 100 an encrypted communication key obtained by encrypting an encryption key (common key) used for encryption by an ID-based encryption method.
The processing device (CPU 911) uses the acquired secret key to decrypt the received encrypted communication key by the ID-based encryption method, and uses it as a decryption communication key.
The processing device (CPU 911) encrypts an operation request message representing an operation performed on the target device 210 by the user by using the decrypted decryption communication key to obtain an encryption operation request.
The transmission apparatus (communication apparatus 915) transmits the encrypted encryption operation request to the authority verification apparatus 100.

  According to the operation request notification method in this embodiment, in the ID-based encryption method, the processing device (CPU 911) acquires the secret key corresponding to the user identification data acquired by the processing device (CPU 911), and acquires the acquired secret. Since the encrypted communication key received by the receiving device (communication device 915) is decrypted by the ID-based encryption method using the key, the encrypted communication key is obtained only when the processing device (CPU 911) obtains the correct secret key. Can be decoded correctly. If the processing device (CPU 911) can acquire the correct private key only when the user has the operation authority for the target device 210, the encrypted communication key can be correctly decrypted only when the user has the operation authority. Therefore, by using this, it is possible to prove to the authority verification device 100 that the user has the operation authority.

The key generation method in which the key generation device 400 in this embodiment generates a secret key in the ID-based encryption method includes the following steps.
The receiving device (communication device 915) receives user identification data for identifying a user.
The processing device (CPU 911) determines whether or not the user has authority to operate the target device 210.
When the processing device (CPU 911) determines that the user has the authority to operate the target device 210, the ID key encryption method generates a secret key corresponding to the received user identification data.
The transmission device (communication device 915) transmits the generated secret key.

  According to the key generation method in this embodiment, when the processing device (CPU 911) determines that the user has the authority to operate the target device 210, the receiving device (communication device 915) uses the ID-based encryption method. Since the processing device (CPU 911) generates a secret key corresponding to the received user identification data, by verifying whether the data encrypted using the user identification data in the ID-based encryption method can be correctly decrypted, It is possible to determine whether the user has operation authority.

The access control method in which the access control system 800 in this embodiment controls the operation of the target device 210 by the user includes the following steps.
The authority verification device 100 (identification generation unit 123) acquires user identification data for identifying a user.
The authority verification device 100 (communication key generation unit 131) generates an encryption key (common key) and a decryption key (common key) corresponding to the encryption key.
The authority verification device 100 (communication key encryption unit 133) encrypts the generated encryption key (common key) using the acquired user identification data by the ID-based encryption method, and encrypts the communication key. And
The authority verification device 100 (encrypted communication key transmission unit 142) transmits the encrypted encrypted communication key.
The user terminal device 300 (terminal user identification receiving unit 331) acquires the user identification data.
The user terminal device 300 (encrypted secret key receiving unit 361 and secret key decrypting unit 362) acquires a secret key corresponding to the acquired user identification data in the ID-based encryption method.
The user terminal device 300 (encrypted communication key receiving unit 332) receives the encrypted communication key transmitted by the authority verification device 100.
The user terminal device 300 (communication key decryption unit 371) uses the acquired secret key to decrypt the received encrypted communication key by the ID-based encryption method to obtain a decrypted communication key.
The user terminal device 300 (operation request encryption unit 382) encrypts an operation request message representing an operation performed on the target device 210 by the user by using the decrypted decryption communication key. To do.
The user terminal device 300 (encryption operation request transmission unit 383) transmits the encrypted encryption operation request to the authority verification device 100.
The authority verification device 100 (encryption operation request reception unit 151) receives the encryption operation request transmitted by the user terminal device 300.
The authority verification apparatus 100 (operation request decryption unit 152) decrypts the received encryption operation request using the generated decryption key (common key) to obtain a decryption operation request.
The authority verification apparatus 100 (operation request verification unit 162) determines whether or not the decrypted decryption operation request is correctly decrypted. When it is determined that the decryption operation request is correctly decrypted, it is determined that the operation authority exists.
When the authority verification device 100 (operation request notifying unit 163) determines that there is an operation authority, the decryption operation request that has been decrypted is notified to the target device 210 as an operation request message.

  According to the access control method in this embodiment, the authority verification device 100 encrypts the encryption key (common key) by the ID-based encryption method using the user identification data, and the user terminal device 300 correctly decrypts it. Since the operation authority of the user is verified depending on whether it is possible, it is not necessary to verify the validity / validity of the public key using PKI. For example, an apparatus with limited processing capability and communication capability such as an embedded device Even when the authority verification device 100 is provided, the operation authority of the user can be verified.

The user terminal device 300 (user device) described above is
A role request transmission unit (authority request transmission unit 322) that transmits role information (role data) regarding a role (role) that operates the device (execution apparatus 200);
An authority confirmation receiving unit (terminal user identification receiving unit 331 / encrypted communication key receiving unit 332) for receiving authority confirmation information (user identification data and encrypted communication key);
A signature unit (signature generation unit 343) that generates signature information (signature data) from the ID information (user identification data) included in the authority confirmation information using a user secret key (secret key in the public key cryptosystem);
Issuance request transmission unit (terminal user identification transmission unit) that transmits user information (individual identification data) including a user public key, ID information (user identification data), and signature information (signature data) as an issuance request. 351 and signature transmission unit 352),
A private key receiving unit (encrypted private key receiving unit 361) for receiving an encrypted private key (encrypted private key);
A secret key decryption unit 362 for decrypting an ID-based secret key (a secret key in the ID-based encryption method) from the encrypted secret key with a user secret key (a secret key in the public key encryption method);
An ID-based decryption unit (communication key decryption unit 371) that decrypts an encryption key (common key) from an encrypted encryption key (encrypted communication key) included in the authority confirmation information using an ID-based secret key (secret key in the ID-based encryption method). )When,
An encryption unit (operation request encryption unit 382) that generates encrypted operation information (encryption operation request) using an encryption key (common key) from operation information (operation request message) for the device (execution device 200);
And an operation request transmission unit (encrypted operation request transmission unit 383) for transmitting the encrypted operation information.

The execution device 200 (device) described above is
A role request receiving unit (authority request receiving unit 111) for receiving role information (role data);
A random number generator 122 for generating a random number;
ID information generation unit (identification generation unit 123) that generates ID information (user identification data) from identification information (target identification data) for identifying a device (execution device 200), role information (role data), and a random number When,
An encryption key generation unit (communication key generation unit 131) for generating an encryption key (common key) and a decryption key (common key);
An ID-based encryption unit (communication key encryption unit 133) that generates an encrypted encryption key (encrypted communication key) from the encryption key (common key) using ID information (user identification data);
An authority confirmation transmission unit (identification transmission unit 141 / encrypted communication key transmission unit 142) that transmits ID information (user identification data) and an encrypted encryption key (encrypted communication key) together as authority confirmation information;
An operation request receiving unit (encrypted operation request receiving unit 151) for receiving encrypted operation information (encrypted operation request);
A decryption unit (operation request decryption unit 152) that decrypts the operation information (operation request message) from the encrypted operation information using a decryption key (common key);
Based on the correctly decrypted operation information (operation request message) and role information (role data), it is determined whether the operation is permitted as a role (role) according to the access control matrix (authorization data). An access control unit (operation request verification unit 162) that generates a result,
The operation is executed when access is permitted from the judgment result.

The key generation device 400 (server) described above is
An issue request receiving unit (generated user identification receiving unit 411 / signature receiving unit 412) for receiving an issue request (user identification data and signature data);
A signature verification unit 423 that verifies signature information (signature data) included in the issue request with signature verification information (public key certificate) and generates a verification result;
When the verification result is correct, role information (role data) included in the ID information (user identification data) included in the issue request, identification information (target identification data) included in the ID information included in the issue request, Based on the user information (individual identification data) included in the issuance request, according to the authentication information (role-corresponding data), whether or not the user has the access right as a role (role) for the device (execution device 200) is authenticated. An access right authentication unit (right determination unit 434) generated as
An ID-based secret key generation unit (secret key generation unit) that generates an ID-based secret key (a secret key in an ID-based encryption method) from ID information (user identification data) when it is authenticated that there is an access right from the authentication result 441),
A secret key encryption unit that generates an encrypted secret key (encrypted secret key) from an ID-based secret key (secret key in the ID-based encryption method) using a user public key (public key in the public key encryption method) included in the user information ( A secret key encryption unit 442),
A secret key transmission unit (encrypted secret key transmission unit 451) for transmitting the encrypted secret key (encrypted secret key).

The access control system 800 (access control method) described above is controlled by the user device (user terminal device 300), the device (execution device 200), and the server (key generation device 400).
The device described above (execution device 200) includes an ID information generation unit (identification generation unit 123) that generates ID information (user identification data) based on a role in the role-based access control method.
In addition, the above-described device (execution apparatus 200) encrypts an encryption key (common key) for encrypting operation information (operation request message) by ID information (user identification data), and an encrypted encryption key ( An ID-based encryption unit (communication key encryption unit 133) for obtaining an encrypted communication key is provided.
The user device (user terminal device 300) described above decrypts the encrypted encryption key (encrypted communication key) encrypted with the ID information (user identification data) with the secret key of the ID-based encryption and encrypts the encryption key. An ID-based decryption unit (communication key decryption unit 371) for obtaining (decryption communication key) is provided.
The server (key generation device 400) described above includes an ID-based secret key generation unit (secret key generation unit 441) that generates a secret key corresponding to ID information (user identification data).
The server (key generation device 400) described above includes identification information (target identification data) of the device (execution device 200), user information (individual identification data), and role information (role data) requested by the user. And an access right authenticating unit (authority determining unit 434) that authenticates the presence / absence of an access right with reference to authentication information (role-corresponding data).

  The operation of the access control system 800 described above will be described in summary.

  First, in advance, the user device (user terminal device 300) holds a user secret key and a user public key in the public key cryptosystem. The device (execution device 200) has an access control matrix (relationship between identification information (target identification data) for enabling identification with other devices (execution device 200), and roles (roles) and permitted operations. Authority-related data). The server (key generation device 400) includes signature verification information (public key certificate) for verifying signature information (signature data), user information (individual identification data), role information (role data), and identification information (target) Authentication information (role-corresponding data) indicating whether or not there is an access right corresponding to (identification data). This completes the preparation.

Then, the user device (user terminal device 300) starts processing.
A user determines a role (role) for operating the device (execution device 200), and a role request transmission unit (authority request transmission unit 322) transmits role information (role data) to the device (execution device 200).

Then, the device (execution device 200) starts processing.
The role request receiving unit (authorization request receiving unit 111) receives role information (role data) from the user device (user terminal device 300). Next, the random number generation unit 122 generates a random number. Next, the ID information generation unit (identification generation unit 123) determines the ID information (user identification) from the identification information (target identification data) for identifying the device (execution device 200), role information (role data), and a random number. Data). Next, the encryption key generation unit (communication key generation unit 131) generates an encryption key (common key) and a decryption key (common key). Next, the ID-based encryption unit (communication key encryption unit 133) encrypts the encrypted encryption key (encryption) using the ID information (user identification data) from the encryption key (common key) to be encrypted by the ID-based encryption. Communication key). Next, the authority confirmation transmission unit (identification transmission unit 141 / encrypted communication key transmission unit 142) combines the ID information (user identification data) and the encrypted encryption key (encrypted communication key) together with the authority confirmation information. To the user device (user terminal device 300).

Then, the user device (user terminal device 300) starts processing.
The authority confirmation receiving unit (terminal user identification receiving unit 331 / encrypted communication key receiving unit 332) receives authority confirmation information (user identification data and encrypted communication key) from the device (execution apparatus 200). The signature unit (signature generation unit 343) generates signature information (signature data) from the ID information (user identification data) included in the authority confirmation information by using the user secret key (secret key in the public key cryptosystem). Next, the issue request transmission unit (terminal user identification transmission unit 351 / signature transmission unit 352) performs user information including the user public key (individual identification data), ID information (user identification data), and signature information ( Together with the signature data), it is sent to the server (key generation device 400) as an issue request.

Then, the server (key generation device 400) starts processing.
The issue request receiving unit (generated user identification receiving unit 411 and signature receiving unit 412) receives the issue request from the user device (user terminal device 300). Next, the signature verification unit 423 verifies the signature information (signature data) included in the issue request with the signature verification information (public key certificate) and generates a verification result.
The signature verification unit 423 may use a user public key passed from the user device (user terminal device 300) to the server (key generation device 400) as a signature verification information by a secure method in advance. .
In addition, the server (key generation device 400) previously generates the user's private key (the private key in the public key cryptosystem) and the user's public key (the public key in the public key cryptosystem). The configuration may be such that the secret key of the user and the public key of the user are passed from the generation device 400) to the user device (user terminal device 300).
Alternatively, the PKI certificate authority may issue a public key certificate to the user public key in advance, and the server (key generation device 400) may use the certificate authority public key certificate as signature verification information.

Next, when the verification result is correct, the access right authentication unit (right determination unit 434) includes the role information (role data) included in the ID information (user identification data) included in the issue request and the issue request. Based on the identification information (object identification data) included in the ID information and the user information (individual identification data) included in the issuance request, according to the authentication information (role-corresponding data), the user device (execution device 200) ) As an authentication result.
For example, the authority determination unit 434 first identifies and identifies a table (role-corresponding data) that represents the relationship between identification information (target identification data) and role information (role data) based on user information (individual identification data). Based on the information (target identification data) and role information (role data), the presence / absence of an access right is determined based on “o” and “x” in the corresponding part of the table (role correspondence data).

  Next, the ID base secret key generation unit (secret key generation unit 441) generates an ID base secret key from the ID information (user identification data) when it is authenticated from the authentication result that there is an access right. Next, the secret key encryption unit (secret key encryption unit 442) uses the user-based public key (public key in the public key cryptosystem) included in the user information (individual identification data) from the ID-based secret key to encrypt the private key ( Encryption secret key). Next, the secret key transmitting unit (encrypted secret key transmitting unit 451) transmits the encrypted secret key (encrypted secret key) to the user device (user terminal device 300).

Then, the user device (user terminal device 300) starts processing.
The secret key receiving unit (encrypted secret key receiving unit 361) receives the encrypted secret key (encrypted secret key). Next, the secret key decryption unit (secret key decryption unit 362) decrypts the ID-based secret key from the encrypted secret key (encrypted secret key) with the user secret key (secret key in the public key cryptosystem). Next, the ID-based decryption unit (communication key decryption unit 371) decrypts the encryption key (common key) from the encrypted encryption key (encrypted communication key) included in the authority confirmation information using the ID-based secret key. Next, the encryption unit (operation request encryption unit 382) generates encrypted operation information (encryption operation request) using an encryption key (common key) from operation information (operation request message) for the device (execution apparatus 200). . Next, the operation request transmission unit (encryption operation request transmission unit 383) transmits the encrypted operation information (encryption operation request) to the device (execution apparatus 200).

Then, the device (execution device 200) starts processing.
The operation request reception unit (encryption operation request reception unit 151) receives the encrypted operation information (encryption operation request). Next, the decryption unit (operation request decryption unit 152) decrypts the operation information (operation request message) from the encrypted operation information (encryption operation request) using the decryption key (common key). Next, when the decryption unit (operation request decryption unit 152) correctly decrypts the operation information (operation request message), the operation request verification unit 162 displays the correctly decrypted operation information (operation request message) and the role information ( Based on the role data, a determination result as to whether or not the operation is permitted as the role (role) is generated according to the access control matrix (authorization correspondence data).
For example, the operation request verification unit 162 determines whether or not the operation is permitted based on “O” and “X” in the corresponding part of the table from the operation (operation content data) and role information (role data).
Next, the device (execution device 200) executes an operation when access is permitted based on the determination result.

  As described above, access control is realized.

Note that the access control matrix (authorization correspondence data) held by the device (execution device 200) may be different for each device (execution device 200) or the same.
Further, the encryption key and the decryption key generated by the device (execution device 200) by the encryption key generation unit may be configured to use the same key based on the common key encryption method, or may be different based on the asymmetric encryption method. It is good also as a structure using a key.
Alternatively, a public key certificate in PKI may be used instead of the user public key, and the public key certificate of the certificate authority that issued the public key certificate may be used as signature verification information.

According to the access control system 800 described above, when performing access control using an ID-based encryption method, a plurality of access destinations can be used while making the access control matrix common to each access destination in the role-based access control method. The presence or absence of individual access rights can be determined.
Also, when performing access control using an ID-based encryption method, the presence / absence of access rights for all access destinations is transmitted in advance to the issuing center (key generation device 400), and the corresponding private key is obtained. There is no need to keep all these private keys safe.
Further, when access control is performed using an ID-based encryption method, it is possible to quickly reflect the expiration of the access right.

  According to the access control system 800 described above, the device (execution device 200) generates an ID information generation unit (identification) that generates ID information (user identification data) based on a role in the role-based access control method. A generation unit 123), and the device (execution apparatus 200) encrypts an encryption key (common key) by which a user encrypts operation information (operation request message) with ID information (user identification data). An ID-based encryption unit (communication key encryption unit 133) that obtains a key (encrypted communication key) is provided, and the user device (user terminal device 300) is encrypted with ID information (user identification data) An ID-based decryption unit (communication key decryption unit 371) that decrypts an encryption key (encrypted communication key) with an ID-based encryption private key to obtain an encryption key (common key), and includes a server (key generation device) 400) includes an ID-based secret key generation unit (secret key generation unit 441) that generates a secret key corresponding to the ID information (user identification data), and performs access control using an ID-based encryption method. In this case, it is possible to determine the presence / absence of individual access rights for a plurality of access destinations while making the access control matrix (authorization-corresponding data) in the role-based access control method common to each access destination (execution apparatus 200) There is an effect.

  According to the access control system 800 described above, the server (key generation device 400) has the ID-based secret key generation unit (secret key generation unit 441) that generates a secret key corresponding to the ID information (user identification data). By providing, when performing access control using an ID-based encryption method, the presence / absence of access rights for all access destinations is transmitted to the issuing center in advance, and the secret keys corresponding to each are obtained, and all these There is an effect that it is not necessary to keep keeping the secret key securely.

  According to the access control system 800 described above, the server (key generation device 400) allows the device (execution device 200) identification information (target identification data), user information (individual identification data), and role information requested by the user ( An access right authenticating unit (authority determining unit 434) that authenticates the presence / absence of an access right by referring to authentication information (role-corresponding data) based on the role data), and the server (key generation device 400) By providing an ID-based secret key generation unit (secret key generation unit 441) that generates a secret key corresponding to information (user identification data), when performing access control using an ID-based encryption method, an access right Is reflected in the authentication information (role-corresponding data), and a secret key corresponding to the ID information is generated only when there is an access right. There is an effect that it reflects.

In addition, after the device (execution device 200) gives the determination result, the device (execution device 200) newly generates an encryption key in the device (execution device 200) for the key update, The ID-based encryption unit (communication key encryption unit 133) generates the encrypted encryption key (encrypted communication key) using the same ID information (user identification data) as the previous time, and the user device (use) as authority confirmation information It is good also as a structure transmitted to the person terminal device 300). In this case, the user device (user terminal device 300) reuses the ID-based secret key corresponding to the same ID information (user identification data), and the ID-based decryption unit (secret key decryption unit 362) uses the encryption key ( The common key is decrypted, and the operation information (operation request message) is encrypted with the encryption key (common key) and sent to the device (execution apparatus 200).
Thus, while the device (execution device 200) treats the access right as valid, the encryption key (encryption of the operation information (operation request message) is encrypted using the same ID information (user identification data) ( (Common key) can be updated.

  In general, access control is performed to control whether or not an object (object) can access an entity (subject, user terminal device 300) that accesses assets such as functions and information of the object (object, target device 210). The technology is used. In a role-based access control method, which is one implementation method of access control, a role (role) assigned to a subject (subject) and whether access is permitted are managed by an access control matrix. In addition, it is necessary to prove that the subject (subject) is correctly given a role by authentication. For this reason, the object (object) needs to hold authentication information (role-corresponding data) for authenticating the subject (subject) and an access control matrix (authorization-corresponding data).

According to the access control system 800 described above, it is possible to determine whether or not the subject (subject) has the access right from the ID information (user identification data) by using the ID-based encryption method. Does not need to set and hold authentication information (role correspondence data) in advance.
That is, it is not necessary for the execution device 200 to hold or verify authentication information such as a public key certificate, and the data set in the execution device 200 is changed even when the user's operation authority changes. There is no need to do. For this reason, it is possible to flexibly cope with a change in operation authority.

Embodiment 2. FIG.
The second embodiment will be described with reference to FIGS.
Note that portions common to the access control system 800 described in Embodiment 1 are denoted by the same reference numerals, and description thereof is omitted.

FIG. 9 is a block configuration diagram showing an example of a functional block configuration of the user terminal device 300 in this embodiment.
In addition to the functional blocks described in the first embodiment, the user terminal device 300 further includes a requested user identification transmission unit 384.

The requested user identification transmission unit 384 uses the CPU 911 to input the user identification data stored in the terminal user identification storage unit 341 when the encryption operation request transmission unit 383 transmits the encryption operation request.
The request user identification transmission unit 384 transmits the input user identification data together with the encryption operation request transmitted by the encryption operation request transmission unit 383 to the execution device 200 using the communication device 915.

FIG. 10 is a block configuration diagram showing an example of a functional block configuration of the execution device 200 in this embodiment.
In addition to the functional blocks described in the first embodiment, the authority verification device 100 further includes an issue time acquisition unit 125, an identification reception unit 153, a request time acquisition unit 154, a communication key deletion unit 155, and a communication key selection unit 156. Have.

  The issue time acquisition unit 125 uses the CPU 911 to acquire the current time when the authority request reception unit 111 receives the authority request message. Using the CPU 911, the issue time acquisition unit 125 outputs data (hereinafter referred to as “issue time data”) representing the acquired current time (hereinafter referred to as “issue time”).

Using the CPU 911, the identification generation unit 123 inputs the role data output from the role acquisition unit 121, the random number output from the random number generation unit 122, and the issue time data output from the issue time acquisition unit 125.
The identification generation unit 123 uses the CPU 911 to generate user identification data based on the input role data, random number, and issue time data. For example, the identification generation unit 123 uses the CPU 911 to combine target identification data for identifying the execution device 200 itself, input role data, input character string data representing a random number, and input issuance time data. The combined data is used as user identification data.
The identification generation unit 123 uses the CPU 911 to output the generated user identification data.

Using the CPU 911, the communication key storage unit 132 inputs the user identification data output from the identification generation unit 123 and the common key output from the communication key generation unit 131.
The communication key storage unit 132 stores the input common key in association with the input user identification data using the magnetic disk device 920. When there is a common key that is already stored, the communication key storage unit 132 stores the input common key in addition to the already stored common key, and stores a plurality of common keys.

  The identification receiving unit 153 uses the communication device 915 to receive the user identification data transmitted from the user terminal device 300 together with the encryption operation request. Using the CPU 911, the identification receiving unit 153 outputs the received user identification data.

  Using the CPU 911, the request time acquisition unit 154 acquires the current time when the encryption operation request reception unit 151 receives an encryption operation request. Using the CPU 911, the request time acquisition unit 154 outputs data (hereinafter referred to as “request time data”) representing the acquired current time (hereinafter referred to as “request time data”).

Using the CPU 911, the communication key deletion unit 155 inputs the user identification data output from the identification reception unit 153 and the request time data output from the request time acquisition unit 154.
Using the CPU 911, the communication key deletion unit 155 acquires issuance time data from the input user identification data. For example, the communication key deletion unit 155 uses the CPU 911 to extract the issue time data by extracting the issue time data from the user identification data including the issue time data.
Using the CPU 911, the communication key deletion unit 155 compares the issue time indicated by the acquired issue time data with the request time indicated by the input request time data, and whether the expiration date of the user identification data has expired. Determine.
For example, when the expiration date of the user identification data is “1 day”, the communication key deletion unit 155 uses the CPU 911 to compare the date of the issue time with the date of the request time, and is valid if the dates are the same. If the date is different within the expiration date, it is determined that the expiration date has expired. Alternatively, when the expiration date of the user identification data is “10 minutes”, the communication key deletion unit 155 uses the CPU 911 to calculate the time 10 minutes after the issue time, and calculates the calculated time (hereinafter “expiration date”). Compared with the request time, it is determined that the request time is within the expiration date if the request time is before the expiration time, and that the expiration date is determined if the request time is after the expiration time.

  The identification generation unit 123 does not generate the user identification data including the issue time data, but uses the CPU 911 to calculate the expiration date from the issue time indicated by the issue time data, and calculates the calculated expiration date. It is also possible to generate user identification data including data representing the following (hereinafter referred to as “expiration time data”). In that case, the communication key deletion unit 155 uses the CPU 911 to acquire the expiration date data from the user identification data, compares the expiration date represented by the acquired expiration date data with the request time, Determine whether the expiration date has expired. If comprised in this way, a different expiration date can also be set for every user identification data.

  If it is determined that the expiration date has expired, the communication key deletion unit 155 uses the CPU 911 to delete the common key associated with the input user identification data from the common keys stored in the communication key storage unit 132.

  Note that the communication key deletion unit 155 has a predetermined number of common keys stored in the communication key storage unit 132 not only when the encryption operation request reception unit 151 receives the encryption operation request but also periodically or the communication key storage unit 132 stores the predetermined number of common keys. When the number exceeds the number, or when the processing capacity of the CPU 911 of the execution device 200 is sufficient, the expiration date of the user identification data associated with the common key stored in the communication key storage unit 132 is determined, A configuration may be adopted in which the common key associated with the user identification data determined to have expired is deleted from the common keys stored in the communication key storage unit 132.

The communication key selection unit 156 uses the CPU 911 to input the user identification data output from the identification reception unit 153.
Using the CPU 911, the communication key selection unit 156 selects a common key associated with the input user identification data from the common keys stored in the communication key storage unit 132, and acquires the selected common key. .
Using the CPU 911, the communication key selection unit 156 outputs the acquired common key.

The operation request decryption unit 152 uses the CPU 911 to input the encryption operation request output from the encryption operation request reception unit 151 and the common key output from the communication key selection unit 156.
The operation request decryption unit 152 uses the CPU 911 to decrypt the input encryption operation request using the input common key as a decryption key by the common key encryption method.
Using the CPU 911, the operation request decryption unit 152 outputs the decrypted decryption operation request.

  When the communication key storage unit 132 does not store the common key associated with the input user identification data, the communication key selection unit 156 does not acquire the common key, and the operation request decryption unit 152 performs the encryption operation. Do not decrypt the request. For example, when the communication key deletion unit 155 deletes the common key due to expiration, the user identification data is falsified during communication, or a third party attacks the execution device 200 to attack the execution device 200. When the identification reception unit 153 receives user identification data different from the user identification data transmitted by the identification transmission unit 141 due to transmission of illegal data, the operation request decryption unit 152 sends an encryption operation request. Do not decrypt.

  FIG. 11 is a flowchart showing an example of the flow of operation request verification processing S660 in which the authority verification device 100 in this embodiment verifies an encryption operation request.

In the encryption operation request reception step S <b> 661, the encryption operation request reception unit 151 receives the encryption operation request transmitted by the user terminal device 300 using the communication device 915.
In the identification receiving step S662, the identification receiving unit 153 receives the user identification data transmitted from the user terminal device 300 using the communication device 915.
In the expiration date determination step S663, the request time acquisition unit 154 uses the CPU 911 to acquire the request time. Using the CPU 911, the communication key deletion unit 155 acquires issuance time data based on the user identification data received by the identification reception unit 153 in the identification reception step S662. Using the CPU 911, the communication key deletion unit 155 determines whether or not it is within the expiration date based on the issue time represented by the acquired issue time data and the request time acquired by the request time acquisition unit 154.
When the communication key deletion unit 155 determines that the period is within the expiration date, the authority verification device 100 proceeds to the communication key selection step S664.
When the communication key deletion unit 155 determines that the expiration date has expired, the authority verification device 100 proceeds to the communication key deletion step S668.

In the communication key selection step S664, the communication key selection unit 156 uses the CPU 911 to convert the user identification data received by the identification reception unit 153 in the identification reception step S662 from the common key stored in the communication key storage unit 132. Select the associated common key.
If there is no common key associated with the user identification data among the common keys stored in the communication key storage unit 132, the authority verification device 100 ends the operation request verification process S660 and executes the process execution process S670. Do not execute.
When the communication key selection unit 156 selects a common key associated with the user identification data from the common keys stored in the communication key storage unit 132, the authority verification device 100 proceeds to the operation request decryption step S665. .

In the operation request decryption step S665, the operation request decryption unit 152 uses the CPU 911 to encrypt the operation key using the common key selected by the communication key selection unit 156 in the communication key selection step S664 as a decryption key by the common key encryption method. The encryption operation request reception unit 151 decrypts the encryption operation request received in the encryption operation request reception step S661.
In the operation request verification step S666, the operation request verification unit 162 uses the CPU 911 to verify the decryption operation request decrypted by the operation request decryption unit 152 in the operation request decryption step S665.
If the operation request verification unit 162 determines that the user has the operation authority as a result of the verification, the authority verification apparatus 100 ends the operation request verification process S660 and proceeds to the process execution process S670.
As a result of the verification, when the operation request verification unit 162 determines that the user has no operation authority, the authority verification apparatus 100 ends the operation request verification process S660 and does not execute the process execution process S670.

In the communication key deletion step S668, the communication key deletion unit 155 uses the CPU 911 to add the user identification data received by the identification reception unit 153 in the identification reception step S662 from the common key stored in the communication key storage unit 132. Delete the associated common key.
Thereafter, the authority verification device 100 ends the operation request verification process S660 and does not execute the process execution process S670.

The authority verification device 100 in this embodiment further includes a storage device (magnetic disk device 920) for storing data, a communication key storage unit 132, an identification reception unit 153, and a communication key selection unit 156.
The communication key storage unit 132 uses the storage device (magnetic disk device 920) to associate the communication key storage unit 132 with the user identification data acquired by the identification acquisition unit (identification generation unit 123). The generated decryption key (common key) is stored.
The identification receiving unit 153 receives the user identification data transmitted by the user terminal device 300 together with the encryption operation request using the receiving device (communication device 915).
The communication key selection unit 156 uses the processing device (CPU 911) to convert the user identification data received by the identification reception unit 153 from the decryption key (common key) stored in the communication key storage unit 132. The associated decryption key (common key) is selected.
The operation request decryption unit 152 uses the processing device (CPU 911) and uses the decryption key (common key) selected by the communication key selection unit 156 to encrypt the encryption operation request reception unit 151. The decryption operation request is decrypted to be a decryption operation request.

  According to the authority verification device 100 in this embodiment, the decryption key (common key) generated by the communication key generation unit 131 is associated with the user identification data acquired by the identification acquisition unit (identification generation unit 123), Since the communication key selection unit 156 selects a decryption key (common key) stored in the communication key storage unit 132 and associated with the user identification data received by the identification reception unit 153, a plurality of decryption keys (common keys) are selected. Can be used for each user identification data, and operations by a plurality of users can be received in parallel.

The authority verification device 100 in this embodiment further includes a communication key deletion unit 155.
The communication key deletion unit 155 determines whether the decryption key (common key) stored in the communication key storage unit 132 is valid or invalid using the processing device (CPU 911), and the communication key storage unit 132 stores the communication key deletion unit 155. The decryption key (common key) determined to be invalid is deleted from the decrypted keys (common key).

  According to the authority verification device 100 in this embodiment, the communication key deletion unit 155 determines whether the decryption key (common key) stored in the communication key storage unit 132 is valid or invalid, and the decryption key determined to be invalid. Since the (common key) is deleted, it is possible to prevent an invalid decryption key (common key) from being used.

The authority verification device 100 in this embodiment further includes a current time acquisition unit (issue time acquisition unit 125).
The current time acquisition unit (issue time acquisition unit 125) uses the processing device (CPU 911) to acquire current time data (issue time data) representing the current time (issue time).
The identification acquisition unit (identification generation unit 123) uses the processing device (CPU 911) based on the current time data (issue time data) acquired by the current time acquisition unit (issue time acquisition unit 125). The user identification data is obtained by generating user identification data.

  According to the authority verification device 100 in this embodiment, the identification acquisition unit (identification generation unit 123) uses the current time data (issue time data) acquired by the current time acquisition unit (issue time acquisition unit 125). Since user identification data is generated, duplication of user identification data can be avoided.

The authority verification device 100 in this embodiment further includes an issue time acquisition unit 125, a request time acquisition unit 154, and an expiration date determination unit (communication key deletion unit 155).
The issue time acquisition unit 125 acquires issue time data representing the time (issue time) when the identification acquisition unit (identification generation unit 123) acquires user identification data, using the processing device (CPU 911).
The request time acquisition unit 154 uses the processing device (CPU 911) to acquire request time data indicating the time (request time) when the encryption operation request reception unit 151 receives the encryption operation request.
The expiration date determination unit (communication key deletion unit 155) uses the processing device (CPU 911) to issue the issue time data acquired by the issue time acquisition unit 125 and the request time data acquired by the request time acquisition unit 154. Based on the above, it is determined whether it is within the expiration date.
The operation request decryption unit 152 is generated by the communication key generation unit 131 when the expiration date determination unit (communication key deletion unit 155) determines that it is within the expiration date using the processing device (CPU 911). Using the decryption key, the encryption operation request received by the encryption operation request reception unit 151 is decrypted to obtain a decryption operation request.

  According to the authority verification device 100 in this embodiment, based on the issue time data acquired by the issue time acquisition unit 125 and the request time data acquired by the request time acquisition unit 154, the expiration date determination unit (communication key deletion) Section 155) determines whether or not the expiration date is within the validity period, the validity period can be set for the decryption key (common key), and if it is within the validity period, the user terminal device 300 uses the same encryption key. Thus, it is possible to perform a plurality of operations, and it is not necessary to communicate with the key generation device 400 to acquire a secret key in the ID-based encryption method, so that the amount of communication in the access control system 800 can be reduced. Further, when the expiration date of the decryption key (common key) expires, the decryption key (common key) is revoked. Therefore, when the operation authority is changed, a user without the operation authority is allowed to apply to the target device 210. Can be prevented from operating.

The authority verification device 100 in this embodiment further includes an identification receiving unit 153.
The identification acquisition unit (identification generation unit 123) uses the processing device (CPU 911) to generate user identification data based on the issue time data acquired by the issue time acquisition unit 125. Acquire person identification data.
The identification receiving unit 153 receives the user identification data transmitted by the user terminal device 300 together with the encryption operation request using the receiving device (communication device 915).
The expiration date determination unit (communication key deletion unit 155) uses the processing device (CPU 911) to acquire issue time data based on the user identification data received by the identification reception unit 153, and to obtain the issued issue Based on the time data and the request time data acquired by the request time acquisition unit 154, it is determined whether it is within the expiration date.

  According to the authority verification device 100 in this embodiment, since the identification acquisition unit (identification generation unit 123) generates user identification data based on the issue time data acquired by the issue time acquisition unit 125, user identification data By examining itself, the issue time of the user identification data can be known, and the expiration date can be easily managed.

The execution device 200 (device) described above is
A role request receiving unit (authority request receiving unit 111) for receiving role information (role data);
A random number generator 122 for generating a random number;
A date acquisition unit (issue time acquisition unit 125) for acquiring date and time (issue time);
ID information generation for generating ID information (user identification data) from identification information (object identification data) for identifying a device (execution device 200), role information (role data), a random number, and date and time (issue time) Part (identification generation part 123),
An encryption key generation unit (communication key generation unit 131) for generating an encryption key (common key) and a decryption key (common key);
Decryption key deletion unit (communication key deletion unit) that deletes the decryption key (common key) based on the date and time (issue time) and the current date and time (request time) acquired from the date and time acquisition unit (request time acquisition unit 154) 155),
An ID-based encryption unit (communication key encryption unit 133) that generates an encrypted encryption key (encrypted communication key) from the encryption key (common key) using ID information (user identification data);
An authority confirmation transmission unit (identification transmission unit 141 / encrypted communication key transmission unit 142) that transmits ID information (user identification data) and an encrypted encryption key (encryption encryption key) together as authority confirmation information;
An operation request receiving unit (encrypted operation request receiving unit 151) for receiving encrypted operation information (encrypted operation request);
A decryption unit (operation request decryption unit 152) that decrypts the operation information (operation request message) from the encrypted operation information using a decryption key (common key);
Based on the correctly decrypted operation information (operation request message) and role information (role data), it is determined whether the operation is permitted as a role (role) according to the access control matrix (authorization data). An access control unit (operation request verification unit 162) that generates a result,
The operation is executed when access is permitted from the judgment result.

  The operation of the access control system 800 described above will be described in summary.

  First, in advance, the user device (user terminal device 300) holds a user secret key and a user public key in the public key cryptosystem. The device (execution device 200) has identification information (target identification data) for enabling identification with other devices (execution device 200), and an access control matrix (authority) indicating the relationship between roles (roles) and permitted operations. Corresponding data). The server (key generation device 400) includes signature verification information (public key certificate) for verifying signature information (signature data), user information (individual identification data), role information (role data), and identification information (target) Authentication information (role-corresponding data) indicating whether there is an access right corresponding to (identification data). This completes the preparation.

Then, the user device (user terminal device 300) starts processing.
A user determines a role (role) for operating the device, and a role request transmission unit (authority request transmission unit 322) transmits role information (role data) to the device (execution apparatus 200).

Then, the device (execution device 200) starts processing.
The role request receiving unit (authorization request receiving unit 111) receives role information (role data) from the user device (user terminal device 300). Next, the random number generation unit 122 generates a random number. Next, the date acquisition unit (issue time acquisition unit 125) acquires the date and time (issue time). Next, the ID information generation unit (identification generation unit 123) uses the identification information (object identification data) for identifying the device, role information (role data), random numbers, and date information (issue time) to obtain ID information (utilization). (Person identification data) is generated. Next, the encryption key generation unit (communication key generation unit 131) generates an encryption key (common key) and a decryption key (common key). Next, the ID-based encryption unit (communication key encryption unit 133) encrypts the encrypted encryption key (encryption) using the ID information (user identification data) from the encryption key (common key) to be encrypted by the ID-based encryption. Communication key). Next, the authority confirmation transmitting unit (identification transmitting unit 141 / encrypted communication key transmitting unit 142) combines the ID information (user identification data) and the encrypted encryption key (encrypted communication key) as authority confirmation information. It transmits to a user apparatus (user terminal device 300).

Then, the user device (user terminal device 300) starts processing.
The authority confirmation receiving unit (terminal user identification receiving unit 331 / encrypted communication key receiving unit 332) receives authority confirmation information (user identification data and encrypted communication key) from the device (execution apparatus 200). Next, the signature unit (signature generation unit 343) generates signature information (signature data) from the ID information (user identification data) included in the authority confirmation information by using the user secret key (secret key in the public key cryptosystem). . Next, the issue request transmission unit (terminal user identification transmission unit 351 / signature transmission unit 352) performs user information including the user public key (individual identification data), ID information (user identification data), and signature information ( Together with the signature data), it is sent to the server (key generation device 400) as an issue request.

Then, the server (key generation device 400) starts processing.
The issue request receiving unit (generated user identification receiving unit 411 and signature receiving unit 412) receives the issue request from the user device (user terminal device 300). Next, the signature verification unit 423 verifies the signature information (signature data) included in the issue request with the signature verification information (public key certificate) and generates a verification result.
The signature verification unit 423 may use a user public key passed from the user device (user terminal device 300) to the server (key generation device 400) as a signature verification information by a secure method in advance. .
Also, the server (key generation device 400) generates the user's private key and the user's public key in advance, and the user's secret is transferred from the server (key generation device 400) to the user device (user terminal device 300) by a secure method. The key and the user's public key may be passed.
Alternatively, the PKI certificate authority may issue a public key certificate to the user public key in advance, and the server (key generation device 400) may use the certificate authority's public key certificate as signature verification information.

Next, when the verification result is correct, the access right authentication unit (right determination unit 434) is included in the role information (role data) included in the ID information included in the issue request and the ID information included in the issue request. Based on the identification information (target identification data) and the user information (individual identification data) included in the issuance request, the role (role) for the user device (execution device 200) according to the authentication information (role-corresponding data). As a result of authentication.
For example, the authority determining unit 434 first specifies a table representing the relationship between identification information (target identification data) and role information (role data) based on user information (individual identification data), and from the identification information and role information. The presence / absence of access right is determined based on “○” and “×” in the corresponding part of the table.

  Next, the ID base secret key generation unit (secret key generation unit 441) generates an ID base secret key from the ID information (user identification data) when it is authenticated from the authentication result that there is an access right. Next, the secret key encryption unit (secret key encryption unit 442) generates an encrypted secret key (encrypted secret key) from the ID base secret key using the user public key included in the user information (individual identification data). Next, the secret key transmitting unit (encrypted secret key transmitting unit 451) transmits the encrypted secret key (encrypted secret key) to the user device (user terminal device 300).

Then, the user device (user terminal device 300) starts processing.
The secret key receiving unit (encrypted secret key receiving unit 361) receives the encrypted secret key (encrypted secret key). Next, the secret key decryption unit 362 decrypts the ID base secret key from the encrypted secret key (encrypted secret key) with the user secret key. Next, the ID-based decryption unit (communication key decryption unit 371) decrypts the encryption key (common key) from the encrypted encryption key (encrypted communication key) included in the authority confirmation information using the ID-based secret key. Next, the encryption unit (operation request encryption unit 382) generates encrypted operation information (encryption operation request) using an encryption key (common key) from operation information (operation request message) for the device (execution apparatus 200). . Next, the operation request transmission unit (encryption operation request transmission unit 383) transmits the encrypted operation information (encryption operation request) to the device (execution apparatus 200).

Then, the device (execution device 200) starts processing.
The operation request reception unit (encryption operation request reception unit 151) receives the encrypted operation information (encryption operation request). Next, based on the date and time (issue time) and the current date and time (request time) acquired by the date and time acquisition unit (request time acquisition unit 154), the decryption key deletion unit (communication key deletion unit 155) Whether or not the immediacy of the revocation of the access right is not impaired is confirmed from the elapse of time, and when the immediacy is impaired, the decryption key (common key) is deleted, and the subsequent processing is interrupted.
Next, the decryption unit (operation request decryption unit 152) decrypts the operation information (operation request message) from the encrypted operation information (encryption operation request) using the decryption key (common key). Next, when the decryption unit (operation request decryption unit 152) correctly decrypts the operation information (operation request message), the operation request verification unit 162 determines that the correctly decrypted operation information (operation request message) and the role information ( Based on the role data, a determination result as to whether or not the operation is permitted as the role (role) is generated according to the access control matrix (the authority correspondence data 9).
For example, the operation request verification unit 162 determines whether or not the operation is permitted based on “O” and “X” in the corresponding part of the table from the operation (operation content data) and role information (role data). .
Next, the device (execution device 200) executes an operation when access is permitted based on the determination result.

  As described above, access control is realized.

  According to the access control system 800 described above, since the date (issue time) is included in the ID information (user identification data), it is possible to avoid duplication with past IDs (user identification data). Further, the decryption key deletion unit (communication key deletion unit 155) uses the date and time (issue time) and the current date and time (request time) acquired by the date and time acquisition unit (request time acquisition unit 154) to It is confirmed whether the immediacy of the access right has been lost from the past, and if the immediacy is lost, the decryption key is deleted and the subsequent processing is interrupted. ) Can be prevented.

Embodiment 3 FIG.
The third embodiment will be described with reference to FIGS.
Note that portions common to the access control system 800 described in Embodiment 1 or Embodiment 2 are denoted by the same reference numerals, and description thereof is omitted.

FIG. 12 is a block configuration diagram showing an example of a functional block configuration of the execution device 200 in this embodiment.
In addition to the functional blocks described in the first embodiment, the authority verification device 100 further includes an identification reception unit 153, a communication key deletion unit 155, a communication key selection unit 156, an operation count storage unit 157, and an operation count counter 158. Have.
The authority verification device 100 may further include the issue time acquisition unit 125 and the request time acquisition unit 154 described in the second embodiment.

  The operation count storage unit 157 uses the magnetic disk device 920 to correlate with the user identification data, and represents data indicating the number of operations performed by the user identification data (hereinafter referred to as “operation count data”). Remember.

Using the CPU 911, the operation count counting unit 158 inputs the user identification data output from the identification receiving unit 153 and the decryption operation request output from the operation request verification unit 162.
When the operation request verification unit 162 outputs a decryption operation request using the CPU 911, the operation number counting unit 158 corresponds to the input user identification data from the operation number data stored in the operation number storage unit 157. Get the operation count data attached. When there is no operation number data associated with the input user identification data in the operation number data stored in the operation number storage unit 157, the operation number counting unit 158 uses the CPU 911 to calculate the operation number 0. Get the operation count data to be represented.
Using the CPU 911, the operation frequency counting unit 158 adds 1 to the operation frequency represented by the input operation frequency data.
Using the CPU 911, the operation frequency counting unit 158 outputs the input user identification data and operation frequency data representing the added operation frequency.
The operation number counting unit 158 uses the CPU 911 to compare the added operation number with a predetermined maximum operation number to determine whether the operation number is less than the maximum operation number or more than the maximum operation number.
Using the CPU 911, the operation number counting unit 158 outputs data representing the determination result.

Using the CPU 911, the operation count storage unit 157 inputs the user identification data and the operation count data output from the operation count counting unit 158.
The operation count storage unit 157 stores the input operation count data in association with the input user identification data using the magnetic disk device 920.

  Using the CPU 911, the communication key deletion unit 155 inputs the user identification data output from the operation count counting unit 158 and data representing the determination result. When the operation number counting unit 158 determines that the number of operations is equal to or greater than the maximum number of operations using the CPU 911 based on the determination result represented by the input data, the communication key deleting unit 155 From the stored common key, the common key associated with the input user identification data is deleted.

  FIG. 13 is a flowchart showing an example of the flow of operation request verification processing S660 in which the authority verification device 100 in this embodiment verifies an encryption operation request.

In the encryption operation request reception step S <b> 661, the encryption operation request reception unit 151 receives the encryption operation request transmitted by the user terminal device 300 using the communication device 915.
In the identification receiving step S662, the identification receiving unit 153 receives the user identification data transmitted from the user terminal device 300 using the communication device 915.
In the communication key selection step S664, the communication key selection unit 156 uses the CPU 911 to convert the user identification data received by the identification reception unit 153 in the identification reception step S662 from the common key stored in the communication key storage unit 132. Select the associated common key.
If there is no common key associated with the user identification data among the common keys stored in the communication key storage unit 132, the authority verification device 100 ends the operation request verification process S660 and executes the process execution process S670. Do not execute.
When the communication key selection unit 156 selects a common key associated with the user identification data from the common keys stored in the communication key storage unit 132, the authority verification device 100 proceeds to the operation request decryption step S665. .

In the operation request decryption step S665, the operation request decryption unit 152 uses the CPU 911 to encrypt the operation key using the common key selected by the communication key selection unit 156 in the communication key selection step S664 as a decryption key by the common key encryption method. The encryption operation request reception unit 151 decrypts the encryption operation request received in the encryption operation request reception step S661.
In the operation request verification step S666, the operation request verification unit 162 uses the CPU 911 to verify the decryption operation request decrypted by the operation request decryption unit 152 in the operation request decryption step S665.
If the operation request verification unit 162 determines that the user has the operation authority as a result of the verification, the authority verification apparatus 100 proceeds to the operation count counting step S667.
As a result of the verification, when the operation request verification unit 162 determines that the user has no operation authority, the authority verification apparatus 100 ends the operation request verification process S660 and does not execute the process execution process S670.

In the operation number counting step S667, the operation number counting unit 158 uses the CPU 911 to add the user identification data received by the identification receiving unit 153 in the identification receiving step S662 among the operation number data stored in the operation number storage unit 157. 1 is added to the number of operations represented by the associated operation number data. The number-of-operations storage unit 157 uses the magnetic disk device 920 to store the number-of-operations data representing the number of operations that the number-of-operations counting unit 158 adds 1, the user identification data received by the identification receiving unit 153 in the identification receiving step S662. Store it in association with.
When the number of operations with 1 added is equal to or greater than the maximum number of operations, the authority verification device 100 proceeds to the communication key deletion step S668.
When the number of operations with 1 added is less than the maximum number of operations, the authority verification device 100 ends the operation request verification process S660 and proceeds to the process execution process S670.

In the communication key deletion step S668, the communication key deletion unit 155 uses the CPU 911 to add the user identification data received by the identification reception unit 153 in the identification reception step S662 from the common key stored in the communication key storage unit 132. Delete the associated common key.
Thereafter, the authority verification device 100 ends the operation request verification process S660 and proceeds to the process execution process S670.

  Thus, when the number of operations reaches the maximum number of operations, the execution device 200 executes processing based on the current operation, but the communication key deletion unit 155 deletes the common key stored in the communication key storage unit 132. Next time, the operation request decryption unit 152 does not decrypt the encryption operation request, and the execution device 200 does not execute the process.

The authority verification device 100 in this embodiment further includes an operation number counting unit 158.
The operation number counting unit 158 uses the processing device (CPU 911) to count the number of times that the operation request verification unit 162 has determined that the operation authority exists, and obtain the number of operations.
The operation request decryption unit 152 is generated by the communication key generation unit 131 when the number of operations counted by the operation number counting unit 158 is less than a predetermined maximum number of operations using the processing device (CPU 911). Using the decryption key (common key), the encryption operation request received by the encryption operation request reception unit 151 is decrypted to obtain a decryption operation request.

  According to the authority verification device 100 in this embodiment, when the operation number counting unit 158 counts the number of times that the operation request verifying unit 162 determines that there is an operation authority, and the counted number of operations is less than the maximum number of operations, Since the operation request decryption unit 152 decrypts the next encryption operation request, the user terminal device 300 performs a plurality of operations using the same encryption key (common key) within the maximum number of operations. In addition, since it is not necessary to communicate with the key generation device 400 to acquire a secret key in the ID-based encryption method, the amount of communication in the access control system 800 can be reduced. In addition, when the maximum number of operations is performed, the decryption key (common key) is revoked. Therefore, when the operation authority is changed, a user without the operation authority operates the target device 210. Can be prevented.

The authority verification device 100 according to this embodiment further includes an identification reception unit 153 and a communication key deletion unit 155.
The identification receiving unit 153 receives the user identification data transmitted by the user terminal device 300 together with the encryption operation request using the receiving device (communication device 915).
The operation number counting unit 158 uses the processing device (CPU 911) to count the number of times the operation request verification unit 162 determines that the user has the operation authority for each user identification data received by the identification receiving unit 153. The number of operations for the user identification data.
The communication key deletion unit 155 stores the communication key storage unit 132 when the number of operations counted by the operation number counting unit 158 is equal to or greater than a predetermined maximum number of operations using the processing device (CPU 911). The decryption key (common key) associated with the user identification data received by the identification receiving unit 153 is deleted from the decryption key (common key).

  According to the authority verification device 100 in this embodiment, the operation frequency counting unit 158 counts the number of times the operation request verification unit 162 determines that there is an operation authority for each user identification data, and the counted operation frequency is the maximum operation frequency. In such a case, the communication key deletion unit 155 deletes the decryption key (common key) associated with the user identification data from the communication key storage unit 132, so that the operation using the user identification data is the maximum number of operations. In such a case, the decryption key (common key) can be revoked, and a user without operating authority can be prevented from operating the target device 210 when the operating authority is changed.

Embodiment 4 FIG.
The fourth embodiment will be described with reference to FIGS.
Note that portions common to the access control system 800 described in any of Embodiments 1 to 3 are denoted by the same reference numerals, and description thereof is omitted.

FIG. 14 is a block configuration diagram showing an example of a functional block configuration of the execution device 200 in this embodiment.
In addition to the functional blocks described in the first embodiment, the authority verification device 100 further includes an identification reception unit 153, a request time acquisition unit 154, a communication key deletion unit 155, a communication key selection unit 156, an operation history storage unit 164, An operation number calculation unit 165 and a deletion user identification unit 166 are provided.
The authority verification device 100 may further include the issue time acquisition unit 125, the operation number storage unit 157, the operation number counting unit 158, and the like described in the second or third embodiment.

Using the CPU 911, the operation history storage unit 164 uses the user identification data output from the identification reception unit 153, the request time data output from the request time acquisition unit 154, and the decryption operation request output from the operation request verification unit 162. Enter.
The operation history storage unit 164 stores the input request time data in association with the input user identification data when the operation request verification unit 162 outputs a decryption operation request using the magnetic disk device 920. For example, using the magnetic disk device 920, the operation history storage unit 164 stores user identification data and request time data as a set of data (records), and stores data composed of a plurality of records. The operation history storage unit 164 uses the CPU 911 to determine whether or not the same user identification data as the input user identification data is already stored. If it is determined that the user identification data is already stored, the operation history storage unit 164 The input request time data is stored by overwriting the request time data. In addition, when it is determined that it is not stored, the operation history storage unit 164 newly generates a record including the input user identification data and the input request time data, and adds it to the already stored record. Remember.

Using the CPU 911, the operation number calculation unit 165 inputs the requested time data stored in the operation history storage unit 164.
Using the CPU 911, the number-of-operators calculation unit 165 calculates the number of user identification data associated with the input request time data (hereinafter referred to as “number of operators”). For example, the operation number calculation unit 165 uses the CPU 911 to count the number of input request time data, and sets the counted number as the number of operations.
Using the CPU 911, the operation number calculation unit 165 outputs data representing the calculated operation number (hereinafter referred to as “operation number data”).

Using the CPU 911, the deletion user identification unit 166 inputs the operation number data output from the operation number calculation unit 165.
Using the CPU 911, the deletion user identification unit 166 compares the number of operations represented by the input number of operations data with a predetermined maximum number of operations, and the number of operations is less than or equal to the maximum number of operations. Determine if there is.
When the CPU 911 is used to determine that the number of operating persons exceeds the maximum number of operating persons, the deletion user specifying unit 166 inputs the requested time data stored in the operation history storage unit 164.
Using the CPU 911, the deletion user specifying unit 166 selects a predetermined number of request time data in order from the oldest request time indicated by the request time data, from among the input request time data.
Using the CPU 911, the deletion user identification unit 166 identifies user identification data (hereinafter referred to as “deletion identification data”) associated with the selected request time data.
Using the CPU 911, the deletion user specifying unit 166 outputs the specified deletion identification data.

Using the CPU 911, the communication key deletion unit 155 inputs the deletion identification data output by the deletion user identification unit 166.
Using the CPU 911, the communication key deletion unit 155 deletes the common key associated with the input deletion identification data from the common keys stored in the communication key storage unit 132.

  FIG. 15 is a flowchart showing an example of the flow of operation request verification processing S660 in which the authority verification device 100 in this embodiment verifies an encryption operation request.

  In the operation request verification step S666, the operation request verification unit 162 uses the CPU 911 to verify the decryption operation request decrypted by the operation request decryption unit 152 in the operation request decryption step S665. In such a case, the authority verification device 100 proceeds to the operation history storage step S691.

In the operation history storage step S <b> 691, the requested time acquisition unit 154 uses the CPU 911 to acquire the requested time. The operation history storage unit 164 uses the magnetic disk device 920 to correlate with the user identification data received by the identification reception unit 153 in the identification reception step S662, and the request time indicating the request time acquired by the request time acquisition unit 154. Store the data.
In the operation number calculation step S692, the operation number calculation unit 165 uses the CPU 911 to calculate the number of operations based on the requested time data stored in the operation history storage unit 164. Using the CPU 911, the deletion user identification unit 166 compares the number of operations calculated by the operation number calculation unit 165 with the maximum number of operations.
When the deletion user specifying unit 166 determines that the number of operating persons is equal to or less than the maximum number of operating persons, the authority verification device 100 ends the operation request verification process S660 and proceeds to the process execution process S670.
When the deletion user specifying unit 166 determines that the number of operating persons exceeds the maximum number of operating persons, the authority verification device 100 proceeds to the deleting user specifying step S693.

In the delete user specifying step S693, the delete user specifying unit 166 uses the CPU 911 to specify delete identification data based on the request time data stored in the operation history storage unit 164.
In the communication key deletion step S668, the communication key deletion unit 155 uses the CPU 911 to delete the common key stored in the communication key storage unit 132 from the deletion user identification unit 166 identified by the deletion user identification unit 166 in the deletion user identification step S693. The common key associated with the identification data is deleted. The operation history storage unit 164 uses the CPU 911 to delete, from the stored request time data, the request time data associated with the delete identification data specified by the delete user specifying unit 166 in the delete user specifying step S693. To do.
Thereafter, the authority verification device 100 ends the operation request verification process S660 and proceeds to the process execution process S670.

  There is a case where the number of users who give the operating authority to the execution device 200 is determined in advance, the operating authority is given to a new user, and the operating authority of the old user is stopped. If there is user identification data that has already been issued to a user whose operation authority has been suspended, it is necessary to invalidate the common key associated with the user identification data so that the execution apparatus 200 cannot be operated. is there.

  In the second embodiment, an expiration date is set, and in the third embodiment, the maximum number of operations is set. If the number is exceeded, the common key is invalidated and the execution apparatus 200 is operated if no new user identification data is issued. It is configured so that it cannot. For this reason, it is necessary to inquire the key generation device 400 for a secret key in the ID-based encryption method corresponding to the new user identification data, and the user whose operation authority has been suspended becomes a secret corresponding to the new user identification data. Since the key is not taught to the key generation device 400, the execution device 200 cannot be operated thereafter.

  The authority verification device 100 according to this embodiment has a predetermined maximum number of users who have operated the execution apparatus 200 when a user who has been newly given an operation authority operates the execution apparatus 200. By determining that the number has exceeded, it is detected that the user authorized to operate has been changed, and the old common key is revoked. Since the common key associated with the user identification data issued to the user is revoked, it is necessary to inquire the key generation device 400 about the secret key in the ID-based encryption method corresponding to the new user identification data. Arise. A user whose operation authority has not been stopped can tell the key generation device 400 of a secret key corresponding to the new user identification data, obtain a new common key, and operate the execution device 200. On the other hand, the user whose operation authority has been stopped cannot tell the key generation device 400 the secret key corresponding to the new user identification data, and thereafter cannot operate the execution device 200. This prevents the user whose operation authority has been stopped from operating the execution device 200 even before the expiration date of the user identification data expires or the number of operations reaches the maximum number of operations. it can.

In this example, the number of operating persons is calculated using the user identification data as a unit, but the operating number may be calculated using the user or the user terminal device 300 as a unit.
In this case, for example, the identification generation unit 123 uses the CPU 911 to generate user identification data including individual identification data. The operation history storage unit 164 uses the CPU 911 to acquire individual identification data from the input user identification data, and uses the magnetic disk device 920 to associate the acquired individual identification data with the input request time data. Remember. Using the CPU 911, the operation number calculation unit 165 calculates the number of individual identification data associated with the requested time data stored in the operation history storage unit 164 and sets it as the operation number.

Further, in this example, the number of operations is calculated for all users who have operated the execution apparatus 200, but the number of operations may be calculated separately for each user role.
In this case, for example, the operating number calculation unit 165 uses the CPU 911 to acquire role data from the user identification data associated with the input request time data, and for each role data, user identification data (or The number of individual identification data) is calculated as the number of operators. In this case, for example, the number of managers is determined in advance, but the number of general users is not determined in advance.

The authority verification device 100 in this embodiment further includes an operation number calculation unit 165 and a deletion user identification unit 166.
The operation number calculation unit 165 uses the processing device (CPU 911) to calculate the number of user identification data of the user that the operation request verification unit 162 determines to have the operation authority, and sets the number as the operation number.
The deletion user identification unit 166 uses the processing device (CPU 911) to exceed the maximum number of operations (maximum number of operations) that the operation number calculated by the operation number calculation unit 165 permits the operation of the target device 210. In this case, the user identification data to be deleted is identified from the user identification data associated with the decryption key (common key) stored in the communication key storage unit 132, and is used as the deletion identification data.
The communication key deletion unit 155 uses the processing device (CPU 911) to delete the deletion identification data specified by the deletion user specifying unit 166 from the decryption key (common key) stored in the communication key storage unit 132. The decryption key (common key) associated with is deleted.

  According to the authority verification device 100 in this embodiment, when the number of operators exceeds a predetermined maximum number, the decryption key (common key) associated with the deletion identification data specified by the deletion user specifying unit 166 is used. Since the communication key deletion unit 155 deletes from the communication key storage unit 132, it is possible to prevent the user who has the old operation authority from operating the execution apparatus 200 when the user who is given the operation authority is changed. it can.

  In the authority verification device 100 in this embodiment, the operation number calculation unit 165 calculates the number of operations for each role of the user using the processing device (CPU 911).

  According to the authority verification device 100 in this embodiment, the number-of-operators calculation unit 165 calculates the number of users for each role of the user, so that the number of users who give the role can be limited for each role. .

Embodiment 5 FIG.
The fifth embodiment will be described with reference to FIGS.
Note that portions common to the access control system 800 described in any of Embodiments 1 to 4 are denoted by the same reference numerals, and description thereof is omitted.

FIG. 16 is a block configuration diagram showing an example of a functional block configuration of the execution device 200 in this embodiment.
In addition to the functional blocks described in the first embodiment, the authority verification device 100 further includes an issue number counting unit 126, an identification receiving unit 153, a communication key deleting unit 155, and a communication key selecting unit 156.
The authority verification device 100 further includes the issue time acquisition unit 125, the request time acquisition unit 154, the operation number storage unit 157, the operation number counting unit 158, and the operation described in any of the second to fourth embodiments. You may have the log | history memory | storage part 164, the operation number calculation part 165, the deletion user specific | specification part 166, etc.

The issue number counting unit 126 uses the magnetic disk device 920 to represent data (hereinafter referred to as “issue number data”) representing the number of user identification data generated by the identification generation unit 123 (hereinafter referred to as “issue number”). .) Remember.
When the authority request receiving unit 111 receives an authority request message using the CPU 911, the issue number counting unit 126 adds 1 to the issue number represented by the stored issue number data, and uses the magnetic disk device 920 to Issuance number data representing the issuance number to which is added.
The issue number counting unit 126 uses the CPU 911 to output the stored issue number data.

Using the CPU 911, the identification generation unit 123 inputs the role data output from the role acquisition unit 121, the random number output from the random number generation unit 122, and the issue number data output from the issue number counting unit 126.
The identification generating unit 123 uses the CPU 911 to generate user identification data based on the input role data, random number, and issue number data. For example, the identification generation unit 123 uses the CPU 911 to combine the target identification data for identifying the execution device 200 itself, the input role data, the input character string data representing the random number, and the input issue number data. The combined data is used as user identification data.
The identification generation unit 123 uses the CPU 911 to output the generated user identification data.

Using the CPU 911, the communication key deletion unit 155 inputs the issue number data (hereinafter referred to as “latest issue number data”) output by the issue number counting unit 126.
The communication key deletion unit 155 uses the CPU 911 to issue the issue number data (hereinafter referred to as “communication key issue number data”) based on the user identification data associated with the common key stored by the communication key storage unit 132. .)
Using the CPU 911, the communication key deletion unit 155 uses a difference between the issue number indicated by the latest issued issue number data and the issue number indicated by the acquired communication key issue number data (hereinafter referred to as “communication key issue number”). Is calculated. The number of issued communication keys calculated by the communication key deletion unit 155 is the user identification data generated by the identification generation unit 123 up to now after the identification generation unit 123 generates user identification data associated with the common key. It is a measure of how old the common key is.
Using the CPU 911, the communication key deletion unit 155 deletes the common key whose calculated communication key issuance number is larger than the predetermined maximum issuance number from the common keys stored in the communication key storage unit 132.

  FIG. 17 is a flowchart showing an example of the flow of the communication key issuing process S620 in which the authority verification device 100 in this embodiment issues a common key.

In the authority request receiving step S <b> 621, the authority request receiving unit 111 receives the authority request message transmitted by the user terminal device 300 using the communication device 915.
In the role acquisition step S622, the role acquisition unit 121 uses the CPU 911 to acquire role data based on the authority request message received by the authority request reception unit 111 in the authority request reception step S621.
In the random number generation step S623, the random number generation unit 122 uses the CPU 911 to generate a random number.
In the issue number counting step S624, the issue number counting unit 126 uses the CPU 911 to add 1 to the issue number represented by the stored issue number data.
In the identification generation step S625, the identification generation unit 123 uses the CPU 911, the role data acquired by the role acquisition unit 121 in the role acquisition step S622, the random number generated by the random number generation unit 122 in the random number generation step S623, and the issue number User identification data is generated based on the issue number counted by the issue number counting unit 126 in the counting step S624.
In the communication key generation step S626, the communication key generation unit 131 uses the CPU 911 to generate a common key used in the common key encryption method. The communication key storage unit 132 uses the magnetic disk device 920 to store the common key generated by the communication key generation unit 131 in association with the user identification data generated by the identification generation unit 123.
In the communication key encryption step S627, the communication key encryption unit 133 uses the CPU 911 to disclose the user identification data generated by the identification generation unit 123 in the identification generation step S625 using the ID-based encryption method in the ID-based encryption method. Using the key as a key, the common key generated by the communication key generation unit 131 in the communication key generation step S626 is encrypted.
In the identification transmission step S628, the identification transmission unit 141 uses the communication device 915 to transmit the user identification data generated by the identification generation unit 123 in the identification generation step S625 to the user terminal device 300.
In the encrypted communication key transmission step S629, the encrypted communication key transmission unit 142 uses the communication device 915 to transmit the encrypted communication key encrypted by the communication key encryption unit 133 in the communication key encryption step S627 to the user. It transmits to the terminal device 300.

  In the communication key selection step S695, the communication key deletion unit 155 uses the CPU 911 to perform the processing from the communication key issuance number calculation step S696 to the communication key deletion step S697 from the common keys stored in the communication key storage unit 132. Select one common key that has not been set. When all the common keys stored in the communication key storage unit 132 have been processed in the communication key issue number calculation step S696 to the communication key deletion step S697 and there is no common key that can be selected, the authority verification device 100 performs the communication key issue processing. S620 ends.

In the communication key issuance number calculation step S696, the communication key deletion unit 155 uses the CPU 911, the common key selected in the communication key selection step S695, and the issue number counted by the issue number counting unit 126 in the issue number counting step S624. Based on the above, the number of issued communication keys is calculated. Using the CPU 911, the communication key deletion unit 155 compares the calculated communication key issuance number with the maximum issuance number to determine the magnitude relationship.
When the communication key deletion unit 155 determines that the communication key issuance number is equal to or less than the maximum issuance number, the authority verification device 100 proceeds to the communication key repetition step S698.
When the communication key deletion unit 155 determines that the communication key issuance number exceeds the maximum issuance number, the authority verification device 100 proceeds to the communication key deletion step S697.

  In the communication key deletion step S697, the communication key deletion unit 155 deletes the common key selected in the communication key selection step S695 from the common keys stored in the communication key storage unit 132 by using the CPU 911.

  In the communication key repetition step S698, the communication key deletion unit 155 returns to the communication key selection step S695 using the CPU 911 and selects the next common key.

In this example, the issue number is a serial number for all user identification data generated by the identification generation unit 123, but the issue number may be a serial number divided for each role.
In that case, the issue number counting unit 126 stores the issue number data in association with the role data using the magnetic disk device 920. The issue number counting unit 126 uses the CPU 911 to input the role data output from the role acquisition unit 121, and selects the issue number data associated with the input role data from the stored issue number data. 1 is added to the issue number represented by the selected issue number data, and the issue number data representing the added issue number is overwritten and stored in association with the input role data.
The communication key deletion unit 155 uses the CPU 911 to obtain the role data acquired based on the user identification data associated with the common key from the common keys stored in the communication key storage unit 132. 121 extracts a common key that is the same as the role data output from 121, and obtains the communication key issuance number data obtained based on the user identification data associated with the common key, and the issuance number counting unit. Based on the latest issue number data counted by 126, the number of issued communication keys is calculated, and the common key to be deleted is determined.

  Further, in this example, each time the identification generating unit 123 generates user identification data, the common key deleted by the communication key deleting unit 155 is extracted from the common keys stored in the communication key storage unit 132. Although the common key has been deleted, the communication key deletion unit 155 has sufficient processing capacity of the CPU 911 of the execution apparatus 200 periodically or when the identification reception unit 153 receives user identification data. In some cases, the common key deleted by the communication key deletion unit 155 may be extracted from the common keys stored in the communication key storage unit 132, and the common key may be deleted.

The authority verification device 100 in this embodiment further includes an issue number counting unit 126 and a communication key deleting unit 155.
Using the CPU 911, the issue number counting unit 126 counts issue numbers that increase when the identification acquisition unit (identification generation unit 123) acquires user identification data.
Using the CPU 911, the identification acquisition unit (identification generation unit 123) acquires the user identification data by generating user identification data based on the issue numbers counted by the issue number counting unit 126.
The communication key deletion unit 155 uses the CPU 911 to issue the issue number counted by the issue number counting unit 126 from the decryption key (common key) stored in the communication key storage unit 132 and the decryption key (common key). The decryption key (common key) having a difference from the issue number acquired based on the user identification data associated with the key is larger than a predetermined maximum issue number is deleted.

  According to the authority verification device 100 in this embodiment, since the identification acquisition unit (identification generation unit 123) generates user identification data based on the issue number counted by the issue number counting unit 126, the user identification data Can be avoided. In addition, since the communication key deletion unit 155 deletes the decryption key (common key) with the old issue number from the decryption keys (common key) stored in the communication key storage unit 132, the operation authority has been changed. For example, it is possible to prevent a user without operating authority from operating the target device 210.

The execution device 200 (device) described above is
A role request receiving unit (authority request receiving unit 111) for receiving role information (role data);
A random number generator 122 for generating a random number;
A count unit (issue number counting unit 126) that generates a count value (issue number);
ID information for generating ID information (user identification data) from identification information (target identification data) for identifying a device (execution device 200), role information (role data), a random number, and a count value (issue number) A generation unit (identification generation unit 123);
An encryption key generation unit (communication key generation unit 131) for generating an encryption key (common key) and a decryption key (common key);
Decryption key erasure unit (deletion of communication key) that erases the decryption key (common key) based on the count value (issue number) and the current count value (issue number) held by the count unit (issue number counter 126) Part 155),
An ID-based encryption unit (communication key encryption unit 133) that generates an encrypted encryption key (encrypted communication key) from the encryption key (common key) using ID information (user identification data);
An authority confirmation transmission unit (identification transmission unit 141 / encrypted communication key transmission unit 142) that transmits ID information (user identification data) and an encrypted encryption key (encrypted communication key) together as authority confirmation information;
An operation request receiving unit (encrypted operation request receiving unit 151) for receiving encrypted operation information (encrypted operation request);
A decryption unit (operation request decryption unit 152) that decrypts the operation information (operation request message) from the encrypted operation information using a decryption key (communication key);
Based on the correctly decrypted operation information (operation request message) and role information (role data), it is determined whether the operation is permitted as a role (role) according to the access control matrix (authorization data). An access control unit (operation request verification unit 162) that generates a result,
The operation is executed when access is permitted from the judgment result.

  The operation of the access control system 800 described above will be described in summary.

  First, in advance, the user device (user terminal device 300) holds a user secret key and a user public key in the public key cryptosystem. The device (execution device 200) has identification information (target identification data) for enabling identification with other devices (execution device 200), and an access control matrix (authority) indicating the relationship between roles (roles) and permitted operations. Corresponding data). The server (key generation device 400) includes signature verification information (public key certificate) for verifying signature information (signature data), user information (individual identification data), role information (role data), and identification information (target) Authentication information (role-corresponding data) indicating whether or not there is an access right corresponding to (identification data). This completes the preparation.

Then, the user device (user terminal device 300) starts processing.
A user determines a role (role) for operating the device (execution device 200), and a role request transmission unit (authority request transmission unit 322) transmits role information (role data) to the device (execution device 200).

Then, the device (execution device 200) starts processing.
The role request receiving unit (authorization request receiving unit 111) receives role information (role data) from the user device (user terminal device 300). Next, the random number generation unit 122 generates a random number. Next, the count unit (issue number counter 126) increments the previously generated count value (issue number) by one to generate a count value (issue number). Next, the ID information generation unit (identification generation unit 123) identifies identification information (target identification data) for identifying the device (execution device 200), role information (role data), a random number, and a count value (issue number). ID information (user identification data) is generated from the above. Next, the encryption key generation unit (communication key generation unit 131) generates an encryption key (common key) and a decryption key (common key). Next, the ID-based encryption unit (communication key encryption unit 133) encrypts the encrypted encryption key (encryption) using the ID information (user identification data) from the encryption key (common key) to be encrypted by the ID-based encryption. Communication key). Next, the authority confirmation transmission unit (identification transmission unit 141 / encrypted communication key transmission unit 142) combines the ID information (user identification data) and the encrypted encryption key (encrypted communication key) together with the authority confirmation information. To the user device (user terminal device 300).

Then, the user device (user terminal device 300) starts processing.
The authority confirmation receiving unit (terminal user identification receiving unit 331 / encrypted communication key receiving unit 332) receives authority confirmation information from the device (execution apparatus 200). Next, the signature unit (signature generation unit 343) generates signature information (signature data) from the ID information (user identification data) included in the authority confirmation information using the user secret key. Next, the issue request transmission unit (terminal user identification transmission unit 351 / signature transmission unit 352) performs user information including the user public key (individual identification data), ID information (user identification data), and signature information ( Together with the signature data), it is sent to the server (key generation device 400) as an issue request.

Then, the server (key generation device 400) starts processing.
The issue request receiving unit (generated user identification receiving unit 411 and signature receiving unit 412) receives the issue request from the user device (user terminal device 300). Next, the signature verification unit 423 verifies the signature information (signature data) included in the issue request with the signature verification information (public key certificate) and generates a verification result.
The signature verification unit 423 may use a user public key passed from the user device (user terminal device 300) to the server (key generation device 400) as a signature verification information by a secure method in advance. .
In addition, the server (key generation device 400) generates the user's private key and the user's public key in advance, and the user (user terminal device 300) transmits the user's user key to the user device (user terminal device 300) by a secure method. The secret key and the public key of the user may be passed.
Alternatively, the PKI certificate authority may issue a public key certificate to the user public key in advance, and the server (key generation device 400) may use the certificate authority public key certificate as signature verification information.

Next, when the verification result is correct, the access right authentication unit (right determination unit 434) is included in the role information (role data) included in the ID information included in the issue request and the ID information included in the issue request. Based on the identification information (target identification data) and the user information (individual identification data) included in the issuance request, the role (role) for the user device (execution device 200) according to the authentication information (role-corresponding data). As a result of authentication.
For example, the authority determining unit 434 first identifies a table representing the relationship between identification information (target identification data) and role information (role data) based on user information (individual identification data), and identifies information (target identification data). ) And role information (role data), the presence / absence of an access right is determined based on “○” and “×” in the corresponding part of the table.

  Next, the ID base secret key generation unit (secret key generation unit 441) generates an ID base secret key from the ID information (user identification data) when it is authenticated from the authentication result that there is an access right. Next, the secret key encryption unit (secret key encryption unit 442) generates an encrypted secret key (encrypted secret key) from the ID base secret key using the user public key included in the user information. Next, the secret key transmitting unit (encrypted secret key transmitting unit 451) transmits the encrypted secret key (encrypted secret key) to the user device (user terminal device 300).

Then, the user device (user terminal device 300) starts processing.
The secret key receiving unit (encrypted secret key receiving unit 361) receives the encrypted secret key (encrypted secret key). Next, the secret key decryption unit 362 decrypts the ID base secret key from the encrypted secret key (encrypted secret key) with the user secret key. Next, the ID-based decryption unit (communication key decryption unit 371) decrypts the encryption key (common key) from the encrypted encryption key (encrypted communication key) included in the authority confirmation information using the ID-based secret key. Next, the encryption unit (operation request encryption unit 382) generates encrypted operation information (encryption operation request) using an encryption key (common key) from operation information (operation request message) for the device (execution apparatus 200). . Next, the operation request transmission unit (encryption operation request transmission unit 383) transmits the encrypted operation information (encryption operation request) to the device (execution apparatus 200).

Then, the device (execution device 200) starts processing.
The operation request reception unit (encryption operation request reception unit 151) receives the encrypted operation information (encryption operation request). Next, the decryption key deletion unit (communication key deletion unit 155) counts based on the count value (issue number) and the current count value (issue number) held by the count unit (issue time acquisition unit 125). Check whether the immediacy of access right revocation is not impaired from the difference (number of communication keys issued), and if the immediacy is impaired, delete the decryption key (common key) and interrupt the subsequent processing To do.

Next, the decryption unit (operation request decryption unit 152) decrypts the operation information (operation request message) from the encrypted operation information (encryption operation request) using the decryption key (common key). Next, when the decryption unit (operation request decryption unit 152) correctly decrypts the operation information, the operation request verification unit 162 displays the correctly decrypted operation information (operation request message) and role information (role data). Based on the access control matrix (authority correspondence data), a determination result as to whether or not an operation is permitted as a role is generated.
For example, the operation request verification unit 162 determines whether or not the operation is permitted based on “O” and “X” in the corresponding part of the table from the operation (operation content data) and role information (role data). .
Next, the device (execution device 200) executes an operation when access is permitted based on the determination result.

  As described above, access control is realized.

  According to the access control system 800 described above, since the count value (issue number) is included in the ID information (user identification data), duplication with past IDs (user identification data) can be avoided. Also, the decryption key deletion unit (communication key deletion unit 155) counts based on the count value (issue number) and the current count value (issue number) held by the count unit (issue time acquisition unit 125). Check whether the immediacy of access right revocation is not impaired from the difference (number of communication keys issued), and if the immediacy is impaired, delete the decryption key (common key) and interrupt the subsequent processing Therefore, the use of the past decryption key (common key) by the user can be prevented.

1 is a system configuration diagram illustrating an example of an overall configuration of an access control system 800 according to Embodiment 1. FIG. 3 is a diagram illustrating an example of hardware resources of a key generation device 400, a user terminal device 300, and an execution device 200 according to Embodiment 1. FIG. 3 is a block configuration diagram illustrating an example of a functional block configuration of the key generation device 400 according to the first embodiment. The figure which represented typically an example of the role corresponding | compatible data 510 which the role memory | storage part 431 in Embodiment 1 has memorize | stored. FIG. 3 is a block configuration diagram illustrating an example of a functional block configuration of a user terminal device 300 according to the first embodiment. FIG. 3 is a block configuration diagram illustrating an example of a functional block configuration of the execution device 200 according to the first embodiment. 6 is a diagram schematically illustrating an example of authority correspondence data 520 stored in an authority storage unit 161 according to Embodiment 1. FIG. FIG. 6 is a flowchart showing an example of a flow of access control processing in which the access control system 800 according to Embodiment 1 controls the operation of the execution device 200 by a user. The block block diagram which shows an example of a structure of the functional block of the user terminal device 300 in Embodiment 2. FIG. FIG. 9 is a block configuration diagram illustrating an example of a functional block configuration of an execution apparatus 200 according to Embodiment 2. The flowchart figure which shows an example of the flow of operation request verification process S660 in which the authority verification apparatus 100 in Embodiment 2 verifies an encryption operation request. FIG. 10 is a block configuration diagram illustrating an example of a functional block configuration of an execution device 200 according to Embodiment 3. The flowchart figure which shows an example of the flow of operation request verification process S660 in which the authority verification apparatus 100 in Embodiment 3 verifies an encryption operation request. FIG. 10 is a block configuration diagram illustrating an example of a functional block configuration of an execution device 200 according to a fourth embodiment. The flowchart figure which shows an example of the flow of operation request verification process S660 in which the authority verification apparatus 100 in Embodiment 4 verifies an encryption operation request. FIG. 20 is a block configuration diagram illustrating an example of a functional block configuration of an execution device 200 according to a fifth embodiment. The flowchart figure which shows an example of the flow of communication key issue processing S620 in which the authority verification apparatus 100 in Embodiment 5 issues a common key.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 Authority verification apparatus, 111 Authority request receiving part, 121 Role acquisition part, 122 Random number generation part, 123 Identification generation part, 124 Identification storage part, 125 Issue time acquisition part, 126 Issue number counting part, 131 Communication key generation part, 132 Communication key storage unit, 133 communication key encryption unit, 141 identification transmission unit, 142 encrypted communication key transmission unit, 151 encryption operation request reception unit, 152 operation request decryption unit, 153 identification reception unit, 154 request time acquisition unit, 155 communication key deletion unit, 156 communication key selection unit, 157 operation count storage unit, 158 operation count count unit, 159 issue number acquisition unit, 161 authority storage unit, 162 operation request verification unit, 163 operation request notification unit, 164 operation history Storage unit, 165 operation number calculation unit, 166 deletion user identification unit, 200 execution device, 210 target device, 21 Operation request acquisition unit, 212 processing execution unit, 213 operation result generation unit, 214 operation result transmission unit, 300 user terminal device, 311 target input unit, 312 role input unit, 313 operation input unit, 321 authority request generation unit, 322 Authority request transmission unit, 331 terminal user identification reception unit, 332 encrypted communication key reception unit, 341 terminal user identification storage unit, 342 user secret key storage unit, 343 signature generation unit, 351 terminal user identification transmission unit, 352 Signature transmission unit, 361 Encrypted secret key reception unit, 362 Secret key decryption unit, 371 Communication key decryption unit, 372 Decryption communication key storage unit, 381 Operation request generation unit, 382 Operation request encryption unit, 383 Encryption operation request Transmission unit, 384 Request user identification transmission unit, 391 operation result reception unit, 392 result output unit, 400 key generation device, 411 User identification receiving unit, 412 Signature receiving unit, 421 Public key certificate storage unit, 422 Generation individual identification acquisition unit, 423 Signature verification unit, 431 Role storage unit, 432 Generation role acquisition unit, 433 Generation target identification acquisition unit, 434 Authority determination unit, 441 secret key generation unit, 442 secret key encryption unit, 451 encrypted secret key transmission unit, 510 role correspondence data, 511 individual identification data, 512 target identification data, 513, 521 role data, 520 authority correspondence Data, 522 Operation content data, 800 Access control system, 901 Display device, 902 Keyboard, 903 Mouse, 904 FDD, 905 CDD, 906 Printer device, 907 Scanner device, 910 System unit, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 Communication device, 920 magnetic disk device, 921 OS, 922 window system, 923 program group, 924 file group, 931 telephone, 932 facsimile machine, 940 Internet, 941 gateway, 942 LAN.

Claims (29)

In the authority verification device that verifies whether the user has the authority to operate the target device,
A processing device that processes data, a transmitting device that transmits data, a receiving device that receives data, an identification acquisition unit, a communication key generation unit, a communication key encryption unit, an encrypted communication key transmission unit, An encryption operation request reception unit, an operation request decryption unit, an operation request verification unit, and an operation request notification unit,
The identification acquisition unit acquires user identification data for identifying a user using the processing device,
The communication key generation unit generates an encryption key and a decryption key corresponding to the encryption key using the processing device,
The communication key encryption unit encrypts the encryption key generated by the communication key generation unit using the user identification data acquired by the identification acquisition unit using an ID-based encryption method using the processing device. Into an encrypted communication key,
The encrypted communication key transmission unit transmits the encrypted communication key encrypted by the communication key encryption unit using the transmission device,
The encrypted operation request receiving unit receives an encrypted operation request obtained by encrypting an operation request message representing an operation on the target device, using the receiving device,
The operation request decryption unit decrypts the encryption operation request received by the encryption operation request reception unit using the decryption key generated by the communication key generation unit using the processing device, and performs a decryption operation As a request,
The operation request verification unit determines whether or not the decryption operation request decrypted by the operation request decryption unit is correctly decrypted using the processing device. Judge that there is,
When the operation request verification unit determines that the operation authority has the operation authority using the processing device, the operation request notification unit sends the decryption operation request decrypted by the operation request decryption unit to the target device as an operation request message. An authority verification device characterized by notifying the user of the problem. The authority verification device further includes a role acquisition unit,
The role acquisition unit acquires role data representing the role of the user using the processing device,
The identification acquisition unit acquires the user identification data by generating user identification data based on the role data acquired by the role acquisition unit using the processing device,
The operation request verification unit determines whether the decryption operation request decrypted by the operation request decryption unit is correctly decrypted using the processing device. When the role represented by the role data acquired by the acquisition unit determines whether or not the role represented by the decryption operation request has the right to perform the operation, and when it is determined that the role has the right to perform the operation, the right to operate The authority verification device according to claim 1, wherein: The authority verification device further includes an issue time acquisition unit and a request time acquisition unit,
The issue time acquisition unit acquires issue time data representing the time when the identification acquisition unit acquires user identification data using the processing device,
The request time acquisition unit acquires request time data representing the time when the encryption operation request reception unit receives the encryption operation request using the processing device,
The expiration date determination unit uses the processing device to determine whether the expiration date is acquired based on the issue time data acquired by the issue time acquisition unit and the request time data acquired by the request time acquisition unit. Judgment,
The operation request decryption unit uses the decryption key generated by the communication key generation unit when the expiration date determination unit determines that the expiration date is within the expiration date using the processing device, and performs the encryption operation 3. The authority verification device according to claim 1, wherein the request receiving unit decrypts the encryption operation request received into a decryption operation request. The authority verification device further includes an operation count counter.
The operation number counting unit uses the processing device to count the number of times the operation request verification unit determines that there is an operation authority, and sets the number of operations,
The operation request decryption unit uses the decryption key generated by the communication key generation unit when the number of operations counted by the operation number counting unit is less than a predetermined maximum number of operations using the processing device. 4. The authority verification device according to claim 1, wherein the encryption operation request received by the encryption operation request receiving unit is decrypted to obtain a decryption operation request. The authority verification device further includes an identification transmission unit,
The authority verification apparatus according to claim 1, wherein the identification transmission unit transmits the user identification data acquired by the identification acquisition unit using the transmission device. The authority verification device further includes a current time acquisition unit,
The current time acquisition unit acquires current time data representing the current time using the processing device,
The identification acquisition unit acquires the user identification data by generating user identification data based on the current time data acquired by the current time acquisition unit using the processing device. The authority verification device according to claim 5. The authority verification device further includes a random number generation unit,
The random number generation unit generates a random number using the processing device,
The said identification acquisition part acquires the said user identification data by producing | generating user identification data based on the random number which the said random number generation part produced | generated using the said processing apparatus. The authority verification apparatus according to claim 5 or 6. The authority verification device further includes a storage device that stores data, a communication key storage unit, an identification reception unit, and a communication key selection unit,
The communication key storage unit stores the decryption key generated by the communication key generation unit in association with the user identification data acquired by the identification acquisition unit using the storage device,
The identification receiving unit receives the user identification data transmitted by the user terminal device together with the encryption operation request using the receiving device,
The communication key selection unit uses the processing device to select a decryption key associated with the user identification data received by the identification reception unit from among the decryption keys stored in the communication key storage unit,
The operation request decryption unit decrypts the encryption operation request received by the encryption operation request reception unit using the decryption key selected by the communication key selection unit using the processing device, and performs a decryption operation. The authority verification device according to claim 1, wherein the authority verification device is a request. The authority verification device further includes a communication key deletion unit,
The communication key deletion unit determines whether the decryption key stored in the communication key storage unit is valid or invalid using the processing device, and is invalid from among the decryption keys stored in the communication key storage unit. 9. The authority verification device according to claim 8, wherein the decryption key determined to be deleted is deleted. The authority verification device further includes an operation number calculation unit and a deletion user identification unit,
The operation number calculation unit calculates the number of user identification data of the user that the operation request verification unit determines to have the operation authority using the processing device, and sets the number of operations as an operation number.
The deletion user identification unit stores the communication key storage unit when the number of operations calculated by the operation number calculation unit exceeds the maximum number of users permitted to operate the target device using the processing device. From the user identification data associated with the decryption key, the user identification data to be deleted is identified as deletion identification data,
The communication key deletion unit deletes the decryption key associated with the deletion identification data specified by the deletion user specifying unit from the decryption keys stored in the communication key storage unit using the processing device. The authority verification device according to claim 9.   The authority verification device according to claim 10, wherein the operation number calculation unit calculates the number of operations for each role of a user using the processing device. In an execution device that executes processing based on an operation request from a user with operation authority,
12. An execution apparatus comprising: the authority verification apparatus according to claim 1; and a target apparatus that executes processing based on an operation request message notified by the authority verification apparatus. In the user terminal device that notifies the user of an operation request for the target device, to the right verification device that verifies whether the user has the right to operate the target device,
A processing device that processes data, a receiving device that receives data, a transmitting device that transmits data, a terminal user identification acquisition unit, a secret key acquisition unit, an encrypted communication key reception unit, and a communication key decryption unit And an operation request encryption unit and an encryption operation request transmission unit,
The terminal user identification acquisition unit uses the processing device to acquire user identification data for identifying a user,
The secret key acquisition unit acquires a secret key corresponding to the user identification data acquired by the terminal user identification acquisition unit in the ID-based encryption method using the processing device,
The encrypted communication key receiving unit receives, from the authority verification device, an encrypted communication key obtained by encrypting an encryption key used for encryption by an ID-based encryption method using the receiving device.
The communication key decryption unit uses the secret key acquired by the secret key acquisition unit by the ID-based encryption method using the processing device, and converts the encrypted communication key received by the encrypted communication key reception unit. Decrypt it as a decryption communication key,
The operation request encryption unit encrypts an operation request message representing an operation on the target device by the user by using the decryption communication key decrypted by the communication key decryption unit, using the processing device. Request
The encryption operation request transmission unit transmits an encryption operation request encrypted by the operation request encryption unit to the authority verification device using the transmission device. . The user terminal device further includes a terminal user identification transmission unit,
The terminal user identification transmission unit transmits the user identification data acquired by the terminal user identification acquisition unit to a key generation device that generates a secret key in an ID-based encryption method using the transmission device. ,
The user terminal device according to claim 13, wherein the secret key acquisition unit acquires the secret key by receiving the secret key generated by the key generation device using the reception device. . In a key generation device that generates a secret key in an ID-based encryption method,
A processing device that processes data, a receiving device that receives data, a transmitting device that transmits data, a generation user identification reception unit, an authority determination unit, a secret key generation unit, and a secret key transmission unit And
The generated user identification receiving unit receives user identification data for identifying a user using the receiving device,
The authority determination unit determines whether the user has the authority to operate the target device using the processing device,
When the authority determination unit determines that the user has the authority to operate the target device using the processing device, the secret user generation unit receives the generation user identification reception unit in an ID-based encryption method. Generate a secret key corresponding to the received user identification data,
The key generation device, wherein the secret key transmission unit transmits the secret key generated by the secret key generation unit using the transmission device. The key generation device further includes a generation role acquisition unit,
The generated user identification receiving unit receives user identification data including role data representing the role of the user using the receiving device,
The generation role acquisition unit acquires the role data based on the user identification data received by the generation user identification reception unit using the processing device,
The authority determination unit determines whether the user has a role represented by the role data with respect to the target device using the processing device, and the user has the role with respect to the target device. 16. The key generation apparatus according to claim 15, wherein when it is determined that the role represented by data is determined, the user is authorized to operate the target apparatus. The key generation device further includes a generation individual identification acquisition unit,
The generated user identification receiving unit receives user identification data including individual identification data for individually identifying the user, using the receiving device,
The generation individual identification acquisition unit acquires the individual identification data based on the user identification data received by the generation user identification reception unit using the processing device,
The authority determination unit determines whether the user individually identified by the individual identification data acquired by the generated individual identification acquisition unit has the authority to operate the target device using the processing device. The key generation apparatus according to claim 15 or 16, characterized by: The key generation device further includes a generation target identification acquisition unit,
The generation user identification receiving unit receives user identification data including target identification data for identifying the target device using the receiving device,
The generation target identification acquisition unit acquires the target identification data based on the user identification data received by the generation user identification reception unit using the processing device,
The authority determining unit determines whether the user has the authority to operate the target device identified by the target identification data acquired by the generation target identification acquiring unit, using the processing device. The key generation device according to any one of claims 15 to 17. In the access control system that controls the operation of the target device by the user,
An access control system comprising: the authority verification device according to any one of claims 1 to 11; and the user terminal device according to claim 13 or claim 14.   20. The access control system according to claim 19, further comprising the key generation device according to any one of claims 15 to 18.   A computer having a processing device for processing data, a transmitting device for transmitting data, and a receiving device for receiving data is caused to function as the authority verification device according to any one of claims 1 to 11. Computer program.   A computer program for causing a computer having a processing device for processing data, a transmitting device for transmitting data, and a receiving device for receiving data to function as the execution device according to claim 12.   A computer having a processing device for processing data, a transmitting device for transmitting data, and a receiving device for receiving data is caused to function as the user terminal device according to claim 13 or 14. Computer program.   A computer having a processing device for processing data, a transmitting device for transmitting data, and a receiving device for receiving data is caused to function as the key generation device according to any one of claims 15 to 18. A computer program.   A plurality of computers having a processing device for processing data, a transmitting device for transmitting data, and a receiving device for receiving data are caused to function as the access control system according to claim 19 or claim 20. Computer program. Authority verification method for verifying whether or not an authority verification apparatus having a processing apparatus for processing data, a transmission apparatus for transmitting data, and a reception apparatus for receiving data has the authority to operate the target apparatus In
The processing device acquires user identification data for identifying a user,
The processing device generates an encryption key and a decryption key corresponding to the encryption key,
The processing device encrypts the generated encryption key using the acquired user identification data by an ID-based encryption method to obtain an encrypted communication key,
The transmission device transmits an encrypted encrypted communication key,
The receiving device receives an encrypted operation request obtained by encrypting an operation request message representing an operation on the target device;
The above processing device uses the generated decryption key to decrypt the received encryption operation request as a decryption operation request,
The processing device determines whether or not the decrypted decryption operation request is correctly decrypted, and when it is determined that the decryption operation request is correctly decrypted, it is determined that there is an operation authority,
An authority verification method characterized in that, when the processing apparatus determines that an operation authority exists, the decryption operation request is notified to the target apparatus as an operation request message. Authority verification for verifying whether a user terminal apparatus having a processing apparatus for processing data, a receiving apparatus for receiving data, and a transmitting apparatus for transmitting data has the authority to operate the target apparatus In an operation request notification method for notifying an operation request for the target device by the user to the device,
The processing device acquires user identification data for identifying a user,
The processing device acquires a secret key corresponding to the acquired user identification data in the ID-based encryption method,
The receiving device receives an encrypted communication key obtained by encrypting an encryption key used for encryption by an ID-based encryption method from the authority verification device;
The above processing device uses the obtained secret key to decrypt the received encrypted communication key by the ID-based encryption method, and uses it as a decryption communication key.
The processing device uses the decrypted decryption communication key to encrypt an operation request message representing an operation on the target device by the user, and obtain an encryption operation request.
An operation request notification method, wherein the transmission device transmits an encrypted encryption operation request to the authority verification device. In a key generation method in which a key generation device including a processing device that processes data, a reception device that receives data, and a transmission device that transmits data generates a secret key in an ID-based encryption scheme,
The receiving device receives user identification data for identifying a user,
The processing device determines whether the user has authority to operate the target device,
When the processing device determines that the user has authority to operate the target device, the ID-based encryption method generates a secret key corresponding to the received user identification data,
A key generation method, wherein the transmission device transmits a generated secret key. In an access control method in which an access control system having an authority verification device and a user terminal device controls operation of a target device by a user,
The authority verification device acquires user identification data for identifying a user,
The authority verification device generates an encryption key and a decryption key corresponding to the encryption key,
The authority verification device encrypts the generated encryption key using the acquired user identification data by an ID-based encryption method to obtain an encrypted communication key,
The authority verification device sends an encrypted encrypted communication key,
The user terminal device acquires the user identification data,
The user terminal device acquires a secret key corresponding to the acquired user identification data in the ID-based encryption method,
The user terminal device receives the encrypted communication key transmitted by the authority verification device,
The user terminal device decrypts the received encrypted communication key using the acquired secret key by the ID-based encryption method, and uses it as a decryption communication key.
The user terminal device uses the decrypted decryption communication key to encrypt an operation request message representing an operation performed on the target device by the user, to obtain an encryption operation request,
The user terminal device transmits an encrypted encryption operation request to the authority verification device,
The authority verification device receives the encryption operation request transmitted by the user terminal device,
Using the generated decryption key, the authority verification device decrypts the received encryption operation request as a decryption operation request,
The authority verification device determines whether or not the decrypted decryption operation request is correctly decrypted. When it is determined that the decryption operation request is decrypted correctly, it is determined that the operation authority is present.
An access control method, wherein when the authority verification device determines that there is an operation authority, the decryption operation request is notified to the target device as an operation request message.

Images