Authenticating a user includes providing a plurality of questions based on user related information stored in at least one data source, wherein none of the plurality of questions is password related. At least one of the plurality of questions is presented to the user in response to receiving a request from the user to access one or more protected resources. access is granted to the authorized set of protected resources if the user correctly answers each of the at least one questions presented. According to the present invention, the user's identity is authenticated without requiring the user to provide a password or biometric data, and without requiring the user to enroll prior to access.
|
1. A method for authenticating a user, comprising;
obtaining authorized access to a plurality of data sources;
identifying a plurality of fields in the plurality of data sources, wherein each field stores a value known to the user;
for each identified field, generating at least one question whose correct answer is the value stored in the field; wherein none of the questions is password related;
for each generated question, associating the generated question with the identified field and with the plurality of data sources;
in response to receiving a request from the user to access at least one of a plurality of protected resources,
presenting to the user at least one generated question, by:
transmitting to the user a first generated question;
in response to receiving an answer to the first generated question from the user;
identifying the data source and the field associated with the first generated question;
using an indication of the user's identity to query and retrieve from the data source the correct answer;
comparing the user's answer with the retrieved correct answer; and
discarding the retrieved correct answer after the compare;
transmitting to the user a next generated question only if the user's answer is correct; and
repeating the comparing and transmitting steps until each of the at least one generated questions presented has been answered correctly, wherein a number of generated questions the user must answer correctly is determined based on a level of security required to access the at least one protected resource;
granting access to the at least one protected resource if the user correctly answers each of the at least one generated questions presented, whereby a user's identity is authenticated without requiring the user to provide a password or biometric data, and without requiring the user to enroll prior to access;
denying access to the protected resource if the user incorrectly answers any of the at least one generated questions presented; and
transmitting an alert message indicating that an attempt to access the protected resource by the user was unsuccessful.
11. A computer readable medium containing programming instructions for authenticating a user comprising instructions for:
obtaining authorized access to a plurality of data sources;
identifying a plurality of fields in the plurality of data sources, wherein each field stores a value known to the user;
for each identified field, generating at least one question whose correct answer is the value stored in the field;
for each generated question, associating the generated question with the identified field and with the plurality of data sources;
in response to receiving a request from the user to access at least one of a plurality of protected resources,
presenting to the user at least one generated question by
transmitting to the user a first generated question;
in response to receiving an answer to the first generated question from the user;
identifying the data source and the field associated with the first generated question presented;
using the indication of the user's identity to retrieve from the data source the correct answer;
comparing the user's answer with the retrieved correct answer; and
discarding the retrieved correct answer after the comparing;
transmitting to the user a next generated question only if the user's answer is correct; and
repeating the comparing and transmitting steps until each of the at least one generated questions presented has been answered correctly, wherein a number of generated questions the user must answer correctly is determined based on a level of security required to access the at least one protected resource; and
granting access to the at least one protected resource if the user correctly answers each of the at least one generated questions presented, whereby a user's identity is authenticated without requiring the user to provide a password or biometric data, and without requiring the user to enroll prior to access;
denying access to the protected resource if the user incorrectly answers any of the at least one generated questions presented; and
transmitting an alert message indicating that an attempt to access the protected resource by the user was unsuccessful.
16. An authentication server for authenticating a user comprising:
a processor for executing an identity management service (IMS) application, wherein the MS application obtains authorized access to at least one of a plurality of external data sources, identifies a plurality of fields in the at least one external data source, wherein each field stores a value known to the user, generates, for each identified field, at least one challenge question whose correct answer is the value stored in the field, and associates each challenge question with the identified field and with the at least one external data source;
memory for storing the challenge questions;
a communication interface for receiving a request from the user to access at least one protected resource, for transmitting at least one challenge question to the user; and for receiving from the user an answer to the at least one challenge question;
a query module for identifying the data source and the field associated with the at least one generated question presented to the user, composing a query that includes the user's identity and the field, submitting the query to the data source, and receiving from the data source a correct answer to the question presented; and
a compare module coupled to the query module for comparing the user's answer to the correct answer, and for discarding the correct answer received from the data source after the comparing,
wherein the IMS application transmits to the user a next challenge question only if the user's answer is correct; and repeats the comparing and transmitting steps until each of the at least one challenge questions presented has been answered correctly, wherein a number of challenge questions the user must answer correctly is determined based on a level of security required to access the at least one protected resource, wherein the IMS application determines whether the user's answer is correct and authenticates the user if the user correctly answers the at least one challenge question; and wherein the IMS application denies access to the protected resource if the user incorrectly answers any of the at least one generated questions presented, and transmits an alert message indicating that an attempt to access the protected resource by the user was unsuccessful.
6. An identity management system for authenticating a user comprising:
a plurality of data sources for storing user related information, wherein at least one of the data sources is either a private database or a public database with restricted access; and
a server coupled to the at least one data source, wherein the server includes:
a processor for executing an identity management service (IMS) application, wherein the IMS application functions for:
obtaining authorized access to the at least one data source;
identifying a plurality of fields in the at least one data source, wherein each field stores a value known to the user;
generating, for each identified field, at least one question whose correct answer is the value stored in the field;
associating the least one generated question for each identified field with the identified field and with the data source; and
a communication interface for transmitting to the user the at least one generated question in response to receiving a request from the user to access at least one of a plurality of protected resources, and for receiving an answer to the at least one generated question from the user,
a query module for identifying the data source and the field associated with the at least one generated question transmitted to the user, composing a query that includes an identity of the user and the field, submitting the query to the data source, and receiving from the data source a correct answer to the question transmitted; and
a compare module coupled to the query module for comparing the user's answer to the correct answer, and for discarding the correct answer received from the data source after the compare,
wherein the IMS application transmits to the user a next generated question only if the user's answer is correct, and repeats the comparing and transmitting steps until each of the at least one generated questions transmitted has been answered correctly, wherein the IMS application authenticates the user without requiring a password or biometric data, and without requiring the user to enroll, and wherein the IMS application denies access to the protected resource if the user incorrectly answers any of the at least one generated questions presented and transmits an alert message indicating that an attempt to access the protected resource by the user was unsuccessful.
2. The method of
receiving from the user an indication of the user's identity, wherein the indication is not a password or biometric data.
3. The method of
encrypting the user's answer and the retrieved correct answer prior to comparing the answers; and
discarding the encrypted answers after comparing the answers.
4. The method of
5. The method of
7. The system of
8. The system of
9. The system of
10. The system of
12. The computer readable medium of
receiving from the user an indication of the user's identity, wherein the indication is not a password or biometric data.
13. The computer readable medium of
encrypting the user's answer and the retrieved correct answer prior to comparing the answers; and
discarding the encrypted answers after comparing the answers.
14. The computer readable medium of
15. The computer readable medium of
17. The server of
|
The present invention relates to identity management, and more particularly to authenticating a user without prior user enrollment.
The Internet environment is characterized by many online resources and services that are purchased by a user or an employer of a user. To protect such resources and services from unauthorized use, i.e., use by an individual who has not purchased the resource or service, user authentication techniques are implemented that typically require an authorized user to provide a valid password prior to accessing the resource or service. Typically, one or more of the following processes are required to set up an authentication service for a user:
A Provisioning Process: In a corporate environment where employees are granted access to corporate resources and services, a new employee typically completes a provisioning process. This process involves setting up the new employee by recording various items of personal information, providing authorization to utilize various corporate resources and services, and assigning an employee identifier and initial passwords for authorized services. When the provisioning process is completed, the new employee is eligible to register or enroll in various services within the corporate environment.
An Enrollment Process: Once the new employee has completed the provisioning process, he or she enrolls in services offered by the corporation. The enrollment process typically requires the new employee to utilize the initially assigned passwords to access services, and once granted access, to fill out a questionnaire containing information of a personal nature.
A Password Creation Process: Once the new employee has enrolled in one or more services, he or she may be allowed to change the initially assigned passwords to user specified passwords.
Once the user has completed the provisioning, enrollment, and password creation processes, access to the service or resource is protected from unauthorized use. Accordingly, an individual who fails to present a valid password will be denied access to the service or resource.
While the above described authentication process is effective for its intended purpose, it is, without doubt, a time consuming and tedious process for the user who must enroll or register with each protected service or resource prior to use. Moreover, if the user forgets the password, the user will be required to contact a system administrator, typically “help desk” personnel, or some other service that has the ability to verify the user's identity and to issue a temporary password so that the user can reset his or her password. This presents significant added costs because “help desk” personnel must be hired or a service must be engaged. Another disadvantage of the typical password-oriented approach is that the passwords and personal information of users must be encrypted and stored in a protected database or in a directory in the protected service or resource. This presents additional costs and poses a security risk for having the confidential and private information misappropriated.
In order to alleviate some of the burdens associated with the authentication process, an authentication system has been developed that eliminates the enrollment requirement by assigning a PIN to the user and utilizing an authenticator, referred to as a “token,” that displays to the user a dynamic token value, i.e., the value changes frequently. When the user attempts to access a protected resource, the user enters the PIN and the current token value. The authentication system verifies the PIN and the token value, and if each matches, the user is granted access to the resource. While this approach minimizes the enrollment process for the user, it still requires the user to remember the PIN/password. If the user forgets the PIN/password, the user must contact the “help desk,” as before. Also, the PIN/password must still be stored and managed, which is costly and presents a potential security risk.
Accordingly, what is needed is an improved method and system for authenticating a user who wishes to utilize a protected resource or service. The method and system should authenticate a user without requiring the user to perform an enrollment process, and without requiring the user to submit a password. The present invention addresses such a need.
The present invention provides a method and system for authenticating a user. The method according to the present invention includes providing a plurality of questions based on user related information stored in at least one data source, wherein none of the plurality of questions is password related. At least one of the plurality of questions is presented to the user in response to receiving a request from the user to access a protected resource. Access is granted to the protected resource if the user correctly answers each of the at least one questions presented.
According to the method and system disclosed herein, the present invention authenticates the user without requiring the user to provide a password or biometric data, and without requiring the user to perform an enrollment process. Instead, the user is required to answer personal questions the answers to which will authenticate the user's identity. Once the user is successfully authenticated, the user is granted access to protected resources to which the user is authorized.
The present invention relates to identity management, and more particularly to authenticating a user without prior user enrollment. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiments and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features described herein.
Currently, in order to protect a resource from use by unauthorized users, an enrollment process is performed for each authorized user so that the user can be authenticated when the user requests access to the resource. As stated above, the enrollment or registration process, typically involves assigning or allowing the user to choose a password or PIN. The user must remember the password or PIN, else the user will not be allowed access to the resource. As stated above, password/PIN oriented authentication is time consuming and tedious to set up, requires costly resources (help desk personnel, storage and data management) to maintain, and presents a security risk because the passwords are stored in a system that can be compromised.
The present invention addresses these concerns. According to a preferred embodiment of the present invention, passwords, PINs, and biometric data are eliminated from the authentication process. Instead, an identity management server (IMS) presents a series of challenge questions to the user when the user requests access to a protected resource. The challenge questions are of a personal nature pertaining to the user, and are derived from information contained in public and/or private data sources. If the user correctly answers the challenge questions, the user is authenticated and granted access to the protected resource. Through aspects of the present invention, the registration process is minimized, if not eliminated, and the user is not required to remember a password for authentication. Moreover, the costs and security risks associated with maintaining a password oriented process, e.g., help desk personnel and storage costs and password misappropriation, are minimized, if not eliminated.
Clients 11 are preferably coupled to the server 19 via a secure communication channel if the network 15b is a public network 15b, or a LAN if the network 15b is a private network. The server 19 is coupled to the plurality of data sources 40a-40d via a network 15a, which may be public or private, or a combination of each, depending on whether the data source 40a-40d is private or public.
A private data source, e.g., 40a or 40b, is a source controlled by a corporation or private entity 17, such as a human resources database or a corporate organization chart. The network 15c connecting the server 19 to the private data sources 40a, 40b would preferably be a private network 15c, e.g., an intranet, that is secure and protected from general public access. Preferably, the server 19 possesses the requisite credentials in order to access the information stored in the private data sources 40a, 40b.
Public data sources, e.g., 40c, 40d, are sources controlled by a public entity, such as the Department of Motor Vehicles or the Internal Revenue Service. While public data sources 40c, 40d are generally available via a public network 15a, access to specific information is usually restricted to administrative personnel or to an individual. The server 19 preferably possesses the requisite credentials in order to access the private information in the public data sources 40c, 40d.
In general, the data sources 40a-40d store personal and confidential information related to users 10 who are affiliated in some way with the entities controlling the data sources 40a-40d. For example, an HR data source, e.g., 40a, controlled by a private employer, stores personal and confidential information related to user employees.
According to a preferred embodiment of the present invention, the authentication server 19 regulates access to the protected resources 50a, 50b by asking a user 10 to answer questions regarding personal information stored in the data sources 40a-40d. The authentication server 19 includes a processor 25, memory 21 and a communication interface 23. The memory 21 stores a plurality of challenge questions 22 directed to the user related information and the IMS 20 application. The memory 21 is preferably nonvolatile and secure. The processor 25 is coupled to the memory 21 and executes the IMS 20 application. The communication interface 23 allows the authentication server 19 to conduct secure communications with the clients 11, sources 40a-40d, and protected resources 50a, 50b.
According to the preferred embodiment, the IMS 20 includes a query module 26, which retrieves user related information from the sources 40a-40d, and a compare module 24 that compares information received from the user 10 to information retrieved by the query module 26. The functional operation of the query 26 and compare 24 modules will be discussed in more detail below.
In a preferred embodiment, the server 19 is configured by a system administrator 30. During the configuration process, connectivity information for each of the data sources 40a-40d is provided, the challenge questions 22 are generated, and security parameters are set. Connectivity information includes the name of the source, e.g., HR database 40a or DMV database 40c, its description, its URL, and authorization credentials, e.g., user ID and password to access the source. This information allows the server 19 to have authorized access to the data sources 40a-40d.
As stated above, the challenge questions 22 are based on the user related information stored in the data sources 40a-40d.
Each data source 40a-40d includes a plurality of fields 42 (
After the user related fields 42 have been identified, the administrator 30 writes or selects at least one challenge question 22 for each field 42 (step 204), where an answer to the question 22 is a value in the field 42. For example, if the field 42 is “employee ID,” then an exemplary challenge question 22 can be “What is your employee ID number?”
In some instances, steps 202 and 204 can be automated because the data source 40a is of a type that is well known and recognized by the IMS 20. For example, well known source types include HR databases and customer billing (financial) databases, etc. Because each well known source type typically includes the same or similar fields 42, the questions 22 associated with the fields 42 can also be associated with the source type. Thus, if the data source 40a is one that is recognized by the IMS 20, the appropriate challenge questions 22 are automatically provided.
Once provided, the challenge question(s) 22 are associated with the field 42 and with the data source 40a (step 206) and stored in the secure memory 21 (step 208). If the server 19 has authorized access to more data sources, e.g., 40b-40d (step 210), then the next data source, e.g., 40b, is designated (step 211), and steps 202 through 208 are optionally repeated. Alternatively, once positive user identity has been determined with correct answers to challenge questions for one service, the user can be granted access to all services within the user's prevue.
Once the challenge questions 22 have been stored for each data source 40a-40d, the system administrator 30 completes the configuration process by designating the number of challenge questions 22 the user must correctly answer (step 212), and setting security parameters (step 214). The number of questions 22 the user must correctly answer can be directly related to the level of security required to access a resource 50a or 50b. For example, if a resource 50a requires a high level of security, i.e., access is very restricted, the number of questions 22 can be large and/or the types of questions 22 can be highly personal, i.e., the answers are known only to the user 10 and maybe to a small select group. If, on the other hand, the resource 50b does not require such security, the number of questions 22 can be smaller. In addition to designating the number of questions 22, the administrator 30 can also designate one or more specific questions 22 that must be answered, or the administrator 30 can select a random question mode that allows the IMS 20 to select randomly from the plurality of questions 22.
The security parameters define what is done when the user 10 answers challenge questions 22 incorrectly and who is notified when certain events take place. For example, the administrator 30 can designate the number of incorrect attempts before terminating a log-on session, and can designate who the server 19 notifies if authentication fails.
In a preferred embodiment, the authentication server 19 is utilized exclusively by the private entity 17 to authenticate users 10 who request access to the private entity's protected resources 50a. In such use, the configuration process is tailored to the private entity 17 and generally directed to the entity's private data sources 40a, 40b. In another preferred embodiment, the IMS 20 is run on a server controlled by an application service provider (“ASP”) that provides authentication services to more than one public or private entities. As an ASP, the server 19 is generally configured once per customer. As more data sources become available, new challenge questions associated with those data sources may be generated and stored or the existing challenge questions may be deemed sufficient to establish positive identity and grant access to added services. In yet another embodiment, the IMS 20 application resides on the client system 11 itself and protects the system 11 and its resources from unauthorized use.
Once the configuration process is completed, the authentication server 19 is prepared to authenticate users 10. As can be seen, according to the present invention, at no time is the user 10 involved in the configuration process, the result of which is enablement of identification and authentication with no prior action by the user 10.
In one preferred embodiment, the request is transmitted to the authentication server 19 via a secure communication channel in the network 15b. When the server 19 receives the request, it then presents to the user 10 a log-on page 27 (step 301). Preferably, the server 19 is a web server that securely receives and transmits IP packets via public and private networks 15a-15c. Accordingly, the server 19 transmits the log-on page 27 to the client computer system 11, which displays it on the system's web browser 12. In another preferred embodiment, the user's web browser 12 is a lock-down browser that transmits and receives data only to and only from the server 19 until a user 10 is authenticated. This type of setup would be useful, for example, inside a corporate office, where it would be undesirable to allow unauthorized users to utilize computer systems to access the Internet without properly logging on to the system first.
The log-on page 27 preferably includes one or more identifying fields for allowing the user 10 to provide an initial indication of the user's purported identity to some level of uniqueness. For example, the log-on page 27 may include identifying fields for the user's last name, first name, middle initial, and zip code. If the IMS 20 cannot narrow the user 10 to an individual, e.g., more than one Tom R. Jones lives in the same zip code, then additional identifying fields can be utilized. Notably, the log-on page 27 does not include a field for a password, PIN, or other information, e.g., biometric data, that requires the user 10 to pre-register with the server 19.
After the log-on page 27 is displayed to the user 10, the user 10 enters the user's indication of identity, e.g., full name and zip code, and submits the same to the server 19 (step 302). In response, the IMS 20 retrieves and presents a first challenge question 22 to the user 10 (step 303). As stated above, the first question 22 can be predetermined by the administrator 30 or it can be randomly selected by the IMS 20. The first question 22 is displayed to the user 10 via the web browser 12, and the user 10 is allowed to submit an answer (step 304). Upon receipt of the answer, the IMS 20 automatically analyzes the user's answer to determine whether it is correct (step 305).
SELECT employee_id FROM table_hr
WHERE employee_name is “Tom Jones”
The field value retrieved by the query module 25 will be used as the correct answer to the question 22.
The query is submitted to the associated data source 40a (step 404), and the correct answer is retrieved and returned to the server 19 (step 406). Next, the IMS 20 compares the user's answer to the correct answer (step 408). If the answers match (step 410), then the user's answer is correct (step 412). Otherwise, the user's answer is incorrect (step 414). Match does not necessarily imply a straight equality match. Any type of other match algorithms may be used such as case insensitive match or a range check.
In a preferred embodiment, both the user's answer and the correct answer are one-way hashed, e.g., “One Way SHA1,” and encrypted before either is received by the server 19. This prevents accidental or intentional discovery of the answers by any entity including the server 19, thereby preserving privacy. The IMS 20 then compares the hashed and encrypted answers, and not the actual answers themselves.
After the analysis of the user's answer has been completed, i.e., after the answers are compared, the answers are discarded from the IMS 20 (step 416). This measure prevents the server 19 itself from becoming a point of vulnerability in a security structure.
Referring again to
If the user's answer is correct (step 306) and more questions 22 are not required (step 309), the IMS 20 authenticates the user 10 and grants access to the protected resource 50a (step 310). In a preferred embodiment, the IMS 20 can serve as a single sign-on service, that is, once the user 10 is authenticated, the IMS 20 can also unlock other or all protected resources 50a, 50b for which the user 10 is authorized. Single sign-on services are well known to those skilled in the art and further elaboration is not required.
If the user's answer is incorrect (step 306), authentication of the user 10 has failed and the IMS 20 transmits an alert message (step 307) to the administrator 30 or to a security officer or to the authorized user 10 who is being impersonated, according to the configured security parameters. Depending on the configuration, the alert message preferably indicates that an attempt to access the protected resource 50a failed and the purported name of the user/imposter. The message can also include the IP address of the intruder and other tracking information to assist the security officer or administrator 30 in identifying a potential hacker. At this point, depending on the configured security parameters, the IMS 20 can deny access to the protected resource 50a (step 308), or allow the user 10 to resubmit his or her answer in case the previously submitted incorrect answer contained a typographical error. The number of chances allowed to answer the question 22 correctly is configurable. If the user 10 continues to provide the incorrect answer, the IMS 20 will terminate the session and deny access (step 308).
Through aspects of the present invention, a user is authenticated without the use of an obscure credential, e.g., a password, or biometric data, and without requiring the user to enroll with the protected resource. According to the preferred embodiment of the present invention, passwords, PINs, and biometric data are eliminated from the authentication process. Instead, an identity management service (IMS) running on an authentication server presents a series of challenge questions to the user when the user requests access to a protected resource. The challenge questions are of a personal nature pertaining to the user, and are derived from information contained in public and/or private data sources. If the user correctly answers the challenge questions, the user is authenticated and granted access to the protected resource.
Through aspects of the present invention, the enrollment process is minimized, if not eliminated, and the user is not required to remember a password for authentication. Moreover, the costs and security risks associated with maintaining a password oriented process, e.g., help desk personnel and storage costs and password misappropriation are minimized, if not eliminated.
A method and system for authenticating a user without prior user enrollment has been disclosed. The present invention has been described in accordance with the embodiments shown, and one of ordinary skill in the art will readily recognize that there could be variations to the embodiments, and any variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.
Patent | Priority | Assignee | Title |
10025842, | Nov 20 2013 | CONSUMERINFO.COM, INC. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
10043214, | Mar 14 2013 | CONSUMERINFO.COM, INC. | System and methods for credit dispute processing, resolution, and reporting |
10061936, | Sep 16 2011 | CONSUMERINFO.COM, INC. | Systems and methods of identity protection and management |
10075446, | Jun 26 2008 | Experian Marketing Solutions, LLC | Systems and methods for providing an integrated identifier |
10078868, | Jan 31 2007 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
10102536, | Nov 15 2013 | Experian Information Solutions, Inc | Micro-geographic aggregation system |
10102570, | Mar 14 2013 | CONSUMERINFO COM, INC | Account vulnerability alerts |
10115079, | Jun 16 2011 | CONSUMERINFO.COM, INC. | Authentication alerts |
10115155, | Aug 14 2008 | EXPERIAN INFORMATION SOLUTION, INC. | Multi-bureau credit file freeze and unfreeze |
10121194, | Oct 05 2006 | Experian Information Solutions, Inc. | System and method for generating a finance attribute from tradeline data |
10169761, | Mar 15 2013 | ConsumerInfo.com Inc. | Adjustment of knowledge-based authentication |
10176233, | Jul 08 2011 | CONSUMERINFO.COM, INC. | Lifescore |
10210539, | Jul 08 2011 | DUN & BRADSTREET EMERGING BUSINESSES CORP | Single system for authenticating entities across different third party platforms |
10242019, | Dec 19 2014 | Experian Information Solutions, Inc | User behavior segmentation using latent topic detection |
10255598, | Dec 06 2012 | CONSUMERINFO COM, INC | Credit card account data extraction |
10262362, | Feb 14 2014 | Experian Information Solutions, Inc | Automatic generation of code for attributes |
10262364, | Dec 14 2007 | CONSUMERINFO.COM, INC. | Card registry systems and methods |
10269065, | Nov 15 2013 | CONSUMERINFO.COM, INC. | Bill payment and reporting |
10277659, | Nov 12 2012 | CONSUMERINFO.COM, INC. | Aggregating user web browsing data |
10311466, | Jan 31 2007 | Experian Information Solutions, Inc. | Systems and methods for providing a direct marketing campaign planning environment |
10325314, | Nov 15 2013 | CONSUMERINFO COM, INC | Payment reporting systems |
10339527, | Oct 31 2014 | Experian Information Solutions, Inc | System and architecture for electronic fraud detection |
10366450, | Nov 30 2012 | CONSUMERINFO.COM, INC. | Credit data analysis |
10373240, | Apr 25 2014 | CSIDENTITY CORPORATION | Systems, methods and computer-program products for eligibility verification |
10402901, | Jan 31 2007 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
10417704, | Nov 02 2010 | Experian Technology Ltd. | Systems and methods of assisted strategy design |
10437895, | Mar 30 2007 | CONSUMERINFO.COM, INC. | Systems and methods for data verification |
10445152, | Dec 19 2014 | Experian Information Solutions, Inc | Systems and methods for dynamic report generation based on automatic modeling of complex data structures |
10453159, | May 23 2013 | CONSUMERINFO.COM, INC. | Digital identity |
10482532, | Apr 16 2014 | CONSUMERINFO.COM, INC. | Providing credit data in search results |
10580025, | Nov 15 2013 | Experian Information Solutions, Inc. | Micro-geographic aggregation system |
10586279, | Sep 22 2004 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
10592982, | Mar 14 2013 | CSIDENTITY CORPORATION | System and method for identifying related credit inquiries |
10593004, | Feb 18 2011 | CSIDENTITY CORPORATION | System and methods for identifying compromised personally identifiable information on the internet |
10614519, | Dec 14 2007 | CONSUMERINFO.COM, INC. | Card registry systems and methods |
10621657, | Nov 05 2008 | CONSUMERINFO.COM, INC. | Systems and methods of credit information reporting |
10628448, | Nov 20 2013 | CONSUMERINFO.COM, INC. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
10642999, | Sep 16 2011 | CONSUMERINFO.COM, INC. | Systems and methods of identity protection and management |
10650448, | Aug 14 2008 | Experian Information Solutions, Inc. | Multi-bureau credit file freeze and unfreeze |
10650449, | Jan 31 2007 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
10664936, | Mar 15 2013 | CSIDENTITY CORPORATION | Authentication systems and methods for on-demand products |
10671749, | Sep 05 2018 | CONSUMERINFO COM, INC | Authenticated access and aggregation database platform |
10685336, | Jun 16 2011 | CONSUMERINFO.COM, INC. | Authentication alerts |
10685398, | Apr 23 2013 | CONSUMERINFO COM, INC | Presenting credit score information |
10692105, | Jan 31 2007 | Experian Information Solutions, Inc. | Systems and methods for providing a direct marketing campaign planning environment |
10699028, | Sep 28 2017 | CSIDENTITY CORPORATION | Identity security architecture systems and methods |
10719873, | Jun 16 2011 | CONSUMERINFO.COM, INC. | Providing credit inquiry alerts |
10735183, | Jun 30 2017 | Experian Information Solutions, Inc | Symmetric encryption for private smart contracts among multiple parties in a private peer-to-peer network |
10740762, | Mar 15 2013 | CONSUMERINFO.COM, INC. | Adjustment of knowledge-based authentication |
10757154, | Nov 24 2015 | Experian Information Solutions, Inc | Real-time event-based notification system |
10798197, | Jul 08 2011 | CONSUMERINFO.COM, INC. | Lifescore |
10878499, | Dec 14 2007 | CONSUMERINFO.COM, INC. | Card registry systems and methods |
10880313, | Sep 05 2018 | CONSUMERINFO COM, INC | Database platform for realtime updating of user data from third party sources |
10891691, | Jan 31 2007 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
10896472, | Nov 14 2017 | CSIDENTITY CORPORATION | Security and identity verification system and architecture |
10909617, | Mar 24 2010 | CONSUMERINFO.COM, INC. | Indirect monitoring and reporting of a user's credit data |
10911234, | Jun 22 2018 | Experian Information Solutions, Inc | System and method for a token gateway environment |
10929925, | Mar 14 2013 | Consumerlnfo.com, Inc. | System and methods for credit dispute processing, resolution, and reporting |
10963434, | Sep 07 2018 | Experian Information Solutions, Inc | Data architecture for supporting multiple search models |
10963959, | Nov 30 2012 | Consumerinfo. com, Inc. | Presentation of credit score factors |
10963961, | Oct 05 2006 | Experian Information Solutions, Inc. | System and method for generating a finance attribute from tradeline data |
10990979, | Oct 31 2014 | Experian Information Solutions, Inc. | System and architecture for electronic fraud detection |
11004147, | Aug 14 2008 | Experian Information Solutions, Inc. | Multi-bureau credit file freeze and unfreeze |
11010345, | Dec 19 2014 | Experian Information Solutions, Inc | User behavior segmentation using latent topic detection |
11012491, | Nov 12 2012 | ConsumerInfor.com, Inc. | Aggregating user web browsing data |
11030562, | Oct 31 2011 | CONSUMERINFO.COM, INC. | Pre-data breach monitoring |
11074641, | Apr 25 2014 | CSIDENTITY CORPORATION | Systems, methods and computer-program products for eligibility verification |
11087022, | Sep 16 2011 | CONSUMERINFO.COM, INC. | Systems and methods of identity protection and management |
11107158, | Feb 14 2014 | Experian Information Solutions, Inc. | Automatic generation of code for attributes |
11113759, | Mar 14 2013 | CONSUMERINFO.COM, INC. | Account vulnerability alerts |
11120519, | May 23 2013 | CONSUMERINFO.COM, INC. | Digital identity |
11132742, | Nov 30 2012 | Consumerlnfo.com, Inc. | Credit score goals and alerts systems and methods |
11151468, | Jul 02 2015 | Experian Information Solutions, Inc | Behavior analysis using distributed representations of event data |
11157650, | Sep 28 2017 | CSIDENTITY CORPORATION | Identity security architecture systems and methods |
11157872, | Jun 26 2008 | Experian Marketing Solutions, LLC | Systems and methods for providing an integrated identifier |
11159593, | Nov 24 2015 | Experian Information Solutions, Inc. | Real-time event-based notification system |
11164271, | Mar 15 2013 | CSIDENTITY CORPORATION | Systems and methods of delayed authentication and billing for on-demand products |
11176570, | Jan 31 2007 | Experian Information Solutions, Inc. | Systems and methods for providing a direct marketing campaign planning environment |
11200620, | Oct 13 2011 | CONSUMERINFO.COM, INC. | Debt services candidate locator |
11227001, | Jan 31 2017 | Experian Information Solutions, Inc. | Massive scale heterogeneous data ingestion and user resolution |
11232413, | Jun 16 2011 | CONSUMERINFO.COM, INC. | Authentication alerts |
11238656, | Feb 22 2019 | CONSUMERINFO COM, INC | System and method for an augmented reality experience via an artificial intelligence bot |
11265324, | Sep 05 2018 | CONSUMERINFO COM, INC | User permissions for access to secure data at third-party |
11288677, | Mar 15 2013 | Consumerlnfo.com, Inc. | Adjustment of knowledge-based authentication |
11308170, | Mar 30 2007 | CONSUMERINFO.COM, INC. | Systems and methods for data verification |
11308551, | Nov 30 2012 | CONSUMERINFO.COM, INC. | Credit data analysis |
11315179, | Nov 16 2018 | CONSUMERINFO COM, INC | Methods and apparatuses for customized card recommendations |
11356430, | May 07 2012 | CONSUMERINFO.COM, INC. | Storage and maintenance of personal data |
11373261, | Sep 22 2004 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
11379916, | Dec 14 2007 | CONSUMERINFO.COM, INC. | Card registry systems and methods |
11399029, | Sep 05 2018 | CONSUMERINFO.COM, INC. | Database platform for realtime updating of user data from third party sources |
11436606, | Oct 31 2014 | Experian Information Solutions, Inc. | System and architecture for electronic fraud detection |
11443373, | Jan 31 2007 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
11461364, | Nov 20 2013 | CONSUMERINFO.COM, INC. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
11514519, | Mar 14 2013 | CONSUMERINFO.COM, INC. | System and methods for credit dispute processing, resolution, and reporting |
11562457, | Sep 22 2004 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
11568348, | Oct 31 2011 | CONSUMERINFO.COM, INC. | Pre-data breach monitoring |
11580259, | Sep 28 2017 | CSIDENTITY CORPORATION | Identity security architecture systems and methods |
11587150, | Apr 25 2014 | CSIDENTITY CORPORATION | Systems and methods for eligibility verification |
11588639, | Jun 22 2018 | Experian Information Solutions, Inc. | System and method for a token gateway environment |
11620403, | Jan 11 2019 | Experian Information Solutions, Inc | Systems and methods for secure data aggregation and computation |
11631129, | Oct 05 2006 | Experian Information Solutions, Inc | System and method for generating a finance attribute from tradeline data |
11636540, | Aug 14 2008 | Experian Information Solutions, Inc. | Multi-bureau credit file freeze and unfreeze |
11645344, | Aug 26 2019 | EXPERIAN HEALTH, INC | Entity mapping based on incongruent entity data |
11651426, | Nov 30 2012 | Consumerlnfo.com, Inc. | Credit score goals and alerts systems and methods |
11652607, | Jun 30 2017 | Experian Information Solutions, Inc. | Symmetric encryption for private smart contracts among multiple parties in a private peer-to-peer network |
11665253, | Jul 08 2011 | CONSUMERINFO.COM, INC. | LifeScore |
11681733, | Jan 31 2017 | Experian Information Solutions, Inc. | Massive scale heterogeneous data ingestion and user resolution |
11729230, | Nov 24 2015 | Experian Information Solutions, Inc. | Real-time event-based notification system |
11734234, | Sep 07 2018 | Experian Information Solutions, Inc. | Data architecture for supporting multiple search models |
11769112, | Jun 26 2008 | Experian Marketing Solutions, LLC | Systems and methods for providing an integrated identifier |
11769200, | Mar 14 2013 | CONSUMERINFO.COM, INC. | Account vulnerability alerts |
11775979, | Mar 15 2013 | CONSUMERINFO.COM, INC. | Adjustment of knowledge-based authentication |
11790112, | Sep 16 2011 | CONSUMERINFO.COM, INC. | Systems and methods of identity protection and management |
11790473, | Mar 15 2013 | CSIDENTITY CORPORATION | Systems and methods of delayed authentication and billing for on-demand products |
11803873, | Jan 31 2007 | Experian Information Solutions, Inc. | Systems and methods for providing a direct marketing campaign planning environment |
11803929, | May 23 2013 | CONSUMERINFO.COM, INC. | Digital identity |
11842454, | Feb 22 2019 | CONSUMERINFO.COM, INC. | System and method for an augmented reality experience via an artificial intelligence bot |
11847693, | Feb 14 2014 | Experian Information Solutions, Inc. | Automatic generation of code for attributes |
11861691, | Apr 29 2011 | CONSUMERINFO.COM, INC. | Exposing reporting cycle information |
11861756, | Sep 22 2004 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
11863310, | Nov 12 2012 | CONSUMERINFO.COM, INC. | Aggregating user web browsing data |
11880377, | Mar 26 2021 | Experian Information Solutions, Inc | Systems and methods for entity resolution |
11908005, | Jan 31 2007 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
8032927, | Oct 30 2000 | Matthews International Corporation | Verification engine for user authentication |
8316418, | Oct 30 2000 | Matthews International Corporation | Verification engine for user authentication |
8380629, | Jun 25 2007 | Visa U.S.A. Inc. | Seeding challenges for payment transactions |
8490201, | Feb 26 2010 | Microsoft Technology Licensing, LLC | Protecting account security settings using strong proofs |
8548818, | Jan 31 2008 | First Data Corporation | Method and system for authenticating customer identities |
8578469, | Jun 12 2007 | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | Computer system protection |
8650310, | Jun 03 2009 | International Business Machines Corporation | Detecting an inactive client during a communication session |
8745698, | Jun 09 2009 | Bank of America Corporation | Dynamic authentication engine |
8955154, | Jul 08 2011 | DUN & BRADSTREET EMERGING BUSINESSES CORP | Single system for authenticating entities across different third party platforms |
8966649, | May 11 2009 | Experian Marketing Solutions, LLC | Systems and methods for providing anonymized user profile data |
8990909, | Jun 25 2013 | Bank of America Corporation | Out-of-band challenge question authentication |
9106691, | Sep 16 2011 | CONSUMERINFO COM | Systems and methods of identity protection and management |
9147042, | Nov 22 2010 | Experian Information Solutions, Inc | Systems and methods for data verification |
9152826, | Oct 31 2006 | Hewlett-Packard Development Company, L.P. | Damage detection for an anti-theft interface |
9197648, | Apr 22 2013 | System and method for verifying the identity of an internet user | |
9230283, | Dec 14 2007 | CONSUMERINFO.COM, INC. | Card registry systems and methods |
9251541, | May 25 2007 | Experian Information Solutions, Inc. | System and method for automated detection of never-pay data sets |
9256904, | Aug 14 2008 | Experian Information Solutions, Inc | Multi-bureau credit file freeze and unfreeze |
9286627, | May 04 2011 | Amazon Technologies Inc | Personal webservice for item acquisitions |
9342783, | Mar 30 2007 | CONSUMERINFO.COM, INC. | Systems and methods for data verification |
9400589, | Nov 30 2012 | CONSUMERINFO COM, INC | Circular rotational interface for display of consumer credit information |
9406085, | Mar 14 2013 | CONSUMERINFO COM, INC | System and methods for credit dispute processing, resolution, and reporting |
9443268, | Nov 15 2013 | CONSUMERINFO.COM, INC. | Bill payment and reporting |
9477737, | Nov 20 2013 | CONSUMERINFO COM, INC | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
9489694, | Aug 14 2008 | Experian Information Solutions, Inc. | Multi-bureau credit file freeze and unfreeze |
9508092, | Jan 31 2007 | Experian Information Solutions, Inc. | Systems and methods for providing a direct marketing campaign planning environment |
9529851, | Dec 02 2013 | Experian Information Solutions, Inc | Server architecture for electronic data quality processing |
9536263, | Oct 13 2011 | CONSUMERINFO.COM, INC. | Debt services candidate locator |
9542553, | Sep 16 2011 | CONSUMERINFO.COM, INC. | Systems and methods of identity protection and management |
9542682, | Dec 14 2007 | CONSUMERINFO.COM, INC. | Card registry systems and methods |
9558519, | Apr 29 2011 | CONSUMERINFO.COM, INC. | Exposing reporting cycle information |
9563916, | Oct 05 2006 | Experian Information Solutions, Inc. | System and method for generating a finance attribute from tradeline data |
9595051, | May 11 2009 | Experian Marketing Solutions, LLC | Systems and methods for providing anonymized user profile data |
9607175, | May 21 2007 | KYNDRYL, INC | Privacy safety manager system |
9607336, | Jun 16 2011 | CONSUMERINFO COM, INC | Providing credit inquiry alerts |
9654541, | Nov 12 2012 | CONSUMERINFO COM, INC | Aggregating user web browsing data |
9665854, | Jun 16 2011 | CONSUMERINFO COM, INC | Authentication alerts |
9684905, | Nov 22 2010 | Experian Information Solutions, Inc. | Systems and methods for data verification |
9697263, | Mar 04 2013 | Experian Information Solutions, Inc | Consumer data request fulfillment system |
9697568, | Mar 14 2013 | CONSUMERINFO.COM, INC. | System and methods for credit dispute processing, resolution, and reporting |
9710852, | Apr 23 2013 | CONSUMERINFO COM, INC | Credit report timeline user interface |
9721147, | May 23 2013 | CONSUMERINFO COM, INC | Digital identity |
9767513, | Dec 14 2007 | CONSUMERINFO.COM, INC. | Card registry systems and methods |
9792648, | Aug 14 2008 | Experian Information Solutions, Inc. | Multi-bureau credit file freeze and unfreeze |
9830646, | Nov 30 2012 | CONSUMERINFO COM, INC | Credit score goals and alerts systems and methods |
9853959, | May 07 2012 | CONSUMERINFO COM, INC | Storage and maintenance of personal data |
9870589, | Mar 14 2013 | CONSUMERINFO COM, INC | Credit utilization tracking and reporting |
9892457, | Apr 16 2014 | CONSUMERINFO COM, INC | Providing credit data in search results |
9916596, | Jan 31 2007 | Experian Information Solutions, Inc. | Systems and methods for providing a direct marketing campaign planning environment |
9923906, | Mar 21 2011 | APPLIED SYSTEMS, INC | System, method and computer program product for access authentication |
9972048, | Oct 13 2011 | CONSUMERINFO.COM, INC. | Debt services candidate locator |
D759689, | Mar 25 2014 | CONSUMERINFO COM, INC | Display screen or portion thereof with graphical user interface |
D759690, | Mar 25 2014 | CONSUMERINFO COM, INC | Display screen or portion thereof with graphical user interface |
D760256, | Mar 25 2014 | CONSUMERINFO COM, INC | Display screen or portion thereof with graphical user interface |
Patent | Priority | Assignee | Title |
4528442, | Feb 02 1982 | Omron Tateisi Electronics, Co. | Personal identification system |
5774525, | Jan 23 1995 | International Business Machines Corporation | Method and apparatus utilizing dynamic questioning to provide secure access control |
5987232, | Sep 08 1995 | IDENTITY VERIFICATION SOLUTIONS LLC | Verification server for use in authentication on networks |
5991882, | Jun 03 1996 | Hewlett Packard Enterprise Development LP | Automated password reset |
6005935, | Nov 20 1996 | AT&T Corp. | Method and system of using personal information as a key when distributing information |
6263447, | May 21 1998 | EQUIFAX INC | System and method for authentication of network users |
6496936, | May 21 1998 | EQUIFAX INC. | System and method for authentication of network users |
6704787, | Dec 03 1999 | US Tax Relief, LLC | Date of birth authentication system and method using demographic and/or geographic data supplied by a subscriber that is verified by a third party |
6853973, | Oct 24 2002 | IGT | Configurable and stand-alone verification module |
7184547, | Jan 27 1999 | CALLAHAN CELLULAR L L C | Authenticating or signature method with reduced computations |
7280984, | May 08 2000 | PHELAN, PATRICIA, MS | Money card system, method and apparatus |
20020133708, | |||
20030046237, | |||
20030154406, | |||
20030187742, | |||
20040078603, | |||
20040123162, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Aug 12 2004 | Avatier Corporation | (assignment on the face of the patent) | / | |||
Aug 12 2004 | CICCHITTO, NELSON A | Avatier Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 015702 | /0381 |
Date | Maintenance Fee Events |
Jul 30 2012 | REM: Maintenance Fee Reminder Mailed. |
Aug 15 2012 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
Aug 15 2012 | M2554: Surcharge for late Payment, Small Entity. |
Jun 02 2016 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
Jun 05 2020 | M2553: Payment of Maintenance Fee, 12th Yr, Small Entity. |
Date | Maintenance Schedule |
Dec 16 2011 | 4 years fee payment window open |
Jun 16 2012 | 6 months grace period start (w surcharge) |
Dec 16 2012 | patent expiry (for year 4) |
Dec 16 2014 | 2 years to revive unintentionally abandoned end. (for year 4) |
Dec 16 2015 | 8 years fee payment window open |
Jun 16 2016 | 6 months grace period start (w surcharge) |
Dec 16 2016 | patent expiry (for year 8) |
Dec 16 2018 | 2 years to revive unintentionally abandoned end. (for year 8) |
Dec 16 2019 | 12 years fee payment window open |
Jun 16 2020 | 6 months grace period start (w surcharge) |
Dec 16 2020 | patent expiry (for year 12) |
Dec 16 2022 | 2 years to revive unintentionally abandoned end. (for year 12) |