Authentication engine 120 may be associated with organization 140, and the users may be members or potential members of the organization. The organization may be a financial institution and/or an insurance company. A user may access organization 140 to perform activities such as activity A 145, activity B 150, activity C 155. Activities such as activity A, activity B, and activity C may include viewing an account, transferring funds, filing an insurance claim, for example.

Authentication may be based on information received through various user interfaces running on computing devices 110A-110M, service provider 125, or other interactions, communications, and/or other inputs (e.g., emails, tokens, and/or communications via other channels). Authentication engine 120 can be calibrated/configured by individual companies or service providers based on risk tolerance and/or other business objectives to authenticate users.

In some cases, authentication to the application, process, website, or activity may be based on different criteria. For example, in addition to rendering an authentication decision, authentication engine 120 may be configured to compute a risk profile or score. That profile may be used by itself to make a decision, or it may be used in conjunction with other profiles, scores, and/or business practices. Authentication engine 120 may also be configured to recommend an access level the user should be granted based on a confidence in the user's identity or a verification of the user's identity. In some embodiments, authentication engine 120 includes various data processing and analytic tools that allow for implementation, creation, and evaluation of users and user information retrieved from data stores 130 and 135.