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

Abstract

A security component according to an exemplary embodiment of the present disclosure is a user authentication processor that performs authentication of input data by determining whether the input data is provided by a legitimate user of the component based on the component user data included in the input data. , a master key generator that generates a master key based on the authenticated part user data of the authenticated input data, a decryption processor that generates security data by decrypting encrypted data included in the authenticated input data based on the master key, and It may include a secure storage for storing secure data.

Description

COMPONENT FOR PROVISIONING OF SECURITY DATA AND PRODUCT INCLUDING THE SAME

The technical idea of the present disclosure relates to injection of security information, and more particularly, to a part for injection of security information and a product including the same.

Security information that must be protected from inappropriate external access can be included in the product in various ways. For example, a component user may receive a component including security information from a component supplier, or may inject security information into the component or a product including the component in the production stage of the product. In the former method, security information can be included in a product relatively safely, and it may not be easy to change security information according to changes in the use environment of parts, as well as inevitably exposing security information to parts suppliers. In addition, in the latter method, security information may be easily changed, and protection of security information against improper access outside the product may be weak due to an interface for injection of security information.

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

In order to achieve the above object, according to an aspect of the technical idea of the present disclosure, a security component that is included in the product and processes input data for authenticating the product is input based on the component user data included in the input data. A user authentication processor that performs authentication of input data by judging whether the data is provided by a legitimate user of the part, a master key generator that generates a master key based on the authenticated part user data of the authenticated input data, a master key It may include a decryption processor for generating secure data by decrypting the encrypted data included in the authenticated input data based on the, and a secure storage for storing the secure data.

According to an aspect of the technical idea of the present disclosure, a product that responds to a product authentication request from the outside based on the security data stored therein receives input data including encrypted data and part user data from the outside of the product a communication interface that performs authentication of input data based on the part user data, and generates security data by decrypting the authenticated encrypted data of the input data authenticated based on the authenticated part user data of the authenticated input data, It may include a security component that stores security data.

According to the component and method for injection of security information according to the technical spirit of the present disclosure, security information can be safely injected into a product including the component under the control of the component user.

In addition, 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 parts user can be remarkably improved.

In addition, according to the parts and method for injecting security information according to the technical spirit of the present disclosure, the production of parts including 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 schematically illustrating a product including security information and peripheral systems according to an exemplary embodiment of the present disclosure;
FIG. 2 is a diagram illustrating input data of FIG. 1 according to an exemplary embodiment of the present disclosure;
Fig. 3 is a block diagram illustrating an example of the security component of Fig. 1 according to an exemplary embodiment of the present disclosure;
4 is a flowchart illustrating an exemplary operation of the user authentication processor of FIG. 3 according to an exemplary embodiment of the present disclosure;
Fig. 5 is a block diagram illustrating an example of the security component of Fig. 1 according to an exemplary embodiment of the present disclosure;
6 is a diagram illustrating input data according to an exemplary embodiment of the present disclosure.
7 is a flow chart 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 illustrating an operation for injecting security information into a security component over time according to an exemplary embodiment of the present disclosure;
9 is a flowchart illustrating a method of injecting security information according to an exemplary embodiment of the present disclosure.
10 is a block diagram illustrating an example of the product of FIG. 1 according to 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 according to an exemplary embodiment of the present disclosure.
12 is a diagram illustrating a network system in which a product including a security component is used according to an exemplary embodiment of the present disclosure.

1 is a block diagram schematically illustrating a product 100 including security information and peripheral systems 200 and 300 according to an exemplary embodiment of the present disclosure. As shown in FIG. 1 , the product 100 may communicate with the data injection system 200 and the authentication system 300 , and may include a communication interface 110 , a security component 120 , and an authentication request processor 130 . may include As components included in the product 100 , each of the communication interface 110 , the security component 120 , and the authentication request processor 130 may include a logic block designed through logic synthesis, etc., and executed by the processor It may also include a software block that is

