{"id":1912,"date":"2007-04-17T00:00:00","date_gmt":"2007-04-17T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/04\/17\/internal-it-threats-in-europe-2006\/"},"modified":"2021-12-30T11:40:17","modified_gmt":"2021-12-30T11:40:17","slug":"internal-it-threats-in-europe-2006","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/04\/17\/internal-it-threats-in-europe-2006\/","title":{"rendered":"Internal IT Threats in Europe 2006"},"content":{"rendered":"<p>InfoWatch and the world&#8217;s &#8212; first-ever annual study on the problems of internal IT security in Europe.  The findings are based on surveys InfoWatch conducted with a range of middle- and upper-tier IT management professions from 410 companies across Europe.  The EU1 &#8212; unlike the US &#8212; has had no directives requiring the mandatory notification of victims in cases of data breach, and companies have been slow at times to initiate notification procedures.  It is natural that company management would fear the major costs &#8212; both financial and in terms of lost reputation &#8212; which accompany a data leak.  And rather than initiate costly procedures against themselves, some have opted to hope that the problem will just go away, especially in the typical case of a lost or stolen laptop.  Such a policy of avoidance can result in hefty losses for those whose data is held on the computer and who become victims of identity theft as a result.  Many companies have, of course, been proactive in dealing with such leaks, notifying those affected, setting up advice hotlines, providing bank account monitoring and bringing in the law-enforcement agencies.  But while, to date, admissions of data leakage across the EU have relied on companies choosing to make that information public &#8212; a decision which has depended on how the company perceives its best interests in the circumstances &#8212; that may soon change.  While InfoWatch welcomes the growing appreciation among IT managers of the importance of viable preventative solutions to internal information security, InfoWatch looks forward to being able to share with their partners and clients the clearer picture of data leakage across Europe that the proposed EU directive will stimulate.<\/p>\n","protected":false},"excerpt":{"rendered":"<p><b>Key conclusions<\/b><br \/>\n&#8211; Europe\u2019s IT professionals overwhelmingly indicate (78%) that data theft represents the primary information security threat \u2013 more significant than either viruses or hacker infiltration<br \/>\n&#8211; Of all possible results of compromised information security, the threat of leakage of confidential information is keeping more members of the IT department (93%) awake at night than any other<br \/>\n&#8211; Europe\u2019s primary data leakage channels are identified as portable storage devices, e-mail, and Internet-based channels such as web-mail and forums<br \/>\n&#8211; Only 11% of those surveyed were confident their company\u2019s information security had not been breached over the last year \u2013 a figure which closely mirrors the number of companies with anti-leakage solutions in place \u2013 with 42% admitting to between 1-5 breaches and 37% unable to say with certainty that that no breach had occurred<br \/>\n&#8211; The lack of industry standards is highlighted as the primary obstacle (42%) to wider implementation of anti-leakage technologies<br \/>\n&#8211; Perceived solutions include the deployment of comprehensive anti-leakage software, the implementation of appropriate organizational measures \u2013 such as clear and consistent internal security policies \u2013 controls on external network access, and raising staff awareness and discipline through training.<\/p>\n<p>http:\/\/www.viruslist.com\/en\/analysis?pubid=204791935<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32],"tags":[],"class_list":["post-1912","post","type-post","status-publish","format-standard","hentry","category-statistics"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1912","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=1912"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1912\/revisions"}],"predecessor-version":[{"id":4399,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1912\/revisions\/4399"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1912"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1912"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}