<?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: What command is used for trying to identify anomaly logons from common users? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455410#M128767</link>
    <description>&lt;P&gt;one idea for detecting a spike or outlier in logons would be to summarize, by user, how often they login.. say # of times a week or day.. you could try for hour but you'll likely get a lot of noise..&lt;/P&gt;

&lt;P&gt;start with something like &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;'index=&amp;lt;security&amp;gt; sourcetype=&amp;lt;logins&amp;gt; |bin span=1d _time | stats count by &amp;lt;user&amp;gt; _time'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then summary index this data over a recurring period to be able to detect outliers. - try the &lt;CODE&gt;|collect&lt;/CODE&gt; command&lt;/P&gt;

&lt;P&gt;Now apply the standard deviation method of detecting outliers - essentially check if the sample is some standard devs from the mean. &lt;BR /&gt;
The MLTK toolkit has some fun features for this, some math behind it is:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;mean logins by user&lt;/LI&gt;
&lt;LI&gt;calculate standard deviation&lt;/LI&gt;
&lt;LI&gt;test for : (logins &amp;lt; (mean + 2 standard deviations) )&lt;/LI&gt;
&lt;LI&gt;if true - this is technically an outlier. you can adjust your standard deviation to experiment&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Then schedule this search to run over a time period and create an alert if there are results.. or to send you a report &lt;/P&gt;

&lt;P&gt;I would check out the MLTK though, lots of great stuff in there.. Security Essentials has a user case for this as well&lt;/P&gt;</description>
    <pubDate>Fri, 17 Jan 2020 02:49:31 GMT</pubDate>
    <dc:creator>aokur_splunk</dc:creator>
    <dc:date>2020-01-17T02:49:31Z</dc:date>
    <item>
      <title>What command is used for trying to identify anomaly logons from common users?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455407#M128764</link>
      <description>&lt;P&gt;Is there a website on Splunk docs that describe interesting fields and what each field is about? &lt;/P&gt;

&lt;P&gt;What command can I use for Splunk with trying to identify anomaly logons from common users and to be able to point out a spike in logons from one user?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2019 13:30:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455407#M128764</guid>
      <dc:creator>keldridg2</dc:creator>
      <dc:date>2019-08-16T13:30:25Z</dc:date>
    </item>
    <item>
      <title>Re: What command is used for trying to identify anomaly logons from common users?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455408#M128765</link>
      <description>&lt;P&gt;Selected fields, are the standard _time, host, sourcetype, and  any fields you specified in your search &lt;/P&gt;

&lt;P&gt;Interesting fields, are the other fields extracted from the events returned by your search. &lt;/P&gt;

&lt;P&gt;The information on the fields extracted from the events, if available, would be found in the documentation of the add-on use to extract the fields.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2019 14:50:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455408#M128765</guid>
      <dc:creator>solarboyz1</dc:creator>
      <dc:date>2019-08-16T14:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: What command is used for trying to identify anomaly logons from common users?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455409#M128766</link>
      <description>&lt;P&gt;Thank you for helping me on my issue.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2019 14:57:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455409#M128766</guid>
      <dc:creator>keldridg2</dc:creator>
      <dc:date>2019-08-16T14:57:25Z</dc:date>
    </item>
    <item>
      <title>Re: What command is used for trying to identify anomaly logons from common users?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455410#M128767</link>
      <description>&lt;P&gt;one idea for detecting a spike or outlier in logons would be to summarize, by user, how often they login.. say # of times a week or day.. you could try for hour but you'll likely get a lot of noise..&lt;/P&gt;

&lt;P&gt;start with something like &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;'index=&amp;lt;security&amp;gt; sourcetype=&amp;lt;logins&amp;gt; |bin span=1d _time | stats count by &amp;lt;user&amp;gt; _time'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then summary index this data over a recurring period to be able to detect outliers. - try the &lt;CODE&gt;|collect&lt;/CODE&gt; command&lt;/P&gt;

&lt;P&gt;Now apply the standard deviation method of detecting outliers - essentially check if the sample is some standard devs from the mean. &lt;BR /&gt;
The MLTK toolkit has some fun features for this, some math behind it is:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;mean logins by user&lt;/LI&gt;
&lt;LI&gt;calculate standard deviation&lt;/LI&gt;
&lt;LI&gt;test for : (logins &amp;lt; (mean + 2 standard deviations) )&lt;/LI&gt;
&lt;LI&gt;if true - this is technically an outlier. you can adjust your standard deviation to experiment&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Then schedule this search to run over a time period and create an alert if there are results.. or to send you a report &lt;/P&gt;

&lt;P&gt;I would check out the MLTK though, lots of great stuff in there.. Security Essentials has a user case for this as well&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2020 02:49:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-command-is-used-for-trying-to-identify-anomaly-logons-from/m-p/455410#M128767</guid>
      <dc:creator>aokur_splunk</dc:creator>
      <dc:date>2020-01-17T02:49:31Z</dc:date>
    </item>
  </channel>
</rss>