The product 100 is an entity including security information and may respond to an external request, for example, an authentication request (A_REQ) based on the 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, a wearable device, and the like. may be, or may be any object that provides a specific function, such as an automobile, a mechanical device, a manufacturing facility, a door, a lighting, 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 similar to the product 100 , through the communication interface 110 included in the product 100 . For example, the product 100 through the communication interface 110, for example, LTE (Long Term Evolution) system, CDMA (Code Division Multiple Access) system, GSM (Global System for Mobile Communications) system, such as mobile communications (mobile) It may be connected to a telecommunication) system, it 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), etc., and may be connected to the Internet of Things (IoT). have. The communication interface 110 may support one or more communication methods, for example, 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 methods.

The security information may include personal information about the user of the product 100, and as information for authentication of the product 100, an identifier (ID) of the product 100, supplier information of the product 100, authentication information ( certificate), a private key, and a pre-shared key (PSK). Information for authentication of the product 100 included in the security information, as a non-limiting example, may be used for tasks requiring authentication of the product 100, such as remote operation of the product 100, software upgrade, etc. . For example, when the product 100 accesses the Internet of Things through the communication interface 110 , the product 100 transmits information acquired by itself through the communication interface 110 or externally through the communication interface 110 . The reliability 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 an unreasonable attempt, the security information needs to be safely protected from inappropriate 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 a component capable of storing data, such as a semiconductor memory device, and the security information may be stored in the component included in the security component 120 . In order to include the security information in the security component 120, when the security information is injected into the security component 120 in the production stage of the security component 120, the security component 120 by the user of the security component 120 In addition to a decrease in utilization, the production efficiency of the security component 120 by the supplier of the security component 120 may decrease. For example, when the product 100 needs to be supplied to be suitable for various use environments, such as when the product 100 is connected to the Internet of Things through the communication interface 110 , the security component 120 is Due to the difficulty in modifying the included security information, 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 decrease. In addition, due to the process for the injection of security information and the preparation of the pre-injected security component 120 , the production efficiency of the security component 120 by the supplier (or producer) of the security component 120 may decrease. can As will be described later, according to the security component 120 and the method of injecting security information according to exemplary embodiments of the present disclosure, the security information is securely stored in the security component 120 post-mortem (ie, the security component 120 ). after shipment of) can be injected, which can be beneficial to both the user and the supplier of the security component 120 . In this specification, 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 includes the security component 120 . may include developers and/or users who use (eg, customize) the product 100 . In addition, in this specification, the supplier of the security component 120 may include a manufacturer of the security component 120 to supply the security component (120).

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

The security component 120 may receive the input data D_IN and provide the security data D_SEC to the authentication request processor 130 . The security component 120 may 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 from the authenticated input data D_IN to the security data ( D_SEC) and may provide 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 .

The authentication system 300 may provide an authentication request (A_REQ) to the security component 120 through the communication interface 110 , and the authentication request processor 130 included in the product 100 transmits the authentication response (A_RES). It may 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 , for example, a supplier or a producer of the product 100 in order 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 or perform software upgrade included in the product 100, and the product ( The product 100 may be authenticated based on the authentication response A_RES provided from 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 the authentication response A_RES to the authentication system 300 through 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 identifier (ID) of the product 100 to the authentication system 300 as an authentication response (A_RES) based on the security data (D_SEC).

FIG. 2 is a diagram illustrating input data D_IN of FIG. 1 according to an exemplary embodiment of the present disclosure. As described above with reference to FIG. 1 , the input data D_IN may be provided to the product 100 from the data injection system 200 , and the security component 120 included in the product 100 may include the input data D_IN ) can be received. Hereinafter, FIG. 2 will be described with reference to FIG. 1 .

