Strong Authentication for Online Banking - A Risk To Customers?

Nov 06 2006

By Kurt Seifried (kurt@seifried.org)

Regulations and recommendations concerning secure authentication of users and transactions for online banking applications have been around for several years now. Sadly, within North America most banks have been very slow to use strong authentication methods for customers and transactions.

Sad for the banks that is….

But all this is starting to change.

Historically the majority of online banking applications made use of the simplest of all authentication schemes to implement: the username and password. Ideally both the username and password are secret, known only to the account holder. However in reality the username is often the account number (e.g.: 23525621), and these account numbers are often publicly known or easily guessed. And as we all know the passwords chosen by users are often far from being truly secure (or if they are “I use a secure password, the same one for all my accounts, it’s secure!”).

The result of this has been that it is relatively trivial for an attacker to either capture a user’s credentials by loading malicious software onto their machine, or by tricking the user into revealing the information through phishing attacks. The attacker then typically cleans out a person’s account and scarpers off. This usually results in the victim complaining to the police, the bank, all their friends, etc. Finally we have the bank reimbursing the customer for all monies lost, and doing their best to retrieve what money they can be reversing the outgoing payments.

Banks don’t like angry customers. But banks don’t like reimbursing stolen money either.

So what’s an acceptable solution to all this, for the banks?

Implementing strong authentication such as two factor systems, ideally using external tokens or external communication channels such as the phone or text messages is the beginning of the process. In doing so these banks actually do make online banking more secure against several classes of attacks; however many of these technologies fail to address the most difficult attack vector. This is of course the compromised end user system. We all know that many users will click on anything that arrives via email, and that this will result in a compromise of their machine. The good news is that there are technologies and authentication procedures that can largely mitigate the risk of using a compromised system to do online banking.

So why is this bad news for customers? Well currently if there is any fraud chances are the bank will reimburse the customer, so the customer is protected and often does not suffer any direct cost. Essentially for online banking all the risk of fraud and theft is carried by the bank. This is great for consumers, and personally I’m all in favor of it (being a bank customer). However with the rise of secure authentication methods, and in some cases of banks offering their customers free anti-virus and firewall applications we will being to see the risk of online fraud and theft shifting from the banks onto the customer. The argument will simply be:

“We provided a secure banking environment, but the customer managed to still fall prey to online criminals, we can’t really do much more, sorry!”

This is not so good for customers, but with the rising cost of online theft it is an inevitable step for banks to take.

Authentication in an Internet Banking Environment
http://www.ffiec.gov/pdf/authentication_guidance.pdf

FFIEC Guidance Authentication in an Internet Banking Environment
http://www.fdic.gov/news/news/financial/2005/fil10305.html

Secure Internet Banking Authentication
http://www.zurich.ibm.com/pdf/csc/SecureInternetBankingAuthentication.pdf

VeriSign Identity Protection
http://www.verisign.com/products-services/security-services/identity-protection/index.html

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Slashdot
  • Digg
  • del.icio.us
  • Reddit
  • digg
  • Technorati
  • StumbleUpon

Related posts:

  1. Privacy Laws - A Threat To U.S. Financial Services Corporations?
  2. Security officially defined
  3. Outsourcing - Intellectual Property Overview
  4. 9 year prison sentence for credit card theft
  5. Vishing Incidents: A Preview of the Road Ahead

Posted by Kurt.Seifried on Monday, November 6th, 2006, at 8:00 am, and filed under Articles, Technical.

Follow any responses to this entry with the RSS 2.0 feed.

You can post a comment, or trackback from your site.