Multi-factor authentication using a smartcard

• US 8,245,292 B2
• Filed: 11/15/2006
• Issued: 08/14/2012
• Est. Priority Date: 11/16/2005
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Buer, Mark
• Primary Examiner(s): Barron, Jr., Gilberto
• Assistant Examiner(s): Okeke, Izunna
• Application Number:
  US11/599,328
• Publication Number:
  US 20070118745A1
• Time in Patent Office: 2,099 Days
• Field of Search: 726/4, 726/5, 726/6, 726/7, 726/9, 726/18, 726/19, 726/20, 713/172, 713/185, 713/168, 713/170
• US Class Current: 726/20
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• 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 2463/082 applying multi-factor authentication cryptographic mechanisms or cryptographic arrangements including means for verifying the identity or authority of a user of the system or for message authentication H04L9/32
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0838 using one-time-passwords
• 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 9/0825 using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
• CPC Class Codes: H04L 9/3228 One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Methods and systems are provided for non-cryptographic capabilities of a token such as a smartcard to be used as an additional authentication factor when multi-factor authentication is required. Smartcards are configured to generate a transaction code each time a transaction is attempted by the smartcard. The transaction code is dynamic, changing with each transaction, and therefore is used as a one-time password. When a user attempts to access a service or application requiring at least two authentication factors, a secure processor is used to read transaction code from the smartcard. The secure processor establishes a secure communication with the remote computer hosting the service or application. The transaction code can then be encrypted prior to transmission over the public Internet, providing an additional layer of security.

Claims

1. A method for performing multi-factor authentication in a processor using a non-cryptographic capability of a smartcard as an authentication factor, comprising:

(a) requesting access to a device;

(b) receiving at least one request for authentication using at least two authentication factors;

(c) receiving authentication data associated with a first authentication factor;

(d) receiving authentication data associated with a second authentication factor from a smartcard, wherein step (d) includes;

(i) establishing communication between the processor and the smartcard,

(ii) simulating a financial payment transaction request with the smartcard to cause the smartcard to generate a transaction code, wherein the simulated financial payment transaction request includes a monetary transaction amount of zero, and

(iii) receiving the transaction code from the smartcard, wherein the transaction code monotonically increases each time a financial payment transaction is attempted with the smartcard;

(e) communicating both the authentication data associated with the first authentication factor and a one-time password determined based on the transaction code as the authentication data associated with the second authentication factor to the device; and

(f) receiving authorization to access the requested device if the first authentication data and the second authentication data were verified.

2. The method of claim 1, wherein the device is remote from the processor.

3. The method of claim 1, wherein the processor is local to the device.

4. The method of claim 1, wherein the authentication data associated with the first authentication factor includes a user identifier and a password.

5. The method of claim 1, wherein the authentication data associated with the first authentication factor includes a biometric template.

6. The method of claim 1, wherein the processor is a secure processor.

7. The method of claim 1, wherein step (e) further includes:

establishing a secure communications session with the device.

8. The method of claim 7, wherein establishing a secure communications session with the device includes:

(i) transmitting a message to the device including a digital certificate for a secure processor;

(ii) receiving a message from the device including an encrypted symmetric key if the device successfully validated the digital certificate for the secure processor, wherein the symmetric key is encrypted with a public key of the secure processor;

(iii) decrypting the encrypted symmetric key with a private key of the secure processor; and

(iv) engaging in secure communications using the symmetric key to encrypt and decrypt communications.

9. A method for performing multi-factor authentication in a remote computer using a non-cryptographic capability of a smartcard as an authentication factor, comprising:

(a) receiving a request from a device to access the remote computer;

(b) requesting authentication using at least two authentication factors from the requesting device;

(c) receiving authentication data associated with a first authentication factor;

(d) receiving a one-time password, determined based on a transaction code for a simulated financial payment transaction from the smartcard, as the authentication data associated with a second authentication factor, wherein the simulated financial payment transaction includes a monetary transaction amount of zero;

(e) verifying the authentication data associated with the first authentication factor;

(g) verifying the authentication data associated with the second authentication factor; and

(f) authorizing access to the remote computer if the authentication data associated with the first authentication factor and the authentication data associated with the second authentication factor are successfully verified.

10. The method of claim 9, wherein the authentication data associated with the first authentication factor includes a user identifier and a password.

11. The method of claim 9, wherein the authentication data associated with the first authentication factor includes a biometric template.

12. The method of claim 9, wherein step (g) includes:

(i) determining an expected transaction code for the smartcard; and

(ii) determining whether the received authentication data associated with the second authentication factor matches the expected transaction code.

13. The method of claim 12, wherein step (g)(i) includes generating a one-time password based on the expected transaction code and step (g)(ii) includes determining whether the received authentication data associated with the second authentication factor matches the generated one-time password.

14. The method of claim 9, wherein step (g) includes:

(i) transmitting a financial payment transaction request to a verification server for validation, wherein the financial payment transaction request includes the transaction code; and

(ii) receiving a validation response, wherein the validation is successful if the transmitted transaction code matches a transaction code for the smartcard expected by the verification server.

15. The method of claim 14, wherein the transaction code monotonically increases each time a financial payment transaction is attempted with the smartcard.

16. The method of claim 9, further comprising:

prior to step (d), establishing a secure communications session with the device.

17. The method of claim 16, wherein establishing the secure communications session with the device includes:

(i) receiving a message from the device, the message including a digital certificate including a public key for the device;

(ii) validating the received digital certificate;

(iii) generating a symmetric key;

(iv) encrypting the generated symmetric key with the public key of the device; and

(v) transmitting the encrypted symmetric key to the device; and

(vi) engaging in secure communications using the symmetric key to encrypt and decrypt communications.

18. A device for performing multi-factor authentication using a non-cryptographic capability of a smartcard as an authentication factor, comprising:

a smartcard reader for receiving a one-time password determined based on a transaction code for a simulated financial payment transaction from a smartcard, wherein the smartcard reader is within a secure boundary and wherein the simulated financial payment transaction request includes a monetary transaction amount of zero;

a processor for establishing a secure communications session with a remote computing device and for securely transmitting the received one-time password as an additional authentication factor to the remote computing device.

19. The device of claim 18, wherein the processor is integrated into a computing device.

20. The device of claim 18, wherein the processor is coupled to a computing device.

21. The device of claim 18, wherein the transaction code monotonically increases each time a financial payment transaction is attempted with the smartcard.