<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Rationalizing existing compliance controls to meet GDPR obligations in Privacy</title>
    <link>https://community.isc2.org/t5/Privacy/Rationalizing-existing-compliance-controls-to-meet-GDPR/m-p/7818#M351</link>
    <description>&lt;P&gt;I wrote a short blog post on rationalizing existing compliance controls like the PCI DSS and NIST regulations to meet GDPR obligations. Thinking of expanding the post and adding a compliance control matrix to include other standards like ISO and HITRUST.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestions for that matrix or feedback on the post would be appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://tokenex.com/utilizing-the-pci-dss-and-nist-regulations-to-prepare-for-the-gdpr/" target="_blank"&gt;https://tokenex.com/utilizing-the-pci-dss-and-nist-regulations-to-prepare-for-the-gdpr/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;John Noltensmeyer&lt;/STRONG&gt;, CIPP/E, CIPM, CISSP, ISA&lt;/P&gt;&lt;P&gt;Privacy and Compliance Solutions Architect&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:jnoltensmeyer@tokenex.com" target="_blank"&gt;jnoltensmeyer@tokenex.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Phone: (202) 431-9829&lt;/P&gt;</description>
    <pubDate>Mon, 26 Feb 2018 14:53:10 GMT</pubDate>
    <dc:creator>JNoltensmeyer</dc:creator>
    <dc:date>2018-02-26T14:53:10Z</dc:date>
    <item>
      <title>Rationalizing existing compliance controls to meet GDPR obligations</title>
      <link>https://community.isc2.org/t5/Privacy/Rationalizing-existing-compliance-controls-to-meet-GDPR/m-p/7818#M351</link>
      <description>&lt;P&gt;I wrote a short blog post on rationalizing existing compliance controls like the PCI DSS and NIST regulations to meet GDPR obligations. Thinking of expanding the post and adding a compliance control matrix to include other standards like ISO and HITRUST.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestions for that matrix or feedback on the post would be appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://tokenex.com/utilizing-the-pci-dss-and-nist-regulations-to-prepare-for-the-gdpr/" target="_blank"&gt;https://tokenex.com/utilizing-the-pci-dss-and-nist-regulations-to-prepare-for-the-gdpr/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;John Noltensmeyer&lt;/STRONG&gt;, CIPP/E, CIPM, CISSP, ISA&lt;/P&gt;&lt;P&gt;Privacy and Compliance Solutions Architect&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:jnoltensmeyer@tokenex.com" target="_blank"&gt;jnoltensmeyer@tokenex.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Phone: (202) 431-9829&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2018 14:53:10 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Privacy/Rationalizing-existing-compliance-controls-to-meet-GDPR/m-p/7818#M351</guid>
      <dc:creator>JNoltensmeyer</dc:creator>
      <dc:date>2018-02-26T14:53:10Z</dc:date>
    </item>
  </channel>
</rss>

