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

Topics:   Security Views : Vulnerability Management Tech Center
  • |   Email this page E-mail
  • |  Print Print
  • |   Bookmark and Share

IE 6 Aftermath: Time To Review Your Browser Strategy

The latest update for Internet Explorer is out, and organizations are busy applying or at least certifying the patch on their testbeds.

Jan 27, 2010 | 07:31 PM | 

By Wolfgang Kandek
Dark Reading
The latest update for Internet Explorer is out, and organizations are busy applying or at least certifying the patch on their testbeds.The out-of-band release certainly causes some additional work for IT admins, but Microsoft did the right thing in anticipating the update because the exploit for the vulnerability had been made public and will become more widespread soon.

So far, so good, everything back to normal. But hold on: There is an opportunity here...

The immense publicity surrounding this Microsoft update due to its participation in the Google/CN data breach gives you an opening to re-evaluate your browser strategy. After all, the browser's constant exposure to external content makes it easily the most attacked software on the average desktop. Internet Explorer 6, still in use by many companies (more than 50% of Qualys users), is almost 10 years old and was designed during a time when the Internet was a much gentler place. IE 7 is better, but does not have many of the specific safety features built into Internet Explorer 8.

So update to IE 8, which has a familiar patch cycle. Alternatively, another modern browser could provide additional security. Firefox from Mozilla is very popular, well-supported, and extremely user configurable. Chrome from Google is the newest in this field, was designed with security in mind, and has a silent update mechanism -- something that I am particularly fond of.

Either option will gain you robustness and performance.

P.S.: If you cannot update, there is a place for you as well -- a small community (1,575 as of this writing) of diehard IE 6 fans exists, and they congregate here.

-- As the CTO for Qualys, Wolfgang Kandek is responsible for product direction and all operational aspects of the QualysGuard platform and its infrastructure. Wolfgang has more than 20 years of experience in developing and managing information systems. His focus has been on Unix-based server architectures and application delivery through the Internet. Wolfgang provides the latest commentary on his blog: laws.qualys.com and also publishes his Patch Tuesday commentary to the QualysGuard channel: www.youtube.com/QualysGuard. He is a frequent source in business and trade media and speaks at industry conferences around the world, most recently at RSA 2009.


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
 
  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