{"id":1914,"date":"2007-04-26T00:00:00","date_gmt":"2007-04-26T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/04\/26\/companies-say-security-breach-could-destroy-their-business\/"},"modified":"2021-12-30T11:40:17","modified_gmt":"2021-12-30T11:40:17","slug":"companies-say-security-breach-could-destroy-their-business","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/04\/26\/companies-say-security-breach-could-destroy-their-business\/","title":{"rendered":"Companies Say Security Breach Could Destroy Their Business"},"content":{"rendered":"<p>One-third of companies said in a recent poll that a major security breach could put their company out of business, according to a report from McAfee.  The security company unveiled a study Tuesday showing that 33% of respondents said they believe a major data-loss incident involving accidental or malicious distribution of confidential data could put them out of business. To protect customers, employees, and shareholders, data loss prevention needs to become a top priority at every level of the organization, from the board room to the lunch room.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>23% said they were able to estimate the total annual cost of data leakage, putting the figure at $1.82 million.<\/p>\n<p>Just last week, the U.S. Department of Agriculture announced that it had exposed the personal identifying information on about 150,000 people over the last 26 years.  The agency admitted inadvertently exposing online sensitive information, such as names and Social Security numbers, in a publicly available database, which had existed since 1981.<\/p>\n<p>People are getting fed up with their personal information leaking out into areas where it could be scooped up by criminals working online.  A report came out earlier this month from Javelin Strategy &#038; Research showing that 77% of 2,750 consumers polled said they would stop shopping at stores that suffer data breaches.<\/p>\n<p>http:\/\/www.informationweek.com\/news\/showArticle.jhtml?articleID=199201085<\/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-1914","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\/1914","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=1914"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1914\/revisions"}],"predecessor-version":[{"id":4401,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1914\/revisions\/4401"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1914"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1914"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1914"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}