{"id":851,"date":"2008-01-03T00:00:00","date_gmt":"2008-01-03T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/01\/03\/uk-gov-sets-rules-for-hacker-tool-ban\/"},"modified":"2021-12-30T11:38:16","modified_gmt":"2021-12-30T11:38:16","slug":"uk-gov-sets-rules-for-hacker-tool-ban","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/01\/03\/uk-gov-sets-rules-for-hacker-tool-ban\/","title":{"rendered":"UK gov sets rules for hacker tool ban"},"content":{"rendered":"<p>The UK government has published guidelines for the application of a law that makes it illegal to create or distribute so-called &#8220;hacking tools&#8221;.  The controversial measure is among amendments to the Computer Misuse Act included in the Police and Justice Act 2006.  However, the ban along with measures to increase the maximum penalty for hacking offences to ten years and make denial of service offences clearly illegal, are still not in force and probably won&#8217;t be until May 2008 in order not to create overlap with the Serious Crime Bill, currently making its way through the House of Commons.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Critics point out that many of these tools are used by system administrators and security consultants quite legitimately to probe for vulnerabilities in corporate systems.<\/p>\n<p>The problem is that anything from nmap through wireshark to perl can be used for both legitimate and illicit purposes, in much the same way that a hammer can be used for putting up shelving or breaking into a car.<\/p>\n<p>Following industry lobbying the government has come through with guidelines that address some, but not all, of these concerns about &#8220;dual-use&#8221; tools.  The guidelines establish that to successfully prosecute the author of a tool it needs to be shown that they intended it to be used to commit computer crime.<\/p>\n<p>http:\/\/www.theregister.co.uk\/2008\/01\/02\/hacker_toll_ban_guidance\/<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-851","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/851","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=851"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/851\/revisions"}],"predecessor-version":[{"id":3338,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/851\/revisions\/3338"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}