<?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 Re: Correlation search - Stream events in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Correlation-search-Stream-events/m-p/437873#M5817</link>
    <description>&lt;P&gt;You can directly use your search and convert to co-relation search.  The below will create a notable only when Total MB is greater than 100. You can change as per your need. You can create using guided mode or directly add the search in the cor.search [ &lt;A href="https://docs.splunk.com/Documentation/ES/5.3.0/Tutorials/GuidedCorrelationSearch"&gt;https://docs.splunk.com/Documentation/ES/5.3.0/Tutorials/GuidedCorrelationSearch&lt;/A&gt;]. You can then setup throttling to not alert for same host or port etc. for next 1 day or so.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=stream_netflow sourcetype="stream:netflow" dest_port=69 OR dest_port=20 OR dest_port=21
| eval totalbytes=(bytes_out)
| eval total_mb=(totalbytes/1024/1024)
| eval total_mb=round(total_mb,2)
| stats sum(total_mb) as "Total MB", count(_raw) as "Event Count" by src_ip, src_port, dest_ip, dest_port 
| where  "Total MB" &amp;gt; 100
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Fri, 03 May 2019 15:39:13 GMT</pubDate>
    <dc:creator>lakshman239</dc:creator>
    <dc:date>2019-05-03T15:39:13Z</dc:date>
    <item>
      <title>Correlation search - Stream events</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Correlation-search-Stream-events/m-p/437872#M5816</link>
      <description>&lt;P&gt;I'll start with the goal of what I am trying to accomplish first. I'd like to be able to detect any source sending data out in the middle of the night (example 11 PM to 6 AM) by means of FTP ( Ports 20,21,69) with a specific amount of data ( x mbs or y bytes ) using our Stream data. I'm not really sure how to build a correlation search to accomplish that but in that, I have a search I've built for a dashboard to attempt to track this which I'll copy below but more so looking to be able to use Enterprise Security to accomplish it. &lt;/P&gt;

&lt;P&gt;index=stream_netflow sourcetype="stream:netflow" dest_port=69 OR dest_port=20 OR dest_port=21&lt;BR /&gt;
| eval totalbytes=(bytes_out)&lt;BR /&gt;
| eval total_mb=(totalbytes/1024/1024)&lt;BR /&gt;
| eval total_mb=round(total_mb,2)&lt;BR /&gt;
| stats sum(total_mb) as "Total MB", count(_raw) as "Event Count" by src_ip, src_port, dest_ip, dest_port &lt;BR /&gt;
| sort -"Total MB" limit=15&lt;/P&gt;

&lt;P&gt;Any help or ideas would be greatly appreciated! &lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:20:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Correlation-search-Stream-events/m-p/437872#M5816</guid>
      <dc:creator>Crashfry</dc:creator>
      <dc:date>2020-09-30T00:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: Correlation search - Stream events</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Correlation-search-Stream-events/m-p/437873#M5817</link>
      <description>&lt;P&gt;You can directly use your search and convert to co-relation search.  The below will create a notable only when Total MB is greater than 100. You can change as per your need. You can create using guided mode or directly add the search in the cor.search [ &lt;A href="https://docs.splunk.com/Documentation/ES/5.3.0/Tutorials/GuidedCorrelationSearch"&gt;https://docs.splunk.com/Documentation/ES/5.3.0/Tutorials/GuidedCorrelationSearch&lt;/A&gt;]. You can then setup throttling to not alert for same host or port etc. for next 1 day or so.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=stream_netflow sourcetype="stream:netflow" dest_port=69 OR dest_port=20 OR dest_port=21
| eval totalbytes=(bytes_out)
| eval total_mb=(totalbytes/1024/1024)
| eval total_mb=round(total_mb,2)
| stats sum(total_mb) as "Total MB", count(_raw) as "Event Count" by src_ip, src_port, dest_ip, dest_port 
| where  "Total MB" &amp;gt; 100
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 03 May 2019 15:39:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Correlation-search-Stream-events/m-p/437873#M5817</guid>
      <dc:creator>lakshman239</dc:creator>
      <dc:date>2019-05-03T15:39:13Z</dc:date>
    </item>
    <item>
      <title>Re: Correlation search - Stream events</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Correlation-search-Stream-events/m-p/437874#M5818</link>
      <description>&lt;P&gt;Just had to rearrange the search to make it work - the where clause had to be above the stats clause. Now it works - thanks for the help. &lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2019 16:48:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Correlation-search-Stream-events/m-p/437874#M5818</guid>
      <dc:creator>Crashfry</dc:creator>
      <dc:date>2019-05-06T16:48:23Z</dc:date>
    </item>
  </channel>
</rss>

