Closed josephtillman11 closed 3 years ago
Huuu hooooo interesting. Could you attach the raw evtx file? I am assuming the process name is not the full path of the binary ( I remember it was an issue between Windows versions ). Also as a note it could also be filtered in the Logstash pipeline at the expense of volume of course. Please post your file and will take a look.
@josephtillman11 could you try to drop first all process creation event?
winlogbeat.event_logs:
- name: Security
processors:
- drop_event.when.or:
- equals.winlog.event_id: 4624
This will help understand whether is a case matching issue.
I was able to resolve the issue. Here's the config that worked:
winlogbeat.event_logs:
- name: Security
processors:
- drop_event.when:
and:
- equals:
winlog.event_data.EventId: 4624
Interesting so this should work:
winlogbeat.event_logs:
- name: Security
processors:
- drop_event.when:
and:
- equals:
winlog.event_data.EventId: 4624
winlog.event_data.ProcessName: "zabbix_agentd.exe"
Thank you @priamai , @josephtillman11 and @robomotic !
The drop_event processor is not taking affect even though the config tests ok. I have also tried -equals.winlog.event_data.ProcessName:
Kibana discovery still shows this after adding drop_event processor: