{"id":1929,"date":"2007-12-02T00:00:00","date_gmt":"2007-12-02T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/12\/02\/security-breach-costs-jump-30\/"},"modified":"2021-12-30T11:40:18","modified_gmt":"2021-12-30T11:40:18","slug":"security-breach-costs-jump-30","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/12\/02\/security-breach-costs-jump-30\/","title":{"rendered":"Security Breach Costs Jump 30%"},"content":{"rendered":"<p>The cost of recovering from a single data breach now averages $6.3 million-that&#8217;s up 31 percent since 2006 and nearly 90 percent since 2005, according to the Ponemon Institute, which studies privacy and information management.  Two-thirds of that cost is spent recovering business that&#8217;s lost after a breach, a cost that has risen 30 percent since last year. More customers stop doing business with a company after their information is exposed, and it&#8217;s getting more expensive to replace them.  They spent an average of $197 per lost record investigating the breach, notifying customers, restoring security infrastructures and recovering lost business.  Breaches by third parties-outsourcers or members of a company&#8217;s supply chain-were the second biggest cause of security compromises and are more expensive.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Notification costs were down 40 percent, to $15 per customer, suggesting that companies are learning from each other, Dasher says.<\/p>\n<p>Dasher says when PGP sells its software, which encrypts data, more people inside a company are now involved in purchasing it.<\/p>\n<p>This is Ponemon&#8217;s third survey of data breach costs since 2005.<\/p>\n<p>http:\/\/www.baselinemag.com\/article2\/0,1540,2223732,00.asp<\/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-1929","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\/1929","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=1929"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1929\/revisions"}],"predecessor-version":[{"id":4416,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1929\/revisions\/4416"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1929"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1929"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1929"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}