ABDS method utilizing security information in authenticating entity access

• US 6,950,940 B2
• Filed: 01/31/2003
• Issued: 09/27/2005
• Est. Priority Date: 08/04/2000
• Status: Expired due to Term

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Wheeler, Lynn Henry, Wheeler, Anne M.
• Primary Examiner(s): Zand, Kambiz
• Application Number:
  US10/248,606
• Publication Number:
  US 20030131235A1
• Time in Patent Office: 970 Days
• Field of Search: 713/175, 713/176, 713/182, 713/201, 713/161, 713/168, 713/169, 713/170, 713/180, 380/278, 380/282, 708/135, 379/93.02
• US Class Current: 713/182
• CPC Class Codes: G06F 21/32 using biometric data, e.g. fingerprints, iris scans or voiceprints
• CPC Class Codes: G06F 2221/2113 Multi-level security, e.g. mandatory access control
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/3558 Preliminary personalisation for transfer to user
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/3676 Balancing accounts
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 20/3825 Use of electronic signatures
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/388 using mutual authentication without cards, e.g. challenge-response
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 20/403 : Solvency checks
• CPC Class Codes: G06Q 20/40975 : using encryption therefor
• CPC Class Codes: G06Q 50/188 : Electronic negotiation
• CPC Class Codes: G07F 7/0886 : the card reader being portable for interacting with a POS or ECR in realizing a payment transaction
• CPC Class Codes: G07F 7/1008 : Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: G07F 7/1016 : Devices or methods for securing the PIN and other transaction-data, e.g. by encryption arrangements for secret communication, see H04L9/00
• CPC Class Codes: H04L 2209/42 : Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 2209/56 : Financial cryptography, e.g. electronic payment or e-cash
• 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/0442 : wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• 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/0823 : using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/083 : using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/12 : Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 9/321 : involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3247 : involving digital signatures

Abstract

Authenticating an entity for access to a controlled resource by an access authentication component for the controlled resource includes the steps of: the requesting entity initially opening a security account with the access authentication component, with the access authentication component establishing and maintaining a record including information pertaining to the account and being retrievable based on a unique identifier for the requesting entity, and associating a public key of a public-private key pair with the record; the requesting entity originating an electronic message and generating a digital signature using a private key of the key pair, and sending the digitally signed electronic message to the access authentication component with the unique identifier; authenticating the electronic message using the public key associated with the record identified by the unique identifier; and upon successful authentication, authenticating access to the controlled resource. Security information is considered in authenticating the requesting entity.

Claims

1. A method of providing a requesting entity with access to a controlled resource, the requesting entity communicating electronically over a communications medium with an access authentication component for the controlled resource, wherein the requesting entity possesses a secure device that maintains therein a private key of a public-private key pair and wherein the secure device is adapted to generate digital signatures using the private key, comprising the steps of:

(a) providing the requesting entity with a security account maintained in a database of the access authentication component, information in the security account being retrievable by the access authentication component based on a unique identifier of the requesting entity, the information identifying the requesting entity'"'"'s authority to access the controlled resource;

(b) associating in the database the public key of the public-private key pair with the security account such that the public key is retrievable by the access authentication component based on the unique identifier;

(c) associating a security profile of the secure device with the security account such that the security profile is retrievable by the access component based on the unique identifier, the security profile identifying security features of the secure device, the security features indicative of the relative security strength of the secure device as compared to the other devices capable of generating digital signatures;

(d) wherein the access authentication component performs the steps of;

(i) receiving the unique identifier of the requesting entity;

(ii) receiving a message and a digital signature of the message;

(iii) based on the unique identifier, obtaining the public key of the requesting entity and the security profile of the secure device;

(iv) using the public key obtained from the database, decrypting the digital signature to verify that the digital signature was generated using the private key of the secure device;

and, (e) if the digital signature verifies, granting the requesting entity with access to the controlled resource as a function of the information pertaining to the requesting entity'"'"'s authority to access the controlled resource and as a function of the relative security strength of the secure device.

2. The method of claim 1 wherein the relative security strength of the secure device is indicative of the uniqueness of the private key.

3. The method of claim 1 wherein the relative security strength of the secure device is indicative of a likelihood that the private key of the secure device has been compromised.

4. The method of claim 1 wherein access to the controlled resource is granted only if the security strength of the secure device exceeds a minimum threshold required for access to the controlled resource.

5. The method of claim 1 wherein the step of granting the requesting entity with access to the controlled resource further comprises generating an access authentication signal for use by the controlled resource.

