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.