Risk
7/24/2013
03:31 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Security and Identity Management: Innovative Authentication Techniques

Today I want to take a closer look at identity. Most people will tell you things are pretty bad today, but things have improved quite a lot.

In my last blog, I broke down security pain points into four categories. Today I want to take a closer look at identity. Most people will tell you things are pretty bad today, but things have improved quite a lot since nobles dispatched their missives authenticated with rings impressed into wax. One needed a ring, a unique seal, and a load of wax. Not to mention recipients sufficiently well-trained to distinguish your seal from fakes. So today, with our richer toolkits - instantaneous communications, unlimited computing power in the cloud, and even ginormous touch screens in every purse and jacket pocket. So what the heck is going on? With amazing technology advances of the last decades, how does identity remain a problem?

Scale might be the most important complication. Today about 6 billion devices are internet connected, and as the so-called internet of things scales, some project 50 billion devices to connect by 2020. Even if we wanted to issue all the human users unique rings and hot wax, we'd still be left with the challenge of identifying the remaining billions of devices which lack the prehensile abilities required to hold and impress ring into wax. Today large public suppliers authenticate more users in seconds than the royal seal examiners did in lifetimes. And the risks have scaled accordingly. In a world that runs on automated authentication decisions, adversaries have become better at exploiting gaps and weaknesses. Estimates place the cost of cybercrime to firms globally as high as $1 trillion. So if your users complain you're being paranoid, let them know you have just cause.

So let's look at it from our users' perspective for a moment. They're continually consumed trying to remember usernames and password for a multitude of accounts - both business and personal. Names of first grade teachers, first pets, first cars. Text messages with one time passwords. And still we lack confidence and suffer risk of fraud as sophisticated malware can hijack the most closely guarded user-provided credential. And then we complicate things with byzantine rules and guidelines for creating and changing passwords. It all would be comical - if our guidelines weren't making it impossible for users to get their work done! So now we're all miserable, if united in our misery.

What if it wasn't like this? What if we could simultaneously simplify life for users while at the same time increasing confidence in authentication decisions? What would it take to build authentication systems less vulnerable to compromise when an end-user was tricked into revealing a password?

There's no mystery around the framework for solutions. It's quite possible to design architectures for robust solutions that rely on all three of the traditional elements of authentication (something you know, something you have, something you are). At the September 2012 Intel Developer Forum, Intel's Chief Technology Officer, Justin Rattner, demonstrated the ability to augment conventional passwords and tokens with the more robust schemes. Justin demonstrated a user walking up to a device and using biometric sensors to locally authenticate a user, then providing attestation to a service provider that user has successfully authenticated. I think it would be great if these types of solutions were broadly available, delivered in solutions that were reliable, difficult to compromise, straightforward to manage and scale for large user populations, and - most importantly - simple for users! While some companies have delivered pieces of the puzzle, it's still too tough for relying parties to stitch together a high quality fabric for authentication and decision making that's easy for users. It may not be rings and wax seals, but we have some distance to go.

It would be great to hear your thoughts on these approaches. What are the biggest challenges you're facing in balancing the robust and simple? Where can the industry do a better job solving your needs? (Hey and vendors, please, no blatant product promos).

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Laurianne
50%
50%
Laurianne,
User Rank: Apprentice
8/1/2013 | 5:11:33 PM
re: Security and Identity Management: Innovative Authentication Techniques
Misery is right. No wonder that "password manager" is one of the popular search terms for our site right now. Where do people see the innovation in identity technology coming from? Will a particular Industry vertical's need spur better solutions?
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio