10:56 AM
Connect Directly

Tech Insight: Two-Factor Authentication Alone Isn't Enough

Protecting online banking customers entails a more holistic approach by banks that includes risk-based authentication, browser protection, and fraud monitoring

About the author: Greg Thompson is vice president of enterprise security services at Scotiabank. This article appears as a special to Dark Reading courtesy of the (ISC)2 Advisory Board of the Americas Executive Writer's Bureau.

Knowing the customer is a fundamental tenet of the banking industry. When we visit our local branch to perform our daily banking or receive other services, we must as a first step identify ourselves to our banking officer, often with multiple pieces of identification. We intuitively understand this and, frankly, expect our banking institution will challenge us to identify ourselves before we do any business.

Why then as online banking customers do we have less tolerance for such minor inconveniences? And is strengthening online authentication enough to thwart criminals who aim to steal our online banking credentials or otherwise compromise our online banking experience?

As criminals turned their sights to banking customers using various sophisticated techniques (phishing, malware, keyloggers, and Trojans, to name a few) designed to steal online banking credentials, the banking industry responded by implementing equally sophisticated, stronger, multifactor authentication technologies and techniques. While these solutions provide greatly improved security, many also added noticeable complexity to the customer's user experience, which from a marketing and customer relationship perspective is not desirable. Consequently, managing the tension between user experience and security became the key success factor for online banking.

It is clear with the ever-evolving nature of online threats, coupled with the desire by our customers to be able to do business with us online from anywhere in the world via the devices of their choice, banks must look beyond authentication to deliver a secure online banking experience, and that we must partner with our customers to ensure our collective online safety.

The term "customer protection" has emerged in the banking sector to refer to the focus banks must have on helping keep their customers safe while online -- not only while they're connected to their online banking sites -- but during all online activity. We have seen most, if not all, forms of strong authentication defeated by motivated criminals. So the answer appears to be multifaceted in terms of what must be in place to keep our customers safe from the predators who wish to steal their credentials. In other words, focusing on strengthening customer authentication, while a critical aspect of the overall defense strategy, appears not to be enough.

Here are a few areas of focus (in no particular order) for solving the customer protection puzzle:

1. Security 101
Plainly stated, our customers still have difficulty doing the basics, such as keeping their antivirus programs up-to-date, making sure they apply the latest security patches, and using a personal firewall. Even though many companies offer free anti-malware programs and despite our industry's best efforts to raise awareness, many customer PCs fall victim to the plethora of malware that aims to steal their credentials or inject malicious code into their browser sessions. International criminal organizations are also building software that is designed to defeat the most pervasive security authentication technologies deployed by banks worldwide. Technology that protects browser sessions have emerged and by all accounts certainly provide an important additional layer of protection. Many banks are looking to this type of technology to extend protection directly to their customers’ computers. Of course, the criminals also have their sights set on this defensive technology.

2. Education
Education is easy to point to as an area of focus, but difficult to quantify in terms of effectiveness are consumer awareness campaigns. Nonetheless, all banks must have a constantly evolving, dynamic set of awareness materials, techniques, and campaigns to ensure customers are aware of the dangers that exist online and that they play the most important role in their own online safety. Remember that fraud loss results are the ultimate measurement here. More important from the banker's perspective is despite the fact banks (especially in North America) typically do not hold our customers liable for losses resulting from online frauds, we must educate our customers that the damage can extend beyond simple financial fraud. The criminals who compromise the customer's credentials could gain access to additional personal information (bill payees, employers, investment status, etc.), which can be used to commit additional and potentially more damaging offline identity theft related fraud.

The key message: Even with zero liability for online fraud related losses, customers do, in fact, have a key responsibility for staying safe online. Even the best and latest technology cannot protect customers once their end device has been compromised.

1 of 2
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Published: 2014-07-11
Multiple cross-site scripting (XSS) vulnerabilities in Dolibarr ERP/CRM 3.5.3 allow remote attackers to inject arbitrary web script or HTML via the (1) dol_use_jmobile, (2) dol_optimize_smallscreen, (3) dol_no_mouse_hover, (4) dol_hide_topmenu, (5) dol_hide_leftmenu, (6) mainmenu, or (7) leftmenu pa...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.