<?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: Total Account lockouts &amp;gt; 2  within 30mins in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476615#M192647</link>
    <description>&lt;P&gt;Hi siddh01r,&lt;BR /&gt;
if you need to create an alert, you can use your search putting as time period:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;earliest=-30m latest=now
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and schedule this alert every 30 minutes.&lt;/P&gt;

&lt;P&gt;if you want to create a panel, you could use timechart command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;description="Account Lockouts" EventCode=4740 user="*" host=primarydc
| eval col=user." ".host
| timechart span=30m count as total by col
| where total &amp;gt; 2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;P.S.: use always index in your searches, it's faster.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2019 11:17:13 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2019-09-13T11:17:13Z</dc:date>
    <item>
      <title>Total Account lockouts &gt; 2  within 30mins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476614#M192646</link>
      <description>&lt;P&gt;Hi There,&lt;/P&gt;

&lt;P&gt;I am trying to find where total account lockouts that are greater than 2 within the time frame of 30 mins. &lt;BR /&gt;
This is to find out potential malicious activity where someone is trying to possibility crack a password for an account. &lt;BR /&gt;
our lockout threshold is 15 mins and it gets unlocked. This way I can see if someone possibly has tried to log into an account more than 2 times and locked an account in 30 mins. &lt;/P&gt;

&lt;P&gt;Here is my query which gives me total results &amp;gt;2, but i am not sure how to specify the timeframe of 30 mins in the query.&lt;BR /&gt;
Any help would be appreciated.&lt;/P&gt;

&lt;P&gt;description="Account Lockouts" EventCode=4740 user="*" host=primarydc&lt;BR /&gt;
| stats count as total by user, host&lt;BR /&gt;
| where total &amp;gt; 2&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2019 04:40:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476614#M192646</guid>
      <dc:creator>siddh01r</dc:creator>
      <dc:date>2019-09-13T04:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: Total Account lockouts &gt; 2  within 30mins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476615#M192647</link>
      <description>&lt;P&gt;Hi siddh01r,&lt;BR /&gt;
if you need to create an alert, you can use your search putting as time period:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;earliest=-30m latest=now
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and schedule this alert every 30 minutes.&lt;/P&gt;

&lt;P&gt;if you want to create a panel, you could use timechart command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;description="Account Lockouts" EventCode=4740 user="*" host=primarydc
| eval col=user." ".host
| timechart span=30m count as total by col
| where total &amp;gt; 2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;P.S.: use always index in your searches, it's faster.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2019 11:17:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476615#M192647</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-09-13T11:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: Total Account lockouts &gt; 2  within 30mins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476616#M192648</link>
      <description>&lt;P&gt;Thank you so much Guiseppe. Great help.&lt;BR /&gt;
Question - what is the below used for, can you please give me some context?&lt;/P&gt;

&lt;P&gt;| eval col=user." ".host&lt;/P&gt;

&lt;P&gt;also,&lt;BR /&gt;
When I use that query, I see that there are events but I get no statistical table with results i.e "0 statistics".&lt;/P&gt;

&lt;P&gt;Cheers&lt;BR /&gt;
Sid&lt;/P&gt;</description>
      <pubDate>Sun, 15 Sep 2019 22:26:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476616#M192648</guid>
      <dc:creator>siddh01r</dc:creator>
      <dc:date>2019-09-15T22:26:10Z</dc:date>
    </item>
    <item>
      <title>Re: Total Account lockouts &gt; 2  within 30mins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476617#M192649</link>
      <description>&lt;P&gt;About the first question, you have to create a timechart with two parameterts, user and host, but timechart can take only one parameter, in thjis way you can use two parameters in timechart.&lt;/P&gt;

&lt;P&gt;About the second question, if you use &lt;CODE&gt;| where total&amp;gt;2&lt;/CODE&gt;, you add a filter for your Alert: in this way, if you have results, alert is triggered otherwise not.&lt;BR /&gt;
If instaed you want to use this search in a panel, you can remove the filter and see all the results.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2019 07:18:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476617#M192649</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-09-16T07:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: Total Account lockouts &gt; 2  within 30mins</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476618#M192650</link>
      <description>&lt;P&gt;you may want to run this more often, maybe every 5 minutes and find a way to deal with dups.  Or run it over a longer period and use delta to find the time between alerts.  If you run it every 30, you could miss failed attempts that cross timespans.  &lt;/P&gt;

&lt;P&gt;For example, if it runs on the 0 &amp;amp;30 minute mark and attempts fail on the 57 and 02 minute marks.  The first run at the 0 min would only see the attempt at 57 and the run at the 30 mark would only see the attempt at 2nd minute.  And so even though the attempts are 5 minutes apart, your alert would miss them.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2019 10:59:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Total-Account-lockouts-gt-2-within-30mins/m-p/476618#M192650</guid>
      <dc:creator>maciep</dc:creator>
      <dc:date>2019-09-16T10:59:41Z</dc:date>
    </item>
  </channel>
</rss>

