KR102779052B1 - Entrance device management method - Google Patents

Abstract

According to one aspect of the present invention, an access device management method is provided, which comprises: a step of mutually authenticating the access device of the access device unit by using a public key infrastructure through an authentication device; a step of preparing encrypted communication by sharing a secret key generated by the authentication device or the access device with the authentication device and the access device; a step of encrypting and decrypting a program authentication key for authenticating a program installed in the access device with the secret key, so that the authentication device performs authentication for the program; and a step of generating a certificate based on the authentication for the program and transmitting it to the access device by the authentication device.

Description

{ENTRANCE DEVICE MANAGEMENT METHOD}

The present invention relates to a method for managing an access device.

Various systems are built and operated to manage the entry and exit of goods, vehicles, and people into specific spaces.

These systems consist of an authentication device and various access devices. The authentication device must perform authentication for the access devices included in the system, and communication must be established between the access devices.

Through this process, external hacking, unauthorized access, or tampering/forgery devices must be blocked.

Publication Patent No. 10-2023-0066694 (Publication Date: May 16, 2023)

The access device management method according to an embodiment of the present invention is to more safely protect the access control system against hacking from the outside, etc.

An access device management method according to an embodiment of the present invention is intended to provide control and management of entrants.

The subject matter of the present application is not limited to the subjects mentioned above, and other subjects not mentioned will be clearly understood by those skilled in the art from the description below.

According to one aspect of the present invention, an access device management method uses a public key infrastructure to allow an authentication device to manage an access device unit. According to one aspect of the present invention, an access device management method is provided, including: a step for mutually authenticating the authentication device and the access device of the access device unit using a public key and a private key; a step for preparing encrypted communication by sharing a secret key generated by the authentication device or the access device with the authentication device and the access device; a step for the authentication device and the access device to perform authentication of a program by encrypting and decrypting a program authentication key for authenticating a program installed in the access device with the secret key; and a step for the authentication device to generate a certificate based on the authentication of the program and transmit it to the access device.

In the mutual authentication step, the authentication device generates an authentication constant for an access device and transmits it to the access device, and the access device receives a digital signature for an access device generated by signing the authentication constant for the access device with the private key of the access device through a digital signature algorithm from the access device, and verifies the digital signature for the access device with the public key of the access device and the authentication constant for the access device through a digital signature verification algorithm to confirm success, thereby authenticating the access device, and the authentication device generates an authentication constant for the authentication device, and transmits a digital signature for the authentication device generated by signing the authentication constant for the authentication device with the private key of the authentication device through a digital signature algorithm and the authentication constant for the authentication device to the access device, and the access device verifies the digital signature for the authentication device with the public key of the authentication device and the authentication constant for the authentication device through a digital signature verification algorithm to confirm success, thereby authenticating the authentication device.

In the step of preparing the encrypted communication, the access device generates the secret key and encrypts the generated secret key with the public key of the authentication device to generate secret key encrypted data and transmits the same to the authentication device, and the authentication device decrypts the secret key encrypted data received from the access device with the private key of the authentication device and shares the secret key, or the authentication device generates the secret key and encrypts the generated secret key with the public key of the access device to generate secret key encrypted data and transmits the same to the access device, and the access device decrypts the secret key encrypted data received from the authentication device with the private key of the access device and shares the secret key, or the authentication device and the access device can share the secret key using a key exchange algorithm.

In the step of authenticating the above program, the authentication device generates a program authentication key, encrypts the program authentication key with the secret key and transmits it to the access device, the access device decrypts the encrypted program authentication key with the secret key, compares whether the decrypted program authentication key is identical to the program authentication key stored in the access device, and transmits the result value to the authentication device, and the authentication device can authenticate the program based on the result value.

The above certificate includes a public key of the authentication device, CA (Certificate Authority) information, owner information, a fingerprint, and a digital signature fingerprint, and the CA information includes one or more of the operating agency information of the authentication device, the person in charge information, the device identification information, and the address of the authentication device, and the owner information may include one or more of the public key of the access device, the access device identification information, the address of the access device, the access device authentication failure information, and the expiration date.

The above access device unit includes a first access device corresponding to the access device and a second access device corresponding to another access device, and a process for communicating between the first access device and the second access device using the certificate may include a step in which one of the first access device and the second access device requests the other certificate, a step in which the first access device verifies the certificate by checking whether the certificate received from the second access device has been manipulated, whether the certificate received from the second access device was generated by the authentication device, and whether the first access device and the second access device belong to the same authentication device group, a step in which a session is established between the first access device and the second access device when the certificate received from the second access device is verified, and a step in which the first access device and the second access device verify the established session.

The first access device generates a public key and CA (Certificate Authority) information of the authentication device, owner information, a fingerprint, and a digital signature fingerprint of the second access device using the certificate of the second access device received above, and in order to check whether the certificate received from the second access device has been tampered with, a new fingerprint of the second access device is generated using the public key and CA information of the authentication device and the owner information of the second access device, and it is possible to check whether the fingerprint generated with the certificate of the second access device and the newly generated fingerprint are the same.

