-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick #18340 to 7.8: [Winlogbeat] Add support for FileDelete events (event id 23) to sysmon module #18363
Conversation
…stic#18340) FileDelete events were added in Sysmon v11. Prior to this change processing such events lead to an 'unexpected sysmon event_id' error message. Closes elastic#18094 (cherry picked from commit 0a327bb)
Pinging @elastic/siem (Team:SIEM) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
backport looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from my one comment which we can do in a follow up PR to the 7.x branch (along with the other changes you suggested in #18340) LGTM
"pid": 776 | ||
}, | ||
"rule": { | ||
"name": "-" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to consider dropping this field if it doesn't actually contain anything valuable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added that to #18364.
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
|
Cherry-pick of PR #18340 to 7.8 branch. Original message:
What does this PR do?
FileDelete events were added in Sysmon v11, this PR adds support for FileDelete events (event id 23) to sysmon module.
Why is it important?
Prior to this change processing such events lead to an 'unexpected sysmon event_id' error message.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.TODO
Empty strings are replaced with “-“ to work around a WEF bugRelated issues
Closes #18094