<?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 Compliance Essentials for Splunk in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Compliance-Essentials-for-Splunk/m-p/681226#M11388</link>
    <description>&lt;P&gt;I was with the NAVSEA team at SKO and they said that if I provided the Canadian compliance requirements you could ad these to the Compliance essentials ap, like you have done for the US and Australia.&lt;/P&gt;&lt;P&gt;Here is what I received from my customer Marine Atlantic:&lt;/P&gt;&lt;DIV&gt;For compliance: we deal with IMO, SOLAS Chapter 9, sometimes referred to as ISM code. This is for existing vessels.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The new vessel is DNV SP1 (Security Profile 1 or Cyber Secure Essential) compliant (some SP3 systems). You may note, SP0 is IMO...&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;We also use ITSG-33 internally which is the Canadian version of NIST 800.53 (but not maintained as well - NIST has added some cloud based controls for example).&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does the Splunk Compliance Ap cover these requirements??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please let me know&lt;/P&gt;&lt;P&gt;thank Alli. RSM PBST Canada.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Mar 2024 18:20:24 GMT</pubDate>
    <dc:creator>acambridge</dc:creator>
    <dc:date>2024-03-19T18:20:24Z</dc:date>
    <item>
      <title>Compliance Essentials for Splunk</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Compliance-Essentials-for-Splunk/m-p/681226#M11388</link>
      <description>&lt;P&gt;I was with the NAVSEA team at SKO and they said that if I provided the Canadian compliance requirements you could ad these to the Compliance essentials ap, like you have done for the US and Australia.&lt;/P&gt;&lt;P&gt;Here is what I received from my customer Marine Atlantic:&lt;/P&gt;&lt;DIV&gt;For compliance: we deal with IMO, SOLAS Chapter 9, sometimes referred to as ISM code. This is for existing vessels.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The new vessel is DNV SP1 (Security Profile 1 or Cyber Secure Essential) compliant (some SP3 systems). You may note, SP0 is IMO...&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;We also use ITSG-33 internally which is the Canadian version of NIST 800.53 (but not maintained as well - NIST has added some cloud based controls for example).&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does the Splunk Compliance Ap cover these requirements??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please let me know&lt;/P&gt;&lt;P&gt;thank Alli. RSM PBST Canada.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 18:20:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Compliance-Essentials-for-Splunk/m-p/681226#M11388</guid>
      <dc:creator>acambridge</dc:creator>
      <dc:date>2024-03-19T18:20:24Z</dc:date>
    </item>
  </channel>
</rss>

