KR20180056351A - Component for provisioning of security data and product including the same - Google Patents

Abstract

According to an exemplary embodiment of the present disclosure, a security component for safely provisioning security information protected from external inappropriate access into a product comprises: a user authentication processor performing authentication of input data by determining whether the input data is provided by a legitimate user of component user data included in the input data; a master key generator generating a master key based on the authenticated component user data of the authenticated input data; a decryption processor generating security data by decrypting encrypted data included in the authenticated input data based on the master key; and a security storage storing the security data.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a component for injecting security information,

Technical aspects of the present disclosure relate to injection of security information, and more particularly, to a component for injection of security information and a product including the same.

Security information that must be protected from external inappropriate access can be included in products in a variety of ways. For example, a part user may receive a part containing security information from a parts supplier, or may inject security information into a part or a product containing parts at the production stage of the product. While the former method can securely incorporate security information into the product, exposure of the security information to the component supplier is inevitable, and it may not be easy to change the security information due to changes in the use environment of the component. In addition, while the latter method can easily change the security information, the protection of the security information against improper access from the outside of the product due to the interface for injecting the security information may be weak.

The technical idea of the present disclosure provides a method of injecting parts and security information contained in a product to safely inject security information protected from external inappropriate access into the product.

According to an aspect of the technical idea of the present disclosure, a security component included in a product and processing input data for authenticating a product includes an input unit for inputting, based on the component user data included in the input data, A master key generator for generating a master key based on authenticated part user data of authenticated input data, a master key generator for generating a master key based on the authenticated part user data of the authenticated input data, A decryption processor for generating secure data by decrypting the encrypted data included in the authenticated input data based on the encrypted input data, and a secure storage for storing secure data.

According to one aspect of the technical idea of the present disclosure, a product that responds to a product certification request from the outside based on security data stored therein stores input data including encrypted data and parts user data from outside the product Generating security data by decrypting authenticated encrypted data of authenticated input data based on authenticated part user data of authenticated input data, And may include security components that store security data.

According to the parts and method for injecting security information according to the technical idea of the present disclosure, security information can be safely injected into a product including the part under the control of the part user.

Further, according to the parts and method for injecting security information according to the technical idea of the present disclosure, since the security information can be easily changed, the utilization of the product including the parts by the part user can be remarkably improved.

Further, according to the parts and method for injecting security information according to the technical idea of the present disclosure, the production of the parts including the preliminary security information is prevented, so that the productivity of the parts by the parts supplier can be remarkably improved.

1 is a block diagram that schematically illustrates a product and peripheral systems including security information in accordance with an exemplary embodiment of the present disclosure.
Figure 2 is a diagram showing the input data of Figure 1 in accordance with an exemplary embodiment of the present disclosure.
Figure 3 is a block diagram illustrating an example of the security component of Figure 1 in accordance with an exemplary embodiment of the present disclosure.
4 is a flow diagram illustrating exemplary operation of the user authentication processor of FIG. 3 in accordance with an exemplary embodiment of the present disclosure.
5 is a block diagram illustrating an example of the security component of FIG. 1 in accordance with an exemplary embodiment of the present disclosure.
6 is a diagram illustrating input data according to an exemplary embodiment of the present disclosure;
FIG. 7 is a flow diagram illustrating exemplary operation of the security component of FIG. 1 receiving input data of FIG. 6 in accordance with an exemplary embodiment of the present disclosure.
8 is a diagram showing, in accordance with time, an operation for injecting security information into a security component according to an exemplary embodiment of the present disclosure;
9 is a flow diagram illustrating a method for injecting security information in accordance with an exemplary embodiment of the present disclosure.
Figure 10 is a block diagram illustrating an example of the product of Figure 1 in accordance with an exemplary embodiment of the present disclosure.
11 is a block diagram illustrating an exemplary structure of hardware and software of the IoT device of FIG. 10 in accordance with an exemplary embodiment of the present disclosure.
12 is a diagram illustrating a network system in which a product including a security component according to an exemplary embodiment of the present disclosure is used.

1 is a block diagram that schematically illustrates a product 100 and peripheral systems 200, 300 that include security information in accordance with an exemplary embodiment of the present disclosure. 1, product 100 may communicate with data injection system 200 and authentication system 300 and may include a communication interface 110, a security component 120 and an authentication request processor 130 . Each of the communication interface 110, the security component 120 and the authentication request processor 130 may include logic blocks designed through logic synthesis or the like and may be executed by a processor ≪ / RTI >

The product (product) 100 may respond to an external request, e.g., an authentication request (A_REQ), based on security information as an entity including security information. For example, the product 100 may be an independent computing device such as a personal computer, a network server, a tablet PC, an e-reader, a personal digital assistant (PDA), a portable multimedia player (PMP), a mobile phone, a smart phone, Or any object that provides a specific function, such as an automobile, a mechanical device, a manufacturing facility, a door, an illumination, and the like.

The product 100 may communicate with other devices, such as the data injection system 200, the authentication system 300, or other products, such as the product 100, via the communication interface 110 included in the product 100. For example, the product 100 may communicate with a mobile communication device 110, such as a long term evolution (LTE) system, a code division multiple access (CDMA) system, a global system for mobile communications (GSM) telecommunication system or may be connected to a communication network such as a wide area network (WAN), a local area network (LAN), a wireless local area network (WLAN), or the like to access the Internet of Things have. The communication interface 110 may support one or more communication schemes, e.g., the data injection system 200 and the authentication system 300 in FIG. 1 may communicate with the product 100 through the same or different communication schemes.

