<?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: Help with creating a report and alert for Cryptolocker (or bulk file modification) in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221127#M4056</link>
    <description>&lt;P&gt;What if you run that search you've got every hour and then if the count is greater than X  it would register.   So in your case you used:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  where count&amp;gt;20
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So if 100/hour is your threshold then run this every hour looking at last 60m where count greater than 100.  Have it trigger alerts or feed into a summary index.  &lt;/P&gt;

&lt;P&gt;You could also get into stats like standard deviation etc. Lots of options.  Standard deviation is probably your best bet because the user will be normaly writing 5/hr then jump to 50000/min or something.&lt;/P&gt;

&lt;P&gt;Yeah check out the stats and eval commands.  They will be your friends for this.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jan 2016 01:54:44 GMT</pubDate>
    <dc:creator>jkat54</dc:creator>
    <dc:date>2016-01-15T01:54:44Z</dc:date>
    <item>
      <title>Help with creating a report and alert for Cryptolocker (or bulk file modification)</title>
      <link>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221124#M4053</link>
      <description>&lt;P&gt;Hi guys&lt;/P&gt;

&lt;P&gt;We were hit with Cryptolocker about 5 months ago, and since then, we have gone through a bit of an overhaul of our security infrastructure and processes. Included in this was installing and configuring Splunk to help with log file collection and reporting.&lt;BR /&gt;
One thing I would like to do it create a report and alert based on basically what Crypto does - bulk file changes - as I know from experience that it will attack as many files on as many shares as it can find as quickly as possible.&lt;/P&gt;

&lt;P&gt;Being a noob to Splunk, I was wondering if anyone has anything useful I could use as a basis for building this into our Splunk alerting and reporting? At the moment, I only have a basic search created, purely for testing as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;"EventCode=4663" WriteData | top limit=20 Account_Name | where count&amp;gt;20
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any help would be appreciated and help me learn a bit more.&lt;BR /&gt;
cheers,&lt;BR /&gt;
Brett&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jan 2016 01:49:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221124#M4053</guid>
      <dc:creator>bretmorr</dc:creator>
      <dc:date>2016-01-08T01:49:45Z</dc:date>
    </item>
    <item>
      <title>Re: Help with creating a report and alert for Cryptolocker (or bulk file modification)</title>
      <link>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221125#M4054</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I've not made a detection mechanism for CryptoLocker in Splunk myself, but I've looked into the issue on one occasion earlier. What I found was that you can (on Windows machines) activate something called &lt;EM&gt;file auditing&lt;/EM&gt;, which track changes on files. If you forward the logs from file auditing to Splunk you could make an alarm that triggers if there are e.g. more that &lt;EM&gt;x&lt;/EM&gt; file changes over &lt;EM&gt;y&lt;/EM&gt; minutes. Have a look at (1) the blog from Hacker Hurricane for more information about Splunk and CryptoLocker, and see (2) the blog from Splunk for information on file auditing in Windows.&lt;/P&gt;

&lt;P&gt;(1) &lt;A href="http://hackerhurricane.blogspot.no/2014/01/how-to-detect-cryptolocker-type-attack.html"&gt;http://hackerhurricane.blogspot.no/2014/01/how-to-detect-cryptolocker-type-attack.html&lt;/A&gt;&lt;BR /&gt;
(2) &lt;A href="http://blogs.splunk.com/2013/07/08/audit-file-access-and-change-in-windows/"&gt;http://blogs.splunk.com/2013/07/08/audit-file-access-and-change-in-windows/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jan 2016 07:50:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221125#M4054</guid>
      <dc:creator>hettervik</dc:creator>
      <dc:date>2016-01-08T07:50:53Z</dc:date>
    </item>
    <item>
      <title>Re: Help with creating a report and alert for Cryptolocker (or bulk file modification)</title>
      <link>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221126#M4055</link>
      <description>&lt;P&gt;Thanks for the information. The current alert seems to be working I just need to tune to avoid too many false positives.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2016 00:15:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221126#M4055</guid>
      <dc:creator>bretmorr</dc:creator>
      <dc:date>2016-01-15T00:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: Help with creating a report and alert for Cryptolocker (or bulk file modification)</title>
      <link>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221127#M4056</link>
      <description>&lt;P&gt;What if you run that search you've got every hour and then if the count is greater than X  it would register.   So in your case you used:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  where count&amp;gt;20
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So if 100/hour is your threshold then run this every hour looking at last 60m where count greater than 100.  Have it trigger alerts or feed into a summary index.  &lt;/P&gt;

&lt;P&gt;You could also get into stats like standard deviation etc. Lots of options.  Standard deviation is probably your best bet because the user will be normaly writing 5/hr then jump to 50000/min or something.&lt;/P&gt;

&lt;P&gt;Yeah check out the stats and eval commands.  They will be your friends for this.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2016 01:54:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Help-with-creating-a-report-and-alert-for-Cryptolocker-or-bulk/m-p/221127#M4056</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-01-15T01:54:44Z</dc:date>
    </item>
  </channel>
</rss>

