Perimeter
5/23/2011
04:59 PM
Taher Elgamal
Taher Elgamal
Commentary
Connect Directly
RSS
E-Mail
50%
50%

From Device to Device, From Site To Site

Obama administration's digital identities initiative relies on private industry to come together and make it work

The Obama administration is championing the idea of cyberidentities for U.S. citizens, and it’s asking for the private sector’s help.

I applaud this effort because, as I’ve discussed several times before, lack of identity verification or validation is responsible for the raft of bad things we’ve seen in recent years -- fraud, identity theft, espionage, and even cyberwars.

On the server authentication side, the administration isn’t recommending any particular technologies or methods because we already have SSL-- which understands credentials that are PKI-formatted -- and its certificates, whose trustworthiness has been improved during the years by the private sector.

The administration isn’t recommending particular technologies or methods for defining identity and authenticating users on the client side, either. Rather, it’s expressing confidence in the validity of the idea of cyberidentities -- and the private sector’s expertise -- by inviting all private-sector technology companies to participate in the project. The administration is acting as the broker of an operability experiment whose goal is for every participant to benefit from every other participant’s work.

Once the private sector finishes up this operability experiment and the client side is figured out, what will it mean for SSL?

Since we can’t map any sort of identity into a PKI credential, we’ll have to detach the client identity from the SSL session. Or rather, we could detach the client identity from the SSL session, theoretically, despite the fact that that’s not what’s really being talked about at the moment.

A reasonable architecture could be as simple as this: Imagine an application layer in a banking session. After the SSL handshake during which the server has been authenticated, the user is asked to authenticate herself. The applications and websites are then left with the burden of determining how the user’s identity is going to be supported. Period.

I think that’s a reasonable architecture. Some identities will be sent across the wire easily, while others will demand more work. Financial services, healthcare, and other sectors will have to choose a way to support the user’s identity.

The real difficulty comes when we ask the question, “What does operability mean?”

It would be really nice if all of these identities could live on top of a single infrastructure. But that infrastructure doesn’t yet exist. Each site or enterprise is building its own user authentication. That means each provider of an identity authentication concept will have to sell to the number of servers it would like to, and that will leave us with a fragmented market. That’s where we are today.

What would be better is if the government encouraged the private sector to build an infrastructure that supports all strong authentication systems with a single API so that regardless of which identity the back end would like to authenticate, the front end will say, “Yes, I support A, B, and C,” and the back end will choose A, B, or C. A small authentication and negotiation protocol layer could then be supported that allows sites to choose the identity types that they would like to support.

Exactly how we’re going to map all of this together -- that’s another story. It’ll be a huge effort because each user has several different types of identities that need supporting (to say nothing about different types of devices, like smartphones and tablets), and each site chooses which of those types of identities it will support.

It’s as if we need a magical infrastructure -- one that can tie an identity to the same trusted user going from device to device and from site to site, and confirm that this is most probably the same trusted user it encountered before.

After 16 years, we’re still not where we had hoped we would be on this. Then again, with all the progress the industry has made in that time, the place we’re at is a pretty good compromise, and the Obama administration’s efforts will surely take us to the next level.

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
Register for Dark Reading Newsletters
Partner Perspectives
What's This?
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.

As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Featured Writers
White Papers
Cartoon
Current Issue
Dark Reading's October Tech Digest
Fast data analysis can stymie attacks and strengthen enterprise security. Does your team have the data smarts?
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-3304
Published: 2014-10-30
Directory traversal vulnerability in Dell EqualLogic PS4000 with firmware 6.0 allows remote attackers to read arbitrary files via a .. (dot dot) in the default URI.

CVE-2013-7409
Published: 2014-10-30
Buffer overflow in ALLPlayer 5.6.2 through 5.8.1 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in a .m3u (playlist) file.

CVE-2014-3446
Published: 2014-10-30
SQL injection vulnerability in wcm/system/pages/admin/getnode.aspx in BSS Continuity CMS 4.2.22640.0 allows remote attackers to execute arbitrary SQL commands via the nodeid parameter.

CVE-2014-3584
Published: 2014-10-30
The SamlHeaderInHandler in Apache CXF before 2.6.11, 2.7.x before 2.7.8, and 3.0.x before 3.0.1 allows remote attackers to cause a denial of service (infinite loop) via a crafted SAML token in the authorization header of a request to a JAX-RS service.

CVE-2014-3623
Published: 2014-10-30
Apache WSS4J before 1.6.17 and 2.x before 2.0.2, as used in Apache CXF 2.7.x before 2.7.13 and 3.0.x before 3.0.2, when using TransportBinding, does properly enforce the SAML SubjectConfirmation method security semantics, which allows remote attackers to conduct spoofing attacks via unspecified vect...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Follow Dark Reading editors into the field as they talk with noted experts from the security world.