Risk-based authentication

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

In Authentication, risk-based authentication is a non-static authentication system which takes into account the profile(IP address, User-Agent HTTP header, time of access, and so on) of the agent requesting access to the system to determine the risk profile associated with that transaction. The risk profile is then used to determine the complexity of the challenge. Higher risk profiles leads to stronger challenges, whereas a static username/password may suffice for lower-risk profiles. Risk-based implementation allows the application to challenge the user for additional credentials only when the risk level is appropriate[1][2][3].

Machine authentication is often used in a risk based authentication set up. The machine authentication will run in the background and only ask the customer for additional authentication if the computer is not recognized. In a risk based authentication system, the institution decides if additional authentication is necessary. If the risk is deemed appropriate, enhanced authentication will be triggered, such as a one time password delivered via an out of band communication. Risk based authentication can also be used during the session to prompt for additional authentication when the customer performs a certain high risk transaction, such as a money transfer or an address change. Risk based authentication is very beneficial to the customer because additional steps are only required if something is out of the ordinary, such as the login attempt is from a new machine.

— [4]

The point is that user validation accuracy is improved without inconveniencing a user[1] and risk-based authentication is used by major companies[5].

Criticism[edit]

  • The system that computes the risk profile has to be diligently maintained and updated as new threats emerge. Improper configuration may lead to unauthorized access.
  • The user's connection profile (e.g. IP Geolocation, connection type, keystroke dynamics, user behaviour) has to be detected and used to compute the risk profile. Lack of proper detection may lead to unauthorized access.

See also[edit]

References[edit]

  1. ^ a b US patent 9021555, Takaya Kato, "Risk-based authentication patent", issued March 29, 2006 
  2. ^ Wiefling, Stephan; Lo Iacono, Luigi; Dürmuth, Markus. "Information website on Risk-based Authentication". Risk-based Authentication. Retrieved 2019-04-29.
  3. ^ Wiefling, Stephan; Lo Iacono, Luigi; Dürmuth, Markus (2019). Dhillon, Gurpreet; Karlsson, Fredrik; Hedström, Karin; Zúquete, André (eds.). "Is This Really You? An Empirical Study on Risk-Based Authentication Applied in the Wild". ICT Systems Security and Privacy Protection. IFIP Advances in Information and Communication Technology. Springer International Publishing: 134–148. doi:10.1007/978-3-030-22312-0_10. ISBN 9783030223120.
  4. ^ Williamson, G. "Enhanced Authentication In Online Banking" Journal of Economic Crime Management 4.2 (2006): 18–19. Print
  5. ^ Wiefling, Stephan; Lo Iacono, Luigi; Dürmuth, Markus. "Who uses RBA? We found evidence that Google, Facebook, LinkedIn, Amazon and GOG.com are using it". Risk-based Authentication. Retrieved 2019-04-29.