Some service providers use conventional risk-based authentication systems to assess risks of processing customer transactions. For example, an online bank may employ a risk engine of such a risk-based authentication system to assign risk scores to banking transactions where higher risk scores indicate higher risk.
In generating a risk score, the risk engine takes, as input values, various transaction attributes (e.g., time of receipt, IP address). For each customer of the online bank, there is an associated history based on values of the transaction attributes associated with previous transactions involving that customer. The risk engine incorporates the history associated with the customer into an evaluation of the risk score. Significant variation of one or more attribute values from those in the customer's history may signify that the banking transaction has a high risk.
For example, suppose that a particular customer historically submitted transaction requests to the online bank at 3:00 PM from a particular internet service provider (ISP), and, under the customer's identifier, a user submits a new transaction request at 2:00 AM from a different ISP. The different ISP would give rise to a different IP address than that historically associated with the particular customer. In this case, owing to the different IP address and the unusual time that the transaction was submitted, the risk engine would assign a larger risk score to a transaction resulting from the new transaction request.