US 8,856,894 B1Grant
Always on authentication
Issue Date:2014-10-07
•20 Claims
•12 Drawing Sheets
Abstract
An Always-On Authentication (“AOA”) system comprises a computer system, such as a server, that automatically monitors and authenticates an enrolled individual's online transactions and/or activities to, for example, detect and/or prevent fraud. The AOA system actively monitors and/or authenticates the individual's online transactions and/or activities with service providers. A risk level may be associated with transactions and/or activities, and if a monitored transaction or activity is determined to exceed risk level for the individual, the individual may be prompted for further authentication information. A risk profile may be built for the individual over time based on the individual's history or pattern of transactions and activities. The AOA system may issue a virtual credential to the individual and/or to one or more of the individual's computing devices. The virtual credential may be provided to participating service provider(s) to enable seamless authentication of the individual during his/her interactions with the service provider(s).
Metadata
Assignee
- Consumerinfo.com, Inc.
Inventors
- Michael John Dean
- Mark Joseph Kapczynski
Application Information
Application Number:US 13/797,364
Filing Date:2013-03-12
Priority Date:2012-11-28
Art Unit:2431
Classifications
IPC:
H04L9/32H04L29/06
Patent Drawings (12 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of priority under 35 U.S.C. §119(e) of U.S. Provisional Application No. 61/730,698, filed Nov. 28, 2012, the disclosure of which is hereby incorporated by reference in its entirety.
BACKGROUND
[0002] Individuals frequently use a variety of electronic devices to access the Internet, conduct transactions online, and engage in various online activities, such as social networking. The corresponding increase in connectivity has improved the ease and convenience with which individuals can conduct transactions online and engage in various online activities. These transactions and activities often have security and/or authentication measures or requirements in order to protect the individual's identity and/or prevent fraud. Whether and when an individual is asked for authentication information, such as a username and/or password, can vary greatly depending on the transaction, activity, and even the device used to conduct the transaction or activity. Consequently, inconsistent security measures can create greater potential for undetected device usage or even fraudulent activity, and contribute to a lesser user experience as individuals may be prompted for additional security information at varying times.
SUMMARY
[0003] Described herein is an Always-On Authentication (“AOA”) system that comprises a computer system, such as a server, that automatically monitors and authenticates an individual's online transactions and/or activities. The AOA system may be useful, for example, to detect and prevent fraud. As stated above, the level of security and/or authentication measures required or recommended can vary depending on the transaction or activity. Some transactions or activities may require a high level of authentication before an individual can proceed. For example, logging into an online financial account (such as a bank or credit card account) typically requires multiple levels of authentication such as a password, confirmation of an account-specific image associated with an individual's account or login information, last four digits of a social security number associated with the individual's account, and/or other various security requirements. Some activities may require a medium or low level of authentication before an individual can proceed. For example, an individual typically must enter an account password prior to placing an order for a product or service from an online service provider (“OSP”), even if the individual may have already “logged in” to the service provider's system. Some activities may not require any authentication before an individual can proceed. For example, conducting an online search or reading a news article are activities which typically do not require an individual to provide account information (for example, username and/or password).
[0004] An Always-on-Authentication system attempts to improve the individual's security and overall user experience by providing a system which actively monitors and/or authenticates an individual's online transactions and/or activities in “real time” or near real-time. According to one embodiment, an individual may initially authenticate his/her identity with the AOA system, for example during an enrollment or registration process. To initially authenticate his/her identity an individual may provide various personally identifying information, such as name, address, social security number, etc. The AOA system may then use the personally identifying information to initially authenticate and/or verify the individual's identity by accessing, for example, credit bureau data and/or consumer data.
[0005] Once the individual has been initially authenticated, the individual can then conduct transactions and/or engage in activities online with various OSPs. During the course of the individual's activities, an OSP may receive from the individual a portion of his/her identifying information (for example, the individual may register an account with the OSP, the OSP may access a cookie associated with the individual and/or his/her devices, etc.). For some transactions or activities, the OSP may determine that further authentication is necessary before the individual may be allowed to proceed. Traditionally, the OSP may require further authentication of the individual by requesting additional personally identifying information from the individual (for example, a password). In some embodiments involving an AOA system, the OSP may request further authentication of the individual from the AOA system. To do so, the OSP may provide the AOA system with some or all of a portion of the individual's identifying information. In some embodiments the AOA system may also receive information about the transaction or activity to be authenticated. The AOA system may then use the received information to authenticate the individual and/or the transaction. For example, in one embodiment, the AOA may access internal data (for example, an account and/or risk profile associated with the individual) and/or external data (for example, credit and/or consumer data sources). The AOA system may then provide a response to the OSP indicating, for example, whether the individual and/or the transaction has been authenticated, or whether further authentication may be recommended or required. Thus, an individual may be authenticated by the AOA system in some situations wherein the OSP would need to obtain further authentication information from the individual in order to authenticate the individual.
[0006] In one embodiment, the AOA system may be configured to store and access an individual risk profile associated with an individual. The risk profile may comprise, for example, information about particular transactions or activities known to be conducted or engaged in by the individual on a recurring basis. The risk profile may also comprise one or more risk indicators, which may indicate that particular transactions or activities may be, for example, “low risk,” “medium risk,” or “high risk.” Risk indicators may be based on any other scale, such as percentage, A-F, 1-10, and the like.
[0007] The risk profile may also comprise information about behavioral patterns associated with the individual, including a record of historical transactions for the individual. The behavioral patterns may be based on the individual's behavior and/or may be based on behavioral patterns of one or more types of individuals which may be similar to the individual. Behavioral patterns may include, for example, information about which websites and/or services an individual visits and how frequently, the times at which the individual usually visits a website and/or service, information about one or more device(s) the individual uses to access the websites and/or services, and the like. The risk profile may also include information related to transactions or activities, such as a type of transaction, a location, a date, a time, or a computing device used for a transaction or activity.
[0008] In some embodiments, a threshold trust level for a transaction or activity may be determined at least in part by analyzing the frequency of historical transactions for the individual. For example, a threshold trust level for a transaction or activity may be low for transactions or activities the individual conducts frequently, such as browsing a favorite website, checking an email account, and the like. In another example, a threshold trust level for a transaction or activity may be higher for transactions or activities the individual conducts infrequently, such as logging into a bank account online, making a purchase at a new or previously unvisited website, and the like. Over time the threshold trust level for a transaction or activity may be adjusted up or down depending on how often the individual engages in the transaction or activity, (for example, the threshold trust level associated with browsing a favorite website may increase over time if the individual does not browse the favorite website for a length of time; or the threshold trust level associated with making a purchase at the new or previously unvisited website may decrease over time if the individual continues to shop at the website on a more regular basis).
[0009] Behavioral patterns may also track the individual's activities and interactions over time to provide additional insight into expected behavior versus unexpected behavior. Some transactions or activities falling outside of an expected behavior pattern may generate a higher risk indicator and/or require further authentication before an individual can proceed. For example, suppose an individual is browsing an online product catalog. The individual's corresponding behavioral pattern may indicate the individual has accessed several different pages of the online product catalog website. If, in a subsequent activity during the same browsing session, the individual switches to browsing a different website which the individual has not previously accessed, the activity may be flagged or identified as potentially higher risk because it is “outside” of the individual's normal or expected browsing behavior. Thus, the AOA system may provide an indication that this “new” activity may have a higher risk rating and recommend or require the website to obtain additional authentication from the individual. Once the individual provides the required additional authentication, the AOA system may update the individual's behavioral pattern and/or risk profile to indicate the particular activity is trusted. When the individual next visits the “new” website, the AOA system may recognize the activity as trusted, and the individual may not need to be prompted for further authentication again.
[0010] The AOA system may use the risk profile information to authenticate transactions or activities which match or are otherwise consistent with the risk profile. The risk profile may also be updated by the AOA system as the individual conducts transactions or activities over time. Thus, behavioral patterns for the individual may change over time and the risk profile may be updated correspondingly. Any risk indicators associated with the risk profile may also be updated over time. Various combinations of risk profile information (for example, user, device, type of activity, time of activity, etc.) may be used to either authenticate the individual or transaction, or to indicate that further authentication may be necessary or recommended. In some embodiments,
[0011] The individual risk profile may be accessed by the AOA system to assess the risk of a transaction or activity, and to authenticate the individual and/or transaction or activity. For example, a risk profile for John Doe may indicate that John Doe regularly checks a social network account at a particular time each day from his tablet PC. The risk profile may include a risk indicator to indicate that this type of activity is “low risk” for John Doe. The AOA system may use this risk profile information to authenticate John Doe when he accesses his social network account at or near the specified time using his tablet PC. The AOA system may also use this risk profile information to require further authentication when John Doe accesses his social network account at or near the specified time, instead using his smart phone.
[0012] In one embodiment, the AOA system may be configured to store and access an OSP risk profile which may be associated with an online service provider. For example, an OSP may want to enable always-on authentication services for one or more activities (for example, logging in, viewing an article, viewing an item detail page, commenting on a web page, online shopping activities (e.g., adding items to an online shopping cart, checking out, placing an order), changing an address, changing a username and/or password, adding or deleting a credit card, accessing private information, etc.) associated with the online service. Further, the OSP may want to indicate that certain activities may have an associated risk level. Thus, for example, an OSP may want to enable always-on authentication for certain activities such as secured transactions, and indicate a risk level which may trigger the AOA system to identify the transaction as potentially higher risk (and thus, require further authentication). The AOA system may also be configured to receive, process, and store custom activity authentication templates or settings provided by the OSP. The OSP risk profile may be configured to store all of the above settings, which may then be accessed by the AOA system for use during the authentication processes described herein.
[0013] In one embodiment, the AOA system may be configured to operate in conjunction with a virtual credential (“VC”) which is provided to an individual and/or the individual's devices. A virtual credential can comprise a cookie, a digital certificate, or some other digital authentication used to uniquely and securely identify and/or authenticate the individual's identity. In some embodiments the VC may be encrypted for the individual and/or for the individual's device. The VC may be associated with an individual and one or more of the individual's devices. In some embodiments the VC may be associated with an individual risk profile. In one embodiment, the VC may be provided to the OSP from the individual and/or device when the individual conducts a transaction or activity. The VC may then be received by the AOA system from the OSP when the OSP requests authentication of the individual, transaction, and/or activity. The AOA system can then look up the VC, for example in an internal data source storing VCs provided to individuals and/or devices, to determine whether it is associated with the individual or device. In some embodiments the VC may also be used to access the individual risk profile for the individual, which may in turn be used to assess the risk of the transaction or activity as described herein.
[0014] In one embodiment, the AOA system may be configured to monitor transactions and/or activities for usage of certain information and/or devices associated with an individual. For example, the AOA system may receive from an individual a request to monitor one or more items of personal information (for example, name, address(es), phone number(s), date of birth, social security number, email address(es), etc.). The risk profile for the individual may then be updated to include the items to be monitored. The AOA system may then actively monitor and/or authenticate transactions and/or activities for the individual which may access, use, or otherwise be related to the items to be monitored.
[0015] In some embodiments, the AOA system may be configured to generate and provide alerts to the individual when a transaction or activity has been flagged as potentially high risk and/or requiring further authentication. In some embodiments the individual can indicate whether he/she wishes to receive these alerts, and/or specify that alerts only be provided for transactions and/or activities identified above a certain risk level (e.g., only send me alerts for transactions identified as high-risk” or the like). Each alert may provide, for example, information about the date and time of a particular transaction, information about the device used for the transaction, the originating location, and the like. Alerts may be delivered, for example, via text, SMS, email, or some other real-time notification system. Alerts may be made available to the user via a standalone application or browser accessible dashboard user interface that the user can view at his/her convenience. In some embodiments alerts may be text-based, while in some embodiments alerts may include a user interface generated by the AOA system.
[0016] In some embodiments, the monitoring and/or authentication performed by the AOA system is performed as a “background” or “behind the scenes” process which is “invisible” or “seamless” to the individual. For example, a transaction or activity may be referred from an online service provider to one embodiment of an AOA system, which may authenticate the transaction or activity without requiring any additional information from the individual. This may improve the individual's user experience by streamlining the authentication process.
[0017] As described herein, a transaction may comprise, for example, commercial and/or financial transactions (for example, making a purchase), as well as online interactions between an individual and an OSP, including a hypertext transfer protocol request. In some embodiments a transaction may be an activity and/or include an activity, such as an activity performed by an individual. Further, as described herein, an activity performed by an individual may comprise, for example, a particular step associated with a transaction (for example, browsing an online product catalog, adding an item to an online shopping cart, proceeding through a checkout process, placing an order, etc.); activities such as viewing and/or updating personal information (for example, address, credit card information, account username, account password, etc.); activities such as reading articles; activities such as receiving, reading, and/or sending e-mails or text messages; activities such as logging into and/or accessing a social networking website or service; and/or any other activity an individual may conduct via the Internet or network. In some embodiments, an activity may correspond to one or more of a “click,” “touch,” “swipe,” “gesture,” or user interaction with an element of web page. For example, an activity may correspond to an individual's clicking on or touching a button, link, or other user-selectable element of a web page, or to an individual's swipe or gesture with respect to a touch-enabled user interface, or other similar actions.
[0018] One embodiment may be a computer system comprising: a computing device in communication with a physical data store storing profile data for an individual, wherein the computing device is configured to: receive, from a user computing device, a request to authenticate an identity for an individual, wherein the request includes at least some personally identifying information for the individual; authenticate the identity of the individual, based on the personally identifying information for the individual and based on profile data for the individual accessed from the physical data store; issue, to the user computing device, a virtual credential for the individual; associate the virtual credential with the profile data for the individual; receive, from a requesting entity, a request to authenticate a transaction, wherein the request includes the virtual credential; access a risk profile associated with the profile data for the individual, wherein the profile data for the individual is accessed using the virtual credential; determine whether a level of trust for the transaction is below a threshold trust level, wherein the level of trust is based on an analysis of the risk profile and the transaction; and in response to a determination that the level of trust for the transaction is below the threshold trust level, provide an indication to the requesting entity that further authentication of the individual is recommended.
[0019] In another embodiment, the computing device is configured to update the risk profile to record information about the transaction in response to a determination that the level of trust for the transaction is not below the threshold trust level.
[0020] In another embodiment, the computing device is further configured to send an alert to the individual in response to a determination that the level of trust for the transaction is below the threshold level.
[0021] Some embodiments may comprise a computer-implemented method for authenticating a transaction for an individual, the computer-implemented method comprising: receiving, from a requesting entity, a request to authenticate a transaction for an individual, wherein the request includes a virtual credential, wherein the virtual credential was provided to the requesting entity from the individual; accessing a risk profile associated with profile data for the individual, wherein the profile data for the individual is accessed from a profile data store using the virtual credential; determining whether a level of trust for the transaction is below a threshold trust level, wherein the level of trust is based on an analysis of the risk profile and the transaction; and in response to a determination that the level of trust for the transaction is below the threshold trust level, providing an indication to the requesting entity that further authentication of the individual is recommended; or in response to a determination that the level of trust for the transaction is not below the threshold trust level, updating the risk profile to record information about the transaction.
[0022] In an embodiment, the computer-implemented method further comprises sending an alert to the individual in response to a determination that the level of trust for the transaction is below the threshold level.
[0023] In an embodiment, the computer-implemented method further comprises updating the risk profile to record information about the transaction in response to a determination that the level of trust for the transaction is not below the threshold trust level.
[0024] Another embodiment may be a non-transitory computer storage having stored thereon a computer program, the computer program including modules configured for execution by a computing system and including at least: an individual authentication module configured to: receive, from a user computing device, a request to authenticate an identity for an individual, wherein the request includes at least some personally identifying information for the individual; authenticate the identity of the individual, based on the personally identifying information for the individual and based on profile data for the individual accessed from the physical data store; issue, to the user computing device, a virtual credential for the individual; associate the virtual credential with the profile data for the individual; a risk assessment module configured to: receive, from a requesting entity, a request to authenticate a transaction, wherein the request includes the virtual credential; access a risk profile associated with the profile data for the individual, wherein the profile data for the individual is accessed using the virtual credential; determine whether a level of trust for the transaction is below a threshold trust level, wherein the level of trust is based on an analysis of the risk profile and the transaction; and in response to a determination that the level of trust for the transaction is below the threshold trust level, provide an indication to the requesting entity that further authentication of the individual is recommended.
[0025] In another embodiment, the risk profile includes a mapping of one or more transaction types and respective one or more threshold trust levels.
[0026] In another embodiment, the risk profile includes a record of historical transactions for the individual, and wherein the threshold trust level is determined at least in part by analyzing the frequency of historical transactions for the individual.
[0027] In another embodiment, the transaction is one of a financial transaction, an online interaction between the individual and the requesting entity, a hypertext transfer protocol request, or an activity.
[0028] In another embodiment, the virtual credential includes a unique digital token, and wherein the virtual credential is associated with one or more computing devices for the individual.
[0029] In another embodiment, the level of trust and the threshold trust level are numeric ratings in the range of one to ten.
[0030] In another embodiment, the level of trust and the threshold trust level are risk ratings indicating a degree of risk associated with a transaction type.
[0031] As described herein, an online service provider (“OSP”) may comprise, for example, websites, online services, mobile web applications, network services, and the like
BRIEF DESCRIPTION OF THE DRAWINGS
[0032] FIG. 1A is a block diagram which illustrates an exemplary data flow between one or more consumer devices, service providers/retailers, and an always-on authentication system, according to one embodiment.
[0033] FIG. 1B is a block diagram which illustrates another exemplary data flow between one or more consumer devices, service providers/retailers, and an always on authentication system, according to one embodiment.
[0034] FIG. 1C is a block diagram which illustrates another exemplary data flow between one or more consumer devices, service providers/retailers, and an always on authentication system, according to one embodiment.
[0035] FIG. 2 is a logical flow diagram of a process for an individual to initially authenticate his/her identity and initiate monitoring of his/her transactions and/or activities involving an embodiment of an AOA system, such as the AOA system of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 .
[0036] FIG. 3 is a logical flow diagram of a process for monitoring an individual's transactions and/or activities involving an embodiment of an AOA system, such as the AOA system of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 .
[0037] FIG. 4 illustrates an example interface of an online shopping website in which an individual's activity has been authenticated by an AOA system, such as the AOA system of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 .
[0038] FIG. 5 illustrates another example user interface of an online checkout cart process using an AOA system, such as the AOA system of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 .
[0039] FIG. 6 illustrates another example user interface of an online checkout cart process using an AOA system, such as the AOA system of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 .
[0040] FIG. 7 illustrates an example user interface of a website which allows the individual to manage their identity and/or virtual credentials in accordance with an AOA system, such as the AOA system of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 .
[0041] FIG. 8 is an example user interface of a website operator merchant portal whereby a website operator may manage the activity authentication settings associated with its website.
[0042] FIG. 9 is a block diagram showing an embodiment in which an always-on authentication computing system (or simply “computing system”) is in communication with one or more networks, and various systems are also in communication with the one or more networks.
DETAILED DESCRIPTION
[0043] Embodiments of the disclosure will now be described with reference to the accompanying figures, wherein like numerals refer to like elements throughout. The terminology used in the description presented herein is not intended to be interpreted in any limited or restrictive manner, simply because it is being utilized in conjunction with a detailed description of certain specific embodiments of the disclosure. Furthermore, embodiments of the disclosure may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the embodiments of the disclosure herein described.
High Level Data Flows
[0044] FIG. 1A is a block diagram which illustrates an exemplary data flow between one or more consumer devices (e.g., computing devices) 162, online service providers (“OSPs”) 164, and an Always-On Authentication (“AOA”) system 100, according to one embodiment. In the data flow of FIG. 1A , one embodiment of the AOA system sets up or initializes the authentication monitoring for an individual. At step (1) the AOA system may authenticate a consumer or individual's identity (“ID”). For example the AOA system may receive identifying information from the individual, which the AOA system can use to initially authenticate the individual. During this step the AOA system may receive from the individual an indication of particular items of personal information the individual wants to have monitored, which the AOA system can use to generate an initial risk profile for the individual. At step (2), once the individual's identity has been authenticated, the AOA system 100 may generate and/or issue a virtual credential (VC) to the individual and/or consumer devices 162. At step (3), the individual then interacts with the OSPs 164, for example, over a network 160. During the course of these transactions and/or activities, the individual, via his/her consumer device, may provide the VC to OSPs 164. The OSPs 164 may then in turn use the VC to request further authentication from the AOA system of the individual's transactions and/or activities.
[0045] FIG. 1B is block diagram which illustrates another exemplary dataflow between the consumer devices 162, AOA system 100, and OSPs 164. This data flow continues from FIG. 1A , after the individual has completed the initial authentication process. At step (4) the AOA system receives from the OSPs 164 a request to validate, or authenticate, a transaction and/or activity associated with the individual and/or the VC as provided by the individual to the OSP 164. At step (5), the AOA system 100 attempts to authenticate the transaction and/or activity, and/or validate the virtual credential, for example, via a consumer authentication/validation module 104. At step (6) the AOA system may access a risk profile associated with the individual. The risk profile may be accessed from, for example, the virtual credential, risk profile, and/or identity data source 108. The AOA system may then use the risk profile to assess the risk level of the transaction and/or activity being referred from the OSPs 164. If the level of risk for the transaction and/or activity is determined to be a certain level, then at step (7) the system may provide an indication to the OSP 164 indicating whether the activity is trusted, or if additional authentication may be required to authenticate the user's identity. Although not shown in FIG. 1B , the AOA system may also send an alert to the individual if the level of risk for the transaction and/or activity is determined to be a certain level.
[0046] FIG. 1C is block diagram which illustrates another exemplary dataflow between an individual's consumer device(s) 162, AOA system 100, and OSPs 164. In the data flow of FIG. 1C , one embodiment of the AOA system sets up or initializes the authentication monitoring for an individual.
[0047] Beginning at step (1), a consumer or individual may interact with one or more OSPs 164, for example by surfing the web (e.g. the Internet or other network) or by using an application, or “app” (e.g. a web application, an application installed on the individual's consumer device(s) 162, and the like). During these interactions the individual may provide identity information (e.g. a name, a username, a digital identification, a virtual credential, a token, a cookie, a supercookie, or any other type of identifier associated with the individual and/or the individual's consumer device(s) 162).
[0048] At step (2), a service provider (e.g. one of the one or more OSPs 164) may check the identity information provided by the individual. In some embodiments, the service provider checks if the individual has provided a token that is valid and associated with the individual, for example by sending a token validation request to the AOA system 100. The AOA system 100 may receive the token (and/or other identity information) and provide verification to the service provider that the token is valid and associated with the individual and/or enable an Always-On Authentication (“AOA”) ID for the individual to the service provider. In some embodiments, the AOA ID may be, for example, a virtual credential. Once the service provider receives verification that the token is valid and associated with the individual, and/or the service provider receives notification from the AOA system that the AOA ID is enabled, the service provider may then authorize the individual's activity or transaction.
[0049] At step (3), the individual may then continue to interact with the service provider (and/or the one or more OSPs 164) using the AOA ID and/or the token. For each activity or transaction, the service provider may, but need not, submit additional requests to validate the token and/or the AOA ID to the AOA system, for example as additional security. For example, activities or transactions which the service provider has determined or identified as low-risk may not give rise to additional validation requests, while activities or transactions which the service provider has determined or identified as medium or high-risk for the particular individual, e.g., based on the browsing history of the individual, may give rise to additional validation requests.
[0050] In some embodiments, the individual may not provide a token to the service provider. For example, if the individual is using an unregistered computing device to access the service provider's website or application, the individual may not yet have a token associated with the unregistered computing device. Further, in some embodiments, the individual may provide an invalid token which the AOA system is unable to validate. For example, the individual may provide an invalid token which is not associated with the individual's account (as might be the case if the token is expired, deactivated, deauthorized, etc.) Thus, step (4) illustrates scenarios in which the individual has not provided a token to the service provider, or if the AOA system is unable to validate a token provided as described at step (2) above.
[0051] At step (4), the service provider may provide one or more options to the individual to provide identity information. FIG. 1C illustrates three options at step (4), however more options may be possible as well. According to the embodiment in FIG. 1C , at step (4) the service provider may prompt the individual for credentials (e.g. a username and a password associated with an account registered with the service provider); prompt the individual to register with the service provider (e.g. if the individual does not have an account registered with the service provider, and/or the individual may be prompted to login using an AOA ID.
[0052] If the third option is selected, then at step (5), the service provider may provide one or more options for the individual to login using an AOA ID. FIG. 1C illustrates two options at step (5), however more options may be possible as well. According to the embodiment in FIG. 1C , at step (5) the service provider may prompt the individual to provide an existing AOA ID associated with the individual's account, and/or prompt the individual to create a new AOA ID. In any event, the service provider submits the individual's request to the AOA system at step (6), which may then result in the AOA unlocking the individual's data. For example, the AOA system may validate the existing AOA ID, if provided, or create the new AOA ID for the individual, as the case may be. Some benefits of unlocking the individual's data, and/or enabling an existing AOA ID or a newly created AOA ID, may include, for example, accessing and providing consumer data from consumer data sources (e.g. virtual credential, risk profile, and/or identity data source 108, and/or data sources 166 described herein) to facilitate use of automatic-fill (“auto-fill”) forms (e.g. web forms requesting input of individual profile data). Additionally, the AOA ID enables service providers to know or recognize their customers, which may facilitate the use of consumer profile data for personalization.
[0053] As described further herein, the AOA ID may be used on a per-transaction, interaction, or activity basis, and in some cases the individual may be prompted for additional information to authorize the transaction, interaction, or activity. In some embodiments the AOA ID may also enable the individual to receive alerts generated by the AOA system for transactions, interactions, or activities which may potentially be fraudulent or inconsistent with a recognized risk profile or pattern for the individual.
[0054] An AOA ID or a virtual credential may have one or more levels of associated data attributes for the individual. The one or more levels may correspond to different degrees of privacy and/or amount of data associated with the individual. For example, some levels may include basic, private, identity, payment, and/or marketing. Thus, basic level data attributes may include for example data which is publicly known about the individual, such as a name, address, phone number, date of birth, birthplace, etc. Private level data attributes may include for example data which is private or otherwise not publicly known about the individual, such as a credit report, personal finance information, credit information, healthcare information, and the like. Identity level information may include even more private data about the individual, such as a social security number, a driver's license identification number, or other secured form of identification. Payment level information may include, for example, data for one or more credit and/or debit cards for the individual (e.g. number, expiration, security code) which may be used, for example, by a service provider to enable automatic payment or facilitate online checkout processes and systems. Marketing level information may include, for example, marketing preferences for the individual, such as a medium of contact (e.g. email, phone, text or SMS, etc.), a frequency of contact (e.g. daily, weekly, monthly, etc.), type of information acceptable to contact the individual about (e.g. sales/coupons/promotions), and the like. In some embodiments of the AOA system, some or all of the data attributes associated with the AOA ID, including but not limited to the one or more levels described above, may be automatically generated and/or populated based on, for example, accessed consumer profile data (e.g. from a virtual credential, risk profile, and/or identity data source 108, and/or data sources 166 described herein) such as a credit report for the individual. In some embodiments of the AOA system, some or all of the data attributes associated with the AOA ID, including but not limited to the one or more levels described above, may be manually provided by the individual or by the service provider (e.g. on behalf of the individual).
[0055] At step (7), once the individual's data has been successfully unlocked (e.g. the existing AOA ID credentials are verified by the AOA system, or the new AOA ID is successfully created for the individual, etc.), the AOA system may issue a new token to the individual's consumer device(s) 162. The data flow may then return, for example, to step (3), where the individual may use the AOA ID, and/or token associated with the AOA ID and/or the consumer device(s) 162, for subsequent activities and/or transactions with the service provider (and/or the one or more OSPs 164).
[0056] In some embodiments, once the AOA ID has been provided or otherwise enabled for use for the individual, the individual may be charged a service fee for use of the AOA ID and the always-on authentication monitoring services. For example, the individual may pay a periodic fee (e.g. monthly, annually, etc.). Payment may be facilitated by automatically populating the AOA ID with payment information, for example from a credit report, as described herein. Individuals subscribing to the AOA service, as provided by the AOA systems and methods described herein, gain the benefit of full authentication during the course of their day-to-day transactions and interactions online.
Examples of Methods Performed by an Always-on Authentication System
[0057] FIG. 2 is a logical flow diagram of a process 200 for an individual to initially authenticate his/her identity and initiate monitoring of his/her transactions and/or activities involving an embodiment of an AOA system, such as the AOA system 100 of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 . Beginning at block 205, the AOA system 100 may initially authenticate the individual's identity. Next at block 215, the AOA system 100 can, after the individual's identity has been authenticated, issue a virtual credential for the individual and/or the individual's devices. The individual may associate this virtual credential with one or more of their own devices for use when they conduct transactions online, for example. Next at block 220, the AOA system can monitor the activity/transactions associated with the virtual credential and/or individual's information to identify potential fraud risk. Next at block 225, AOA system may assess the risk and/or trust level of the monitored activity and/or transactions. At block 230, the system determines whether or not the trust level is too low. In response to a determination that the trust level is too low, the system may proceed to block 235 where it may initiate further individual authentication. According to some embodiments, at block 240, the system may also provide an alert to the individual indicating that their identity may be associated with a potential risk. With respect once again to the determination made at block 230, in response to a determination that the trust level is not too low (e.g. the activity is trusted or the level of risk is minimal), the system may proceed to block 245 where it may update a risk profile associated with the individual. The risk profile associated with the individual may include information about certain activities and/or transactions which an individual conducts regularly, as well as risk ratings associated with the activities and/or transactions. At block 245 then, the risk profile may be updated to reflect, for example, that the particular activity and/or transaction authenticated by the process 200 is trusted or low-risk. Such information may be accessed, for example as shown in the process of FIG. 3 , for future authentication requests, and used to develop behavioral trends for the individual over time.
[0058] FIG. 3 is a logical flow diagram of a process 300 for monitoring an individual's transactions and/or activities involving an embodiment of an AOA system, such as the system 100 of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 . At block 305 the AOA system may access or receive transactions and/or activities associated with an individual. For example, in one embodiment the AOA system may receive a request to authenticate a transaction or activity from a requesting entity, such as an OSP. Here the AOA system may also receive a VC associated with the individual and/or his/her device, if the individual has been issued a VC. Next at block 310, the system may generate and/or update a risk profile associated with the VC. For example, the system may compare behavioral patterns associated with the risk profile to the user activity/transaction and identify whether or not the transactions and/or activities are consistent with the behavioral patterns associated with the risk profile. Next at block 315, the system may assess the risk and/or trust level of the transaction and/or activity. At block 320, the system determines whether the trust is below a certain sensitivity or threshold level for the transaction and/or activity. If the system determines that the trust level is below the sensitivity or threshold level for the transaction and/or activity, the system may proceed to block 325. At block 325 the system may initiate further individual authentication in order to authenticate the individual. At this point, the system may then proceed to block 330 and the risk profile associated with the virtual credential may be updated based on the assessed risk and/or trust level of the current activity or transaction. Alternatively, proceeding from block 320, if the system determines that the trust level is not below the sensitivity or threshold level for a certain activity or transaction, then the system may determine that the activity or transaction is trusted and simply update the risk profile at block 330 to reflect that the activity is a trusted activity. Finally, at block 335, the system may optionally provide an alert to the individual once the system determines that the current activity or transaction is below the certain trust level.
Examples of User Interfaces for an Always-on Authentication System
[0059] FIGS. 4 , 5, 6, 7, and 8 illustrate several example user interfaces as used in one or more embodiments of an always-on authentication system, such as the AOA system 100 of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 . The sample user interfaces may be displayed, for example, via a web browser or standalone application. However, in some embodiments, the sample user interfaces shown in FIGS. 4 , 5, 6, 7, and 8 may also be displayed on a suitable computer device, such as a personal computer, desktop, laptop, cell/smart phone, tablet, or portable computing device, and are not limited to the samples as described herein. The user interfaces are examples of only certain features that an AOA system may provide. In other embodiments, additional features may be provided, and they may be provided using various different user interfaces and software code. Depending on the embodiment, the user interface and functionality described with reference to FIGS. 4 , 5, 6, 7, and 8 may be provided by software executing on a computing device, by an AOA system located remotely that is in communication with the computing device via one or more networks, and/or some combination of software executing on the computing device and the address verification system.
[0060] FIG. 4 illustrates an example interface 400 of an online shopping website in which an individual's activity has been authenticated by the AOA system. In one embodiment, the individual's activity may have been authenticated based on his/her virtual credential. As FIG. 4 illustrates, the particular individual, John, is presented a display message 405 indicating that his activity has been authenticated for his identity. This message may be displayed, for example, with respect to FIG. 4 , at some point during a checkout process for an online shopping cart. In some embodiments, no message may be displayed at all and the individual (e.g. John) may enjoy a completely seamless user experience.
[0061] FIG. 5 presents another example user interface 500 of an online checkout cart process. In this example the individual is being prompted for his or her password because the AOA system has identified the current activity as outside of the trust level required for completing the transaction. The AOA system may have determined this based on, for example, the individual risk profile, behavioral patterns for the individual associated with the individual risk profile, and/or the OSP risk profile. Thus, the AOA system may have provided an indication to the website that further authentication is recommended or required. According to a display message 505 shown in FIG. 5 , to proceed further, the individual must provide additional identity authentication information. In this example, the additional identity authentication information being requested by the website is the individual's password 510. In other embodiments, additional information may be required. For example, out-of-wallet type questions which ask, for example, personal questions which only the individual may know the answer, such as the individual's make and model of their first car, the name of their first boy/girlfriend, where they were born, where they went to high school, the name of their favorite teacher in high school, and other types of personally identifying questions. Once the individual provides his or her password (or other identity authentication information that may be required), the individual can select the “continue” option as shown in FIG. 5 . Once the individual's information is further authenticated the individual may proceed through the checkout process.
[0062] FIG. 6 is another example user interface 600 of a checkout process similar to the one described with respect to FIG. 5 above. In this example the user's activity has again been identified outside the trust level for this particular transaction on this website. As such, the individual is being prompted to provide additional identity authentication information via a display message 605. In this example, the individual is being prompted to provide the make and model of their first car 610 as well as their date of birth 615. And again as was mentioned with respect to FIG. 5 , additional information may also be required in any possible combination that the website may decide to setup depending on the particular transaction and trust level.
[0063] FIG. 7 illustrates an example user interface 700 of a website which allows the individual to manage their identity and/or virtual credentials in accordance with an embodiment of the AOA system 100, such as the AOA system 100 of FIG. 1A , FIG. 1B , FIG. 1C , and/or FIG. 9 . As FIG. 7 shows, the user interface 700 presents various information including alerts 705 which provide an indication of various devices 710, dates 715, and websites 715 associated with the particular transaction being alerted. Thus, for example, here an individual is being shown that on July 15th their iPhone was used to access google.com and as a result an alert may have been generated. Similarly, in another example, on Aug. 6, 2012, the individual's HP laptop may have been used to access ubid.com, and as a result of that transaction an alert may have been generated for the individual. FIG. 7 also illustrates various data fields associated with the individual's personal information which may be actively monitored 725 by the AOA system in conjunction with their virtual credential. In some embodiments, the individual may be presented with the option to selectively choose which of these data fields or personal identifying information to actively monitor. Thus, for example, an individual may want the AOA system to actively monitor usage of their name 760, address 735, social security number 740, phone number 745, date of birth 750, and/or email address 755. Other personal information not shown in FIG. 7 may also be made available for selection for monitoring.
[0064] FIG. 8 is an example user interface 800 of a website operator merchant portal whereby a website operator may manage the activity authentication settings associated with its website. In one embodiment, the website operator may be able to manage activity authentication settings 805 associated with various transactions and activities on their website, such as via an activity map which associates certain activities 810 with certain risk levels. For example, as FIG. 8 illustrates, the website operator may be able to configure authentication and/or associate risk levels for activities such as login, checkout, changing an address, changing a password, and other similar activities. As FIG. 8 shows, for each of the activities being configured, the website operator may be presented with an option to enable always-on authentication 815 for a particular activity or transaction and specify a risk level 820 associated with that activity. Thus, for example, in FIG. 8 , the website operator has configured the activity of logging in to use always-on authentication, but with a risk level of “low.” Thus, for example, an individual may provide their virtual credential to the website and instead of logging in to the website, the virtual credential may provide sufficient authentication. Thus, no further authentication may be required because the risk level has been set to “low.” In other embodiments, the risk level may be set higher which may trigger the website to prompt the individual for additional login information along with the virtual credential being provided. Thus, for example, the activity level for “checking out” has been enabled with respect to FIG. 8 with a risk level of “medium.” Thus, for example, the individual may not be able to complete the checkout process without first providing some additional authentication information such as a password to the website. Further with respect to FIG. 8 , the activity levels of changing an address and changing a password have also been enabled for always-on authentication, but with a risk level of “high” which may trigger the website to require further authentication even if a virtual credential has been provided.
[0065] FIG. 8 also illustrates an option for the website operator to customize their activity authentication settings 825. In this example, they may specify a particular template 830 and upload the template 835. The template might include information as described above with respect to various transactions or activities, whether to enable always on authentication for each transaction or activity, and what risk level is acceptable for each transaction or activity. In other embodiments, the template may be more of a web-based template which may include details about the website content itself or website form itself, associate various authentication settings with various web forms and/or elements of web forms may be customizable at various levels of detail.
[0066] In some embodiments, the website operator may have the option to tag certain website functionality (e.g., buttons, links, actions, segments of code, etc.) which may be associated with certain risk levels. The tags may be configurable, for example, via the activity map and/or via a configuration user interface such as the one shown in FIG. 8 . In some embodiments, the website operator may further be provided an authentication code module configured to access the processes and features of the AOA system directly. For example, the authentication code module may be generated by the AOA system and provided to the website operator, which may then install the code module to enable always-on authentication services for the website or various activities provided by the website. In some embodiments, the authentication code module may be configured to associate activities with risk level, or may be configured to access an activity map and/or other always-on authentication settings associated with the website. The authentication code module may comprise, for example, HTML, Javascript, and/or code in any other programming language useable by a website.
Example System Implementation and Architecture
[0067] FIG. 9 is a block diagram showing an embodiment in which an always-on authentication computing system 100 (or simply “computing system 100”) is in communication with a network 160 and various systems, such as user computing device(s) 162 and web-based and/or online service(s) 164, are also in communication with the network 160. The computing system 100 may be used to implement systems and methods described herein.
[0068] The computing system 100 includes, for example, a personal computer that is IBM, Macintosh, or Linux/Unix compatible or a server or workstation. In one embodiment, the computing system 100 comprises a server, a laptop computer, a smart phone, a personal digital assistant, a kiosk, or an media player, for example. In one embodiment, the exemplary computing system 100 includes one or more central processing unit (“CPU”) 105, which may each include a conventional or proprietary microprocessor. The computing system 100 further includes one or more memory 130, such as random access memory (“RAM”) for temporary storage of information, one or more read only memory (“ROM”) for permanent storage of information, and one or more mass storage device 120, such as a hard drive, diskette, solid state drive, or optical media storage device. Typically, the modules of the computing system 100 are connected to the computer using a standard based bus system 180. In different embodiments, the standard based bus system could be implemented in Peripheral Component Interconnect (“PCI”), Microchannel, Small Computer System Interface (“SCSI”), Industrial Standard Architecture (“ISA”) and Extended ISA (“EISA”) architectures, for example. In addition, the functionality provided for in the components and modules of computing system 100 may be combined into fewer components and modules or further separated into additional components and modules.
[0069] The computing system 100 is generally controlled and coordinated by operating system software, such as Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In other embodiments, the computing system 100 may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface, such as a graphical user interface (“GUI”), among other things.
[0070] The exemplary computing system 100 may include one or more commonly available input/output (I/O) devices and interfaces 110, such as a keyboard, mouse, touchpad, and printer. In one embodiment, the I/O devices and interfaces 110 include one or more display devices, such as a monitor, that allows the visual presentation of data to a user. More particularly, a display device provides for the presentation of GUIs, application software data, and multimedia presentations, for example. The computing system 100 may also include one or more multimedia devices 140, such as speakers, video cards, graphics accelerators, and microphones, for example.
[0071] In the embodiment of FIG. 9 , the I/O devices and interfaces 110 provide a communication interface to various external devices. In the embodiment of FIG. 9 , the computing system 100 is electronically coupled to a network 160, which comprises one or more of a LAN, WAN, and/or the Internet, for example, via a wired, wireless, or combination of wired and wireless, communication link 115. The network 160 communicates with various computing devices and/or other electronic devices via wired or wireless communication links.
[0072] According to FIG. 9 , in some embodiments information may be provided to the computing system 100 over the network 160 from one or more data sources 166. The data sources 166 may include one or more internal and/or external data sources. The data sources 166 may include internal and external data sources which store, for example, credit bureau data (for example, credit bureau data from File OneSM) and/or other consumer data. In some embodiments, one or more of the databases or data sources may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, and/or a record-based database.
[0073] In the embodiment of FIG. 9 , the computing system 100 includes a dashboard-user interface module 102, a consumer authentication/validation module 104, an alert module 106, a risk profile/assessment module 107, and a virtual credential, risk profile, and/or identity data source 108. The dashboard/user interface module 102 may be configured to provide one or more user interfaces, for example the user interfaces described with respect to FIGS. 4 , 5, 6, 7, and 8, as well as other user interfaces as may be generated by the AOA system 100. The consumer authentication/validation module 104 may be configured to authenticate and/or validate a consumer's identity for example by accessing data in the virtual credential risk profile and/or identity data store 108, and performing various of the methods and processes described herein. The risk profile/assessment module 107 may be configured to access a risk profile stored in the risk profile and/or identity data store 108 and use the risk profile to assess the trust level associated with a particular activity or transaction being referred from the website/online service 164. The risk assessment may be performed with respect to the various processes and methods described herein. The alert module 106 may be configured to provide an alert to an individual in response to a determination that the risk associated with a particular activity or transaction is too high for a particular risk profile associated with the virtual credential of the user. These and other modules in the computing system 100 may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
[0074] In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, or any other tangible medium. Such software code may be stored, partially or fully, on a memory device of the executing computing device, such as the computing system 100, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.
Other
[0075] Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The code modules may be stored on any type of non-transitory computer-readable medium or computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be transmitted as generated data signals (for example, as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (for example, as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, for example, volatile or non-volatile storage.
[0076] The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
[0077] Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
[0078] Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
[0079] All of the methods and processes described above may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. For example, the methods described herein may be performed by the address verification computing system 100 and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tape, flash drives, and optical data storage devices.
[0080] It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
Claims
What is claimed is:
1. A computer system for monitoring transactions for an individual, the computer system comprising:
a computing device in communication with a physical data store storing profile data for an individual, wherein the computing device is configured to:
receive, from a user computing device, a request to authenticate an identity for an individual, wherein the request includes at least some personally identifying information for the individual;
authenticate the identity of the individual, based on the personally identifying information for the individual and based on profile data for the individual accessed from the physical data store;
issue, to the user computing device, a virtual credential for the individual;
associate the virtual credential with the profile data for the individual;
receive, from a requesting entity, a request to authenticate a transaction, wherein the request includes the virtual credential;
access a risk profile associated with the profile data for the individual, wherein the profile data for the individual is accessed using the virtual credential;
determine whether a level of trust for the transaction is below a threshold trust level, wherein the level of trust is based on an analysis of the risk profile and the transaction; and
in response to a determination that the level of trust for the transaction is below the threshold trust level, provide an indication to the requesting entity that further authentication of the individual is recommended.
2. The computer system of claim 1, wherein the computing device is configured to update the risk profile to record information about the transaction in response to a determination that the level of trust for the transaction is not below the threshold trust level.
3. The computer system of claim 1, wherein the level of trust and the threshold trust level are numeric ratings in the range of one to ten.
4. The computer system of claim 1, wherein the level of trust and the threshold trust level are risk ratings indicating a degree of risk associated with a transaction type.
5. The computer system of claim 1, wherein the computing device is further configured to send an alert to the individual in response to a determination that the level of trust for the transaction is below the threshold level.
6. The computer system of claim 1, wherein the risk profile includes a mapping of one or more transaction types and respective one or more threshold trust levels.
7. The computer system of claim 1, wherein the risk profile includes a record of historical transactions for the individual, and wherein the threshold trust level is determined at least in part by analyzing the frequency of historical transactions for the individual.
8. The computer system of claim 1, wherein the transaction is one of a financial transaction, an online interaction between the individual and the requesting entity, a hypertext transfer protocol request, or an activity.
9. The computer system of claim 1, wherein the virtual credential includes a unique digital token, and wherein the virtual credential is associated with one or more computing devices for the individual.
10. A computer-implemented method for authenticating a transaction for an individual, the computer-implemented method comprising:
receiving, from a requesting entity, a request to authenticate a transaction for an individual, wherein the request includes a virtual credential, wherein the virtual credential was provided to the requesting entity from the individual;
accessing a risk profile associated with profile data for the individual, wherein the profile data for the individual is accessed from a profile data store using the virtual credential;
determining whether a level of trust for the transaction is below a threshold trust level, wherein the level of trust is based on an analysis of the risk profile and the transaction; and
in response to a determination that the level of trust for the transaction is below the threshold trust level, providing an indication to the requesting entity that further authentication of the individual is recommended; or
in response to a determination that the level of trust for the transaction is not below the threshold trust level, updating the risk profile to record information about the transaction.
11. The computer-implemented method of claim 10, further comprising sending an alert to the individual in response to a determination that the level of trust for the transaction is below the threshold level.
12. The computer-implemented method of claim 10, further comprising updating the risk profile to record information about the transaction in response to a determination that the level of trust for the transaction is not below the threshold trust level.
13. The computer-implemented method of claim 10, wherein the risk profile includes a record of historical transactions for the individual, and wherein the threshold trust level is determined at least in part by analyzing the frequency of historical transactions for the individual.
14. The computer-implemented method of claim 10, wherein the risk profile includes a mapping of one or more transaction types and respective one or more threshold trust levels.
15. The computer-implemented method of claim 10, wherein the transaction is one of a financial transaction, an online interaction between the individual and the requesting entity, a hypertext transfer protocol request, or an activity.
16. Non-transitory computer storage having stored thereon a computer program, the computer program including modules configured for execution by a computing system and including at least:
an individual authentication module configured to:
receive, from a user computing device, a request to authenticate an identity for an individual, wherein the request includes at least some personally identifying information for the individual;
authenticate the identity of the individual, based on the personally identifying information for the individual and based on profile data for the individual accessed from the physical data store;
issue, to the user computing device, a virtual credential for the individual;
associate the virtual credential with the profile data for the individual;
a risk assessment module configured to:
receive, from a requesting entity, a request to authenticate a transaction, wherein the request includes the virtual credential;
access a risk profile associated with the profile data for the individual, wherein the profile data for the individual is accessed using the virtual credential;
determine whether a level of trust for the transaction is below a threshold trust level, wherein the level of trust is based on an analysis of the risk profile and the transaction; and
in response to a determination that the level of trust for the transaction is below the threshold trust level, provide an indication to the requesting entity that further authentication of the individual is recommended.
17. The non-transitory computer storage of claim 16, wherein the risk assessment module is configured to update the risk profile to record information about the transaction in response to a determination that the level of trust for the transaction is not below the threshold trust level.
18. The non-transitory computer storage of claim 16, wherein the virtual credential includes a unique digital token, and wherein the virtual credential is associated with one or more computing devices for the individual
19. The non-transitory computer storage of claim 16, wherein the risk profile includes a record of historical transactions for the individual, and wherein the threshold trust level is determined at least in part by analyzing the frequency of historical transactions for the individual.
20. The non-transitory computer storage of claim 16, wherein the transaction is one of a financial transaction, an online interaction between the individual and the requesting entity, a hypertext transfer protocol request, or an activity.
Patent Citations (444)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4346442(A) | 1982-08-01 | Musmanno | Applicant |
| US4755940(A) | 1988-07-01 | Brachtl et al. | Applicant |
| US4795890(A) | 1989-01-01 | Goldman | Applicant |
| US4977595(A) | 1990-12-01 | Ohta et al. | Applicant |
| US5220501(A) | 1993-06-01 | Lawlor et al. | Applicant |
| US5336870(A) | 1994-08-01 | Hughes et al. | Applicant |
| US5351293(A) | 1994-09-01 | Michener et al. | Applicant |
| US5361201(A) | 1994-11-01 | Jost et al. | Applicant |
| US5383113(A) | 1995-01-01 | Kight et al. | Applicant |
| US5500513(A) | 1996-03-01 | Langhans et al. | Applicant |
| US5590038(A) | 1996-12-01 | Pitroda | Applicant |
| US5640577(A) | 1997-06-01 | Scharmer | Applicant |
| US5659731(A) | 1997-08-01 | Gustafson | Applicant |
| US5715314(A) | 1998-02-01 | Payne et al. | Applicant |
| US5844218(A) | 1998-12-01 | Kawan et al. | Applicant |
| US5857174(A) | 1999-01-01 | Dugan | Applicant |
| US5903830(A) | 1999-05-01 | Joao et al. | Applicant |
| US5903881(A) | 1999-05-01 | Schrader et al. | Applicant |
| US5956693(A) | 1999-09-01 | Geerlings | Applicant |
| US5999596(A) | 1999-12-01 | Walker et al. | Applicant |
| US6021943(A) | 2000-02-01 | Chastain | Applicant |
| US6038551(A) | 2000-03-01 | Barlow et al. | Applicant |
| US6064990(A) | 2000-05-01 | Goldsmith | Applicant |
| US6072894(A) | 2000-06-01 | Payne | Applicant |
| US6073106(A) | 2000-06-01 | Rozen et al. | Applicant |
| US6073140(A) | 2000-06-01 | Morgan et al. | Applicant |
| US6115694(A) | 2000-09-01 | Cheetham et al. | Applicant |
| US6128602(A) | 2000-10-01 | Northington et al. | Applicant |
| US6233566(B1) | 2001-05-01 | Levine et al. | Applicant |
| US6253202(B1) | 2001-06-01 | Gilmour | Applicant |
| US6254000(B1) | 2001-07-01 | Degen et al. | Applicant |
| US6263447(B1) | 2001-07-01 | French et al. | Applicant |
| US6282658(B2) | 2001-08-01 | French et al. | Applicant |
| US6311169(B2) | 2001-10-01 | Duhon | Applicant |
| US6321339(B1) | 2001-11-01 | French et al. | Applicant |
| US6327578(B1) | 2001-12-01 | Linehan | Applicant |
| US6353778(B1) | 2002-03-01 | Brown | Applicant |
| US6422462(B1) | 2002-07-01 | Cohen | Applicant |
| US6463533(B1) | 2002-10-01 | Calamera et al. | Applicant |
| US6473740(B2) | 2002-10-01 | Cockrill et al. | Applicant |
| US6496936(B1) | 2002-12-01 | French et al. | Applicant |
| US6523041(B1) | 2003-02-01 | Morgan et al. | Applicant |
| US6581025(B2) | 2003-06-01 | Lehman | Applicant |
| US6581059(B1) | 2003-06-01 | Barrett et al. | Applicant |
| US6601173(B1) | 2003-07-01 | Mohler | Applicant |
| US6615193(B1) | 2003-09-01 | Kingdon et al. | Applicant |
| US6622266(B1) | 2003-09-01 | Goddard et al. | Applicant |
| US6665715(B1) | 2003-12-01 | Houri | Applicant |
| US6703930(B2) | 2004-03-01 | Skinner | Applicant |
| US6750985(B2) | 2004-06-01 | Rhoads | Applicant |
| US6754665(B1) | 2004-06-01 | Futagami et al. | Applicant |
| US6766946(B2) | 2004-07-01 | Iida et al. | Applicant |
| US6792088(B2) | 2004-09-01 | Takeuchi | Applicant |
| US6792263(B1) | 2004-09-01 | Kite | Applicant |
| US6804346(B1) | 2004-10-01 | Mewhinney | Applicant |
| US6845448(B1) | 2005-01-01 | Chaganti et al. | Applicant |
| US6857073(B2) | 2005-02-01 | French et al. | Applicant |
| US6871287(B1) | 2005-03-01 | Ellingson | Applicant |
| US6907408(B2) | 2005-06-01 | Angel | Applicant |
| US6908030(B2) | 2005-06-01 | Rajasekaran et al. | Applicant |
| US6910624(B1) | 2005-06-01 | Natsuno | Applicant |
| US6934714(B2) | 2005-08-01 | Meinig | Applicant |
| US6934858(B2) | 2005-08-01 | Woodhill | Applicant |
| US6950858(B2) | 2005-09-01 | Ogami | Applicant |
| US6968319(B1) | 2005-11-01 | Remington et al. | Applicant |
| US6983381(B2) | 2006-01-01 | Jerdonek | Applicant |
| US6985887(B1) | 2006-01-01 | Sunstein et al. | Applicant |
| US7028013(B2) | 2006-04-01 | Saeki | Applicant |
| US7028052(B2) | 2006-04-01 | Chapman et al. | Applicant |
| US7046139(B2) | 2006-05-01 | Kuhn et al. | Applicant |
| US7058386(B2) | 2006-06-01 | McGregor et al. | Applicant |
| US7059531(B2) | 2006-06-01 | Beenau et al. | Applicant |
| US7072909(B2) | 2006-07-01 | Polk | Applicant |
| US7089594(B2) | 2006-08-01 | Lal et al. | Applicant |
| US7121471(B2) | 2006-10-01 | Beenau et al. | Applicant |
| US7133935(B2) | 2006-11-01 | Hedy | Applicant |
| US7154375(B2) | 2006-12-01 | Beenau et al. | Applicant |
| US7194416(B1) | 2007-03-01 | Provost et al. | Applicant |
| US7209895(B2) | 2007-04-01 | Kundtz et al. | Applicant |
| US7218912(B2) | 2007-05-01 | Erskine et al. | Applicant |
| US7234156(B2) | 2007-06-01 | French et al. | Applicant |
| US7234160(B2) | 2007-06-01 | Vogel et al. | Applicant |
| US7237267(B2) | 2007-06-01 | Rayes et al. | Applicant |
| US7246067(B2) | 2007-07-01 | Austin et al. | Applicant |
| US7246740(B2) | 2007-07-01 | Swift et al. | Applicant |
| US7281652(B2) | 2007-10-01 | Foss | Applicant |
| US7302272(B2) | 2007-11-01 | Ackley | Applicant |
| US7303120(B2) | 2007-12-01 | Beenau et al. | Applicant |
| US7310611(B2) | 2007-12-01 | Shibuya et al. | Applicant |
| US7314167(B1) | 2008-01-01 | Kiliccote | Applicant |
| US7330717(B2) | 2008-02-01 | Gidron et al. | Applicant |
| US7330835(B2) | 2008-02-01 | Deggendorf | Applicant |
| US7333976(B1) | 2008-02-01 | Auerbach et al. | Applicant |
| US7343149(B2) | 2008-03-01 | Benco | Applicant |
| US7356516(B2) | 2008-04-01 | Richey et al. | Applicant |
| US7370044(B2) | 2008-05-01 | Mulhern et al. | Applicant |
| US7373324(B1) | 2008-05-01 | Engin et al. | Applicant |
| US7383988(B2) | 2008-06-01 | Slonecker, Jr. | Applicant |
| US7386511(B2) | 2008-06-01 | Buchanan et al. | Applicant |
| US7389913(B2) | 2008-06-01 | Starrs | Applicant |
| US7403942(B1) | 2008-07-01 | Bayliss | Applicant |
| US7412228(B2) | 2008-08-01 | Barclay et al. | Applicant |
| US7433864(B2) | 2008-10-01 | Malik | Applicant |
| US7444414(B2) | 2008-10-01 | Foster et al. | Applicant |
| US7451095(B1) | 2008-11-01 | Bradley et al. | Applicant |
| US7451113(B1) | 2008-11-01 | Kasower | Applicant |
| US7458508(B1) | 2008-12-01 | Shao et al. | Applicant |
| US7460857(B2) | 2008-12-01 | Roach, Jr. | Applicant |
| US7478157(B2) | 2009-01-01 | Bohrer et al. | Applicant |
| US7490356(B2) | 2009-02-01 | Lieblich et al. | Applicant |
| US7503489(B2) | 2009-03-01 | Heffez | Applicant |
| US7509117(B2) | 2009-03-01 | Yum | Applicant |
| US7512221(B2) | 2009-03-01 | Toms | Applicant |
| US7529698(B2) | 2009-05-01 | Joao | Applicant |
| US7533179(B2) | 2009-05-01 | Tarquini et al. | Applicant |
| US7542993(B2) | 2009-06-01 | Satterfield et al. | Applicant |
| US7548886(B2) | 2009-06-01 | Kirkland et al. | Applicant |
| US7552089(B2) | 2009-06-01 | Bruer et al. | Applicant |
| US7575157(B2) | 2009-08-01 | Barnhardt et al. | Applicant |
| US7581112(B2) | 2009-08-01 | Brown et al. | Applicant |
| US7584146(B1) | 2009-09-01 | Duhon | Applicant |
| US7587366(B2) | 2009-09-01 | Grim, III et al. | Applicant |
| US7603701(B2) | 2009-10-01 | Gaucas | Applicant |
| US7606725(B2) | 2009-10-01 | Robertson et al. | Applicant |
| US7610216(B1) | 2009-10-01 | May et al. | Applicant |
| US7620596(B2) | 2009-11-01 | Knudson et al. | Applicant |
| US7623844(B2) | 2009-11-01 | Herrmann et al. | Applicant |
| US7644042(B2) | 2010-01-01 | Ramavarjula et al. | Examiner |
| US7647274(B2) | 2010-01-01 | Peterson et al. | Applicant |
| US7647344(B2) | 2010-01-01 | Skurtovich, Jr. et al. | Applicant |
| US7653592(B1) | 2010-01-01 | Flaxman et al. | Applicant |
| US7653600(B2) | 2010-01-01 | Gustin | Applicant |
| US7668725(B2) | 2010-02-01 | Alston | Applicant |
| US7672833(B2) | 2010-03-01 | Blume et al. | Applicant |
| US7688813(B2) | 2010-03-01 | Shin et al. | Applicant |
| US7689487(B1) | 2010-03-01 | Britto et al. | Applicant |
| US7689505(B2) | 2010-03-01 | Kasower | Applicant |
| US7690032(B1) | 2010-03-01 | Peirce | Applicant |
| US7698445(B2) | 2010-04-01 | Fitzpatrick et al. | Applicant |
| US7708190(B2) | 2010-05-01 | Brandt et al. | Applicant |
| US7715832(B2) | 2010-05-01 | Zhou | Applicant |
| US7739139(B2) | 2010-06-01 | Robertson et al. | Applicant |
| US7747494(B1) | 2010-06-01 | Kothari et al. | Applicant |
| US7761384(B2) | 2010-07-01 | Madhogarhia | Applicant |
| US7761568(B1) | 2010-07-01 | Levi et al. | Applicant |
| US7765148(B2) | 2010-07-01 | German et al. | Applicant |
| US7765311(B2) | 2010-07-01 | Itabashi et al. | Applicant |
| US7769696(B2) | 2010-08-01 | Yoda | Applicant |
| US7769697(B2) | 2010-08-01 | Fieschi et al. | Applicant |
| US7774270(B1) | 2010-08-01 | MacCloskey | Applicant |
| US7787869(B2) | 2010-08-01 | Rice et al. | Applicant |
| US7792715(B1) | 2010-09-01 | Kasower | Applicant |
| US7793835(B1) | 2010-09-01 | Coggeshall et al. | Applicant |
| US7797725(B2) | 2010-09-01 | Lunt et al. | Applicant |
| US7801811(B1) | 2010-09-01 | Merrell et al. | Applicant |
| US7802104(B2) | 2010-09-01 | Dickinson | Applicant |
| US7805362(B1) | 2010-09-01 | Merrell et al. | Applicant |
| US7809398(B2) | 2010-10-01 | Pearson | Applicant |
| US7827115(B2) | 2010-11-01 | Weller et al. | Applicant |
| US7841004(B1) | 2010-11-01 | Balducci et al. | Applicant |
| US7841008(B1) | 2010-11-01 | Cole et al. | Applicant |
| US7849014(B2) | 2010-12-01 | Erikson | Applicant |
| US7853493(B2) | 2010-12-01 | DeBie et al. | Applicant |
| US7856203(B2) | 2010-12-01 | Lipovski | Applicant |
| US7865958(B2) | 2011-01-01 | Lieblich et al. | Applicant |
| US7912865(B2) | 2011-03-01 | Akerman et al. | Applicant |
| US7970679(B2) | 2011-06-01 | Kasower | Applicant |
| US7991689(B1) | 2011-08-01 | Brunzell et al. | Applicant |
| US7991901(B2) | 2011-08-01 | Tarquini et al. | Applicant |
| US7996912(B2) | 2011-08-01 | Spalink et al. | Applicant |
| US8001042(B1) | 2011-08-01 | Brunzell et al. | Applicant |
| US8032932(B2) | 2011-10-01 | Speyer et al. | Examiner |
| US8037097(B2) | 2011-10-01 | Guo et al. | Applicant |
| US8060424(B2) | 2011-11-01 | Kasower | Applicant |
| US8078453(B2) | 2011-12-01 | Shaw | Applicant |
| US8095443(B2) | 2012-01-01 | DeBie | Applicant |
| US8095458(B2) | 2012-01-01 | Peterson et al. | Applicant |
| US8127986(B1) | 2012-03-01 | Taylor et al. | Applicant |
| US8195549(B2) | 2012-06-01 | Kasower | Applicant |
| US8224723(B2) | 2012-07-01 | Bosch et al. | Applicant |
| US8234498(B2) | 2012-07-01 | Britti et al. | Applicant |
| US8271393(B2) | 2012-09-01 | Twining et al. | Applicant |
| US8285656(B1) | 2012-10-01 | Chang et al. | Applicant |
| US8290840(B2) | 2012-10-01 | Kasower | Applicant |
| US8312033(B1) | 2012-11-01 | McMillan | Applicant |
| US8321952(B2) | 2012-11-01 | Spalink et al. | Applicant |
| US8327429(B2) | 2012-12-01 | Speyer et al. | Examiner |
| US8355967(B2) | 2013-01-01 | Debie et al. | Applicant |
| US8453226(B2) | 2013-05-01 | Hammad | Examiner |
| US8463919(B2) | 2013-06-01 | Tarquini et al. | Applicant |
| US8515844(B2) | 2013-08-01 | Kasower | Applicant |
| US8533118(B2) | 2013-09-01 | Weller et al. | Examiner |
| US8600886(B2) | 2013-12-01 | Ramavarjula et al. | Examiner |
| US2001/0001877(A1) | 2001-05-01 | French et al. | Applicant |
| US2001/0029482(A1) | 2001-10-01 | Tealdi et al. | Applicant |
| US2001/0039532(A1) | 2001-11-01 | Coleman, Jr. et al. | Applicant |
| US2002/0004736(A1) | 2002-01-01 | Roundtree et al. | Applicant |
| US2002/0026519(A1) | 2002-02-01 | Itabashi et al. | Applicant |
| US2002/0035684(A1) | 2002-03-01 | Vogel et al. | Applicant |
| US2002/0049624(A1) | 2002-04-01 | Raveis, Jr. | Applicant |
| US2002/0052841(A1) | 2002-05-01 | Guthrie et al. | Applicant |
| US2002/0069122(A1) | 2002-06-01 | Yun et al. | Applicant |
| US2002/0077964(A1) | 2002-06-01 | Brody et al. | Applicant |
| US2002/0082892(A1) | 2002-06-01 | Raffel et al. | Applicant |
| US2002/0099635(A1) | 2002-07-01 | Guiragosian | Applicant |
| US2002/0099824(A1) | 2002-07-01 | Bender et al. | Applicant |
| US2002/0128962(A1) | 2002-09-01 | Kasower | Applicant |
| US2002/0156676(A1) | 2002-10-01 | Ahrens et al. | Applicant |
| US2002/0157029(A1) | 2002-10-01 | French et al. | Applicant |
| US2002/0161664(A1) | 2002-10-01 | Shaya et al. | Applicant |
| US2002/0169747(A1) | 2002-11-01 | Chapman et al. | Applicant |
| US2002/0194120(A1) | 2002-12-01 | Russell et al. | Applicant |
| US2003/0009418(A1) | 2003-01-01 | Green et al. | Applicant |
| US2003/0009426(A1) | 2003-01-01 | Ruiz-Sanchez | Applicant |
| US2003/0018578(A1) | 2003-01-01 | Schultz | Applicant |
| US2003/0061163(A1) | 2003-03-01 | Durfield | Applicant |
| US2003/0078897(A1) | 2003-04-01 | Florance et al. | Applicant |
| US2003/0097342(A1) | 2003-05-01 | Whittingtom | Applicant |
| US2003/0097380(A1) | 2003-05-01 | Mulhern et al. | Applicant |
| US2003/0115133(A1) | 2003-06-01 | Bian | Applicant |
| US2003/0171942(A1) | 2003-09-01 | Gaito | Applicant |
| US2003/0177028(A1) | 2003-09-01 | Cooper et al. | Applicant |
| US2003/0182214(A1) | 2003-09-01 | Taylor | Applicant |
| US2003/0195859(A1) | 2003-10-01 | Lawrence | Applicant |
| US2003/0220858(A1) | 2003-11-01 | Lam et al. | Applicant |
| US2004/0006488(A1) | 2004-01-01 | Fitall et al. | Applicant |
| US2004/0010458(A1) | 2004-01-01 | Friedman | Applicant |
| US2004/0015714(A1) | 2004-01-01 | Abraham et al. | Applicant |
| US2004/0015715(A1) | 2004-01-01 | Brown | Applicant |
| US2004/0019518(A1) | 2004-01-01 | Abraham et al. | Applicant |
| US2004/0030649(A1) | 2004-02-01 | Nelson et al. | Applicant |
| US2004/0044563(A1) | 2004-03-01 | Stein | Applicant |
| US2004/0044628(A1) | 2004-03-01 | Mathew et al. | Applicant |
| US2004/0044739(A1) | 2004-03-01 | Ziegler | Applicant |
| US2004/0062213(A1) | 2004-04-01 | Koss | Applicant |
| US2004/0078323(A1) | 2004-04-01 | Johnston et al. | Applicant |
| US2004/0078324(A1) | 2004-04-01 | Lonnberg et al. | Applicant |
| US2004/0102197(A1) | 2004-05-01 | Dietz | Applicant |
| US2004/0123162(A1) | 2004-06-01 | Antell et al. | Applicant |
| US2004/0128150(A1) | 2004-07-01 | Lundegren | Applicant |
| US2004/0133493(A1) | 2004-07-01 | Ford et al. | Applicant |
| US2004/0153521(A1) | 2004-08-01 | Kogo | Applicant |
| US2004/0158523(A1) | 2004-08-01 | Dort | Applicant |
| US2004/0167793(A1) | 2004-08-01 | Masuoka et al. | Applicant |
| US2004/0177035(A1) | 2004-09-01 | Silva | Applicant |
| US2004/0193891(A1) | 2004-09-01 | Ollila | Applicant |
| US2004/0230527(A1) | 2004-11-01 | Hansen et al. | Applicant |
| US2004/0230534(A1) | 2004-11-01 | McGough | Applicant |
| US2004/0236688(A1) | 2004-11-01 | Bozeman | Applicant |
| US2004/0243450(A1) | 2004-12-01 | Bernard, Jr. et al. | Applicant |
| US2004/0243518(A1) | 2004-12-01 | Clifton et al. | Applicant |
| US2004/0243832(A1) | 2004-12-01 | Wilf et al. | Applicant |
| US2005/0005168(A1) | 2005-01-01 | Dick | Applicant |
| US2005/0027983(A1) | 2005-02-01 | Klawon | Applicant |
| US2005/0027995(A1) | 2005-02-01 | Menschik et al. | Applicant |
| US2005/0050027(A1) | 2005-03-01 | Yeh et al. | Applicant |
| US2005/0055231(A1) | 2005-03-01 | Lee | Applicant |
| US2005/0058262(A1) | 2005-03-01 | Timmins et al. | Applicant |
| US2005/0097320(A1) | 2005-05-01 | Golan et al. | Examiner |
| US2005/0137899(A1) | 2005-06-01 | Davies et al. | Applicant |
| US2005/0154664(A1) | 2005-07-01 | Guy et al. | Applicant |
| US2005/0154665(A1) | 2005-07-01 | Kerr | Applicant |
| US2005/0166262(A1) | 2005-07-01 | Beattie et al. | Applicant |
| US2005/0251474(A1) | 2005-11-01 | Shinn et al. | Applicant |
| US2005/0256809(A1) | 2005-11-01 | Sadri | Applicant |
| US2005/0273442(A1) | 2005-12-01 | Bennett et al. | Applicant |
| US2005/0279827(A1) | 2005-12-01 | Mascavage et al. | Applicant |
| US2005/0288998(A1) | 2005-12-01 | Verma et al. | Applicant |
| US2006/0010487(A1) | 2006-01-01 | Fierer et al. | Applicant |
| US2006/0036870(A1) | 2006-02-01 | Dasari et al. | Applicant |
| US2006/0041464(A1) | 2006-02-01 | Powers et al. | Applicant |
| US2006/0059110(A1) | 2006-03-01 | Madhok et al. | Applicant |
| US2006/0074986(A1) | 2006-04-01 | Mallalieu et al. | Applicant |
| US2006/0080263(A1) | 2006-04-01 | Willis et al. | Applicant |
| US2006/0106670(A1) | 2006-05-01 | Cai et al. | Applicant |
| US2006/0129481(A1) | 2006-06-01 | Bhatt et al. | Applicant |
| US2006/0131390(A1) | 2006-06-01 | Kim | Applicant |
| US2006/0155573(A1) | 2006-07-01 | Hartunian | Applicant |
| US2006/0161435(A1) | 2006-07-01 | Atef et al. | Applicant |
| US2006/0173776(A1) | 2006-08-01 | Shalley et al. | Applicant |
| US2006/0178971(A1) | 2006-08-01 | Owen et al. | Applicant |
| US2006/0204051(A1) | 2006-09-01 | Holland, IV | Applicant |
| US2006/0218407(A1) | 2006-09-01 | Toms | Applicant |
| US2006/0223043(A1) | 2006-10-01 | Dancy-Edwards et al. | Applicant |
| US2006/0229943(A1) | 2006-10-01 | Mathias et al. | Applicant |
| US2006/0229961(A1) | 2006-10-01 | Lyftogt et al. | Applicant |
| US2006/0239512(A1) | 2006-10-01 | Petrillo | Applicant |
| US2006/0253323(A1) | 2006-11-01 | Phan et al. | Applicant |
| US2006/0253358(A1) | 2006-11-01 | Delgrosso et al. | Applicant |
| US2006/0262929(A1) | 2006-11-01 | Vatanen et al. | Applicant |
| US2006/0265243(A1) | 2006-11-01 | Racho et al. | Applicant |
| US2006/0271456(A1) | 2006-11-01 | Romain et al. | Applicant |
| US2006/0271457(A1) | 2006-11-01 | Romain et al. | Applicant |
| US2007/0005508(A1) | 2007-01-01 | Chiang | Applicant |
| US2007/0027816(A1) | 2007-02-01 | Writer | Applicant |
| US2007/0038568(A1) | 2007-02-01 | Greene et al. | Examiner |
| US2007/0067297(A1) | 2007-03-01 | Kublickis | Applicant |
| US2007/0067437(A1) | 2007-03-01 | Sindambiwe | Applicant |
| US2007/0073889(A1) | 2007-03-01 | Morris | Applicant |
| US2007/0078985(A1) | 2007-04-01 | Shao et al. | Applicant |
| US2007/0083460(A1) | 2007-04-01 | Bachenheimer | Applicant |
| US2007/0112667(A1) | 2007-05-01 | Rucker | Applicant |
| US2007/0112668(A1) | 2007-05-01 | Celano et al. | Applicant |
| US2007/0124256(A1) | 2007-05-01 | Crooks et al. | Applicant |
| US2007/0174122(A1) | 2007-07-01 | Howard et al. | Applicant |
| US2007/0174186(A1) | 2007-07-01 | Hokland | Applicant |
| US2007/0174448(A1) | 2007-07-01 | Ahuja et al. | Applicant |
| US2007/0226047(A1) | 2007-09-01 | Ward | Applicant |
| US2007/0244807(A1) | 2007-10-01 | Andringa et al. | Applicant |
| US2007/0250459(A1) | 2007-10-01 | Schwarz et al. | Applicant |
| US2007/0261114(A1) | 2007-11-01 | Pomerantsev | Applicant |
| US2007/0262140(A1) | 2007-11-01 | Long, Sr. | Applicant |
| US2007/0288355(A1) | 2007-12-01 | Roland et al. | Applicant |
| US2007/0288360(A1) | 2007-12-01 | Seeklus | Applicant |
| US2008/0010206(A1) | 2008-01-01 | Coleman | Applicant |
| US2008/0010687(A1) | 2008-01-01 | Gonen et al. | Applicant |
| US2008/0028067(A1) | 2008-01-01 | Berkhin et al. | Applicant |
| US2008/0033742(A1) | 2008-02-01 | Bernasconi | Applicant |
| US2008/0052182(A1) | 2008-02-01 | Marshall | Applicant |
| US2008/0052244(A1) | 2008-02-01 | Tsuei et al. | Applicant |
| US2008/0059352(A1) | 2008-03-01 | Chandran | Applicant |
| US2008/0065774(A1) | 2008-03-01 | Keeler | Applicant |
| US2008/0066188(A1) | 2008-03-01 | Kwak | Applicant |
| US2008/0071682(A1) | 2008-03-01 | Dominguez | Applicant |
| US2008/0077526(A1) | 2008-03-01 | Arumugam | Applicant |
| US2008/0086759(A1) | 2008-04-01 | Colson | Applicant |
| US2008/0091519(A1) | 2008-04-01 | Foss | Applicant |
| US2008/0103800(A1) | 2008-05-01 | Domenikos et al. | Applicant |
| US2008/0103972(A1) | 2008-05-01 | Lanc | Applicant |
| US2008/0109875(A1) | 2008-05-01 | Kraft | Applicant |
| US2008/0114670(A1) | 2008-05-01 | Friesen | Applicant |
| US2008/0115191(A1) | 2008-05-01 | Kim et al. | Applicant |
| US2008/0120569(A1) | 2008-05-01 | Mann et al. | Applicant |
| US2008/0126233(A1) | 2008-05-01 | Hogan | Applicant |
| US2008/0162317(A1) | 2008-07-01 | Banaugh et al. | Applicant |
| US2008/0162383(A1) | 2008-07-01 | Kraft | Applicant |
| US2008/0175360(A1) | 2008-07-01 | Schwarz et al. | Applicant |
| US2008/0183480(A1) | 2008-07-01 | Carlson et al. | Applicant |
| US2008/0205655(A1) | 2008-08-01 | Wilkins et al. | Applicant |
| US2008/0208873(A1) | 2008-08-01 | Boehmer | Applicant |
| US2008/0221972(A1) | 2008-09-01 | Megdal et al. | Applicant |
| US2008/0222027(A1) | 2008-09-01 | Megdal et al. | Applicant |
| US2008/0222706(A1) | 2008-09-01 | Renaud et al. | Examiner |
| US2008/0255992(A1) | 2008-10-01 | Lin | Applicant |
| US2008/0263058(A1) | 2008-10-01 | Peden | Applicant |
| US2008/0270209(A1) | 2008-10-01 | Mauseth et al. | Applicant |
| US2008/0277465(A1) | 2008-11-01 | Pletz et al. | Applicant |
| US2008/0281737(A1) | 2008-11-01 | Fajardo | Applicant |
| US2008/0288299(A1) | 2008-11-01 | Schultz | Applicant |
| US2008/0294501(A1) | 2008-11-01 | Rennich et al. | Applicant |
| US2008/0301016(A1) | 2008-12-01 | Durvasula et al. | Applicant |
| US2008/0306750(A1) | 2008-12-01 | Wunder et al. | Applicant |
| US2008/0319889(A1) | 2008-12-01 | Hammad | Applicant |
| US2009/0006230(A1) | 2009-01-01 | Lyda et al. | Applicant |
| US2009/0024484(A1) | 2009-01-01 | Walker et al. | Applicant |
| US2009/0031426(A1) | 2009-01-01 | Dal Lago et al. | Applicant |
| US2009/0037332(A1) | 2009-02-01 | Cheung et al. | Applicant |
| US2009/0043691(A1) | 2009-02-01 | Kasower | Applicant |
| US2009/0055894(A1) | 2009-02-01 | Lorsch | Applicant |
| US2009/0060343(A1) | 2009-03-01 | Rosca | Applicant |
| US2009/0094674(A1) | 2009-04-01 | Schwartz et al. | Applicant |
| US2009/0106141(A1) | 2009-04-01 | Becker | Applicant |
| US2009/0106150(A1) | 2009-04-01 | Pelegero et al. | Applicant |
| US2009/0106846(A1) | 2009-04-01 | Dupray et al. | Applicant |
| US2009/0126013(A1) | 2009-05-01 | Atwood et al. | Applicant |
| US2009/0138335(A1) | 2009-05-01 | Lieberman | Applicant |
| US2009/0144166(A1) | 2009-06-01 | Dickelman | Applicant |
| US2009/0150166(A1) | 2009-06-01 | Leite et al. | Applicant |
| US2009/0150238(A1) | 2009-06-01 | Marsh et al. | Applicant |
| US2009/0177529(A1) | 2009-07-01 | Hadi | Applicant |
| US2009/0177562(A1) | 2009-07-01 | Peace et al. | Applicant |
| US2009/0199264(A1) | 2009-08-01 | Lang | Applicant |
| US2009/0210241(A1) | 2009-08-01 | Calloway | Applicant |
| US2009/0234775(A1) | 2009-09-01 | Whitney et al. | Applicant |
| US2009/0240624(A1) | 2009-09-01 | James et al. | Examiner |
| US2009/0248573(A1) | 2009-10-01 | Haggerty et al. | Applicant |
| US2009/0254476(A1) | 2009-10-01 | Sharma et al. | Applicant |
| US2009/0260064(A1) | 2009-10-01 | Mcdowell et al. | Applicant |
| US2009/0307778(A1) | 2009-12-01 | Mardikar | Applicant |
| US2009/0328173(A1) | 2009-12-01 | Jakobson et al. | Applicant |
| US2010/0011428(A1) | 2010-01-01 | Atwood et al. | Applicant |
| US2010/0023448(A1) | 2010-01-01 | Eze | Applicant |
| US2010/0030677(A1) | 2010-02-01 | Melik-Aslanian et al. | Applicant |
| US2010/0043055(A1) | 2010-02-01 | Baumgart | Applicant |
| US2010/0100945(A1) | 2010-04-01 | Ozzie et al. | Applicant |
| US2010/0114724(A1) | 2010-05-01 | Ghosh et al. | Applicant |
| US2010/0114744(A1) | 2010-05-01 | Gonen | Applicant |
| US2010/0114747(A1) | 2010-05-01 | Kasower | Applicant |
| US2010/0114776(A1) | 2010-05-01 | Weller et al. | Applicant |
| US2010/0145840(A1) | 2010-06-01 | Kasower | Applicant |
| US2010/0153278(A1) | 2010-06-01 | Farsedakis | Applicant |
| US2010/0179906(A1) | 2010-07-01 | Hawkes | Applicant |
| US2010/0205662(A1) | 2010-08-01 | Ibrahim et al. | Applicant |
| US2010/0229245(A1) | 2010-09-01 | Singhal | Applicant |
| US2010/0241535(A1) | 2010-09-01 | Nightengale et al. | Applicant |
| US2010/0250411(A1) | 2010-09-01 | Ogrodski | Applicant |
| US2010/0250497(A1) | 2010-09-01 | Redlich et al. | Applicant |
| US2010/0257102(A1) | 2010-10-01 | Perlman | Examiner |
| US2010/0280914(A1) | 2010-11-01 | Carlson | Applicant |
| US2010/0299262(A1) | 2010-11-01 | Handler | Applicant |
| US2010/0325048(A1) | 2010-12-01 | Carlson et al. | Applicant |
| US2010/0325694(A1) | 2010-12-01 | Bhagavatula et al. | Applicant |
| US2010/0332393(A1) | 2010-12-01 | Weller et al. | Applicant |
| US2011/0016533(A1) | 2011-01-01 | Zeigler et al. | Applicant |
| US2011/0029388(A1) | 2011-02-01 | Kendall et al. | Applicant |
| US2011/0035788(A1) | 2011-02-01 | White et al. | Applicant |
| US2011/0040629(A1) | 2011-02-01 | Chiu et al. | Applicant |
| US2011/0071950(A1) | 2011-03-01 | Ivanovic | Applicant |
| US2011/0137760(A1) | 2011-06-01 | Rudie et al. | Applicant |
| US2011/0166988(A1) | 2011-07-01 | Coulter | Applicant |
| US2011/0270618(A1) | 2011-11-01 | Banerjee et al. | Applicant |
| US2012/0016948(A1) | 2012-01-01 | Sinha | Applicant |
| US2012/0022990(A1) | 2012-01-01 | Kasower | Applicant |
| US2012/0047219(A1) | 2012-02-01 | Feng et al. | Applicant |
| US2012/0110677(A1) | 2012-05-01 | Abendroth et al. | Applicant |
| US2012/0124498(A1) | 2012-05-01 | Santoro et al. | Applicant |
| US2012/0136763(A1) | 2012-05-01 | Megdal et al. | Applicant |
| US2012/0158574(A1) | 2012-06-01 | Brunzell et al. | Applicant |
| US2012/0173339(A1) | 2012-07-01 | Flynt et al. | Applicant |
| US2012/0216125(A1) | 2012-08-01 | Pierce | Applicant |
| US2012/0265607(A1) | 2012-10-01 | Belwadi | Applicant |
| US2012/0323954(A1) | 2012-12-01 | Bonalle et al. | Applicant |
| US2013/0018811(A1) | 2013-01-01 | Britti et al. | Applicant |
| US2013/0031624(A1) | 2013-01-01 | Britti et al. | Applicant |
| US2013/0110557(A1) | 2013-05-01 | Kasower | Applicant |
| US2013/0124392(A1) | 2013-05-01 | Achanta et al. | Applicant |
| US2013/0205135(A1) | 2013-08-01 | Lutz | Examiner |
| US2013/0339249(A1) | 2013-12-01 | Weller et al. | Examiner |
| US2014/0061302(A1) | 2014-03-01 | Hammad | Examiner |
| US2014/0110477(A1) | 2014-04-01 | Hammad | Examiner |
| EP542298 | 1993-05-01 | Applicant | |
| EP1028401 | 2000-08-01 | Applicant | |
| EP1077419 | 2001-02-01 | Applicant | |
| EP2088743 | 2009-08-01 | Applicant | |
| GB2102606 | 1983-02-01 | Applicant | |
| KR10-2004-0078798 | 2004-09-01 | Applicant | |
| WO91/16691 | 1991-10-01 | Applicant | |
| WO99/60481 | 1999-11-01 | Applicant | |
| WO/30045 | 2000-05-01 | Applicant | |
| WO1/84281 | 2001-11-01 | Applicant | |
| WO2010/062537 | 2010-06-01 | Applicant | |
| WO2010/150251 | 2010-12-01 | Applicant | |
| WO2011/005876 | 2011-01-01 | Applicant | |
| WO2013/009920 | 2013-01-01 | Applicant |
Non-Patent Literature (33)
- U.S. Appl. No. 12/705,489, filed Feb. 12, 2010, Bargoli et al.Applicant
- U.S. Appl. No. 12/705,511, filed Feb. 12, 2010, Bargoli et al.Applicant
- “Aggregate and Analyze Social Media Content: Gain Faster and Broader Insight to Market Sentiment”, SAP Partner, Mantis Technology Group, Apr. 2011, pp. 4.Applicant
- BackupBox, http://mybackupbox.com printed Feb. 8, 2013 in 2 pages.Applicant
- BlueCava, “What We Do”, http://www.bluecava.com/what-we-do/, printed Nov. 5, 2012 in 3 pages.Applicant
- Chores & Allowances. “Do Kids Have Credit Reports?”, Oct. 15, 2007, http://choresandallowances.blogspot.com/2007/10/do-kids-have-credit-reports.html, pp. 5.Applicant
- “Consumers Gain Immediate and Full Access to Credit Score Used by Majority of U.S. Lenders.” PR Newswire, ProQuest Copy; Mar. 19, 2001; p. 1.Applicant
- Ettorre, Paul Kahn on Exceptional Marketing, Management Review, vol. 38(11), Nov. 1994, pp. 48-51.Applicant
- Expensr.com http://www.expensr.com/, as retrieved on Sep. 17, 2008.Applicant
- Gibbs, Adrienne; “Protecting Your Children from Identity Theft,” Nov. 25, 2008, http://www.creditcards.com/credit-card-news/identity-ID-theft-and-kids-children-1282.php, pp. 4.Applicant
- Hojoki, http://hojoki.com printed Feb. 8, 2013 in 5 pages.Applicant
- Hoofnagle, Chris Jay, “Identity Theft: Making the Known Unknowns Known,” Harvard Journal of Law & Technology, Fall 2007, vol. 21, No. 1, pp. 98-122.Applicant
- ID Theft Assist, “Do You Know Where Your Child's Credit Is?” Nov. 26, 2007, http://www.idtheftassist.com/pages/story14, pp. 3.Applicant
- Ideon, Credit-Card Registry that Bellyflopped this Year, Is Drawing some Bottom-Fishers, The Wall Street Journal, Aug. 21, 1995, pp. C2.Applicant
- IFTTT, “About IFTTT”, http://ifttt.com/wtf printed Feb. 18, 2013 in 4 pages.Applicant
- Iovation, Device Identification & Device Fingerprinting, http://www.iovation.com/risk-management/device-identification printed Nov. 5, 2012 in 6 pages.Applicant
- Leskovec, Jure, “Social Media Analytics: Tracking, Modeling and Predicting the Flow of Information through Networks”, WWW 2011-Tutorial, Mar. 28-Apr. 1, 2011, Hyderabad, India, pp. 277-278.Applicant
- Li et al., “Automatic Verbal Information Verification for User Authentication”, IEEE Transactions on Speech and Audio Processing, vol. 8, No. 5, Sep. 2000, pp. 585-596.Applicant
- LifeLock; “How Can LifeLock Protect My Kids and Family?” http://www.lifelock.com/lifelock-for-people/how-we-do-it/how-can-lifelock-protect-my-kids-and-family printed Mar. 14, 2008 in 1 page.Applicant
- LifeLock, Various Pages, www.lifelock.com/, 2007.Applicant
- Magid, Lawrence, J., Business Tools: When Selecting an ASP Ensure Data Mobility, Los Angeles Times, Los Angeles, CA, Feb. 26, 2001, vol. C, Issue 4, pp. 3.Applicant
- Mover, “One API for the Cloud”, http://mover.io printed Feb. 6, 2013 in 3 pages.Applicant
- Ogg, Erica, “Apple Cracks Down on UDID Use”, http://gigaom.com/apple/apple-cracks-down-on-udid-use/ printed Nov. 5, 2012 in 5 Pages.Applicant
- Otixo, “Your Dashboard for the Cloud”, http://Otixo.com/product printed Feb. 6, 2013 in 3 pages.Applicant
- Pipes, http://pipes.yahoo.com/pipes printed Feb. 18, 2013 in 1 page.Applicant
- Primadesk, http://primadesk.com printed Feb. 8, 2013 in 1 page.Applicant
- Ramaswamy, Vinita M., Identity-Theft Toolkit, The CPA Journal, Oct. 1, 2006, vol. 76, Issue 10, pp. 66-70.Applicant
- Storage Made Easy(SME), http://storagemadeeasy.com printed Feb. 6, 2013 in 1 page.Applicant
- Vamosi, Robert, “How to Handle ID Fraud's Youngest Victims,” Nov. 21, 2008, http://news.cnet.com/8301-10789—3-10105303-57.html.Applicant
- Zapier, “Integrate Your Web Services”, http://www.Zapier.com, printed Feb. 18, 2013 in 3 pages.Applicant
- International Search Report and Written Opinion for Application No. PCT/US2012/046316, dated Sep. 28, 2012.Applicant
- International Search Report and Written Opinion for Application No. PCT/US10/34434, dated Jun. 23, 2010.Applicant
- Provisional Application as filed in U.S. Appl. No. 60/168,273, dated Dec. 1, 1999 in 21 pages.Applicant