The first access device generates a public key and CA (Certificate Authority) information of the authentication device, owner information, fingerprint, and digital signature fingerprint of the second access device using the certificate of the second access device received above, and verifies the digital signature fingerprint of the second access device with the fingerprint of the second access device and the public key of the authentication device according to a digital signature verification algorithm to confirm whether the certificate received from the second access device was generated by the authentication device, thereby confirming the success or failure.

The first access device generates a public key and CA (Certificate Authority) information of the authentication device with the received certificate of the second access device, and owner information, a fingerprint, and a digital signature fingerprint of the second access device, and determines whether the public key of the authentication device stored in the first access device and the public key generated with the certificate of the second access device are the same in order to confirm whether the first access device and the second access device belong to the same authentication device group, and confirms whether the CA information of the authentication device stored in the first access device and the CA information generated with the certificate of the second access device are the same.

In the step of establishing the session, the first access device transmits at least one of the components of the owner information of the second access device to the authentication device, and receives a session ID for communication between the first access device and the second access device, a secret key for encrypted communication between the first access device and the second access device, and the owner information of the second access device from the authentication device, and the second access device receives the session ID, the secret key for encrypted communication between the first access device and the second access device, and the owner information of the first access device from the authentication device, so that a session can be established between the first access device and the second access device.

In the step of verifying the session, the first access device and the second access device may include a session verification step of mutually transmitting the session ID received from the authentication device by encrypting it with a secret key received from the authentication device, and decrypting the mutually transmitted session ID with the secret key to confirm whether the mutually transmitted session ID is the same.

The first access device generates a public key and CA (Certificate Authority) information of the authentication device with the received certificate of the second access device, and owner information, a fingerprint, and a digital signature fingerprint of the second access device, and the authentication device of the session setup step receives at least one of the elements of the owner information of the second access device from the first access device, and acquires owner information of the second access device from an owner information group provided in the authentication device using at least one of the elements of the received owner information of the second access device, and transmits the acquired owner information to the first access device.

The first access device generates a public key and CA (Certificate Authority) information of the authentication device with the received certificate of the second access device, and the owner information, fingerprint, and digital signature fingerprint of the second access device, and the authentication device of the session setup step acquires the owner information of the second access device from an owner information group provided in the authentication device using at least one of the components of the owner information of the second access device received from the first access device and transmits the acquired owner information of the second access device to the first access device, and acquires the owner information of the first access device from the owner information group using session information between the authentication device and the first access device and transmits the acquired owner information of the first access device to the second access device, and the first access device compares the owner information generated from the certificate received from the second access device with the owner information of the second access device received from the authentication device to determine whether the second access device is not authenticated, and determines whether the second access device is forged or altered through the owner information of the second access device received from the authentication device, The second access device determines whether the first access device has been forged or altered through the owner information of the first access device received from the authentication device, and if the first access device determines whether forgery or alteration of the second access device has not occurred and whether it has not been authenticated, and if the second access device determines whether forgery or alteration of the first access device has not occurred, the first access device and the second access device can establish a session between each other.

The above first access device and the above second access device can perform communication only during the overlapping period among the valid periods of the first access device and the above second access device.

When the above authentication device and the access device are connected to the Internet through different lines, the connection port of the authentication device can be opened to communicate with the access device through the gateway by setting the gateway that manages the network to which the authentication device belongs.

According to another aspect of the present invention, the present invention comprises: a login step in which an access control server receives login information of an administrator; a device management step in which the access control server provides information on access devices according to an input device operation by an administrator; an access management step in which the access control server provides an access record of an entrant for each access device according to an input device operation by the administrator; and an access control step in which the access control server provides personal information about the entrant according to an input device operation by the administrator. In the device management step, the information about the access device includes a device ID, a firmware version, and network address information of the access device. In the access management step, the access record of the entrant includes an authentication date, an entrant ID, an entrant department, and an access device ID. In the access management step, personal information about the entrant includes an entrant ID, an entrant name, access authority, department, and position.

The access device management method according to an embodiment of the present invention can protect the access control system more safely against hacking from the outside, etc., by not only authenticating between the authentication device and the access device, but also authenticating the program installed in the access device by the authentication device.

The access device management method according to an embodiment of the present invention can efficiently provide control and management of entrants through a device management step, an access control step, and an access control step.

The effects of the present application are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

FIG. 1 illustrates an example of an access control system in which an access device management method according to an embodiment of the present invention can be implemented.
Figure 2 illustrates an access device management method according to an embodiment of the present invention.
Figure 3 shows a mutual authentication procedure between an authentication device and an access device.
Figures 4 and 5 illustrate a procedure for preparing encrypted communication between an authentication device and an access device.
Figures 6 and 7 are intended to explain the steps for authenticating a program.
Figure 8 shows the communication process between input/output devices.
Figure 9 shows the process of checking whether a certificate has been manipulated during certificate verification during the communication process between access devices.
Figure 10 shows a process for verifying whether a certificate was generated by an authentication device during a communication process between access devices.
Figure 11 shows a process for verifying whether a first access device and a second access device belong to the same authentication device group during certificate verification during a communication process between access devices.
Figure 12 is intended to explain the session setup process and session verification process.
Figure 13 shows the session setup process of the authentication device.

Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings. However, the attached drawings are only described to more easily disclose the contents of the present invention, and it will be readily apparent to those skilled in the art that the scope of the present invention is not limited to the scope of the attached drawings.

