Multifactor authentication with changing unique values
First Claim
1. A method for multifactor authentication having changing unique values, comprising the steps of:
- maintaining an access history database of transactions made by a user;
maintaining a client device history log on an input device;
receiving a request for a transaction from the input device;
causing the input device to select a subset from the client device history log;
sending the subset along with the request to an authentication server;
comparing the subset to the access history database;
proceeding with the transaction when a match is found between the subset and the access history database; and
terminating the transaction when no match is found between the subset and the access history database.
1 Assignment
0 Petitions
Accused Products
Abstract
A method of authentication includes the steps of providing a transaction service provider having a secure server; providing a user; requesting access authorization to the server of the service provider by the user, the server storing a set of use parameters obtained from the authorization access request, the use parameters including at least several prior location coordinates, methods of access, transaction information and access hardware used during the authentication to be used by the transaction service provider in subsequent requests by the user to access the server, the use parameters used in the authentication to be continually updated with the most recent data.
64 Citations
9 Claims
-
1. A method for multifactor authentication having changing unique values, comprising the steps of:
-
maintaining an access history database of transactions made by a user; maintaining a client device history log on an input device; receiving a request for a transaction from the input device; causing the input device to select a subset from the client device history log; sending the subset along with the request to an authentication server; comparing the subset to the access history database; proceeding with the transaction when a match is found between the subset and the access history database; and terminating the transaction when no match is found between the subset and the access history database. - View Dependent Claims (2, 3)
-
-
4. A computer program product for multifactor authentication having changing unique values, said computer program product comprising:
-
a computer readable medium; first program instructions to maintain an access history database of transactions made by a user; second program instructions maintain a client device history log on an input device; third program instructions to receive a request for a transaction from the input device; fourth program instructions to cause the input device to select a subset from the client device history log; fifth program instructions to send the subset along with the request to an authentication server; sixth program instructions to compare the subset to the access history database; seventh program instructions to proceed with the transaction when a match is found between the subset and the access history database; eighth program instructions to terminate the transaction when no match is found between the subset and the access history database; wherein said first, second, third, fourth, fifth, sixth, seventh, and eighth program instructions are stored on said computer readable media. - View Dependent Claims (5, 6)
-
-
7. A system which performs multifactor authentication with changing unique values, comprising:
-
an access history database of transactions made by a user; a client device history log on an input device; means for receiving a request for a transaction from the input device; means for causing the input device to select a subset from the client device history log; means for sending the subset along with the request to an authentication server; means for comparing the subset to the access history database; means for proceeding with the transaction when a match is found between the subset and the access history database; and means for terminating the transaction when no match is found between the subset and the access history database. - View Dependent Claims (8, 9)
-
Specification