Referring to FIG. 2 , input data D_IN may include part user data D_USR and encrypted data D_ENC. The component user data D_USR may include information about a user of the secure component 120 (eg, a supplier or a 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. As will be described later with reference to FIG. 8 , 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 . 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 supply of the security component 120 , The user of the security component 120 may provide the user identifier U_ID, the user key U_KEU, and the seed SEED to the security component 120 as part of the input data D_IN. As will be described later with reference to FIG. 3 and the like, the component user data D_USR may 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 security information in advance by a user of the security component 120 . In order to protect 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, the security information is encrypted and the input data ( 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 provider of the security component 120 , and an encryption key (eg, M_KEY in FIG. 8 ) provided by the provider of the security component 120 . ) can be encrypted using Accordingly, by maintaining the security of the master key issued to the user of the security component 120 , even if the input data D_IN is exposed, the security included in the input data D_IN as a part of the encrypted data D_ENC Information can be protected from inappropriate external access.

3 is a block diagram illustrating an example of the security component 120 of FIG. 1 according to an exemplary embodiment of the present disclosure. As described above with reference to FIG. 1 , the security component 120 ′ of FIG. 3 may receive the input data DIN provided from the data injection system 200 of FIG. 1 , and receive the security data D_SEC It may be provided to the authentication request processor 130 of FIG. 1 . 3, the secure component 120' may include a user authentication processor 121', a master key generator 122', a decryption processor 123' and a secure storage 124', Each of the user authentication processor 121', the master key generator 122', the decryption processor 123', and the secure storage 124' may include a logic block designed through logical synthesis or the like, and is executed by the processor. It may also include a software block that is Hereinafter, FIG. 3 will be described with reference to 1. 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 ′. By determining, the input data D_IN may 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 secure component 120 ′ by the supplier of the secure component 120 ′. The user identifier (U_ID) and the user key (U_KEY) provided to the legitimate user of the security component 120' may satisfy a predetermined relationship, and accordingly, the user authentication processor 121' is the user included in the input data D_IN. By detecting whether the relationship between the identifier U_ID and the user key U_KEY satisfies such a predetermined relationship, it can be determined whether the input data D_IN is provided by a legitimate user of the secure component 120'. can The user authentication processor 121 ′ activates the enable signal ENA when it is determined that the input data D_IN is provided by a legitimate user of the security component 120 ′, that is, when authentication of the input data D_IN is successful. may be provided, otherwise, an inactivated enable signal ENA may be provided. Details of the operation of the user authentication processor 121 ′ will be described later with reference to FIG. 4 .

The master key generator 122 ′ may generate the master key M_KEY by using the seed SEED included in the input data D_IN. As described above with reference to FIG. 2 , the seed SEED may be provided in advance to a legitimate user of the secure component 120 ′ by the supplier of the secure component 120 ′, and a master key used to encrypt the security information. It may also be provided in advance to legitimate users of the secure component 120' by the supplier of the secure component 120'. The seed SEED and the master key provided to the legitimate user of the security component 120' may satisfy a predetermined relationship, and accordingly, the master key M_KEY generated by the master key generator 122' is the seed SEED. If is of a legitimate user of the secure component 120', it may match the master key used when the secure information was encrypted. Accordingly, the master key M_KEY may not be exposed to the outside while the input data D_IN is transmitted to the product 100 , and as a result, 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 secure component 120' uses a master key provided from the supplier of the secure component 120' to obtain security information in a shared manner with the supplier of the secure component 120'. Since the encrypted data (D_ENC) generated by encryption is included, if the master key (M_KEY) provided by the master key generator 122' is legitimate, the decryption processor 123' generates the encrypted data (D_ENC) by decrypting it. The security data D_SEC may include security information.

The secure storage 124 ′ may store the security data D_SEC provided from the decryption processor 123 ′ and provide the stored security data D_SEC to the authentication request processor 130 of FIG. 1 . For example, the secure storage 124 ′ is a non-volatile memory that does not lose stored data even when power supplied to the secure component 120 ′ is cut off, and as a non-limiting example, non-volatile memory (EEPROM) such as a Electrically Erasable Programmable Read-Only Memory), Flash memory, Phase Change Random Access Memory (PRAM), Resistance 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 may be included. In some embodiments, the secure storage 124 ′ may include a One Time Programmable (OTP) memory that stores at least a portion of the secure data D_SEC, and at least a portion of the secure data D_SEC is stored in the OTP memory. Thus, deletion and/or alteration may be prevented. In some embodiments, secure storage 124 ′ may include a rewritable memory that stores at least a portion of secure data D_SEC, wherein at least a portion of secure data D_SEC is a rewritable memory. may be deleted and/or changed by being stored in

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