In addition, the terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise.

In this application, it should be understood that terms such as “include” or “have” are intended to specify the presence of a feature, number, step, operation, component, part or combination thereof described in the specification, but do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts or combinations thereof.

Figure 1 shows an example of an access control system in which an access control device management method according to an embodiment of the present invention can be implemented. The access control device management method according to an embodiment of the present invention relates to a method in which an authentication device (100) manages an access control device unit (200) using a public key infrastructure.

As illustrated in FIG. 1, the access device unit (200) includes an access device (210), and the access device (210) may be a reader such as an RF card reader or a biometric information reader (e.g., an iris scanner, a fingerprint scanner, a vein scanner, a facial scanner, etc.), an ACU (ACCESS CONTROL UNIT), an access control server, or may be another device.

The authentication device (100) can perform authentication, guarantee, forgery notification, etc. of the access device (200). The ACU relays communication between access devices (210) and can act as a temporary server when the access control server is down. The access control server can store a database required for the access management system.

The access device management method according to an embodiment of the present invention includes a step of mutually authenticating an authentication device (100) and an access device (210) of an access device unit (200) using a public key and a private key. That is, the authentication device (100) can authenticate an access device (210), and the access device (210) can authenticate the authentication device (100). By going through the process of mutually authenticating the authentication device (100) and the access device (210) in this way, the authentication device (100) can accurately identify an authenticated or unauthenticated access device (210).

The access device management method according to an embodiment of the present invention includes a step of preparing encrypted communication by having the authentication device (100) and the access device (210) share a secret key generated by the authentication device (100) or the access device (210). Accordingly, communication between the authentication device (100) and the access device (210) can be accomplished through the secret key.

Mutual authentication between the authentication device (100) and the access device (210) is performed based on PKI, i.e., asymmetric keys (public key, private key), and encrypted communication between the authentication device (100) and the access device (210) can be performed based on symmetric keys (secret keys).

The above-mentioned encrypted communication preparation step may be performed between the authentication of the access device (210) by the authentication device (100) and the authentication of the authentication device (100) by the access device (210), or may be performed after mutual authentication between the authentication device (100) and the access device (210).

The access device management method according to an embodiment of the present invention includes a step in which the authentication device (100) and the access device (210) perform authentication of a program by encrypting and decrypting a program authentication key for authenticating a program installed in the access device (210) with a secret key. A program (e.g., firmware, software, etc.) for the operation of the access device (210) may be installed in the access device (210). The program authentication key may be in the form of a hash value, and the hash value of the program authentication key may be encrypted and decrypted by a secret key.

The program authentication key may include at least one of a firmware type authentication key and a software type authentication key. The firmware type authentication key may be composed of one or more of a hash value, size, and version of the firmware, and an access device model name, serial number, and production date.

The software type authentication key may consist of one or more of the following: operating system type and version, access device software version and configuration file list, access device software configuration file name, hash value and size, and hardware unique information.

An access device management method according to an embodiment of the present invention includes a step in which an authentication device (100) generates a certificate based on authentication for a program and transmits the certificate to an access device (210).

The access device management method according to an embodiment of the present invention can protect the access control system more safely against hacking from the outside by not only authenticating the authentication device (100) and the access device (210) but also authenticating the program installed in the access device (210).

As illustrated in FIG. 3, in the mutual authentication step, the authentication device (100) can generate an authentication constant for an access device and transmit it to the access device (210). The authentication device (100) can store the generated authentication constant for an access device in the authentication device (100).

The authentication device (100) can receive, from the access device (210), a digital signature for the access device created by signing an authentication constant for the access device with the private key of the access device (210) through a digital signature algorithm.

The authentication device (100) can verify the digital signature for the access device (210) using the public key of the access device (210) and the authentication constant for the access device through a digital signature verification algorithm. The authentication device (100) can authenticate the access device (210) by checking whether the verification is successful.

In addition, as illustrated in FIG. 3, the authentication device (100) can generate an authentication constant for the authentication device. The authentication device (100) can store the generated authentication constant for the authentication device in the authentication device (100).

The authentication device (100) can transmit a digital signature for the authentication device and an authentication constant for the authentication device, which are created by signing the authentication constant for the authentication device with the private key of the authentication device (100) through a digital signature algorithm, to the access device (210).

The access device (210) can authenticate the authentication device (100) by verifying the digital signature for the authentication device using the public key of the authentication device (100) and the authentication constant for the authentication device through a digital signature verification algorithm and confirming whether the verification is successful.

The same digital signature algorithm and digital signature verification algorithm can be installed in both the authentication device and the access device. The digital signature algorithm and digital signature verification algorithm can be implemented in software or hardware.

