Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

11/22/2010
06:43 PM
Taher Elgamal
Taher Elgamal
Commentary
50%
50%

What About Biometrics?

Integrating fingerprints in a standard way so that Web and enterprise applications can take advantage of them

I mentioned earlier how authentication hasn't traditionally served the user's interest. It was built for, and sold *to* the back ends, and it's resulted in significant security issues, forced us to deal with multiple authentication schemes, and created serious confusion.

This brings to mind universal authentication schemes. How can we embed authentication in the middle of these Web and enterprise applications in a standard way?

Biometrics is the obvious choice, since virtually all users have fingerprints. But how can we integrate fingerprints in a *standard* way so that Web and enterprise applications can take advantage of them? How can we build middleware in a standard way so that anybody could log into any system with a fingerprint, so that applications could attach access control to different resources based on the identity associated with the fingerprint?

When we answer these questions, we will have in our midst a standard for authentication that makes a far simpler demand of the user than any currently being made. We will also have quite an interesting way to boost the overall authentication level of the Internet. And I've read more than one study that suggests users would warm up to this biometric method more quickly than to others.

Iris scans, for instance, are possible, but a bit invasive and probably not ideal for a universal authentication scheme.

Voice recognition isn’t invasive necessarily, but if the user catches a cold, gets hoarse, or attempts to log in at a loud event, all reliability is lost.

Most laptops and phones come with built-in cameras today, so facial recognition might work, but that's reliable only if the software can distinguish between a still photograph and a real person, and since most standard webcams on laptops typically capture at relatively low resolutions, this is a problem, too.

Whatever our endgame, our opening gambit is clear: we need to drive competition between vendors, and we need to do this by driving standards, because vendors of different equipment (i.e., the application developers and the hardware manufacturers) will need a standard way for the applications to talk to the hardware.

It is important, when we’re thinking of these things, to simplify solutions, but with authentication involving biometrics, it's very important that we design the systems correctly, to not oversimplify solutions.

One of the things that creep people out about biometrics is this sense that, "Oh my God, some server on the Web is going to store all the fingerprints for all the people in the world. What’s next?"

Obviously, that's not a great idea, but what is a great idea is the continued fostering of efforts to come up with protocols that actually make it possible to recognize the same fingerprint in a strong cryptographic way without ever sending any of the actual fingerprint images anywhere.

Different entities can still add things on top if there is a need (e.g., adding PKI to enable signatures and encryption). I'm fine with that. If they want to add one-time passwords because they want to be sure that people don’t replay things -- I'm fine with that, too. But even without these extras, a minimal level of biometric authentication will, in my prediction, prove quite resilient.

And what a bad day for the bad guys that's going to be.

Recognized in the industry as the "inventor of SSL," Dr. Taher Elgamal led the SSL efforts at Netscape. He also wrote the SSL patent and promoted SSL as the Internet security standard within standard committees and the industry. Dr. Elgamal invented several industry and government standards in data security and digital signatures area, including the DSS government standard for digital signatures. In addition to serving on numerous corporate advisory boards, Dr. Elgamal is the Chief Security Officer at Axway, a global provider of multi-enterprise solutions and infrastructure. He holds a Ph.D. and M.S. in Computer Science from Stanford University. View more of his blog posts here.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18934
PUBLISHED: 2019-11-19
Unbound 1.6.4 through 1.9.4 contain a vulnerability in the ipsec module that can cause shell code execution after receiving a specially crafted answer. This issue can only be triggered if unbound was compiled with `--enable-ipsecmod` support, and ipsecmod is enabled and used in the configuration.
CVE-2012-6070
PUBLISHED: 2019-11-19
Falconpl before 0.9.6.9-git20120606 misuses the libcurl API which may allow remote attackers to interfere with security checks.
CVE-2012-6071
PUBLISHED: 2019-11-19
nuSOAP before 0.7.3-5 does not properly check the hostname of a cert.
CVE-2012-6135
PUBLISHED: 2019-11-19
RubyGems passenger 4.0.0 betas 1 and 2 allows remote attackers to delete arbitrary files during the startup process.
CVE-2016-10002
PUBLISHED: 2019-11-19
Node-cookie-signature before 1.0.6 is affected by a timing attack due to the type of comparison used.