MODULES TO SECURELY PROVISION AN ASSET TO A TARGET DEVICE

• US 20150326567A1
• Filed: 11/06/2014
• Published: 11/12/2015
• Est. Priority Date: 05/07/2014
• Status: Active Grant

• Current Assignee: Cryptography Research, Inc. (Rambus Inc.)
• Original Assignee: Cryptography Research, Inc. (Rambus Inc.)
• Inventors: Hamburg, Michael, Jun, Benjamin Che-Ming, Kocher, Paul C., O'Loughlin, Daniel, Pochuev, Denis Alexandrovich
• Granted Patent: US 10,015,164 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 21/72 in cryptographic circuits
• CPC Class Codes: G06F 21/73 by creating or determining hardware identification, e.g. serial numbers
• CPC Class Codes: G06F 2221/2107 File encryption
• CPC Class Codes: G06F 2221/2135 Metering
• CPC Class Codes: G06F 2221/2145 Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G06F 2221/2153 Using hardware token as a secondary aspect
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/062 for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04W 12/0431 Key distribution or pre-distribution; Key agreement
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning

Abstract

The embodiments described herein describe technologies for Module management, including Module creation and Module deployment to a target device in an operation phase of a manufacturing lifecycle of the target device in a cryptographic manager (CM) environment. One implementation includes a Root Authority (RA) device that receives a command to create a Module and executes a Module Template to generate the Module in response to the command. The Module is deployed to an Appliance device. A set of instructions of the Module, when executed by the Appliance device, results in a secure construction of a sequence of operations to securely provision a data asset to the target device. The Appliance device is configured to distribute the data asset to a cryptographic manager (CM) core of the target device.

Claims

1. A method comprising:

receiving, by a Root Authority (RA) device, a command to create a Module, wherein the Module is a first application that securely provisions a data asset to a target device in an operation phase of a manufacturing lifecycle of the target device;

in response to the command, executing a Module Template by the RA device to generate the Module, wherein the Module Template is a second application that defines a set of instructions for the Module and the data asset; and

deploying the Module to an Appliance device, wherein the set of instructions of the Module, when executed by the Appliance device, results in a secure construction of a sequence of operations to securely provision the data asset to the target device, wherein the Appliance device is configured to distribute the data asset to a cryptographic manager core of the target device.

2. The method of claim 1, further comprising receiving a pre-computed data (PCD) asset containing the data asset, and wherein executing the Module Template comprises generating the Module with the PCD asset.

3. The method of claim 2, further comprising retrieving a key from a Root database, and wherein executing the Module Template comprises generating the Module with the PCD asset and the key.

4. The method of claim 2, further comprising receiving input from a RA operator, the input comprising arguments associated with a specific transaction type, wherein executing the Module Template comprises generating the Module with the PCD asset and the arguments.

5. The method of claim 4, wherein executing the Module Template comprises generating the Module with the PCD asset, the arguments and a placeholder for data to be provided by the Appliance device.

6. The method of claim 1, wherein deploying the Module comprises storing, by the RA device, the Module in a removable storage device to transfer the Module to a Service device, wherein the Service device is configured to distribute the Module over a network to the Appliance device.

7. The method of claim 1, further comprising:

generating a Module deployment authorization by the RA device; and

storing, by the RA device, the Module deployment authorization to a removable storage device to transfer the Module deployment authorization to a Service device, wherein the Service device is configured to distribute the Module deployment authorization over a network to the Appliance device.

8. The method of claim 1, further comprising signing the Module by the RA device with a root Module private key.

9. A method comprising:

receiving, by an Appliance device, a Module over a network from a Service device;

receiving, by the Appliance device, a communication from a cryptographic manager (CM) client library of a tester device, wherein the communication comprises an argument from the CM client library;

in response to the communication, invoking the Module by the Appliance device to generate a Module sequence based on the argument; and

sending, by the Appliance device, the Module sequence to the CM client library, wherein a tester script of the tester device delivers the Module sequence a CM Core of a target device in an operation phase of a manufacturing lifecycle of the target device.

10. The method of claim 9, further comprising:

assembling, by a hardware security module (HSM) on the Appliance device, tester information and a pre-computed data (PCD) asset;

signing, by the HSM, a delegate signing block (DSB); and

creating, by the HSM, the Module sequence with the tester information, PCD asset and the DSB.

11. The method of claim 10, wherein the tester device is configured to deliver the Module sequence to the CM Core of the target device as part of a test script.

12. A Root Authority (RA) device comprising:

a processor; and

a removable storage device interface configured to connect to a removable storage device, wherein the removable storage device interface is coupled to the processor, wherein the processor is operable to;

receive a command to create a Module, wherein the Module is a first application that securely provisions a data asset to a target device in an operation phase of a manufacturing lifecycle of the target device;

in response to the command, execute a Module Template to generate the Module, wherein the Module Template is a second application that defines a set of instructions for the Module and the data asset; and

deploy the Module to an Appliance device, wherein the set of instructions of the Module, when executed by the Appliance device, results in a secure construction of a sequence of operations to securely provision the data asset to the target device, wherein the Appliance device is configured to distribute the data asset to a cryptographic manager core of the target device.

13. The RA device of claim 12, wherein the processor is further operable to create the Module using pre-computed data (PCD).

14. The RA device of claim 12, wherein the processor is further operable to create the Module using at least one of a pre-computed data (PCD) asset or an argument associated with a specific transaction type.

15. The RA device of claim 12, wherein the processor is further operable to create the Module using a placeholder for data to be provided by the Appliance device.

16. The RA device of claim 12, wherein the processor is further operable to store the Module in the removable storage device via the removable storage device interface to transfer the Module to a Service device, wherein the Service device is configured to distribute the Module over a network to the Appliance device.

17. The RA device of claim 12, wherein the processor is further operable to:

generate a Module deployment authorization; and

store the Module deployment authorization to a removable storage device via the removable storage device interface to transfer the Module deployment authorization to a Service device, wherein the Service device is configured to distribute the Module over a network to the Appliance device.

18. An Appliance device comprising:

a processor;

a network interface coupled to the processor; and

a tester device interface coupled to the processor, wherein the processor is operable to;

receive a Module over the network interface from a Service device;

receive a communication over the tester device interface from a cryptographic manager (CM) client library of a tester device, wherein the communication comprises an argument from the CM client library;

in response to the communication, invoke the Module to generate a Module sequence based on the argument; and

send the Module sequence to the CM client library to be run by the tester device to deliver the Module sequence to a CM Core of a target device in an operation phase of a manufacturing lifecycle of the target device.

19. The Appliance device of claim 18, further comprising a hardware security module (HSM), wherein the HSM is operable to:

assemble tester information and a pre-computed data (PCD) asset;

sign a delegate signing block (DSB); and

create the Module sequence with the tester information, PCD asset and the DSB.

20. The Appliance device of claim 18, wherein the tester device is configured to deliver the Module sequence to the CM Core of the target device as part of a test script.