Since the public key is disclosed to the authentication device (100) and the access device (210), before the access device (210) authenticates the authentication device (100), the access device (210) can receive and store the public key of the authentication device (100) from the authentication device (100).

In addition, since the public key and private key of the authentication device (100) perform digital signature and digital signature verification as a pair, the fact that the access device (210) successfully verifies the digital signature for the authentication device using the public key of the authentication device (100) and the authentication constant for the authentication device confirms that the digital signature for the authentication device was generated by the authentication device (100) and not by another external device.

By using the public key and private key of the authentication device (100), a digital signature and digital signature verification for the authentication constant for the authentication device are performed, so that the access device (210) can authenticate the authentication device (100).

The authentication constant for the access device and the authentication constant for the authentication device described above can be generated by the random number generator of the authentication device (100).

As described above, the successful creation and verification of a digital signature using the private key and public key of the authentication device (100) and the access device (210) confirms that each digital signature was created by the authentication device (100) and the access device (210), and thus the access device (210) and the authentication device (100) can authenticate each other.

That is, the authentication constant for the access device and the authentication constant for the authentication device can be signed with a private key according to a digital signature algorithm and verified with a public key and the authentication constant according to a digital signature verification algorithm.

As shown in Fig. 4, in the step of preparing encrypted communication, the access device (210) can generate a secret key. The access device (210) can encrypt the generated secret key with the public key of the authentication device (100) to generate secret key encryption data. The access device (210) can transmit the generated secret key encryption data to the authentication device (100).

The authentication device (100) can decrypt the secret key encryption data received from the access device (210) with the private key of the authentication device (100) and share the secret key.

Or, as illustrated in FIG. 5, in the step of preparing encrypted communication, the authentication device (100) can generate a secret key and encrypt the generated secret key with the public key of the access device (210) to generate secret key encrypted data.

The authentication device (100) can transmit the generated secret key encryption data to the access device (210). The access device (210) can decrypt the secret key encryption data received from the authentication device (100) with the private key of the access device (210) and share the secret key.

In this way, in the process of sharing a secret key, the access device (210) can share a secret key by encrypting the secret key with the public key of the authentication device (100) disclosed to the access device, or by encrypting the secret key with the public key of the access device (210) disclosed to the authentication device (100).

In addition, although not shown in the drawing, the authentication device (100) and the access device (210) can share a secret key using a key exchange algorithm. The key exchange algorithm includes the Diffie-Hellman algorithm, and the same key exchange algorithm can be installed in both the authentication device (100) and the access device (210).

As illustrated in FIG. 6, in the step of authenticating a program, the authentication device (100) can receive a program authentication key encrypted using a secret key from the access device (210) and decrypt it using the secret key.

The authentication device (100) searches for the program authentication key of the access device (210) from the program authentication key group stored in the authentication device (100), compares it with the decrypted program authentication key, and if they are the same, the program of the access device (210) can be authenticated.

In the previous example, the authentication device (100) determined whether the program authentication keys were identical, but as shown in FIG. 7, the access device (210) can also determine whether the program authentication keys were identical.

That is, the authentication device (100) can generate a program authentication key, encrypt the program authentication key with a secret key, and transmit it to the access device (210).

The access device (210) can decrypt an encrypted program authentication key with a secret key and transmit the result of comparing whether the decrypted program authentication key is identical to the program authentication key stored in the access device (210) to the authentication device (100). At this time, the result value can also be encrypted with a secret key and decrypted with the secret key in the authentication device (100).

The authentication device (100) can authenticate a program based on the result value. That is, the authentication device (100) can authenticate a program if the result value corresponds to the same program authentication key.

The certificate may include a public key and CA (Certificate Authority) information of the authentication device (100), owner information, a fingerprint, and a digital signature fingerprint. The digital signature fingerprint may be a fingerprint encrypted with the private key of the authentication device (100).

CA information may include one or more of the operating agency information of the authentication device (100), the person in charge information, the device identification information of the authentication device (100), and the address.

Owner information may include one or more of the public key of the access device (210), access device identification information, address of the access device (210), access device authentication failure information, and expiration date. The access device (210) may use a certificate received from the authentication device (100) for communication between access devices.

Next, the communication between the access devices is explained with reference to the drawings.

The access device unit (200) may include a first access device (210) corresponding to an access device (210) and a second access device (220) corresponding to another access device (220). The process of the authentication device (100) transmitting a certificate to the first access device (210) through the authentication procedure of the authentication device (100) and the first access device (210) has been described above. The second access device (220) may also receive a certificate in the same manner through communication with the authentication device (100).

The process of communicating between the first access device (210) and the second access device (220) using a certificate (hereinafter, the device-to-device communication process) may include a step in which one of the first access device (210) and the second access device (220) requests the certificate of the other. That is, the first access device (210) may request the certificate of the second access device (220) from the second access device (220), the second access device (220) may request the certificate of the first access device (210) from the first access device (210), or the first access device (210) and the second access device (220) may request each other's certificate.

The device-to-device communication process may include a step of verifying a certificate by checking whether the certificate received from the second access device (220) has been manipulated by the first access device (210), whether the certificate received from the second access device (220) was generated by the authentication device (100), and whether the first access device (210) and the second access device (220) belong to the same authentication device group.

The device-to-device communication process includes a step of establishing a session between the first access device (210) and the second access device (220) when a certificate received from the second access device (220) is verified.

Additionally, the device-to-device communication process includes a step of verifying the session established between the first access device (210) and the second access device (220).

Even when the second access device (220) requests a certificate, the certificate can be verified through the same process as verifying the certificate when the first access device (210) requests the certificate.

In addition, when the first access device (210) and the second access device (220) mutually authenticate each other's certificates, the certificates can be verified through the same process.

When communication between access devices is made through a certificate, the authentication device (100) can record and check the connection history between the first access device (210) and the second access device (220).

Hereinafter, as illustrated in FIG. 8, the communication process between the first access device (210) and the second access device (220) will be described in more detail, with the first access device (210) requesting a certificate from the second access device (220).

As illustrated in FIG. 9, the first access device (210) can generate the public key and CA (Certificate Authority) information of the authentication device (100) using the certificate of the second access device (220) received, as well as the owner information, fingerprint, and digital signature fingerprint of the second access device (220).

The first access device (210) can newly generate a fingerprint of the second access device (220) using the public key and CA information of the authentication device (100) and the owner information of the second access device (220) to check whether the certificate received from the second access device (220) has been manipulated.

The first access device (210) can verify whether the fingerprint generated with the certificate of the second access device (220) and the newly generated fingerprint are the same.

If the fingerprint generated with the certificate of the second access device (220) and the newly generated fingerprint are the same, the first access device (210) can confirm that the certificate received from the second access device (220) has not been tampered with.

As described above, the first access device (210) can generate the public key and CA (Certificate Authority) information of the authentication device (100) using the certificate of the second access device (220) received, as well as the owner information, fingerprint, and digital signature fingerprint of the second access device (220).

As shown in Fig. 10, the first access device (210) can verify whether the certificate received from the second access device (220) was generated by the authentication device (100) by verifying the digital signature fingerprint of the second access device (220) with the fingerprint of the second access device (220) and the public key of the authentication device (100) according to the digital signature verification algorithm, thereby confirming whether the verification was successful.

If the above verification is successful, the first access device (210) can confirm that the certificate received from the second access device (220) was generated by the authentication device (100).

As before, the first access device (210) can generate the public key and CA (Certificate Authority) information of the authentication device (100) using the certificate of the second access device (220) received, as well as the owner information, fingerprint, and digital signature fingerprint of the second access device (220).

As illustrated in FIG. 11, the first access device (210) can determine whether the public key of the authentication device (100) stored in the first access device (210) and the public key generated by the certificate of the second access device (220) are the same in order to confirm whether the first access device (210) and the second access device (220) belong to the same authentication device group.

In addition, the first access device (210) can verify whether the CA information of the authentication device (100) stored in the first access device (210) and the CA information generated by the certificate of the second access device (220) are the same.

The first access device (210) can determine that the first access device (210) and the second access device (220) belong to the same authentication device group if the public key and CA information are the same. In other words, the first access device (210) can determine that the first access device (210) and the second access device (220) are managed by the same authentication device (100).

Next, the session setup process described with reference to Fig. 8 is described in more detail.

As illustrated in FIG. 12, in the step of establishing a session, the first access device (210) may transmit one or more of the components of the owner information of the second access device (220) to the authentication device (100).

Owner information can be derived through the certificate of the second access device (220) received from the second access device (220), as explained above through FIG. 8.

The first access device (210) can receive a session ID for communication between the first access device (210) and the second access device (220), a secret key for encrypted communication between the first access device (210) and the second access device (220), and owner information of the second access device (220) from the authentication device (100).

The owner information described above through FIGS. 9 to 11 is information included in the certificate of the second access device (220) transmitted from the second access device (220), and the owner information of FIG. 12 may be received from the authentication device (100).

In addition, the secret key described with reference to FIG. 2 is for communication between the authentication device (100) and the first access device (210), and the secret key in FIG. 12 is for communication between the first access device (210) and the second access device (220), and the authentication device (100) can transmit to both the first access device (210) and the second access device (220). At this time, the same secret key or different secret keys can be used for communication between the authentication device (100)/the first access device (210) and between the first access device (210)/the second access device (220).

The second access device (220) receives a session ID, a secret key for encrypted communication between the first access device (210) and the second access device (220), and the owner information of the first access device from the authentication device (100), so that a session can be established between the first access device (210) and the second access device (220).

In the step of verifying a session, as illustrated in FIG. 12, the first access device (210) and the second access device (220) can perform session verification by encrypting the session ID received from the authentication device (100) with a secret key received from the authentication device (100) and transmitting the encrypted session ID to each other, decrypting the encrypted session ID with the secret key, and confirming whether the encrypted session IDs are the same.

