Splunk Enterprise Security

Splunk_TA_windows puts failed logon events in Change Datamodel

asobiesiak
New Member

Hi Splunkers,
It is strange to me and I hope someone can explain - what is the reason for ingesting Windows failed logon events to Data Model "Change" with Splunk_TA-Windows app.

This is done by labeling windows_audit_log_logon eventtype with "change" and "audit" tags.
Mentioned eventtype is basically any windows log with EventID 4625, there is SubStatus restriction but it catches both events caused by account lockout and wrong credentials, besides there is 4740: A user account was locked out that suits this purpose better IMHO.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...