Welcome Guest. | Log In | Register | Membership Benefits
Dark Reading's security-views Weblog

Topics:   Authentication Tech Center : Security Views

Leaps Of Faith

Mobile is more secure than the browser realm because most mobile transactions are conducted through applications, not the browser

Jun 20, 2011 | 10:43 PM | 

By Taher Elgamal
Dark Reading

Certificates and SSL use a proven, time-honored cryptographic protocol that most of us benefit from every day. Still, phishing attacks do occur; bad guys continue to use fake forms that trick users into providing sensitive information. The protocols are by no means responsible for these events, but they do get blamed, largely because an act of trust was committed through the browser, and certificates and SSL are directly involved in determining who the browser trusts.

So who should the browser trust?

This is a question we asked about 15 years ago when we were developing SSL, and it’s still relevant. Just as it was back then, the browser today is the client through which the world accesses websites, and no one wants to restrict access to sites, especially trusted ones.

So what we are facing is a compromise between security and functionality, one that allows users to trust whomever they wish, but delivers warnings in a pop-up window if the certificate they’re about to accept comes from an unknown source. If they wish to go ahead and trust it, then they may proceed -- and the fact is that nearly everyone ignores the pop-up warning and clicks through, behaving as if they trust most sites they approach.

It’s this assumption of trust, not the SSL protocol, that is responsible for the success of phishing attacks and identity theft. In fact, when SSL is used in the back-end and in server-to-server connections, it is literally not possible to connect to the wrong place. Because this use of SSL relies on mutual authentication, one simply does not see the kinds of security issues that crop up when individual users in charge of the decision to trust or not trust a certificate.

Similarly -- and this might come as a surprise -- from a security standpoint, the mobile realm is far more secure than the browser realm, because most mobile transactions are conducted through applications, not browsers. With mobile apps, for instance, the certificates are already built in -- they don’t allow the user to trust any random site and click “Yes” to a pop-up window that should genuinely give them pause. They don’t force the user to wonder who the browser should trust, because it’s not a browser.

The pop-up “warning” window that makes certificate trust a user option was, frankly, the wrong decision. We didn’t spend enough time thinking about how to give the browser an absolutely trusted certificate, and how to eliminate the need for the user to take frequent leaps of faith with random sites.

Will those who blame certificates and SSL for phishing attacks be silenced when every transaction has its own dedicated application, and the browser is relegated to a “stand-by” app for when no dedicated app is available? I believe many of us are already previewing this phishing-free future as we access the Web via smartphones, and rely more and more on a wide range of applications that have come of age since the debut of the app stores some years back.

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









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
  June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
 
Featured Webcasts
Featured Whitepapers
Featured Reports