{"id":240,"date":"2013-05-09T00:00:00","date_gmt":"2013-05-09T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2013\/05\/09\/hacking-back-digital-revenge-is-sweet-but-risky\/"},"modified":"2021-12-30T11:36:49","modified_gmt":"2021-12-30T11:36:49","slug":"hacking-back-digital-revenge-is-sweet-but-risky","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2013\/05\/09\/hacking-back-digital-revenge-is-sweet-but-risky\/","title":{"rendered":"Hacking back: Digital revenge is sweet but risky"},"content":{"rendered":"<p>Whether criminals are hacking our passwords, or Anonymous is simply making a statement, the disruptions and data breaches exact a heavy toll in terms of time, money, and security.How that digital revenge is wreaked, and whether any of it is legal, are issues being actively debated right now\u2014to the extent that anyone wants to talk about it, let alone admit to trying it.&nbsp;&nbsp;Hacking back at a cyber-assailant is tempting, but it&#8217;s just as illegal as the original cyberattack.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This law has undergone numerous revisions since it was first enacted in 1986, but Title 18, Sec. 1030 is clear on the point that using a computer to intrude upon or steal something from another computer is illegal. \u201cThere is no law that actually allows you to engage in an attack,\u201d says Ray Aghaian, a partner with McKenna Long &amp; Aldridge, and a former attorney with the Department of Justice\u2019s Cyber &amp; Intellectual Property Crimes Section.\u201c<\/p>\n<p style=\"margin: 0px;\">According to Ahlm, the companies tracking the bad guys collect vast amounts of data on Internet activity and can hone in on specific \u201cactors\u201d who engage in criminal activity. \u201cWithout touching or hacking the individual, they can tell you how trustworthy they are, where they are, what kind of systems they use,&#8221; says Ahlm.<\/p>\n<p style=\"margin: 0px; min-height: 14px;\"><\/p>\n<p style=\"margin: 0px;\">While private companies cannot take offensive action with any such intelligence, they can use it defensively to thwart suspicious actors if they&#8217;re found to be sniffing around company data. \u201cBased off your intelligence of who\u2019s touching you,\u201d says Ahlm, \u201cyou can selectively disconnect them or greatly slow them down from network access.\u201d<\/p>\n<p style=\"margin: 0px; min-height: 14px;\"><\/p>\n<p style=\"margin: 0px;\">In the grand scheme of fight-back tricks, this is one that causes relatively little harm but does a lot of good,&#8221; says Matthew Prince, co-founder and CEO. This company drew raves\u2014as well as criticism\u2014for creating a way to spam back at spammers, clogging their systems and preventing them from sending out more spam.<\/p>\n<p style=\"margin: 0px; min-height: 14px;\"><\/p>\n<p style=\"margin: 0px;\">Hacking back can also have unintended consequences, such as damaging hijacked computers belonging to otherwise innocent individuals, while real criminals remain hidden several layers back on the Internet.<\/p>\n<p style=\"margin: 0px;\"><\/p>\n<p style=\"margin: 0px;\">Link: <a href=\"http:\/\/www.pcworld.com\/article\/2038226\/hacking-back-digital-revenge-is-sweet-but-risky.html\">http:\/\/www.pcworld.com\/article\/2038226\/hacking-back-digital-revenge-is-sweet-but-risky.html<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-240","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/240","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=240"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/240\/revisions"}],"predecessor-version":[{"id":2727,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/240\/revisions\/2727"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=240"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=240"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=240"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}