Analytics
11/1/2012
07:45 AM
Tim Wilson
Tim Wilson
Quick Hits
Connect Directly
RSS
E-Mail
50%
50%

Companies Should Think About Hacking Back Legally, Attorney Says

Fighting back against cybercriminals can be risky, but there are legal ways to do it, says Hacker Halted speaker

MIAMI -- Hacker Halted 2012 -- If you're so frustrated with hackers that you're thinking about hitting them back, then be careful -- but it can be done.

That was the message delivered Tuesday by David Willson, an attorney from Titan Info Security Group, here at the Hacker Halted conference.

While many companies have the technical tools and knowledge they need to inflict damage on their online opponents, most of them do not pursue the idea because of concerns that the law will regard them as hackers themselves, Willson says.

"The bad news is that [corporations'] security sucks," he says. "The good news is that the bad guys' security sucks, too. There are tools, techniques, and intelligence that you can use to anticipate attacks as well as effectively stop them -- and potentially identify attackers once discovered in your network."

For example, a corporation could place code on a bot that has infected its network, Willson says. Eventually, that code might be transferred back to the attacker's command-and-control server, and could be programmed to block the attacker's communications path.

The trick, Willson says, is how to hack back legally. U.S. firms are governed by the federal Computer Fraud and Abuse Act, which essentially states that any unauthorized access of another organization's computers could be considered a crime. Some states have computer trespass laws, and other countries have laws that might get a company into legal trouble for cracking others' computers if those others are cybercriminals, he notes.

In the above example, where code is attached to a bot, an automated tool might be seen by the courts as being similar to cookies or adware, which are not illegal, Willson says.

Companies could also use honeypots, which allow users to legally collect intelligence about their attackers, or beacons, which legally illuminate an attacker's trail, Willson says.

Hacking back should never be a company's first response, but in the case of a persistent attacker, it might be the only answer. "You might be spending $50,000 to $100,000 a week to battle a persistent threat" he says. "You've tried all of the traditional approaches. Calling law enforcement doesn't help -- they are simply overwhelmed with other cases. What do you do?"

The key is to stay within criminal law while taking your chances with civil law, Willson says. "Obviously, you don't want law enforcement turning around and coming after you," he says. "But if a hacker wants to sue you for unauthorized access, that might be a chance you're willing to take."

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4734
Published: 2014-07-21
Cross-site scripting (XSS) vulnerability in e107_admin/db.php in e107 2.0 alpha2 and earlier allows remote attackers to inject arbitrary web script or HTML via the type parameter.

CVE-2014-4960
Published: 2014-07-21
Multiple SQL injection vulnerabilities in models\gallery.php in Youtube Gallery (com_youtubegallery) component 4.x through 4.1.7, and possibly 3.x, for Joomla! allow remote attackers to execute arbitrary SQL commands via the (1) listid or (2) themeid parameter to index.php.

CVE-2014-5016
Published: 2014-07-21
Multiple cross-site scripting (XSS) vulnerabilities in LimeSurvey 2.05+ Build 140618 allow remote attackers to inject arbitrary web script or HTML via (1) the pid attribute to the getAttribute_json function to application/controllers/admin/participantsaction.php in CPDB, (2) the sa parameter to appl...

CVE-2014-5017
Published: 2014-07-21
SQL injection vulnerability in CPDB in application/controllers/admin/participantsaction.php in LimeSurvey 2.05+ Build 140618 allows remote attackers to execute arbitrary SQL commands via the sidx parameter in a JSON request to admin/participants/sa/getParticipants_json, related to a search parameter...

CVE-2014-5018
Published: 2014-07-21
Incomplete blacklist vulnerability in the autoEscape function in common_helper.php in LimeSurvey 2.05+ Build 140618 allows remote attackers to conduct cross-site scripting (XSS) attacks via the GBK charset in the loadname parameter to index.php, related to the survey resume.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.