{"id":706,"date":"2005-10-03T00:00:00","date_gmt":"2005-10-03T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/10\/03\/compliance-whats-that\/"},"modified":"2021-12-30T11:38:00","modified_gmt":"2021-12-30T11:38:00","slug":"compliance-whats-that","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/10\/03\/compliance-whats-that\/","title":{"rendered":"Compliance? What\u2019s That?"},"content":{"rendered":"<p>The majority of information security executives range from ambivalent (at best) to downright dismissive (at worst) about the intentions, effect and pertinence of security regulations.<br \/>\nIs it the comparatively low number of respondents who are in compliance?  Or the shockingly high number of respondents who cop to not complying even though they know that they have to?  Just 11 percent of respondents said they needed to be in compliance with California&#8217;s SB 1386 law, which mandates that companies report breaches of personal data to consumers.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Here are two theories, both of which probably play some role: One, the regs are confusing and difficult to comply with.<\/p>\n<p>Companies don&#8217;t fear any serious repercussions for not complying with the regulations, either because the mandates are too vague to really be enforced, or the regulatory agencies aren&#8217;t devoting resources to enforcement.<\/p>\n<p>Supporting the &#8220;lack of teeth&#8221; theory is the fact that only a third of respondents reported having compliance testing in place, and only a quarter link their security organization to the compliance group.<\/p>\n<p>Lobel offers a third factor: &#8220;There&#8217;s just a lot of regs for these guys to deal with.&#8221;<\/p>\n<p>http:\/\/www.csoonline.com\/read\/100105\/survey_compliance.html<\/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-706","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\/706","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=706"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/706\/revisions"}],"predecessor-version":[{"id":3193,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/706\/revisions\/3193"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=706"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=706"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}