Splunk Search

How do I edit my transaction search to find over 3 failed Windows logon events that happen within a 10 minute timespan?

strangelaw
Explorer

So I am working a bit with transaction and I am unable to verify how it should work. This is my search:

index = "myintestindex" sourcetype = "WinEventLog:Security" EventCode = 529 OR EventCode = 4625 AND Failure_Reason = "Unknown user name or bad password." | transaction maxspan=10m | table Account_Name, Failure_Reason

What I am looking for is a) to find all those EventCodes and Failure_Reason that happen on 10m span then b) to count that if there is over 3 of them on that specific 10min timespan. I dont want to end the search to Account_Name being allowed (so no failure).

This is on the simplest form and I do not want to do it with alert/reporting - but with a search.

0 Karma
1 Solution

somesoni2
Revered Legend

How about this

 index = "myintestindex" sourcetype = "WinEventLog:Security" EventCode = 529 OR EventCode = 4625 AND Failure_Reason = "Unknown user name or bad password." | transaction maxspan=10m Account_Name | table Account_Name Failure_Reason duration eventcount | where eventcount>=3

View solution in original post

0 Karma

somesoni2
Revered Legend

How about this

 index = "myintestindex" sourcetype = "WinEventLog:Security" EventCode = 529 OR EventCode = 4625 AND Failure_Reason = "Unknown user name or bad password." | transaction maxspan=10m Account_Name | table Account_Name Failure_Reason duration eventcount | where eventcount>=3
0 Karma

strangelaw
Explorer

This forks. Thanks!

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...