<?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 What are Splunk SOC rules? in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/What-are-Splunk-SOC-rules/m-p/603902#M13988</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;Please help me with the splunk alerts for below scenario&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Vijay Sri S&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jun 2022 13:35:57 GMT</pubDate>
    <dc:creator>VijaySrrie</dc:creator>
    <dc:date>2022-06-30T13:35:57Z</dc:date>
    <item>
      <title>What are Splunk SOC rules?</title>
      <link>https://community.splunk.com/t5/Alerting/What-are-Splunk-SOC-rules/m-p/603902#M13988</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;Please help me with the splunk alerts for below scenario&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Vijay Sri S&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 13:35:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/What-are-Splunk-SOC-rules/m-p/603902#M13988</guid>
      <dc:creator>VijaySrrie</dc:creator>
      <dc:date>2022-06-30T13:35:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk SOC rules</title>
      <link>https://community.splunk.com/t5/Alerting/What-are-Splunk-SOC-rules/m-p/603904#M13989</link>
      <description>&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;TABLE width="360"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;Criminals gain access to the platform and install Ransomware that disrupts platform&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;An employee deliberately or accidentally misusing their access to PII records&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;Denial of service attack by criminals or state-sponsored actors flooding cloud resources, causing platform to become unavailable and inaccessible.&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;Supply chain security is compromised and Ovo loses access to services it is provided&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;Ineffective controls on endpoint devices, enabling unauthorised access by criminals or state-sponsored actors&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;Criminals gain access to underlying cloud infrastructure and steal PII data&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;Criminals gain access to exposed APIs and steal PII data&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN&gt;Users could escalate privileges and/or move laterally in the platform to see data they shouldn't&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Thu, 30 Jun 2022 08:31:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/What-are-Splunk-SOC-rules/m-p/603904#M13989</guid>
      <dc:creator>VijaySrrie</dc:creator>
      <dc:date>2022-06-30T08:31:54Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk SOC rules</title>
      <link>https://community.splunk.com/t5/Alerting/What-are-Splunk-SOC-rules/m-p/603916#M13990</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/164779"&gt;@VijaySrrie&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can take reference from these:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://research.splunk.com/detections/" target="_blank"&gt;https://research.splunk.com/detections/&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://splunkbase.splunk.com/app/3449/" target="_blank"&gt;https://splunkbase.splunk.com/app/3449/&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.splunk.com/Documentation/ESSOC" target="_blank"&gt;https://docs.splunk.com/Documentation/ESSOC&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Actually, this is not the list of scenarios, actually to achieve one of the items you listed here you may require to implement many alerts.&lt;/P&gt;&lt;P&gt;For example,&amp;nbsp; to implement the "Criminals gain access to the platform and install Ransomware that disrupts platform" scenario, there are many sample searches already provided here -&amp;nbsp;&lt;A href="https://research.splunk.com/stories/ransomware/" target="_blank"&gt;https://research.splunk.com/stories/ransomware/&lt;/A&gt;&amp;nbsp;And you can make countless more.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, I'm happy to hear from others who have better security experience than me to find out if there is a quicker way to go about this.&lt;span class="lia-unicode-emoji" title=":thinking_face:"&gt;🤔&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I hope this helps!!!&amp;nbsp;&lt;/P&gt;&lt;P&gt;SOC is not installation but rather a journey.!!!!&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 09:28:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/What-are-Splunk-SOC-rules/m-p/603916#M13990</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2022-06-30T09:28:13Z</dc:date>
    </item>
  </channel>
</rss>