In an embodiment, the security component 120 ′ may be set to be immutable after storing the security data D_SEC generated from the authenticated input data D_IN. That is, at least one of the user authentication processor 121', the master key generator 122', the decryption processor 123', and the secure storage 124' performs only the operation on the first authenticated input data D_IN. can For example, the security component 120' may include a memory device that stores information on whether an operation is completed for the first authenticated input data D_IN, the user authentication processor 121', the master key At least one of the generator 122', the decryption processor 123', and the secure storage 124' may ignore the input data D_IN provided to the secure component 120' according to the information stored in the memory device, The previously stored security data D_SEC may be protected. In some embodiments, the memory device that stores information on whether the operation on the first authenticated input data D_IN is completed may include an OTP device that irreversibly stores information, such as an anti-fuse, When the operation on the first authenticated input data D_IN is completed, the OTP device may be programmed. In some embodiments, a memory device that stores information on whether an operation on the first authenticated input data D_IN is completed may include a rewritable memory device, and the first authenticated input data D_IN may include a rewritable memory device. When the operation is completed, data indicating the completion may be written to the rewritable memory device.

4 is a flowchart illustrating an exemplary operation of the user authentication processor 121' of FIG. 3 according to an exemplary embodiment of the present disclosure. As described above with reference to FIG. 3 , 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 the input data D_IN to the security component 120 . '), it is possible to authenticate the input data (D_IN) by determining whether it is provided by a legitimate user. Hereinafter, FIG. 4 will be described with reference to FIG. 3 .

Referring to FIG. 4 , an operation of generating an evaluation key from a user identifier (U_ID) may be performed in step S41. For example, the user authentication processor 121 ′ may generate an evaluation key from the user identifier U_ID based on a predetermined method, for example, a mathematical operation, a logical operation, a lookup table, or the like. The user authentication processor 121' is configured such that the evaluation key generated from the user identifier (U_ID) issued to the rightful user of the security component 120' matches the user key (U_KEY) issued at the same time as the user identifier (U_ID), It may be designed by the supplier of the security component 120'.

In step S42, an operation of determining whether the evaluation key matches the user key (U_KEY) may be performed. When the evaluation key and the user key (U_KEY) match, that is, when the user identifier (U_ID) and the user key (U_KEY) included in the input data D_IN are those of a legitimate user of the secure part 120', step S43 An 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, the user identifier (U_ID) and the user key (U_KEY) included in the input data D_IN are the If not, an operation of deactivating the enable signal ENA may be performed in step S44.

5 is a block diagram illustrating an example of the security component 120 of FIG. 1 according to an exemplary embodiment of the present disclosure. As described above with reference to FIG. 1 , the security component 120 ″ of FIG. 5 may receive input data DIN′ provided from the data injection system 200 of FIG. 1 , and secure data D_SEC. may be provided to the authentication request processor 130 of Fig. 1. As shown in Fig. 5, the security component 120" includes a user authentication processor 121", a master key generator 122", and a decryption processor ( 123") and secure storage 124". Compared with the security component 120 ′ of FIG. 3 , the seed SEED may be excluded from the input data D_IN″ received by the security component 120 ″. Hereinafter, content that overlaps with the description of the security component 120' of FIG. 3 among the description of the security component 120 ″ of FIG. 5 will be omitted.

According to an exemplary embodiment of the present disclosure, the master key (M_KEY) in the secure component 120″ may be generated from a user identifier (U_ID) and/or a user key (U_KEY). That is, the secure component 120″. Instead of issuing separate seed information to a legitimate user of the secure component 120", the provider of It can be issued to legitimate users. The user of the secure component 120" can prepare the encrypted data D_ENC by encrypting the security information using the master key provided from the supplier of the secure component 120", and the encrypted data D_ENC and the user data The input data D_IN' including the user identifier U_ID as (D_USR) may be provided 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 a master key (M_KEY) from the user identifier (U_ID) and/or the user key (U_KEY) according to a predetermined method.

FIG. 6 is a diagram illustrating input data D_IN" according to an exemplary embodiment of the present disclosure, and FIG. 7 is a diagram of FIG. 1 receiving input data D_IN" of FIG. 6 according to an exemplary embodiment of the present disclosure. A flowchart illustrating an exemplary operation of the secure component 120 . For example, the input data D_IN″ of 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. 3 . Hereinafter, FIGS. 6 and 7 will be described with reference to FIG. 3 .

