Commentary

George Hulme
 

Disclosure Isn't Working

After a decade of writing about IT security, I don't know how anyone would think this current system of disclose and patch is working. It's not.

After a decade of writing about IT security, I don't know how anyone would think this current system of disclose and patch is working. It's not.Do you know when the riskiest time for an attack against a vulnerability is? Is it:

1) When a vulnerability has been discovered by a security researcher? 2) While the vendor is working on a patch? 3) Right after the vulnerability has been disclosed and the patch announced?


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

If you answered 3, you win.

Once the patch has been released, any security researchers or cybercriminals worth their salt can reverse-engineer the patch and find the vulnerability to attack. Which they do -- within days, if not hours, and then, undoubtedly, begin attacking the legions of unpatched systems.

But you're thinking, "The software flaw was always there, and we've been susceptible all along to attack!"

You're just looking at one variable of the risk equation (note: Cost should be factored in for enterprises, but it's not necessary now):

Risk = Threat x Vulnerability

By this equation, when a vulnerability exists in a software application and no one knows about it, there's no risk because there's no threat to its exploitation. But once a vulnerability is discovered and more people know about it, the higher the risk. Too often in this industry, we all focus on Vulnerability and not Threat.

Now, let's assume that shiny new browser you installed -- we'll call it ExplorerFox Opera -- has 100 vulnerabilities the day it's released, but no one knows that they're there. You're risk to attack is now low.

But in a few days criminal hackers find 10 flaws to exploit. Your risk is now high, and attackers begin infecting people with keystroke loggers and spyware. A week later, white-hat security researchers find 10 -- completely different flaws -- and they call the makers of ExplorerFox Opera to have patches made, and within a month or two all of those flaws found by the white hats are patched. How much more secure are you now? You're still at risk from the 10 vulnerabilities being attacked in the underground, and there are 80 flaws still left to be discovered by good and bad guys alike. Who will find them?

But wait, the show goes on: News reports start surfacing of those 10 zero-day flaws being actively exploited, and the makers of ExplorerFox Opera rush out a set of new patches to fix those.

But security researchers find that those patches actually create more vulnerabilities than they fixed ...

If only we built and maintained buildings, cars, airplanes, oil refineries, and nuclear power plants this way.


Related Reading




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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links