<?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: Successfull brute force loggings in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369454#M92940</link>
    <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 09 May 2017 15:53:05 GMT</pubDate>
    <dc:creator>alemarzu</dc:creator>
    <dc:date>2017-05-09T15:53:05Z</dc:date>
    <item>
      <title>Successfull brute force loggings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369451#M92937</link>
      <description>&lt;P&gt;I am looking for successfull brute force logins&lt;BR /&gt;
basically I am looking for 5 failed logings followed by 1 successfull login&lt;BR /&gt;
I found the below search and it seems to be working, but it's just counting the fails and success,&lt;BR /&gt;
there is no time sequence&lt;BR /&gt;
it isnt looking for the first 5 failed loggings, it counts all the failed and succeefull logings&lt;BR /&gt;
and then makes a count,&lt;BR /&gt;
how can I add the time awareness (5 failed loggings followed by 1 successfull within 5 or 10 min)?&lt;/P&gt;

&lt;P&gt;action= failed or success (login) &lt;BR /&gt;
user= userid's&lt;BR /&gt;
    index=* | bucket _time span=30m | stats list(action) as Attempts, count(eval(match(action,"failure"))) as Failed, count(eval(match(action,"success"))) as Success by user | where mvcount(Attempts)&amp;gt;=6 AND Success=1 AND Failed&amp;gt;=5&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 11:52:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369451#M92937</guid>
      <dc:creator>ecanmaster</dc:creator>
      <dc:date>2017-05-09T11:52:25Z</dc:date>
    </item>
    <item>
      <title>Re: Successfull brute force loggings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369452#M92938</link>
      <description>&lt;P&gt;Hi there @ecanmaster&lt;/P&gt;

&lt;P&gt;Perhaps something like this might help you.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;earliest=-11min@min latest=-1min@min your_main_search_here action="success"
 | stats count, latest(_time) AS lastLogin by user
 | eval timewindow=lastLogin - 600 
 | map maxsearches=100 search="your_main_search_here action="failure" earliest=$timewindow$ latest=$lastLogin$ user=$user$"
 | stats count, latest(_time) AS "Latest Attempt" by user 
 | convert ctime("Latest Attempt") 
 | rename user AS "Compromised Account", count AS "loginAttempts"
 | where loginAttempts &amp;gt; 4
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should search successful user logins in a 10 min window and if it finds one it goes back in time 10 min to find failed attempts in the last 10 minutes for each user/success login.&lt;/P&gt;

&lt;P&gt;Could't tested it, hope it helps.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;EDIT:&lt;/STRONG&gt; Fixed. Thank you @DalJeanis&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 14:51:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369452#M92938</guid>
      <dc:creator>alemarzu</dc:creator>
      <dc:date>2017-05-09T14:51:46Z</dc:date>
    </item>
    <item>
      <title>Re: Successfull brute force loggings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369453#M92939</link>
      <description>&lt;P&gt;@alemarzu - looks good with one fix and one improvement...&lt;/P&gt;

&lt;P&gt;1)  &lt;CODE&gt;latest=-11m@m earliest=-1m@m&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;2) No need to kill the field &lt;CODE&gt;count&lt;/CODE&gt;; it gets thrown away at the next command ( &lt;CODE&gt;map&lt;/CODE&gt; ) anyway.&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 15:30:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369453#M92939</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-05-09T15:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Successfull brute force loggings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369454#M92940</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 15:53:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369454#M92940</guid>
      <dc:creator>alemarzu</dc:creator>
      <dc:date>2017-05-09T15:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: Successfull brute force loggings</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369455#M92941</link>
      <description>&lt;P&gt;hmm,so for each successful login we go and execute?&lt;BR /&gt;
isn’t more normal to search only when I see a fail, which are not so often as successful logins?&lt;BR /&gt;
thanks&lt;/P&gt;</description>
      <pubDate>Sat, 23 Feb 2019 20:09:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Successfull-brute-force-loggings/m-p/369455#M92941</guid>
      <dc:creator>printul77700</dc:creator>
      <dc:date>2019-02-23T20:09:33Z</dc:date>
    </item>
  </channel>
</rss>