Referring 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 , user data (D_USR) may include a user identifier (U_ID), a user key (U_KEY), and a seed (SEED) issued by a legitimate user of the secure component 120 ′ from the supplier of the secure component 120 ′. In , as described above with reference to Fig. 5, the user data (D_USR) may include only the user identifier (U_ID) and the user key (U_KEY) The encrypted data (D_ENC) is described above with reference to Fig. 2 . Similarly, a legitimate user of the secure component 120' may be created by encrypting the security information based on a master key issued from the supplier of the secure 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. That is, security After storing the security data D_SEC, the part 120' permanently sets the security data D_SEC to be immutable when the lock function is activated according to the lock data LOCK of the authenticated input data D_IN" can be

Referring to FIG. 7 , an operation of determining whether to activate the lock function may be performed in step S71. For example, at least one of the user authentication processor 121', the master key generator 122', the decryption processor 123', and the secure storage 124' of the secure component 120' includes the authenticated input data ( D_IN"), it may be determined whether the lock function is activated based on the lock data LOCK. When the lock function is activated according to the lock data LOCK, step S72 may be subsequently performed.

In step S72, an operation of permanently setting the stored security data D_SEC to be immutable 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 storage 124', the secure data (D_SEC) is the secure store 124'. When stored in , the stored security data (D_SEC) can be permanently set to be immutable. That is, at least one of the user authentication processor 121', the master key generator 122', the decryption processor 123', and the secure storage 124' is input data D_IN received after the secure data D_SEC is stored. ) may be set not to perform an operation for As described above with reference to FIG. 3 , the security component 120 ′ may include an OTP element such as an anti-fuse, and the OTP element may be programmed when the lock function is activated. At least one of the user authentication processor 121', the master key generator 122', the decryption processor 123' and the secure storage 124' is based on the programmed OTP element, and then provided to the secure component 120' The input data (D_IN) to be used can be ignored.

Fig. 8 is a diagram illustrating an operation for injecting security information into the secure component 120" over time according to an exemplary embodiment of the present disclosure. Specifically, Fig. 8 is a view showing the secure component 120" and the external It is a diagram showing signals transmitted between the systems 200 , 400 , and 500 over time. As shown in Figure 8, the secure component 120", the data injection system 200, the account issuance system 400, and the data processing system 500 may communicate with each other. Systems 200, 400, 500 ) can transmit and receive signals by communicating in any communication method For example, the systems 200 , 400 , 500 may be connected to a network such as the Internet, and among the systems 200 , 400 , 500 At least two may communicate directly through a dedicated communication channel. Although not shown in FIG. 8 , the security component 120 ″ may be included in a product having a specific purpose (eg, the product 100 of FIG. 1 ). The data injection system 200 and data processing system 500 may communicate with the secure component 120 by sending a signal to or receiving a signal from the product including the secure component 120 ″. Hereinafter, FIG. 8 will be described with reference to FIG. 5 .

The account issuance system 400 may be operated by a supplier of the secure component 120 , and the data injection system 200 and the data processing system 500 may be operated by a legitimate user of the secure component 120 . In this specification, the operation of the system refers not only to being directly operated by an operating entity, for example, a supplier of the secure component 120 and a legitimate user of the secure component 120 , but also to being operated by another entity under the control of the operating entity. can do.

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

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, if the account request received from the data injection system 200 is by a legitimate user of the secure component 120", the account issuance system 400 may An identifier (U_ID), a user key (U_KEY), and a master key (M_KEY) can be generated. The account issuing system 400 may generate a user identifier (U_ID) and a user key (U_KEY) so that the user identifier (U_ID) and the user key (U_KEY) have a certain relationship. That is, since the user identifier (U_ID) is used to generate the evaluation key by the secure component 120", the evaluation key generated from the user identifier (U_ID) of the legitimate user of the secure component 120" is the user key (U_KEY) To match, 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 a 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 certain relationship. That is, as will be described later, the master key (M_KEY) generated by the account issuance system 400 can be used to generate encrypted data (D_ENC) by encrypting security information and is encrypted by the security component 120 ″. Since it is used to decrypt the data D_ENC, the user identifier (U_ID) and/or the user key (U_KEY) of the legitimate user of the security component 120" is the master key (M_KEY) generated by the security component 120" and To match, the account issuing system 400 may generate a master key (M_KEY).

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

In step S83 , the data injection system 200 may transmit the security data D_SEC and the master key M_KEY to the data processing system 500 . That is, the data injection system 200 uses the master key (M_KEY) to generate the encrypted data (D_ENC) from the security data (D_SEC), the security data (D_SEC) and the master key (M_KEY) to the data processing system ( 500) can be transmitted. As described above, the security data D_SEC may include security information about a product including the security component 120 ″.

In step S84 , the data processing system 500 may generate 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, and the encryption method is encrypted in the secure part 120". It may correspond to a method of decrypting the encrypted data D_ENC. The data processing system 500 may use any encryption algorithm to generate the encrypted data D_ENC. For example, the data processing system 500 Based on the master key (M_KEY), DES (Data Encryption Standard), AES (Advanced Encryption Standard), SEED, ARIA (Academy, Research Institute, Agency), LEA (Lightweight Encryption Algorithm), RC4, RSA, ECC (Elliptic) The encrypted data (D_ENC) may be generated using curve cryptography), Digital Signature Standard (DSS), or the like.

In step S85 , the data processing system 500 may 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 the data Operations of processing system 500 may be performed in a single system under the control of secure 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 secure component 120″. That is, the data injection system 200 may provide the input data D_IN" including the user identifier U_ID, the user key U_KEY, and the encrypted data D_ENC to the security component 120".

In step S87, the security component 120" may perform an operation for authenticating the input data D_IN". For example, the user authentication processor 121" of the security component 120" may generate an evaluation key from the user identifier U_ID, and compare the generated evaluation key with the user key U_KEY to input data D_IN ") can be authenticated. When the generated evaluation key and the user key U_KEY match, that is, when authentication of the input data D_IN" is successful, the security component 120" performs step S88 successively. can

In step S88, the secure component 120" may generate a master key M_KEY. For example, the master key generator 122" of the secure component 120" may include a user identifier U_ID and/or a user A master key (M_KEY) may be generated from the key (U_KEY) according to a predetermined method.

In step S89, the security component 120" may generate and store the security data D_SEC. For example, the decryption processor 123" may generate the master key M_KEY generated by the master key generator 122". security data (D_SEC) can be generated by decrypting the encrypted data (D_ENC) using This may not be the case, and as a result, security information encrypted by the master key (M_KEY) can be protected.

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

9 is a flowchart illustrating a method of injecting security information according to 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 , which will be described below with reference to FIG. 1 .

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

In operation S92 , an operation of authenticating the input data D_IN based on the component user data D_USR may be performed. For example, the security component 120 may generate an evaluation key from the user identifier (U_ID) included in the part user data (D_USR), and the user key (U_KEY) and the evaluation key included in the user data (D_USR). By comparing, it can be determined 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 subsequently performed.

In operation S94, an operation of generating the master key M_KEY based on the seed SEED may be performed. For example, the security component 120 may 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 other data in the input data D_IN, and in another embodiment, at least a part of the part user data D_USR of the input data D_IN includes the master key M_KEY. By being used to create it, it can perform the same function as SEED.

In operation 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 may generate the security data D_SEC by decrypting the encrypted data D_ENC in a predetermined manner using the master key M_KEY generated in step S94 .

In step S96, an operation of storing the security data D_SEC may be performed. For example, the security component 120 may store the security data D_SEC in a nonvolatile memory. In an exemplary embodiment, the input data D_IN received by the security component 120 may be ignored so that the security data D_SEC remains unchanged after the security data D_SEC is stored. In another embodiment, as described above with reference to FIGS. 6 and 7 , whether the stored security data D_SEC is changeable may be determined according to the lock data LOCK included in the input data D_IN.

10 is a block diagram illustrating an example of the product 100 of FIG. 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 connectable to the Internet of Things, an application processor (AP) 610 , a bus 620 , a sensor 630 , It may include 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 may be connected to the bus 620 , and may exchange data with each other through the bus 620 .

The Internet of Things (IoT) may refer to a network between things using wired/wireless communication. For example, the Internet of Things (IoT) is an IoT network system, a Ubiquitous Sensor Network (USN) communication system, a Machine Type Communications (MTC) communication system, a Machine Oriented Communication (MOC) communication system, a Machine to Machine (M2M) communication system, or It may be variously referred to as a D2D (Device to Device) communication system.

The application processor 610 may control the overall operation of the IoT device 600 . For example, the application processor 610 may execute applications that provide an Internet browser, a game, a video, and the like. In an embodiment, the 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, or a hexa-core (Hexa-Core). Also, the application processor 610 may further include a cache memory.

The sensor 630 may sense the external environment of the IoT device 600 . In an 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 detects biometric information, and as a non-limiting example, corresponds to the detected information by detecting a fingerprint, an iris pattern, a blood vessel pattern, a heart rate, a blood sugar, etc. sensing data can be generated. According to embodiments, the sensor 630 may include any sensor such as an illuminance sensor, an acoustic sensor, an acceleration sensor, or 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 and/or a flash memory device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), or the like. ) and a non-volatile memory device such as a solid state drive (SSD).

The secure memory 650 may store data requiring security while the IoT device 600 operates. For example, the secure memory 650, similar to the secure storage 124' of FIG. 3, stores security data (D_SEC) including security information for the IoT device 600 that needs protection from inappropriate external access. can be saved According to embodiments, the secure memory 650 may store information detected by the sensor 630 , for example, data including body information. Although the normal memory 640 and the secure memory 650 are illustrated separately in FIG. 10 , the technical spirit of the present disclosure is not limited thereto, and the normal memory 640 and the secure memory 650 are one physical memory. may be integrated and implemented. In one embodiment, normal memory 640 and/or secure memory 650 may be removably coupled to IoT device 600 , eg, normal memory 640 and/or secure memory 650 may include connector pins and / or it may 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 serve to store or read data requiring security in the secure memory 650 while the IoT device 600 operates. For example, the security module 660 may perform at least one operation of the user authentication processor 121 ′, the master key generator 122 ′, and the decryption processor 123 ′ of FIG. 3 , and thus the secure memory The storage and reading of the security data D_SEC stored in the 650 may 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.

The display 670 may output data. For example, the display 670 may output image data sensed using the sensor 630 or data calculated using the application processor 610 .

The input/output device 680 may include parts for receiving the user's input of the IoT device 600 such as a touch pad, a keypad, an input button, etc., and may include parts for outputting a signal such as an LED and a speaker to the outside. may be

11 is a block diagram illustrating an exemplary structure of hardware and software of the IoT device 600 of FIG. 10 according to 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 includes a firmware 721 and a wireless baseband chipset 722 . and a security module 723 .

The IoT device application 710 may control the communication module 720 as a software block, and may be executed by the CPU (eg, the application processor 610 of FIG. 10 ) of the IoT device 700 . Communication module 720, LAN (Local Area Network), WLAN (Wireless Local Area Network) such as Wi-Fi, Bluetooth (Bluetooth), such as WPAN (Wireless Personal Area Network), Wireless USB (Universal Serial Bus), Zigbee ( Zigbee); It may be a wireless communication block capable of exchanging data through Near Field Communication (NFC), Radio-Frequency Identification (RFID), or a mobile communication system.

The firmware 721 may provide an application programming interface (API) 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 connectivity to a wireless communication network. The security module 723 may store data (eg, security data D_SEC in FIG. 1 ) for authenticating the IoT device 700 to access the wireless communication network, and the IoT device 700 for a wireless network service. may perform an operation to authenticate. The security module 723 may authenticate data provided from outside the IoT device 700 (eg, input data D_IN of FIG. 1 ), and secure data from the authenticated data, according to an exemplary embodiment of the present disclosure. can be saved by creating

12 is a diagram illustrating a network system 900 in which a product including a security component is used according to an exemplary embodiment of the present disclosure. Referring to FIG. 12 , the network system 900 manages a communication connection device 910 , a plurality of lighting fixtures 920 and 930 , a server 940 , and a server connected to be communicable with the communication connection device 910 . It may include a computer 950 , a communication base station 960 , a communication network 970 , and a mobile device 980 .

Each of the plurality of lighting devices 920 and 930 installed in an open external space such as a street or a park may include smart engines 921 and 931 . The smart engines 921 and 931 may include a sensor and a communication module that collects information of the surrounding environment, and as a non-limiting example, communicate with other devices in the vicinity according to a communication protocol such as WiFi, Zigbee, LiFi, etc. can do. For example, the smart engine 921 may be connected to communicate with another smart engine 931 , and a WiFi extension technology (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 wired/wireless communication. For high communication efficiency, two or more smart engines (eg, 921 and 931 ) may be connected to the communication connection device 910 as a group.

Each of the smart engines 921 and 931 may store unique information of the lighting fixtures 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 (eg, the input data ( D_IN)) to be safely stored in the smart engines 921 and 931 .

The communication connection device 910 is an access point (AP) capable of wired/wireless communication, and may mediate communication between the communication network 970 and other equipment. The communication connection device 910 may be connected to the communication network 970 by at least one of a wired/wireless method, and for example, may be mechanically accommodated in at least one of the lighting devices 920 and 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 may receive the surrounding environment information collected by the smart engines 921 and 931 through the communication connection device 910 connected to the smart engine 921 of the adjacent lighting fixture 920 . can The communication connection device 910 may send an authentication request to the smart engines 921 , 931 , and based on the authentication response provided by the smart engines 921 , 931 based on the security information stored therein, the smart engines By authenticating 921 and 931 , communication between the smart engines 921 and 931 and the mobile device 980 may be relayed. The mobile device 980 may be connected to the communication network 970 through a wireless cellular communication method such as 3G or 4G through the communication base station 960 .

On the other hand, the server 940 connected to the communication network 970 receives the information collected by the smart engines 921 and 931 of the lighting fixtures 920 and 930 through the communication connection device 910 and at the same time, the lighting Operational states of the devices 920 and 930 may be monitored. In order to manage each of the lighting fixtures 920 and 930 based on the monitoring result of the operating state of the lighting fixtures 920 and 930 , the server 940 may be connected to a computer 950 providing a management system. According to an exemplary embodiment of the present disclosure, server 940 injects security information into smart engines 921 , 931 of lighting fixtures 920 , 930 , similar to data injection system 200 of FIG. 1 . It is possible to provide data for this 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 (eg, U_ID, U_KEY, etc. in FIG. 8 ) provided in advance by the provider of the smart engines 921 and 931 , and the smart It may include data encrypted according to information (eg, M_KEY of FIG. 8 ) provided by the provider of the engines 921 and 931 . The computer 950 may execute software capable of monitoring and managing the operating state of the lighting fixtures 920 and 930 through the smart engines 921 and 931 .

Exemplary embodiments have been disclosed in the drawings and specification as described above. Although the embodiments have been described using specific terms in the present specification, these are used only for the purpose of explaining the technical spirit of the present disclosure and are not used to limit the meaning or the scope of the present disclosure described in the claims. . Therefore, it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible therefrom. Accordingly, the true technical protection scope of the present disclosure should be defined by the technical spirit of the appended claims.

Claims (10)

As a security component included in the product to process input data for authenticating the product,
The security component receives input data including component user data and encrypted data from an external data injection system,
a user authentication processor for authenticating the input data by determining whether the input data is provided by a legitimate user of the security part based on the part user 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 authenticated based on the master key; and
a secure component comprising a secure repository for storing the secure data. The method according to claim 1,
The part user data includes a user identifier and a user key,
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. 3. The method according to claim 2,
The authenticated part user data further includes seed data,
The master key generator, Security component, characterized in that for generating the master key based on the seed data. 3. The method according to claim 2,
The master key generator is configured to generate the master key based on at least one of the user identifier and the user key. The method according to claim 1,
At least one of the user authentication processor, the master key generator, the decryption processor and the secure storage is permanently set so that the stored security data is immutable when the security data is stored in the secure storage. 6. The method of claim 5,
The secure storage includes at least one of a One Time Programmable (OTP) memory and a rewritable memory for storing the secure data. The method according to claim 1,
At least one of the user authentication processor, the master key generator, the decryption processor and the secure storage is permanently set so that the stored security data is immutable according to lock data included in the authenticated input data. security parts. A product that responds to a product authentication request from the outside based on security data stored therein, the product comprising:
a communication interface for receiving input data including encrypted data and part user data from a data injection system external to the product; and
The security data by 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 A product comprising a security component for generating and storing the security data. 9. The method of claim 8,
The security data includes at least one of an identifier of the product, a certificate, a private key, and a pre-shared key. 9. The method of claim 8,
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