Commentary

George Hulme
 

Corporate Patch Management Lags In Maturity

If one of the most important disciplines necessary for keeping systems secure is a systematic vulnerability management program, why have so few organizations reached a decent level of maturity in their patch management efforts?

If one of the most important disciplines necessary for keeping systems secure is a systematic vulnerability management program, why have so few organizations reached a decent level of maturity in their patch management efforts?According to data released this week by security research firm Securosis, 70 percent (out of 100 respondents) don't current measure how well, or efficiently, they roll out their software patch updates. In fact, 40 percent of respondents to Securosis' survey said they either have an informal patch process, or no patch management process in place at all.

The notion that 40 percent of companies aren't taking a formal approach to patching is scary in itself. But the news is actually worse that that -- the survey isn't based on a broad sample of organizations with varying degrees of IT maturity. No. Unfortunately, the survey was garnered by reaching out to companies engaged in security metrics and patch management groups -- so the survey is actually biased toward the more progressive companies, one could presume.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The survey results stem from Project Quant, an open initiative led by Securosis and Microsoft, that aims to understand the underlying costs associated with patch management and try to improve processes. Not surprisingly, participating organizations seem further along in their efforts to patch workstations and server operating systems -- but lag in keeping applications up to date. Unfortunately, it's the application layer that is under greatest attack.

In an effort to ease organization's patch burden, Project Quant has been working on a superset "process framework" that should encompass most patching activities within any organization, regardless of the systems they have in place. The framework consists of ten phases and forty steps. Because patching is often labor intensive, a substantial portion of the model is geared toward those types of detailed patching activities.

Patch management and the associated toolsets are relatively mature. That's why these results are so surprising, to me. Last fall, InformationWeek ran a feature, Vulnerability Management That Works that discussed how vulnerability management must be aligned with business values to succeed.

Securosis' Project Quant is just getting underway, and the survey results are already interesting. In the full report [PDF], there are also very detailed worksheets for measuring your organization's patch management effectiveness. It'll be a worthwhile exercise to go through, and most likely an eye-opener.

If you're interested in mobile security, technology, and business updates, consider following my Twitter account.


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