Kind Of A Mess
Internet needs an infrastructure that enables back ends and users to communicate with each other using better authentication--and allows any number of authentication technologies to sign into it
I’ve blogged previously about how, back in the early days of SSL, we tried to do client authentication, but our direction somehow went sideways and we were never able to pull it off. Since then, and especially over the past 10 years or so, a number of authentication companies have developed interesting technologies aimed at selling Internet service providers and enterprises a better technique than password-based authentication.
The result: Some organizations have actually adopted these new technologies, leading to a proliferation of varying back-end authentication methods across the Internet.
More Security Insights
- Forrester Study: The Total Economic Impact of VMware View
- Securing Executives and Highly Sensitive Documents of Corporations Globally
- Agile Service Desk: Keeping Pace or Getting out Paced by New Technology?
- Big Data Analytics: Are You Ready?
It’s kind of a mess.
It’s a mess because each of these technologies requires two things: First, they require the back end to sign up and integrate the Web service interface of the authentication product into the login screen of the website and into the enterprise. Second, they require a user to do something specific to authenticate himself into this new website.
For the user, it’s confusing -- he gets a message on his screen asking for information additional to information he has already provided. And users can’t stand that.
Now, if it were his bank, the user would probably be willing to take extra steps because he’s used to banks making these kinds of requests. But if it’s another entity, it doesn’t fly.
So it seems that what the world actually needs is a piece of Internet infrastructure -- one that is altogether missing at this point -- that does two things: One, it enables websites (financial and others) to one-time-only participate in a stronger authentication infrastructure that allows them to choose any available strong authentication scheme without having to integrate the specific product each time; and two, it enables users to access these services in a seamless way -- perhaps not 100 percent seamless, since they may need to do a one-time registration, but as near seamless as possible.
We need to conceive of a new infrastructure that basically sits on top of today’s Internet e-commerce -- an infrastructure that enables back ends and users to communicate with each other using better authentication, and allows any number of authentication technologies to get signed into it. In this scenario, enterprises wouldn’t need to do multiple integrations and needlessly complicate their users’ workflow.
Additionally, the concept of “inferred identity” would need to live in the middle of this new infrastructure, allowing a back end to access either a user or device identity without actually asking the user to do anything. This new infrastructure would be able to tell what a specific device looks like, and then the back end would get the data and validate that the device is what they expect for this kind of session.
In order for this new kind of authentication to flourish, a lot of people will have to get on board. I believe that time is coming soon because we cannot continue to field the complexity that results from every single site determining which form of authentication it prefers. As it stands, all of these forms understand SSL, so the back-end authentication is certainly going to be an SSL certificate, just as it has always been. That means that the SSL session can actually secure the connection between the user, the front end, the client end, and the back end in order to set up the user authentication session. Once those actions are completed, it can then set up the stronger authentication session.
Is this goal little more than a dream? I hope not. The Internet needs a more intelligent way of handling stronger authentication. So until the patchwork mess of technologies is cleaned up, it’s a dream worth pursuing.
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.