As explained above through FIGS. 9 to 11, the first access device (210) can generate the public key and CA (Certificate Authority) information of the authentication device (100) using the certificate of the second access device (220) received, as well as the owner information, fingerprint, and digital signature fingerprint of the second access device (220).

As illustrated in FIGS. 12 and 13, the authentication device (100) in the session setup step can receive one or more of the components of the owner information of the second access device (220) from the first access device (210).

As illustrated in FIG. 13, the authentication device (100) can acquire the owner information of the second access device (220) from the owner information group provided in the authentication device (100) by using one or more of the components of the owner information of the received second access device (220) and transmit it to the first access device (210).

For example, the authentication device (100) can determine whether the public key of the second access device (220) and the access device identification information of the second access device (220) among the received owner information of the second access device (220) are identical to the public key of the second access device (220) and the access device identification information of the second access device (220) among the acquired owner information of the second access device (220). Through this, the authentication device (100) can check for falsification of the owner information of the second access device (220).

As explained through FIGS. 9 to 11, the first access device (210) can generate the public key and CA (Certificate Authority) information of the authentication device (100) using the certificate of the second access device (220) received, as well as the owner information, fingerprint, and digital signature fingerprint of the second access device (220).

In addition, as explained through FIG. 13, the authentication device (100) in the session setup step can obtain the owner information of the second access device (220) from the owner information group provided in the authentication device (100) by using one or more of the components of the owner information of the second access device (220) received from the first access device (210). The authentication device (100) can transmit the obtained owner information of the second access device (220) to the first access device (210).

The authentication device (100) can obtain the owner information of the first access device (210) from the owner information group using the session information between the authentication device (100) and the first access device (210) and transmit the obtained owner information of the first access device (210) to the second access device (220).

Session information is information allocated for communication with the first access device (210) during the process of authenticating the first access device (210) by the authentication device (100) or after authentication, and may be different from the session ID for communication between the first access device (210) and the second access device (220).

The first access device (210) can compare the owner information generated from the certificate received from the second access device (220) with the owner information of the second access device (220) received from the authentication device (100) to determine whether the second access device (220) is not authenticated. That is, the first access device (210) can determine that the two devices are normal if they match, and can determine that the two devices are not authenticated if they do not match.

The first access device (210) can determine whether the second access device (220) has been forged or altered through the owner information of the second access device (220) received from the authentication device (100). That is, the first access device (210) trusts the owner information of the second access device (220) received from the authentication device (100), and if the forgery and alteration information in the owner information of the second access device (220) received from the authentication device (100) includes the content that there is no forgery or alteration, it can determine that there is no forgery or alteration of the second access device (210).

In addition, the second access device (220) can determine whether the first access device (210) has been forged or altered through the owner information of the first access device (210) received from the authentication device (100). That is, the second access device (220) trusts the owner information of the first access device (210) received from the authentication device (100), and if the forgery and alteration information in the owner information of the first access device (210) received from the authentication device (100) includes the content that there is no forgery or alteration, it can determine that there is no forgery/alteration of the first access device (210).

When the first access device (210) determines whether the second access device (220) has been forged or tampered with and whether it has not been authenticated, and when the second access device (220) determines whether the first access device (210) has been forged or tampered with, the first access device (210) and the second access device (220) can establish a session with each other.

The authentication device (100) searches for the owner information of the first access device (210) in the owner information group of the authentication device (100) using session information with the first access device (210), and searches for the owner information of the second access device (220) in the owner information group of the authentication device (100) using at least one of the owner information components of the second access device (220) sent by the first access device (210), thereby enabling the authentication device (100) to check whether the first access device (210) and the second access device (220) have been forged or altered.

The access device authentication failure information may be one of the components of the owner information of the first access device (210) and the second access device (220) acquired by searching the owner information group of the authentication device (100), and may include information on whether the first access device (210) and the second access device (220) were normally authenticated by the authentication device (100).

In addition, the authentication device (100) can compare whether the address of the second access device (220) included in the owner information of the second access device (220) transmitted from the first access device (210) and the address of the second access device (220) included in the owner information of the second access device (220) acquired from the owner information group of the authentication device (100) are the same, thereby confirming whether the address of the second access device (220) has been changed without authorization.

The first access device (210) and the second access device (220) can perform communication only during the overlapping period of the validity periods of the first access device (210) and the second access device (220). For example, if the validity period of the first access device (210) is from January 1, 2024 to December 31, 2024 and the validity period of the second access device (220) is from July 1, 2024 to June 30, 2025, the overlapping period of the first access device (210) and the second access device (220) can be from July 1, 2024 to December 31, 2024.

The validity period of the first access device (210) and the second access device (220) may be included in the owner information on the certificate of the first access device (210) and the second access device (220) held by the authentication device (100).

Communication between the first access device (210) and the second access device (220) can be made only when the current time to communicate is included in the overlapping period, and communication may not be made if the current time is outside the overlapping period.

