Commentary

George Hulme
 

Is It Time For Security To Go On The Offense?

Security researcher Joel Eriksson recently demonstrated how security vulnerabilities within hacker attack tools can be used to turn the tide on online criminals.

Security researcher Joel Eriksson recently demonstrated how security vulnerabilities within hacker attack tools can be used to turn the tide on online criminals.According to a Wired blog post, Eriksson, a security researcher with Swedish security form Bitsec, demonstrated how he has successfully reverse engineered attack software, such as Trojan horses, so that he can upload his own exploits on the attacking systems.

It seems Eriksson is finding vulnerabilities in a number of "remote administration" tools, including Bifrost and PCShare.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

"If there is a vulnerability, it is still game over for the hacker," Eriksson is quoted as saying.

It's truly turning the tables on attackers: Once a vulnerability is found in a Trojan, it's then possible to crash, or even infect, the attacking system with the software of your choosing.

I'm all for nailing the bad guys, and while this is interesting, there's the obvious question: are you legally justified toasting the machine that is attacking you? And what about the innocent bystander, albeit infected, systems potentially caught in the crossfire?

This research sort of reminds me of a story I wrote one week short of five years ago, about the digital tar pit, LaBrea, developed by Tom Liston. LaBrea would entrap hackers and worms -- but it froze their machine and forced the hacker to break off the attack. That story is available here, and goes into how LaBrea might go afoul of the Digital Millennium Copyright Act of 1998.

Both Eriksson's and Liston's works are laudable, in my opinion. And maybe, one day, there will be a legal mechanism, akin to digital self-defense, that would let us all safely and legally temporarily brick -- or at least reboot -- an offending system.


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