{"id":174,"date":"2007-05-19T00:00:00","date_gmt":"2007-05-19T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/05\/19\/iso-2700-security-sleeper\/"},"modified":"2021-12-30T11:36:39","modified_gmt":"2021-12-30T11:36:39","slug":"iso-2700-security-sleeper","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/05\/19\/iso-2700-security-sleeper\/","title":{"rendered":"ISO 2700&#8211;Security Sleeper"},"content":{"rendered":"<p>Let&#8217;s face it, the ISO security standards&#8211;first ISO 17799, which I covered in detail back in March of 2003, and now ISO 27001 and 27002, which are replacing it&#8211;are real yawners.  Would you really have eaten your peas at age 4 if your mama didn&#8217;t make you?  Funny thing is, despite the fact that they are boring but good for you, the ISO standards may now be turning into the sleeper hits of the season.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since the author&#8217;s cover story on PCI compliance ran last month, he has heard from a couple CISOs who maintain that PCI compliance was a cinch&#8211;because they already followed ISO 17799 or 2700.  &#8220;This gave us the opportunity to easily adapt to other security standards such as PCI and others without much effort.&#8221;<\/p>\n<p>You should be concerned about the maturity of a security practice at companies who take 2+ years to receive PCI certification.  I don&#8217;t want my credit card in the hands of those companies&#8230;.<\/p>\n<p>Then, this morning, the author had a talk with Patrick A. C\u00f4t\u00e9, information security officer of Houghton Mifflin, the venerable textbook publisher.  He said, in not quite so many words, the same thing&#8211;that their PCI compliance was fairly painless because they already had the underlying processes in place.<\/p>\n<p>http:\/\/blogs.csoonline.com\/iso_2700_securitys_sleeper<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-174","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/174","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=174"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/174\/revisions"}],"predecessor-version":[{"id":2661,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/174\/revisions\/2661"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=174"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}