The security information may include personal information about the user of the product 100 and may include an identifier (ID) of the product 100, supplier information of the product 100, proof information certificate, a private key, and a pre-shared key (PSK). Information for authentication of the product 100 included in the security information can be used for operations requiring authentication of the product 100, such as, for example, remote operation of the product 100, software upgrade, etc. as a non-limiting example . For example, when the product 100 accesses the object Internet through the communication interface 110, the information acquired by the product 100 itself is transmitted through the communication interface 110 or through the communication interface 110, The trustworthiness of the information received from the product 100 may be based on the authentication of the product 100. Accordingly, in order to prevent the security information from being exposed, deleted or changed due to unjustified attempts, the security information needs to be safely protected from improper access from outside the product 100.

The security information may be included in the security component 120 included in the product 100. For example, the security component 120 may include components capable of storing data, such as semiconductor memory devices, and security information may be stored in such components included in the security component 120. When security information is injected into the security part 120 at the production stage of the security part 120 in order to include the security information in the security part 120, The productivity of the security component 120 by the supplier of the security component 120 can be reduced as well as the utilization efficiency is reduced. For example, if the product 100 needs to be supplied to suit various usage environments, such as when the product 100 is connected to the Internet via the communication interface 110, The utilization of the security component 120 by the user (or the supplier or producer of the product 100) of the security component 120 may be reduced due to the fact that the modification of the included security information is not easy. In addition, the production efficiency of the security component 120 by the supplier (or producer) of the security component 120 decreases due to the process for injecting the security information and the preparation of the preliminarily injected security component 120 . As described below, according to the security component 120 and the method of injecting security information in accordance with the exemplary embodiments of the present disclosure, the security information is securely delivered to the security component 120 (i. E., The security component 120) And thus both the user and the supplier of the security component 120 may be advantageous. A user of the security component 120 may include a supplier and / or producer of the product 100 that supplies the product 100 using the security component 120 and may include a security component 120 (E.g., customizing) the product 100 that the user is using. Further, in this specification, the supplier of the security component 120 may include a manufacturer of the security component 120 that supplies the security component 120. [

Referring to FIG. 1, a data injection system 200 may provide input data D_IN to a security component 120 via a communication interface 110. The data injection system 200 may be operated by a user of the security component 120, for example, a supplier or producer of the product 100, for the injection of security information. For example, the data injection system 200 may provide input data D_IN at the production stage of the product 100 and may provide the input data D_IN after the product 100 is shipped. 2, input data D_IN may include part user information and encrypted data, and the security information may be encrypted as part of the encrypted data and transmitted from data injection system 200 Can be provided.

The security component 120 can receive the input data D_IN and provide the security data D_SEC to the authentication request processor 130. [ The security component 120 can authenticate the input data D_IN by determining whether the input data D_IN is provided by a legitimate user of the security component 120 and retrieve the security data 120 from the authenticated input data D_IN D_SEC) to the authentication request processor 130 and provides security data D_SEC to the authentication request processor 130. [ Details of the security component 120 will be described later with reference to Figs. 3 and 5 and the like.

The authentication system 300 may provide an authentication request (A_REQ) to the security component 120 via the communication interface 110 and the authentication request processor 130 included in the product 100 may provide an authentication response (A_RES) And can be provided to the authentication system 300 through the communication interface 110. The authentication system 300 may be operated by a user of the security component 120, e.g., a supplier or producer of the product 100, to authenticate the product 100. [ For example, the authentication system 300 may provide an authentication request (A_REQ) to the product 100 to remotely control the product 100, perform software upgrades included in the product 100, 100 based on the authentication response (A_RES) provided from the authentication server (100). Although not shown, other products similar to the product 100 may also provide an authentication request (A_REQ) to the product 100 for communication with the product 100.

The authentication request processor 130 may provide an authentication response A_RES to the authentication system 300 via the communication interface 110 based on the security data D_SEC provided to the security component 120. [ For example, the authentication request processor 130 may provide the authentication system 300 with an identifier (ID) of the product 100 as an authentication response (A_RES) based on the security data D_SEC.

2 is a diagram showing the input data D_IN of FIG. 1 according to an exemplary embodiment of the present disclosure. Input data D_IN may be provided to product 100 from data injection system 200 and security component 120 contained in product 100 may be provided with input data D_IN Can be received. Hereinafter, Fig. 2 will be described with reference to Fig.

Referring to FIG. 2, input data D_IN may include part user data D_USR and encrypted data D_ENC. The part user data D_USR may include information about the user of the security component 120 (e.g., the supplier or producer of the product 100). For example, as shown in FIG. 2, the part user data D_USR may include a user identifier U_ID, a user key U_KEY, and a seed (or seed data) SEED. The component user data D_USR may be data provided to the user of the security component 120 from the supplier of the security component 120, as described below with reference to FIG. That is, the supplier of the security component 120 may issue a user identifier U_ID, a user key U_KEU, and a seed SEED to the user of the security component 120 before and after the supply of the security component 120, The user of security component 120 may provide user identifier U_ID, user key U_KEU and SEED to security component 120 as part of input data D_IN. As described later with reference to FIG. 3 and the like, the part user data D_USR can be used by the security component 120 to authenticate the input data D_IN and to decrypt the encrypted data D_ENC.

The encrypted data D_ENC may include data generated by encrypting the security information in advance by the user of the security component 120. [ In order to protect the security information when the input data D_IN is exposed by improper access in the process of providing the input data D_IN from the data injection system 200 to the product 100, D_IN). The encryption method of the security information used by the user of the security component 120 may be shared in advance with the supplier of the security component 120 and may be encrypted using the encryption key provided by the supplier of the security component 120 ). ≪ / RTI > Accordingly, even if the input data D_IN is exposed, the user of the security component 120 maintains security with respect to the master key issued to the security component 120. Therefore, even when the input data D_IN is exposed, Information can be protected from inappropriate external access.

FIG. 3 is a block diagram illustrating an example of the security component 120 of FIG. 1 in accordance with an exemplary embodiment of the present disclosure. 1, the security component 120 'of FIG. 3 may receive input data DIN provided from the data injection system 200 of FIG. 1 and may include security data D_SEC To the authentication request processor 130 of FIG. 3, the secure part 120 'may include a user authentication processor 121', a master key generator 122 ', a decryption processor 123' and a secure repository 124 ' Each of the user authentication processor 121 ', the master key generator 122', the decryption processor 123 'and the security repository 124' may include a logic block designed through logic synthesis or the like, ≪ / RTI > Hereinafter, FIG. 3 will be described with reference to FIG.

The user authentication processor 121 'uses the user identifier U_ID and the user key U_KEY included in the input data D_IN to determine whether the input data D_IN is provided by a legitimate user of the security component 120' The input data D_IN can be authenticated. As described above with reference to FIG. 2, the user identifier U_ID and the user key U_KEY may be provided in advance to a legitimate user of the security component 120 'by the supplier of the security component 120'. The user identifier U_ID and the user key U_KEY provided to a legitimate user of the secure part 120 'may satisfy a predetermined relationship and accordingly the user authentication processor 121' It is determined whether or not the input data D_IN is provided by a legitimate user of the security component 120 'by detecting whether the relationship between the identifier U_ID and the user key U_KEY satisfies such a predetermined relationship . The user authentication processor 121'corresponds to the enable signal ENA activated when the input data D_IN is determined to have been provided by a legitimate user of the security component 120 ', that is, when the authentication of the input data D_IN is successful, While providing a disabled enable signal (ENA) if not. Details of the operation of the user authentication processor 121 'will be described later with reference to FIG.

The master key generator 122 'may generate the master key M_KEY using the seed SEED included in the input data D_IN. As described above with reference to FIG. 2, the SEED can be provided in advance to a legitimate user of the security component 120 'by the supplier of the security component 120' May also be provided in advance to a legitimate user of the security component 120 'by the supplier of the security component 120'. The SEED and the master key provided to the legitimate user of the secure part 120 'may satisfy a predetermined relationship and the master key M_KEY generated by the master key generator 122' May be the same as the master key used when the security information is encrypted, if it is the legitimate user of the secure part 120 '. Accordingly, the master key M_KEY may not be exposed to the outside in the process of transmitting the input data D_IN to the product 100, so that the security information encrypted by the master key M_KEY may be protected .

The decryption processor 123 'may decrypt the encrypted data D_ENC included in the input data D_IN using the master key M_KEY provided from the master key generator 122'. The input data D_IN provided by a legitimate user of the security component 120'is used to authenticate the security information in a manner shared with the supplier of the security component 120'by using the master key provided by the supplier of the security component 120 ' (D_ENC) generated by encrypting the encrypted data D_ENC, the decryption processor 123 'decrypts the encrypted data D_ENC if the master key M_KEY provided by the master key generator 122' is legitimate The security data D_SEC may include security information.

The secure repository 124 'may store the secure data D_SEC provided from the decryption processor 123' and may provide the stored secure data D_SEC to the authentication request processor 130 of FIG. For example, the secure storage 124 'is a non-volatile memory that does not lose stored data even if power supplied to the secure part 120' is blocked, including but not limited to non-volatile memory such as EEPROM (Random Access Memory), Random Access Memory (RRAM), Nano Floating Gate Memory (NFGM), Polymer Random Access Memory (PoRAM), MRAM (Magnetic Random Access Memory), FRAM (Ferroelectric Random Access Memory), and the like. In some embodiments, the secure repository 124 'may include an OTP (One Time Programmable) memory that stores at least a portion of the secure data D_SEC, and at least some of the secure data D_SEC may be stored in the OTP memory Deletion and / or modification can be prevented. In some embodiments, the secure repository 124 'may include a rewritable memory that stores at least a portion of the secure data D_SEC, and at least some of the secure data D_SEC may include a rewritable memory May be deleted and / or changed by being stored in the storage medium.

As shown in FIG. 3, the master key generator 122 ', the decryption processor 123', and the secure repository 124 'may be included in the first group G1. The first group G1 may receive an enable signal ENA from the user authentication processor 121 'and may include a master key generator 122', a decryption processor 123 ' And secure storage 124 'may perform operations in response to an enabled enable signal (ENA), but may not perform at least some of the operations in response to a disabled enable signal (ENA) have. For example, the master key generator 122 'and the decryption processor 123' may be disabled in response to the disabled enable signal ENA and the secure store 124 ' Only the output operation of the secure data D_SEC can be performed.

In one embodiment, the security component 120 'may be configured to store the security data D_SEC generated from the authenticated input data D_IN, and then the stored security data D_SEC may be unchanged. That is, at least one of the user authentication processor 121 ', the master key generator 122', the decryption processor 123 'and the secure repository 124' only performs operations on the first authenticated input data D_IN . For example, the security component 120 'may include a memory element that stores information about whether the operation for the first authenticated input data D_IN is complete, and includes a user authentication processor 121', a master key At least one of the generator 122 ', the decryption processor 123' and the secure repository 124 'may ignore the input data D_IN provided to the security component 120' according to the information stored in the memory element, Security data D_SEC already stored can be protected. In some embodiments, the memory element that stores information about the completion of the operation for the first authenticated input data D_IN may include an OTP element that irreversibly stores information such as anti-fuse, When the operation for the first authenticated input data D_IN is completed, the OTP element can be programmed. In some embodiments, the memory element that stores information about the completion of the operation for the first authenticated input data D_IN may include a rewritable memory element, and the first authenticated input data D_IN, The data indicating the completion can be written to the rewritable memory element.

FIG. 4 is a flow diagram illustrating exemplary operation of the user authentication processor 121 'of FIG. 3 in accordance with an exemplary embodiment of the present disclosure. 3, the user authentication processor 121 'uses the user identifier U_ID and the user key U_KEY contained in the input data D_IN so that the input data D_IN is stored in the secure part 120 The user can authenticate the input data D_IN by determining whether the input data D_IN is provided by a legitimate user. Hereinafter, FIG. 4 will be described with reference to FIG.

Referring to FIG. 4, in step S41, an operation of generating an evaluation key from the user identifier U_ID may be performed. For example, the user authentication processor 121 'may generate an evaluation key from a user identifier (U_ID) based on a predetermined method, such as a mathematical operation, a logical operation, a lookup table, and the like. The user authentication processor 121'compares the evaluation key generated from the user identifier U_ID issued to the authorized user of the security component 120 'so that it matches the user key U_KEY issued simultaneously with the user identifier U_ID, May be designed by the supplier of security component 120 '.

In step S42, an operation of determining whether the evaluation key matches the user key U_KEY may be performed. If the evaluation key and the user key U_KEY coincide with each other, that is, if the user identifier U_ID and the user key U_KEY included in the input data D_IN belong to a legitimate user of the security component 120 ' The operation of activating the enable signal ENA may be performed. On the other hand, if the evaluation key and the user key U_KEY do not match, that is, if the user identifier U_ID and the user key U_KEY included in the input data D_IN are the same as those of the legitimate user of the security component 120 ' , An operation of deactivating the enable signal ENA in step S44 may be performed.

5 is a block diagram illustrating an example of the security component 120 of FIG. 1 in accordance with an exemplary embodiment of the present disclosure. 1, the security component 120 "of FIG. 5 may receive input data DIN 'provided from the data injection system 200 of FIG. 1 and may include security data D_SEC, To the authentication request processor 130 of Figure 1. As shown in Figure 5, the security component 120 "includes a user authentication processor 121 ", a master key generator 122 ", a decryption processor 123 ") and secure repository 124 ". The SEED can be excluded from the input data D_IN "received by the security component 120 ", as compared to the security component 120 'of FIG. Hereinafter, the description of the security component 120 '' in FIG. 5 and the description of the security component 120 'in FIG. 3 will be omitted.

In accordance with an exemplary embodiment of the present disclosure, a master key M_KEY in a security component 120 " may be generated from a user identifier U_ID and / or a user key U_KEY, Instead of issuing separate seed information to a legitimate user of the security component 120 ", the supplier of the security component 120 "has a master key having a certain relationship with the user identifier U_ID and / or the user key U_KEY It can be issued to a legitimate user. The user of security component 120 " can prepare encrypted data D_ENC by encrypting the security information using the master key provided by the supplier of security component 120 ", and the encrypted data D_ENC and user data < (D_IN ') including the user identifier (U_ID) as security data (D_USR) to the security component 120 ".

5, the master key generator 122 "receives the user identifier U_ID and / or the user key U_KEY from the input data D_IN" authenticated by the user authentication processor 121 " And may generate the master key M_KEY according to a predetermined method from the user identifier U_ID and / or the user key U_KEY.

FIG. 6 is a diagram showing input data D_IN "in accordance with an exemplary embodiment of the present disclosure, and FIG. 7 is a block diagram of the input data D_IN " Is a flow diagram illustrating exemplary operation of the security component 120. FIG. For example, the input data D_IN "in FIG. 6 may be provided to the security component 120 'of FIG. 3, and the flowchart of FIG. 7 may represent the operation of the security component 120' of FIG. Hereinafter, Figs. 6 and 7 will be described with reference to Fig.

6, input data D_IN "may include user data D_USR, lock data LOCK, and encrypted data D_ENC. Similar to that described above with reference to FIG. 2, (D_USR) may include a user identifier (U_ID), a user key (U_KEY) and a seed (SEED) that a legitimate user of the security component 120 'has been issued from the supplier of the security component 120'. [ The user data D_USR may include only the user identifier U_ID and the user key U_KEY as described above with reference to Figure 5. The encrypted data D_ENC may be transmitted to the user Similarly, a legitimate user of security component 120 'may be created by encrypting security information based on a master key issued from a supplier of security component 120'.

The lock data LOCK may include information indicating whether to allow the security data D_SEC stored in the security component 120 'to be changed due to the provision of other input data D_IN "in the future. After the security data D_SEC is stored, the part 120 'is permanently set so that the security data D_SEC is unchanged when the lock function is activated in accordance with the lock data LOCK of the authenticated input data D_IN " .

Referring to FIG. 7, in step S71, an operation of determining whether to activate the lock function may be performed. For example, at least one of the user authentication processor 121 ', the master key generator 122', the decryption processor 123 'and the secure repository 124' of the security component 120 ' D_IN ") included in the lock data LOCK. If the lock function is activated in accordance with the lock data LOCK, step S72 may be performed subsequently.

In step S72, an operation of permanently setting the stored security data D_SEC to be unchanged may be performed. For example, at least one of the user authentication processor 121 ', the master key generator 122', the decryption processor 123 'and the secure repository 124' may be configured such that the secure data D_SEC is stored in the secure repository 124 ' The stored security data D_SEC may be permanently set to be unchanged. That is, at least one of the user authentication processor 121 ', the master key generator 122', the decryption processor 123 'and the secure repository 124' may store the input data D_IN received after storing the security data D_SEC May be set so as not to perform the operation on the " As described above with reference to FIG. 3, the secure part 120 'may include an OTP element such as an anti-fuse, and the OTP element may be programmed when the locking function is activated. At least one of the user authentication processor 121 ', the master key generator 122', the decryption processor 123 'and the secure repository 124' is then provided to the security component 120 'based on the programmed OTP element The input data D_IN can be ignored.

8 is a time-wise diagram of an operation for injecting security information into a security component 120 "in accordance with an exemplary embodiment of the present disclosure. Specifically, FIG. 8 illustrates a security component 120" And signals transmitted between the systems 200, 400 and 500 according to the flow of time. 8, the security components 120 ", the data injection system 200, the account issuing system 400 and the data processing system 500 may communicate with one another. The systems 200, 400 and 500 may be connected to a network such as the Internet and may be connected to other systems such as the system 200, At least two of them may communicate directly over a dedicated communication channel. Although not shown in Figure 8, the security component 120 "may be included in a product having a particular purpose (e.g., the product 100 of Figure 1) And data injection system 200 and data processing system 500 may communicate with security component 120 by transmitting signals to or receiving signals from products that include security components 120 ". Hereinafter, FIG. 8 will be described with reference to FIG.

The account issuing system 400 may be operated by a supplier of the security component 120 and the data injection system 200 and the data processing system 500 may be operated by a legitimate user of the security component 120. [ The operation of the system herein is referred to as being operated by an operating entity, such as a provider of the security component 120, and other entity under the control of the operating entity, as well as being operated directly by a legitimate user of the security component 120 can do.

Referring to FIG. 8, in step S80, the data injection system 200 may transmit an account request for use of the parts to the account issuance system 400. FIG.

In step S81, the account issuing system 400 may generate a user identifier (U_ID), a user key (U_KEY) and a master key (M_KEY) in response to the account request. For example, the account issuance system 400 may allow a user for a legitimate user of the security component 120 ", if the account request received from the data injection system 200 is by a legitimate user of the security component 120 & An identifier U_ID, a user key U_KEY, and a master key M_KEY. The account issuing system 400 may generate the user identifier U_ID and the user key U_KEY such that the user identifier U_ID and the user key U_KEY have a predetermined relationship. That is, since the user identifier U_ID is used by the security component 120 " to generate the evaluation key, the evaluation key generated from the user identifier U_ID of the authorized user of the security component 120 " The account issuing system 400 may generate a user identifier U_ID and a user key U_KEY.

The account issuing system 400 may generate the master key M_KEY such that the user identifier U_ID and / or the user key U_KEY and the master key M_KEY have a predetermined relationship. That is, as described below, the master key M_KEY generated by the account issuing system 400 can be used to generate the encrypted data D_ENC by encrypting the security information, and encrypted by the security component 120 " (M_KEY) generated by the security component 120 "from the user identifier U_ID of the legitimate user of the secure part 120 " and / or the user key U_KEY since it is used to decrypt the data D_ENC, The account issuing system 400 may generate a master key M_KEY to match.

In step S82, the account issuing system 400 may transmit the user identifier U_ID, the user key U_KEY, and the master key M_KEY to the data injection system 200. [

In step S83, the data injection system 200 may send the security data D_SEC and the master key M_KEY to the data processing system 500. [ That is, the data injection system 200 transmits the security data D_SEC and the master key M_KEY to the data processing system (D_SEC) in order to generate the encrypted data D_ENC from the security data D_SEC using the master key M_KEY 500). As described above, the security data D_SEC may include security information about the product including the security component 120 ".

In step S84, the data processing system 500 may generate the encrypted data D_ENC. For example, the data processing system 500 may generate the encrypted data D_ENC by encrypting the secure data D_SEC using the master key M_KEY, The data processing system 500 may use any encryption algorithm to generate the encrypted data D_ENC. For example, the data processing system 500 may use any encryption algorithm to generate the encrypted data D_ENC, (Advanced Encryption Standard), SEED, ARIA (Academy, Research Institute, Agency), LEA (Lightweight Encryption Algorithm), RC4, RSA, ECC (Elliptic curve cryptography, DSS (Digital Signature Standard), or the like to generate encrypted data D_ENC.

In step S85, the data processing system 500 can transmit the encrypted data D_ENC.

Although the data injection system 200 and the data processing system 500 operated by a legitimate user of the security component 120 "in FIG. 8 are shown separately, in one embodiment the data injection system 200 and data Operations of the processing system 500 may be performed in a single system under the control of the security component 120 ". Accordingly, the operation of transmitting the security data D_SEC and the master key M_KEY in step S83 and the operation of transmitting the encrypted data D_ENC in step S85 may be omitted.

In step S86, the data injection system 200 may transmit the input data D_IN "to the security component 120 ". That is, the data injection system 200 may provide the security component 120 " with the input data D_IN "including the user identifier U_ID, the user key U_KEY, and the encrypted data D_ENC.

In step S87, the security component 120 "may perform the operation of authenticating the input data D_IN ". For example, the user authentication processor 121 " of the security component 120 " can generate an evaluation key from the user identifier U_ID and compare the generated evaluation key and the user key U_KEY to generate input data D_IN If the generated evaluation key and the user key U_KEY match, that is, if the authentication of the input data D_IN "is successful, the security component 120 " .

For example, the master key generator 122 "of the secure part 120" may generate a user identifier (U_ID) and / or a user ID < RTI ID = The master key M_KEY may be generated from the key U_KEY according to a predetermined method.

For example, the decryption processor 123 " may generate the master key M_KEY generated by the master key generator 122 ", and the secure part 120 "may generate and store the secure data D_SEC in step S89. The master key M_KEY can be used to generate the secure data D_SEC by decrypting the encrypted data D_ENC by using the master key M_KEY in the process of transmitting the input data D_IN to the product 100. [ And as a result, the security information encrypted by the master key M_KEY can be protected.

Although an example has been shown in FIG. 8 in which the master key M_KEY is generated from the user identifier U_ID and / or the user key U_KEY, the master key M_KEY, as described above with reference to FIGS. 2 and 3, May be generated from the seed (SEED) contained in the input data D_IN. To this end, the account issuance system 400 may provide a SEED as well as a user identifier U_ID, a user key U_KEY and a master key M_KEY to the data injection system 200, 200 provides the SEED with the input data D_IN including the seed SEED with the user identifier U_ID, the user key U_KEY and the encrypted data D_ENC to the security component 120 " can do.

9 is a flow diagram illustrating a method for injecting security information in accordance with an exemplary embodiment of the present disclosure. For example, the method of FIG. 9 may be performed by the security component 120 of FIG. 1, and hereinafter, FIG. 9 will be described with reference to FIG.

In step S91, an operation of receiving the input data D_IN may be performed. For example, the security component 120 may receive input data D_IN from the outside of the product 100 (e.g., the data injection system 200 of FIG. 1) via the communication interface 110. As described above with reference to Fig. 2 and the like, the input data D_IN may include the part user data D_USR and the encrypted data D_ENC.

In step S92, an operation of authenticating the input data D_IN based on the part user data D_USR may be performed. For example, the security component 120 can generate the evaluation key from the user identifier U_ID included in the parts user data D_USR, and generate the evaluation key using the user key U_KEY included in the user data D_USR It can be determined by comparing whether the input data D_IN is provided by a legitimate user of the security component 120. [ In step S93, if authentication of the input data D_IN is successful, step S94 may be performed subsequently.

In step S94, an operation of generating the master key M_KEY based on the seed SEED may be performed. For example, the security component 120 can extract the seed (SEED) included in the authenticated input data D_IN and generate the master key M_KEY in a predetermined manner based on the extracted seed SEED can do. In one embodiment, the seed SEED may be included independently of the other data in the input data D_IN, and in another embodiment at least a portion of the part user data D_USR of the input data D_IN may be included in the master key M_KEY It is possible to perform the same function as the seed SEED.

In step S95, an operation of decrypting the encrypted data D_ENC based on the master key M_KEY may be performed. For example, the security component 120 can generate the security data D_SEC by decrypting the data D_ENC encrypted in a predetermined manner using the master key M_KEY generated in step S94.

In step S96, an operation of storing security data D_SEC may be performed. For example, security component 120 may store security data D_SEC in a non-volatile memory. In one embodiment, the input data D_IN received at the security component 120 so that the security data D_SEC is unchanged after the security data D_SEC is stored may be ignored. In another embodiment, it may be determined whether or not the stored security data D_SEC is changeable, according to the lock data LOCK included in the input data D_IN, as described above with reference to Figs. 6 and 7.

Figure 10 is a block diagram illustrating an example of the product 100 of Figure 1 in accordance with an exemplary embodiment of the present disclosure. As shown in FIG. 10, the product 100 of FIG. 1 is an IoT device 600 that can be connected to the Internet through an application processor (AP) 610, a bus 620, a sensor 630, A normal memory 640, a secure memory 650, a security module 660, a display 670, and an input / output device 680. Each of the components 610, 630 to 680 of the IOT device 600 can be connected to the bus 620 and can exchange data with each other via the bus 620.

The Internet (IoT) can refer to a network of objects using wired / wireless communication. For example, the Internet (IoT) may be an IoT network system, a Ubiquitous Sensor Network (USN) communication system, a MTC (Machine Type Communications) communication system, an MOC (Machine Oriented Communication) communication system, an M2M D2D (Device to Device) communication system, and the like.

The application processor 610 may control the overall operation of the IoT device 600. [ For example, application processor 610 may execute applications that provide Internet browsers, games, animations, and the like. In one embodiment, application processor 610 may include one or more cores. For example, the application processor 610 may include a multi-core such as a dual-core, a quad-core, and a hexa-core. In addition, the application processor 610 may further include a cache memory.

The sensor 630 can sense the external environment of the IoT device 600. In one embodiment, the sensor 630 may be an image sensor, and may generate image information and provide it to the application processor 610. In another embodiment, the sensor 630 may be a biosensor that senses biometric information and may correspond to information sensed by sensing a fingerprint, an iris pattern, a blood line pattern, a heart rate, blood glucose, etc. as a non-limiting example It is possible to generate sensing data. In accordance with embodiments, the sensor 630 may include any sensor, such as an illuminance sensor, an acoustic sensor, an acceleration sensor, and the like.

The normal memory 640 may store data necessary for the operation of the IoT device 600. [ For example, the normal memory 640 may be a volatile memory device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), and / or a flash memory device ), A solid state drive (SSD), and the like.

The secure memory 650 may store data that requires security during the operation of the IoT device 600. [ For example, secure memory 650 may include security data (D_SEC) including security information for IoT device 600 that needs protection from external improper access, similar to security store 124 ' Can be stored. In accordance with embodiments, secure memory 650 may store data sensed through sensor 630, e.g., data including body information. Although the normal memory 640 and the secure memory 650 are shown separately in FIG. 10, the technical idea of the present disclosure is not limited thereto, and the normal memory 640 and the secure memory 650 may include one physical memory As shown in FIG. In one embodiment, normal memory 640 and / or secure memory 650 may be removably coupled to IoT device 600, such as normal memory 640 and / or secure memory 650, / RTI > can be connected to the IoT device 600 using a socket or the like.

The security module 660 may manage the secure memory 650. That is, the security module 660 may store the data requiring security in the process of operating the IOT device 600 in the security memory 650, or may lead the security module 650 from the security memory 650. For example, the security module 660 may perform at least one of the operations of the user authentication processor 121 ', the master key generator 122', and the decryption processor 123 'of FIG. 3, And the security data D_SEC stored in the storage 650 can be controlled. The security module 660 may include a logic block designed by logic synthesis, and may include a processor and a software block executed by the processor.

 Display 670 can output data. For example, the display 670 may output the sensed image data using the sensor 630 or may output the computed data using the application processor 610. [

The input / output device 680 may include a component for receiving an input of a user of the IoT device 600 such as a touch pad, a keypad, an input button, or the like, and may include a component for outputting a signal such as an LED, It is possible.

FIG. 11 is a block diagram illustrating an exemplary structure of the hardware and software of IoT device 600 of FIG. 10 in accordance with an exemplary embodiment of the present disclosure. 11, the IoT device 700 may include an IoT device application 710 and a communication module 720 and the communication module 720 may include firmware 721, a wireless baseband chipset 722, And a security module 723.

The IoT device application 710 can control the communication module 720 as a software block and can be executed by the CPU of the IoT device 700 (e.g., the application processor 610 of Fig. 10). The communication module 720 may be a wireless local area network (WLAN), a wireless local area network (WLAN) such as Wi-Fi, a wireless personal area network (WPAN) such as Bluetooth, a wireless USB Zigbee); (NFC), a Radio Frequency Identification (RFID), or a wireless communication block capable of exchanging data through a mobile communication system.

The firmware 721 may provide an API (Application Programming Interface) to the IoT device application 710 and may control the wireless baseband chipset 722 based on the control of the IoT device application 710. [ The wireless baseband chipset 722 may provide a connection to a wireless communication network. The security module 723 may store data (e.g., security data D_SEC in FIG. 1) for authenticating the IoT device 700 to access the wireless communication network and may be configured to communicate with the IoT device 700 for wireless network services, As shown in FIG. The security module 723 may authenticate data provided from outside the IoT device 700 (e.g., input data D_IN in FIG. 1), and retrieve security data from the authenticated data, according to an exemplary embodiment of the present disclosure. And the like.

12 is a diagram illustrating a network system 900 in which an article comprising a security component in accordance with an exemplary embodiment of the present disclosure is used. 12, the network system 900 includes a plurality of lighting devices 920 and 930, a server 940, and a server 940 that are communicably connected to the communication connection device 910, the communication connection device 910, A communication base station 960, a communication network 970, and a mobile device 980. The computer 950,

Each of a plurality of light fixtures 920, 930 installed in an open external space such as a street or a park may include smart engines 921, 931. The smart engines 921 and 931 may include sensors and communication modules for collecting information on the surrounding environment, and may include, but are not limited to, communication with other peripheral devices according to communication protocols such as WiFi, Zigbee, and LiFi can do. For example, the smart engine 921 may be communicatively coupled to another smart engine 931, and WiFi Mesh may be used for communication between the smart engines 921 and 931. The smart engine 921 may be connected to the communication connection device 910 connected to the communication network 970 by wire / wireless communication. For high communication efficiency, two or more smart engines (e.g., 921, 931) may be coupled to the communication link 910 as a group.

Each of the smart engines 921 and 931 may store unique information of the lighting devices 920 and 930 as security information. The security information stored in each of the smart engines 921 and 931 may be different and the data after the lighting devices 920 and 930 are installed in accordance with the exemplary embodiment of the present disclosure D_IN) to be stored securely in the smart engines 921, 931.

The communication connection device 910 is an access point (AP) capable of wired / wireless communication, and can mediate communication between the communication network 970 and other devices. The communication connection device 910 may be connected to the communication network 970 by at least one of wire / wireless methods, and may be mechanically housed, for example, in at least one of the lighting devices 920, 930.

The communication connection device 910 may be connected to the mobile device 980 through a communication protocol such as WiFi. The user of the mobile device 980 receives the surrounding information collected by the smart engines 921 and 931 through the communication connection device 910 connected to the smart engine 921 of the neighboring lighting device 920 . The communication link 910 may send an authentication request to the smart engines 921 and 931 and may be used by the smart engines 921 and 931 to communicate with the smart engines 921 and 931 based on the authentication responses they provide based on the security information stored in them. (921, 931), it is possible to relay the communication between the smart engines 921, 931 and the mobile device 980. The mobile device 980 may be connected to the communication network 970 via a communication base station 960 in a wireless cellular communication scheme such as 3G or 4G.

The server 940 connected to the communication network 970 receives information collected by the smart engines 921 and 931 of the lighting devices 920 and 930 through the communication connection device 910, The operating states of the mechanisms 920 and 930, and the like. The server 940 may be coupled to a computer 950 that provides a management system to manage each of the luminaire 920, 930 based on the monitoring results of the operating conditions of the luminaire 920, 930. In accordance with an exemplary embodiment of the present disclosure, server 940 is configured to inject security information into smart engines 921, 931 of lighting fixtures 920, 930, similar to data injection system 200 of FIG. To the smart engines 921 and 931 through the communication network 970 and the communication connection device 910. [ As described above, the data provided by the server 940 may include information previously provided by the suppliers of the smart engines 921 and 931 (e.g., U_ID, U_KEY, etc. in FIG. 8) May include encrypted data according to the information provided by the suppliers of the engines 921 and 931 (e.g., M_KEY in Fig. 8). The computer 950 may execute software or the like that can monitor and manage the operating conditions of the lighting fixtures 920, 930 via the smart engines 921, 931.

As described above, exemplary embodiments have been disclosed in the drawings and specification. Although the embodiments have been described herein with reference to specific terms, it should be understood that they have been used only for the purpose of describing the technical idea of the present disclosure and not for limiting the scope of the present disclosure as defined in the claims . Therefore, those skilled in the art will appreciate that various modifications and equivalent embodiments are possible without departing from the scope of the present invention. Accordingly, the true scope of protection of the present disclosure should be determined by the technical idea of the appended claims.

Claims (10)

A security component included in a product that processes input data for authenticating the product,
A user authentication processor for performing authentication of the input data by determining whether the input data is provided by a legitimate user of the security component based on the part user data included in the input data;
A master key generator for generating a master key based on the authenticated part user data of the authenticated input data;
A decryption processor for generating secure data by decrypting the encrypted data included in the input data authenticated based on the master key; And
And a security store for storing the security data. The method according to claim 1,
Wherein the part user data includes a user identifier and a user key,
Wherein the user authentication processor generates an evaluation key from the user identifier and authenticates the input data when the evaluation key and the user key match. The method of claim 2,
Wherein the authenticated part user data further comprises seed data,
Wherein the master key generator generates the master key based on the seed data. The method of claim 2,
Wherein the master key generator generates the master key based on at least one of the user identifier and the user key. The method according to claim 1,
Wherein at least one of the user authentication processor, the master key generator, the decryption processor, and the secure repository is permanently set such that the stored secure data is permanently stored when the secure data is stored in the secure repository. The method of claim 5,
Wherein the secure storage comprises at least one of an OTP (One Time Programmable) memory storing the secure data and a rewritable memory. The method according to claim 1,
Wherein at least one of the user authentication processor, the master key generator, the decryption processor and the secure repository is permanently set such that the stored secure data is unchanged according to the lock data contained in the authenticated input data Security parts. A product that responds to an external product certification request based on security data stored therein,
A communication interface for receiving, from outside the product, input data including encrypted data and part user data; And
Performing authentication of the input data based on the part user data and decrypting the authenticated encrypted data of the input data authenticated based on the authenticated part user data of the authenticated input data, And storing the security data. The method of claim 8,
Wherein the secure data comprises at least one of an identifier, a certificate, a private key, and a pre-shared key of the product. The method of claim 8,
Wherein the communication interface receives the product authentication request,
And an authentication request processor responsive to the product authentication request based on the security data.

Images