<?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 How to find the source of excessive failed logins (bruteforce)? in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-find-the-source-of-excessive-failed-logins-bruteforce/m-p/308691#M2794</link>
    <description>&lt;P&gt;We see there are 40,000 failed login attempts to a DC on our network but are unable to verify the source (IP) using Splunk. Assuming we are collecting all the necessary data, what should we search for to find the culprit?&lt;/P&gt;

&lt;P&gt;We have ES and the indicators are consistent with a brute force attack.&lt;/P&gt;

&lt;P&gt;Here is what we run to find those results.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| from datamodel:"Authentication"."Failed_Authentication" | search src="companydomain.com" | stats count by user | sort - count
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 22 Feb 2018 17:04:13 GMT</pubDate>
    <dc:creator>iKickFish</dc:creator>
    <dc:date>2018-02-22T17:04:13Z</dc:date>
    <item>
      <title>How to find the source of excessive failed logins (bruteforce)?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-find-the-source-of-excessive-failed-logins-bruteforce/m-p/308691#M2794</link>
      <description>&lt;P&gt;We see there are 40,000 failed login attempts to a DC on our network but are unable to verify the source (IP) using Splunk. Assuming we are collecting all the necessary data, what should we search for to find the culprit?&lt;/P&gt;

&lt;P&gt;We have ES and the indicators are consistent with a brute force attack.&lt;/P&gt;

&lt;P&gt;Here is what we run to find those results.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| from datamodel:"Authentication"."Failed_Authentication" | search src="companydomain.com" | stats count by user | sort - count
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 22 Feb 2018 17:04:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-find-the-source-of-excessive-failed-logins-bruteforce/m-p/308691#M2794</guid>
      <dc:creator>iKickFish</dc:creator>
      <dc:date>2018-02-22T17:04:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to find the source of excessive failed logins (bruteforce)?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-find-the-source-of-excessive-failed-logins-bruteforce/m-p/308692#M2795</link>
      <description>&lt;P&gt;use iplocation commmand &lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2018 18:46:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-find-the-source-of-excessive-failed-logins-bruteforce/m-p/308692#M2795</guid>
      <dc:creator>sushantmhatre</dc:creator>
      <dc:date>2018-02-22T18:46:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to find the source of excessive failed logins (bruteforce)?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-find-the-source-of-excessive-failed-logins-bruteforce/m-p/308693#M2796</link>
      <description>&lt;P&gt;Depending on authentication load, and given this is a DC, this could be normal, it depends.&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/4434iA6686CE1213F8506/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;You could try selecting this link from your notable-event (which you might have already). Ensure your assets.csv correctly reflects reality, with both IPs and DNS/Hostnames, should make your ES experience better.&lt;/P&gt;

&lt;P&gt;Otherwise you could remove "| search src="companydomain.com" from the search and look at everything that is failing authentication to deduce what's happening.&lt;/P&gt;

&lt;P&gt;Cheers.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Feb 2018 05:15:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-find-the-source-of-excessive-failed-logins-bruteforce/m-p/308693#M2796</guid>
      <dc:creator>Splunker</dc:creator>
      <dc:date>2018-02-23T05:15:31Z</dc:date>
    </item>
  </channel>
</rss>

