Welcome Guest. | Log In | Register | Membership Benefits


Topics:   Authentication Tech Center : Security Views

Embedding Digital Certificates In Hardware

A natural evolution, but there are a few potential pitfalls to avoid

Nov 28, 2011 | 07:00 PM | 

By Taher Elgamal
Dark Reading

It was always known that if we chain trust to a known trusted source that the overall trust is improved. Most of the implementations of PKI certificates use some hardware to store the private keys so that forging a signature or obtaining a key is difficult. At this time, the hardware takes the form of hardware security modules (HSMs) in the case of server operations, or a USB device for client machines.

The question is: What if these keys were embedded in the processor itself?

It is only natural for the industry to attempt to combine the trusted hardware into the main processor -- that will enhance the value of the hardware and make strong authentication part of the mainstream industry. The growth of applications that require strong authentication and the growth of e-commerce and other applications that handle sensitive data will perhaps make these feature very important additions to the standard “faster, better, cheaper” way of the growth of the processor industry.

A couple of issues about trust models: First, we should avoid the full flexibility that we did in the browser world since its beginning. A good number of the weaknesses of the current e-commerce environment can be avoided if we prevent “suspect” CAs from being trusted at the root, for example.

Second, we don't want to swing the pendulum the other way completely and create monopolies. Instead, we should embark on designing a good system that will allow us to build this industry correctly. Allowing a trusted CA to be a part of the system should be easy to do, assuming that we know how to revoke a CA key and that revocation checking is a standard part of all operations -- all standard operations.

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.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Authentication Reports

report What's Next for Certificate Technology
A recent rash of certificate authority breaches has left a bad taste in many people's mouths. There is no one reason for the breaches. The compromises were the result of a breakdown in people, processes and technology, but not necessarily the certificates themselves. We take a look at what?s wrong with certificate technology, what can be done to fix it, and what's down the road for certificates and CAs.

report Will Smartcards Live Up to Their Name?
Recent compromises of smartcard data have exacerbated concerns about the technology?s privacy, security and standards (or lack thereof). Yet the promise of smartcards is too compelling to ignore. New technologies and applications prompt us to take a fresh look.

report Get The Best Of Biometrics
As data volume and sensitivity grow, companies cannot rely on password- and token-based authentication. Biometrics can be used to provide strong access control, but you must weigh added complexity and costs against assurance that users are who they say they are.

Other reports from the Authentication Tech Center:




Featured Webcasts
Featured Whitepapers
Featured Reports