System and Method for Developing Computer Chips Containing Sensitive Information

• US 20100161996A1
• Filed: 12/23/2008
• Published: 06/24/2010
• Est. Priority Date: 12/23/2008
• Status: Abandoned Application

• Current Assignee: Exar Corporation (Maxlinear Incorporated)
• Original Assignee: Exar Corporation (Maxlinear Incorporated)
• Inventors: Savarda, Raymond R., Whiting, Douglas L.
• Application Number:
  US12/343,306
• Publication Number:
  US 20100161996A1
• Time in Patent Office: Days
• US Class Current: 713/189
• CPC Class Codes: H04L 9/0877 using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

A system and method for developing a software program containing sensitive information requires the use of a developer key (a unique public/private key pair) to download the software onto a uniquely identified developer chip. The software program can then be developed and debugged on the developer chip. After being developed and debugged, the software program is transferred to a uniquely identified release chip for subsequent use. Specifically, transfer of the software program requires use of a release key (also a public/private key pair) that is different from the developer key. The private key part of the developer key, as well as all developer chips (albeit a limited number) are protected by strict security procedures.

Claims

1. A system for creating a software program, wherein the software program includes sensitive information protected by a cryptographic boundary, the system comprising:

a developer chip formed with a means for fixing its unique identification as a developer chip, wherein the software program, with its sensitive information, is downloaded onto the developer chip for developing and debugging the software on the developer chip; and

a release chip formed with a means for fixing its unique identification as a release chip and for preventing its use as a developer chip, wherein, after development and debugging of the software on the developer chip, the software program with its sensitive information is transferred to the release chip for use of the software.

2. A system as recited in claim 1 wherein the identification fixing means of the developer chip and the identification fixing means of the release chip are each part of a One Time Programmable (OTP) non-volatile memory.

3. A system as recited in claim 1 wherein the developer chip and the release chip have a same silicon structure.

4. A system as recited in claim 1 wherein downloading the software onto the developer chip requires use of a digital signature established by a developer key.

5. A system as recited in claim 4 wherein the developer key includes debug code for developing and debugging the software.

6. A system as recited in claim 4 wherein transferring the software to the release chip requires use of a digital signature established by a release key.

7. A system as recited in claim 6 wherein the developer key is a private/public key pair, and wherein the release key is a private/public key pair.

8. A system as recited in claim 1 wherein a predetermined plurality of developer chips are created.

9. A system as recited in claim 8 wherein each developer chip is individually marked, inventoried, and monitored to track its physical location at all times.

10. A system as recited in claim 1 wherein the developer chip and the release chip each include sensitive information to be protected by the cryptographic boundary in the software.

11. A system for developing and debugging a software program wherein the software program includes sensitive information protected by a cryptographic boundary, the device comprising:

a developer key for downloading the software program, with its sensitive information, onto a developer chip, wherein the developer key signs code to develop and debug the software program and its sensitive information on the developer chip, and further wherein the developer chip has an electronic latch activated to identify it as a developer chip; and

a release key for signing the developed and debugged software program, and its sensitive information, to download the software program to a release chip for use of the software program, wherein the release chip has an electronic latch irreversibly activated to prevent its use as a developer chip.

12. A system as recited in claim 11 wherein the release chip and the developer chip have a same silicon structure.

13. A system as recited in claim 11 wherein the electronic latch on the developer chip is part of a One Time Programmable (OTP) non-volatile memory, and the electronic latch on the release chip is part of a One Time Programmable (OTP) non-volatile memory.

14. A system as recited in claim 11 wherein the developer key is a private/public key pair and the release key is a private/public key pair.

15. A system as recited in claim 14 wherein each developer chip is individually marked, inventoried, and monitored to track its physical location at all times.

16. A method for creating a software program wherein the software program includes sensitive information protected by a cryptographic boundary, the method comprising the steps of:

identifying at least one developer chip and at least one release chip by activating an electronic latch to identify the developer chip, and by irreversibly activating an electronic latch to prevent use of the release chip as a developer chip;

downloading the software program with its sensitive information onto the developer chip;

employing debug code to develop and debug the software program and its sensitive information on the developer chip;

removing the debug code from the software program, after the employing step;

testing the software program on the developer chip, after the removing step;

repeating the employing step, the removing step, and the testing step in sequence, if necessary; and

transferring the developed and debugged software to the release chip for use of the software program.

17. A method as recited in claim 16 further comprising the steps of:

using a digital signature established by a developer key to accomplish the downloading step, wherein the developer key is a private/public key pair;

using a digital signature established by a release key to accomplish the transferring step, wherein the release key is a private/public key pair; and

protecting the respective private keys of the developer key and the release key.

18. A method as recited in claim 16 wherein the electronic latch on the developer chip is part of a One Time Programmable (OTP) non-volatile memory, and the electronic latch on the release chip is part of a One Time Programmable (OTP) non-volatile memory.

19. A method as recited in claim 18 wherein the developer chip and the release chip have a same silicon structure.

20. A method as recited in claim 16 further comprising the steps of:

uniquely marking each developer chip in a plurality of developer chips;

inventorying the plurality of developer chips; and

monitoring each developer chip to track its physical location at all times.