The authentication device (100) and the access device (210) can connect to the Internet through different lines. For example, the authentication device (100) and the access device (210) can each connect to the networks of different Internet service providers, or connect to the Internet through different lines of the same Internet service provider.

By setting up a gateway that controls the network to which the authentication device (100) belongs, the connection port of the authentication device (100) can be opened to communicate with the access device (210) via the gateway.

The authentication device (100) and the access device (210) can communicate with each other via the gateway. However, if they communicate via different lines, communication between the authentication device (100) and the access device (210) may not occur. The gateway can enable communication between the authentication device (100) and the access device (210) by setting the connection port of the authentication device (100) to be open to different lines outside the gateway.

A gateway may be a separate device from a router or shared router, or a router or shared router may perform the gateway function.

According to another embodiment of the present invention, an access device management method includes a login step in which an access control server receives login information of an administrator, a device management step in which the access control server provides information on an access device according to an input device operation by an administrator, an access management step in which the access control server provides an access record of an entrant for each access device according to an input device operation by an administrator, and an access user management step in which the access control server provides personal information on an entrant according to an input device operation by an administrator.

The administrator's input device may be a keyboard, mouse, touch screen, or stylus pen, but the present invention is not limited thereto.

At this time, in the device management stage, information about the access device may include the device ID, firmware version, and network address information of the access device.

At the entry control stage, the entry/exit record of an entrant may include the authentication date, entrant ID, entrant's department, and entry/exit device ID.

In the access control stage, personal information about entrants may include the entrant ID, entrant's name, access rights, department, and position.

As described above, the embodiments according to the present invention have been examined, and it is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the spirit or scope thereof in addition to the embodiments described above. Therefore, the above-described embodiments should be considered as illustrative rather than restrictive, and accordingly, the present invention is not limited to the above description, but may be modified within the scope of the appended claims and their equivalents.

Authentication device (100)
Entry/Exit Device Department (200)
Entry device, 1st entry device (210)
2nd Entry Device (220)

Claims (17)

