Commentary

Alexander Wolfe
 

Are Worms Always Bad?

Self-replicating programs, which spread unchecked across the Internet, are always bad. Except when they're good. At least that's the theory behind U.S Patent number 7,296,923, awarded to Symantec for "Using a benevolent worm to assess and correct computer security vulnerabilities."

Self-replicating programs, which spread unchecked across the Internet, are always bad. Except when they're good. At least that's the theory behind U.S Patent number 7,296,923, awarded to Symantec for "Using a benevolent worm to assess and correct computer security vulnerabilities."True, this is not the newest story in the world: Symantec was granted this patent in November 2007, and it was originally filed back in 2002. Still, "good" worms periodically pop back into the news, so I guess you could say I'm simply ahead of the curve.

So just what exactly is a "good" worm? As inventor Henri Isenberg explained it in the Symantec patent -- I'm paraphrasing -- the intent of the benevolent is to assess potential security vulnerabilities of a computer. First, the worm attempts to copy itself onto the computer, to see if it can be done. (Really! That's how it checks for vulnerability; no copy, no problem.)


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The worm then tries to replicate itself on a second computer. If it's able to multiply, the assumption is that a "bad" worm could do likewise. So goody-good worm "communicat[es] information concerning at least one security vulnerability ... to a benevolent worm controller."

Even better, the good worm can be used to execute antivirus software, in effect patching the problem at the source. (A form of targeted security software-microsurgery, really.)

Clearly, the intention of a benevolent worm such as Symantec is patenting is mostly to serve as an early warning system. It'll alert admins that their systems are potentially vulnerable.

That's a good plan, but just how workable is it? Authorities more knowledgeable than myself -- Bruce Schneier comes to mind -- don't think they're such a good idea. For one, worms, by their very self-replicating nature, suck up bandwidth. Also, a worm by definition runs without the user's consent. That's pretty much a violation of the security world's Star Trekian prime directive.

Clearly, there is a positive to the early-warning and vulnerability-assessment aspect of a good worm. Just as obviously, though, few people are brave enough to bite. As Luke Bellamy, Damien Hutchinson, and Jason Wells of Australia's Deakin University point out in their paper, User Perceptions and Acceptance of Benevolent Worms -- A Matter of Fear?: "There has been no hint of commercial adoption of these worms, which one researcher has described as being due to a 'fear factor.'" (This paper was delivered at an IEEE conference last year. I'd really like to read it. Unfortunately, only an abstract is available online.)

Fear factor of worms? Yeah, I get that. So what do you think; is there any value in this approach?



Symantec's Good Worm (Click picture to enlarge and see second flowchart.)

See also "8 Dirty Secrets Of The Security Industry"

Like this blog? Subscribe to its RSS feed, here.

For a mobile experience, follow my daily observations on Twitter.

Check out my tech videos on this YouTube channel.


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