Mobile

11/15/2017
02:30 PM
Seth Ruden
Seth Ruden
Commentary
50%
50%

Who Am I? Best Practices for Next-Gen Authentication

By their very nature, antiquated, static identifiers like Social Security numbers and dates of birth are worse than passwords.

There is no ignoring it: our financial security is compromised daily. Many security professionals reading this wouldn't hesitate to recount all the breaches they've been a part of as consumers: merchant breaches in which replacement cards forced you to update your linked accounts, or data compromises when personal information was stolen and identity theft protection was provided, forcing you to consider freezing new credit originations.

These are only the ones we know about, however. A recent report from SkyHigh Networks concluded that up to 7% of all Amazon S3 servers leave volumes of exposed via "public access" configuration. Consider the residual risk of all the data breaches we've historically been exposed to and the totality of this vulnerability becomes immense. Back in the first quarter of 2014, I suggested we were experiencing data breach fatigue; today it's data breach exhaustion, and consumers may now feel powerless.

These consumer attitudes are reflected in ACI Worldwide's "Global Consumer Trust and Security Perceptions Survey," which revealed that an average 65% of consumers across 20 countries stop shopping with a merchant or a retailer once they experience fraud or a data breach. In select regions like Brazil and Mexico, this figure rises as high as 86% and 84%, respectively. It is a risk that few are willing to take and a stern lesson in the strategic importance of data security across the enterprise in 2017.

We must ask ourselves, as both consumers and enterprise security professionals: What exactly is compromised here? What information falls into the hands of an attacker and how could they use it to attack me? As we're compromised once, twice, multiple times, we are falling under greater risk from hackers and fraudsters.

Typically, most concerning for consumers is the demographic data that is baked directly into authentication procedures. If an attacker has the relevant non-public personal information, they can coordinate illegitimate identity theft, use a payment card for unauthorized spending, or potentially take over a whole account.

So what lessons are out there? Well, for starters: Why are we still using knowledge-based authentication based on third-party-issued data elements to verify transactions? Government identity numbers such as Social Security numbers, home addresses, and users' date of births are "zombie authenticators," devoid of enterprise-caliber security, yet constantly resurfacing. By their very nature as sensitive data, these antiquated static authenticators are worse than passwords. And yet, despite being compromised multiple times and being available on occasion through public or searchable sources, using personal information for authentication is still a common tactic in 2017. I cringe when merchants use these types of questions to authenticate customers.

Fraudsters maintain active databases to store these elements and anyone with an account on the Dark Web can search for identifying information concerning the intended target. In fact, a neologism already exists for this phenomenon, "credential stuffing." The act of intercepting and using as many authentication elements as possible to construct a target profile and take over an account is an established process, built on archives of already compromised data.

In a world where emerging technologies are transforming protocols and workflows across the entire economy, businesses are missing a valuable opportunity to establish a more rigid authentication process, one that uses dynamic, original, and more sophisticated tactics to validate who  a person is. 

The rise of biometrics in remote and mobile app settings (retina scans, face and voice recognition, fingerprints, etc.), dynamic account-based questions with answers known only to the service provider and customer, and multifactor out-of-band authentication provided via a separate network are just three alternatives that can be embraced in tandem for a smoother authentication experience that simultaneously reduces the potential for account takeover. Would I feel more secure in a world of high-frequency data breaches knowing my financial institution authenticates me with at least two factors? Could this be faster than the present authentication practice of asking multiple questions throughout a contact center session? The answer to both questions is yes.

A formal overhaul of payments authentication is already underway in some regions. As European institutions prepare for PSD2 and its residual impact on digital commerce and cross-border payments, the Strong Consumer Authentication standards within this mandate have created a potential benchmark for secure authentication in the enterprise. With Stratistics MRC estimating that the global multifactor authentication market will grow to $13.59 billion by 2022, we're procuring new security mechanisms that will tap into a range of interchangeable knowledge, possession, and inherence-based identifiers. 

Organizations in the US must follow suit in their network and data protection methods. Establishing proactive monitoring processes and preparing an incident response plan in advance can reduce the flow of sensitive data leaving a business. Taking steps to encrypt the data itself is another means of ensuring that hackers don't have free rein over data, and the well-being of an organization's reputation once they've bypassed peripheral security solutions.

While no one wants to receive a somber letter from their financial institution, or look themselves up on a newly created security webpage to determine the status of their security following a breach, this is the new reality we live in. To sit idly by and continue authenticating with the most consistent static data elements is a lesson of any breach du jour. 

Related Content:

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

Seth Ruden is a senior fraud consultant at ACI Worldwide with more than a decade of direct experience in financial services. As a certified fraud examiner and anti-money laundering specialist, Seth has worked with banks, law enforcement, regulators and analysts across the US, ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15594
PUBLISHED: 2018-08-20
arch/x86/kernel/paravirt.c in the Linux kernel before 4.18.1 mishandles certain indirect calls, which makes it easier for attackers to conduct Spectre-v2 attacks against paravirtual guests.
CVE-2018-15572
PUBLISHED: 2018-08-20
The spectre_v2_select_mitigation function in arch/x86/kernel/cpu/bugs.c in the Linux kernel before 4.18.1 does not always fill RSB upon a context switch, which makes it easier for attackers to conduct userspace-userspace spectreRSB attacks.
CVE-2018-15573
PUBLISHED: 2018-08-20
** DISPUTED ** An issue was discovered in Reprise License Manager (RLM) through 12.2BL2. Attackers can use the web interface to read and write data to any file on disk (as long as rlm.exe has access to it) via /goform/edit_lf_process with file content in the lfdata parameter and a pathname in the lf...
CVE-2018-15574
PUBLISHED: 2018-08-20
** DISPUTED ** An issue was discovered in the license editor in Reprise License Manager (RLM) through 12.2BL2. It is a cross-site scripting vulnerability in the /goform/edit_lf_get_data lf parameter via GET or POST. NOTE: the vendor has stated "We do not consider this a vulnerability."
CVE-2018-15570
PUBLISHED: 2018-08-20
In waimai Super Cms 20150505, there is stored XSS via the /admin.php/Foodcat/editsave fcname parameter.