In a method for managing access devices using a public key infrastructure, an authentication device manages an access device section.
A step for mutually authenticating the authentication device and the access device of the access device unit using a public key and a private key;
A step of preparing encrypted communication by sharing a secret key generated by the authentication device or the access device between the authentication device and the access device;
The authentication device and the access device perform a step of authenticating the program by encrypting and decrypting the program authentication key for authenticating the program installed in the access device with the secret key; and
The above authentication device comprises a step of generating a certificate based on authentication for the above program and transmitting it to the access device,
In the above mutual authentication step
The above authentication device
An authentication constant for an access device is generated and transmitted to the access device, and the access device receives a digital signature for the access device generated by signing the authentication constant for the access device with the private key of the access device through a digital signature algorithm, and verifies the digital signature for the access device with the public key of the access device and the authentication constant for the access device through a digital signature verification algorithm to confirm success, thereby authenticating the access device.
The above authentication device
Generate an authentication constant for an authentication device, sign the authentication constant for the authentication device with the private key of the authentication device through a digital signature algorithm, and transmit the digital signature for the authentication device and the authentication constant for the authentication device to the access device.
The above entry/exit device
An access control method characterized in that the authentication device is authenticated by verifying the digital signature for the authentication device using the public key of the authentication device and the authentication constant for the authentication device through a digital signature verification algorithm to confirm success. delete In the first paragraph,
In the step of preparing the above encrypted communication,
The above access device generates the secret key and encrypts the generated secret key with the public key of the authentication device to generate secret key encrypted data and transmits it to the authentication device, and the authentication device decrypts the secret key encrypted data received from the access device with the private key of the authentication device to share the secret key, or
Or, the authentication device generates the secret key and encrypts the generated secret key with the public key of the access device to generate secret key encrypted data and transmits it to the access device, and the access device decrypts the secret key encrypted data received from the authentication device with the private key of the access device to share the secret key, or
Or, an access device management method characterized in that the authentication device and the access device share a secret key using a key exchange algorithm. In the first paragraph,
At the stage of authenticating the above program,
An access device management method characterized in that the authentication device receives an encrypted program authentication key from the access device through the secret key, decrypts it with the secret key, searches for the program authentication key of the access device from the program authentication key group stored in the authentication device, and then authenticates the program of the access device by confirming whether it is identical to the decrypted program authentication key. In the first paragraph,
At the stage of authenticating the above program,
The above authentication device generates a program authentication key, encrypts the program authentication key with the secret key, and transmits it to the access device.
The above access device decrypts the encrypted program authentication key with the secret key, compares whether the decrypted program authentication key is identical to the program authentication key stored in the above access device, and transmits the result to the authentication device.
An access device management method characterized in that the above authentication device authenticates the above program according to the above result value. In the first paragraph,
The above certificate includes the public key of the authentication device, CA (Certificate Authority) information, owner information, fingerprint, and digital signature fingerprint.
The above CA information includes at least one of the operating agency information, person in charge information, device identification information, and address of the above authentication device.
An access device management method, characterized in that the above owner information includes at least one of the public key of the access device, access device identification information, the address of the access device, access device authentication failure information, and the expiration date. In Article 6,
The above entry/exit device section includes a first entry/exit device corresponding to the above entry/exit device and a second entry/exit device corresponding to another entry/exit device.
The process of communication between the first access device and the second access device using the above certificate is as follows:
A step in which one of the first entry/exit device and the second entry/exit device requests another certificate;
A step of verifying the certificate by checking whether the first access device has manipulated the certificate received from the second access device, whether the certificate received from the second access device was generated by the authentication device, and whether the first access device and the second access device belong to the same authentication device group.
A step of establishing a session between the first access device and the second access device when the certificate received from the second access device is verified, and
An access device management method, characterized in that it includes a step of verifying the established session by the first access device and the second access device. In Article 7,
The above first entry/exit device
Generate the public key and CA (Certificate Authority) information of the authentication device, the owner information, fingerprint, and digital signature fingerprint of the second access device using the certificate of the second access device received above,
An access device management method characterized in that, in order to verify whether a certificate received from the second access device has been manipulated, a new fingerprint of the second access device is generated using the public key and CA information of the authentication device and the owner information of the second access device, and it is verified whether the fingerprint generated using the certificate of the second access device and the newly generated fingerprint are the same. In Article 7,
The above first entry/exit device
Generate the public key and CA (Certificate Authority) information of the authentication device, the owner information, fingerprint, and digital signature fingerprint of the second access device using the certificate of the second access device received above,
An access device management method characterized in that the digital signature fingerprint of the second access device is verified using the fingerprint of the second access device and the public key of the authentication device according to a digital signature verification algorithm to confirm whether the certificate received from the second access device was generated by the authentication device, and the success or failure is confirmed. In Article 7,
The above first entry/exit device
Generate the public key and CA (Certificate Authority) information of the authentication device, the owner information, fingerprint, and digital signature fingerprint of the second access device using the certificate of the second access device received above,
An access device management method characterized in that it is determined whether the public key of the authentication device stored in the first access device and the public key generated by the certificate of the second access device are the same in order to confirm whether the first access device and the second access device belong to the same authentication device group, and it is confirmed whether the CA information of the authentication device stored in the first access device and the CA information generated by the certificate of the second access device are the same. In Article 7,
In the step of setting up the above session,
The above first entry/exit device
Transmitting at least one component of the owner information of the second access device to the authentication device,
A session ID for communication between the first access device and the second access device, a secret key for encrypted communication between the first access device and the second access device, and owner information of the second access device are received from the authentication device,
The above second entry/exit device
An access device management method characterized in that a session is established between the first access device and the second access device by receiving the session ID, a secret key for encrypted communication between the first access device and the second access device, and owner information of the first access device from the authentication device. In Article 11,
In the step of verifying the above session,
The above first entry/exit device and the above second entry/exit device
An access device management method characterized by including a session verification step of encrypting the session ID received from the authentication device with a secret key received from the authentication device and transmitting it to each other, and decrypting the mutually transmitted session ID with the secret key to confirm whether the mutually transmitted session ID is the same. In clause 7 or 11,
The above first entry/exit device
Generate the public key and CA (Certificate Authority) information of the authentication device, the owner information, fingerprint, and digital signature fingerprint of the second access device using the certificate of the second access device received above,
The above authentication device in the above session setup step
Receiving at least one component of the owner information of the second access device from the first access device,
An access device management method characterized in that the owner information of the second access device is acquired from the owner information group provided in the authentication device by using at least one of the components of the owner information of the second access device received, and the owner information is transmitted to the first access device. In Article 11,
The above first entry/exit device
Generate the public key and CA (Certificate Authority) information of the authentication device, the owner information, fingerprint, and digital signature fingerprint of the second access device using the certificate of the second access device received above,
The above authentication device in the above session setup step
By using at least one component of the owner information of the second access device received from the first access device, the owner information of the second access device is acquired from the owner information group provided in the authentication device, and the acquired owner information of the second access device is transmitted to the first access device.
By using the session information between the above authentication device and the first access device, the owner information of the first access device is acquired from the owner information group, and the acquired owner information of the first access device is transmitted to the second access device.
The first access device determines whether the second access device is not authenticated by comparing the owner information generated from the certificate received from the second access device with the owner information of the second access device received from the authentication device, and determines whether the second access device is forged or altered through the owner information of the second access device received from the authentication device.
The second access device determines whether the first access device is forged or altered through the owner information of the first access device received from the authentication device.
An access device management method characterized in that when the first access device determines whether forgery or alteration of the second access device has occurred and whether it has not been authenticated, and when the second access device determines whether forgery or alteration of the first access device has occurred, the first access device and the second access device establish a session with each other. In Article 7,
An access device management method, characterized in that the first access device and the second access device perform communication only during an overlapping period among the valid periods of the first access device and the second access device. In the first paragraph,
When the above authentication device and the above access device connect to the Internet through different lines,
An access device management method characterized in that the access port of the authentication device is opened to communicate with the access device via the gateway by setting a gateway that governs the network to which the authentication device belongs. delete