Splunk Search

How can I use Splunk to determine Phishing attempts?

Yancy
Path Finder

What are some methods of determining anomalous login behavior with Splunk?

1 Solution

Yancy
Path Finder

One method we've been using is looking for multiple failed logins from a single IP.

sourcetype="some source where login attempts are logged" ipaddress!=10.* NOT Succeeded| stats distinct_count(loginname) AS logincount by ipaddress | where logincount > 10

IE: For all ips not in our local subnet and without a "Succeeded" message in our application access log, provide stats on each login grouped by ipaddress, and only show me the results where 10 or more accounts had unsuccessful access attempted to.

Another method:

If you know the site that is phishing user data, you can also use Splunk to create a honeypot. To do this setup a saved search & alert on some sort of input value known only to you, and then use that value on the site. If the value you provided is attempted, you'll get an alert (hopefully with the data necessary to mitigate further). This is helpful as often the site phishing the data is not the IP that is attempting to re-use and exploit the data.

View solution in original post

Yancy
Path Finder

One method we've been using is looking for multiple failed logins from a single IP.

sourcetype="some source where login attempts are logged" ipaddress!=10.* NOT Succeeded| stats distinct_count(loginname) AS logincount by ipaddress | where logincount > 10

IE: For all ips not in our local subnet and without a "Succeeded" message in our application access log, provide stats on each login grouped by ipaddress, and only show me the results where 10 or more accounts had unsuccessful access attempted to.

Another method:

If you know the site that is phishing user data, you can also use Splunk to create a honeypot. To do this setup a saved search & alert on some sort of input value known only to you, and then use that value on the site. If the value you provided is attempted, you'll get an alert (hopefully with the data necessary to mitigate further). This is helpful as often the site phishing the data is not the IP that is attempting to re-use and exploit the data.

jrodman
Splunk Employee
Splunk Employee

Consider accepting your answer 😄

0 Karma

piebob
Splunk Employee
Splunk Employee

i ❤️ your icon!!!

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

Splunk is officially part of Cisco

Revolutionizing how our customers build resilience across their entire digital footprint.   Splunk ...

Splunk APM & RUM | Planned Maintenance March 26 - March 28, 2024

There will be planned maintenance for Splunk APM and RUM between March 26, 2024 and March 28, 2024 as ...