<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Security Matters</title>
      <link>http://www.ebizq.net/blogs/securitymatters/</link>
      <description>This blog will cover information security and regulatory compliance issues that organizations are facing today; news, analysis, discussion, musings and other interesting bits will be featured.</description>
      <language>en</language>
      <copyright>Copyright 2011</copyright>
      <lastBuildDate>Thu, 29 Jan 2009 17:50:53 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=4.21-en</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

      
      <item>
         <title>Titanic Compliance</title>
         <description>I saw this posted on another blog and I just love this: &quot; ... the problem here was that the &quot;Titanic&quot; indeed did meet all of the safety requirements of the time. And that a big part of the problem...</description>
         <link>http://www.ebizq.net/blogs/securitymatters/2009/01/titanic_compliance.php</link>
         <guid>http://www.ebizq.net/blogs/securitymatters/2009/01/titanic_compliance.php</guid>
         <category></category>
         <pubDate>Thu, 29 Jan 2009 17:50:53 -0500</pubDate>
          <author>chuvakin</author>
      </item>
      
      <item>
         <title>On Security and Compliance</title>
         <description>Welcome to my new readers! In this blog I will cover the issues of information security, infosec-related and IT-related regulatory compliance issues (the usual suspects: PCI DSS, HIPAA, SOX, GLBA, ISO, ITIL, etc) as well as related news, events, trends....</description>
         <link>http://www.ebizq.net/blogs/securitymatters/2009/01/on_security_and_compliance.php</link>
         <guid>http://www.ebizq.net/blogs/securitymatters/2009/01/on_security_and_compliance.php</guid>
         <category>Compliance</category>
         <pubDate>Wed, 21 Jan 2009 23:57:25 -0500</pubDate>
          <author>chuvakin</author>
      </item>
      
   </channel>
</rss>


