Method for using a portable computing device as a smart key device

• US 7,475,247 B2
• Filed: 12/16/2004
• Issued: 01/06/2009
• Est. Priority Date: 12/16/2004
• Status: Active Grant

• Current Assignee: ServiceNow Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Bade, Steven A., Chao, Ching-Yun
• Primary Examiner(s): Vu; Kimyen
• Assistant Examiner(s): Dada; Beemnet W
• Application Number:
  US11/014,067
• Publication Number:
  US 20060133615A1
• Time in Patent Office: 1,482 Days
• Field of Search: 713/164, 713/167, 713/169, 713/172, 713/189, 713/193, 726/9, 726/20, 380/277, 380/281, 380/282, 380/285
• US Class Current: 713/169
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/805 Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• CPC Class Codes: H04L 9/3265 using certificate chains, trees or paths; Hierarchical trust model
• CPC Class Codes: H04L 9/3273 for mutual authentication network architectures or network communication protocols for achieving mutual authentication in a packet data network H04L63/0869

Abstract

A first data processing system, which includes a first cryptographic device, is communicatively coupled with a second data processing system, which includes a second cryptographic device. The cryptographic devices then mutually authenticate themselves. The first cryptographic device stores a private key of a first asymmetric cryptographic key pair and a public key of a second asymmetric cryptographic key pair that is associated with the second data processing system. The second cryptographic device stores a private key of the second asymmetric cryptographic key pair and a public key of the first asymmetric cryptographic key pair that is associated with the first data processing system. In response to successfully performing the mutual authentication operation between the two cryptographic systems, the first data processing system is enabled to invoke sensitive cryptographic functions on the first cryptographic device while the first data processing system remains communicatively coupled with the second data processing system.

Claims

1. A method for performing cryptographic functions, the method comprising:

engaging a first removable hardware device with a first system unit;

engaging a second removable hardware device with a second system unit;

communicatively coupling the first system unit and the second system unit while the first removable hardware device is engaged with the first system unit and the second removable hardware device is engaged with the second system unit;

wherein the first system unit includes a first hardware security unit and the second system unit includes a second hardware security unit,

wherein the first hardware security unit includes a first private key corresponding to a first asymmetric cryptographic key pair, a first public key corresponding to a second asymmetric cryptographic key pair, a second private key corresponding to a third asymmetric cryptographic key pair; and

a second public key corresponding to a fourth asymmetric cryptographic key pair; and

wherein the second hardware security unit contains a third private key corresponding to the second asymmetric cryptographic key pair, a third public key corresponding to the first asymmetric cryptographic key pair, a fourth private key corresponding to the fourth asymmetric cryptographic key pair, and a fourth public key corresponding to the third asymmetric cryptographic key pair;

executing a mutual authentication operation between the first hardware security unit and the first removable hardware device based upon the first and second asymmetric cryptographic key pairs, which the first system unit and the second system unit are communicatively coupled;

executing a mutual authentication operation between the second hardware security unit and the second removable hardware device based upon a fifth and sixth asymmetric cryptographic key pairs while first system unit and the second system unit are communicatively coupled;

executing a mutual authentication operation between the first hardware security unit and the second hardware security based upon the third and fourth asymmetric cryptographic key pairs while the first system unit and the second system unit are communicatively coupled; and

in response to successfully performing the mutual authentication operation between the first and second hardware security units, enabling the first system unit to invoke cryptographic functions on the first hardware security unit while the first and second system units remain communicatively coupled.

2. The method of claim 1, further comprising:

executing a software security unit on the first system unit,

wherein the software security unit contains a seventh private key corresponding to a seventh asymmetric cryptographic key pair and a seventh public key corresponding to a eighth asymmetric cryptographic key pair, and

wherein the first hardware security unit contains an eighth private key corresponding to the eighth asymmetric cryptographic key pair and an eighth public key corresponding to the seventh asymmetric cryptographic key pair;

performing a mutual authentication operation between the software security unit and the first hardware security unit based upon the seventh and eighth asymmetric cryptographic key pairs; and

in response to successfully performing the mutual authentication operation between the software security unit and the first hardware security unit, enabling the software security unit to invoke functions on the first hardware security unit while the first and second system units remain communicatively coupled.

3. The method of claim 2, further comprising performing a cryptographic function by the first hardware security unit for the software security unit in response to a request from the software security unit after successfully performing a mutual authentication operation between the first and second the hardware security units without requiring the first and second system units to remain communicatively coupled.

4. The method of claim 3, further comprising exchanging a session key between the software security unit and the first hardware security unit during the mutual authentication operation between the software security unit and the first hardware security unit.

5. The method of claim 4, further comprising employing the session key by the software security unit to encrypt subsequent requests to the first hardware security unit in order to prove the software security unit'"'"'s identity.

6. The method of claim 2, further comprising, in response to a request from the software security unit, generating a digital certificate for the software security unit by the first hardware security unit while the first and second system units remain communicatively coupled.

7. The method of claim 2, further comprising, in response to a request from the software security unit, digitally signing a data item from the software security unit by the first hardware security unit while the first and second system units remain communicatively coupled.