6. The method of claim 1 wherein the message comprises the unique identifier.

7. The method of claim 1 wherein the message includes the security profile of the secure device.

8. The method of claim 1 wherein the step of decrypting the digital signature of the message using the public key further comprises generating a message digest of the message and comparing the message digest with the decrypted digital signature.

9. The method of claim 1 wherein a portion of the message is input into the secure device before the digital signature is generated by the secure device.

10. In a system for authenticating a requesting entity for access to a controlled resource in which access to the controlled resource is controlled by an access authentication component, wherein the requesting entity possesses a secure device that maintains therein a private key of a public-private key pair and wherein the access authentication component does not reside in and is not part of the secure device, a method comprising the steps of:

(a) providing the requesting entity with a security account maintained in a database, information in the security account being retrievable by the access authentication component based on a unique identifier of the requesting entity;

(b) associating the public key of the public-private key pair with the security account such that the public key is retrievable based on the unique identifier;

(c) associating a security profile of the secure device with the security account such that the security profile is retrievable based on the unique identifier, the security profile identifying security features of the secure device;

(c) generating a digital signature of a message using the private key of the secure device, the message comprising a request by the requesting entity for access to the controlled resource;

(e) transmitting over a communications medium an electronic communication to the access authentication component, the electronic communication including the unique identifier of the requesting entity, the message, and the digital signature of the message;

(f) wherein the access authentication component performs the steps of;

(i) receiving the electronic communication;

(ii) based on the unique identifier in the electronic communication, obtaining the public key of the requesting entity and the security profile of the secure device;

(iii) using the public key obtained from the record, decrypting the digital signature to verify that the digital signature was generated using the private key of the secure device; and

(iv) determining the relative likelihood that the digital signature was in fact generated by the secure device based on the security features of the secure device.

11. The method of claim 10 further comprising granting the requesting entity with access to the controlled resource based on said determination.

12. The method of claim 11 wherein the database is maintained by the access authentication component.

13. The method of claim 11 wherein the database is maintained by a third party other than the requesting entity and access authentication component.

14. The method of claim 11 wherein the controlled resource is a database of accounts and wherein the step of granting the requesting entity with access to the controlled resource includes enabling the requesting entity to view one of the accounts in the database.

15. The method of claim 10 further comprising the step of establishing an account with the controlled resource on behalf of the requesting entity.

16. The method of claim 15 wherein the message includes an instruction regarding the account of the controlled resource.

17. A method of providing access to an entity requesting access to a controlled resource, the requesting entity communicating electronically over a communications medium with an access authentication component for the controlled resource, comprising the steps of:

(a) providing the requesting entity with a security account maintained in a database accessible by the access authentication component, the security account having information that is retrievable based on a unique identifier, the information pertaining to the requesting entity'"'"'s right to access the controlled resource, the information further including security features of a genuine device that generates digital signatures using a private key of a public-private key pair, wherein the genuine device does not reside in and is not part of the access authentication component;

(b) associating the public key of the genuine device with the security account such that the public key is retrievable based on the unique identifier in the database;

(c) thereafter,

(i) receiving an electronic communication including the unique identifier, a message, and a digital signature of the message, the digital signature generated by a suspect device and the message comprising a request for access to the controlled resource;

(ii) obtaining the public key associated with the unique identifier received;

(iii) authenticating the message using the public key associated with the unique identifier;

(iv) upon successful authentication, identifying the security features retrievable by the unique identifier as being the security features of the genuine device; and

(v) granting the requesting entity with access to the controlled resource in response to the request as a function of the information pertaining to the requesting entity'"'"'s right to access the controlled resource and as a function of the relative likelihood that the digital signature generated by the suspect device was actually generated by the genuine device based on the security features of the genuine device.

18. The method of claim 17 wherein the security features of the genuine device as indicative of the uniqueness of the private key in the genuine device.

19. The method of claim 17 wherein the security features are indicative of a likelihood that the private key of the genuine device has been compromised.

20. The method of claim 17 wherein access to the controlled resource is granted only if the security features of the genuine device exceed a minimum threshold of reliability.

21. The method of claim 17 wherein the database is maintained by the access authentication component.

22. The method of claim 17 wherein the data is maintained by a third party other than the requesting entity and access authentication component.

23. The method of claim 17 wherein the controlled resource is a database of accounts and wherein the step of granting the requesting entity with access to the controlled resource includes enabling the requesting entity to view one of the accounts in the database.