windows: add file hash fields for the new Sysmon EID 29#7015
Merged
andrewkroh merged 5 commits intoelastic:mainfrom Jul 31, 2023
Merged
windows: add file hash fields for the new Sysmon EID 29#7015andrewkroh merged 5 commits intoelastic:mainfrom
andrewkroh merged 5 commits intoelastic:mainfrom
Conversation
The current pipeline does not create the "file.hash" field for the new sysmon Event ID 29. As a result, that information is lost and does not end up on the event.
|
💚 CLA has been signed |
Contributor
|
@fopson, please sign the CLA so that we can take a look at this. If you believe you have signed it, please check that the email address that you used agrees with the email address in the commits. |
Contributor
Author
|
Hi @efd6, I have signed the agreement twice now, but it is still showing up as unsigned. Not sure why. |
Contributor
|
@fopson Looks good now. |
Contributor
Author
Done. |
Contributor
Contributor
Author
Contributor
|
/test |
🌐 Coverage report
|
andrewkroh
approved these changes
Jul 31, 2023
|
Package windows - 1.28.0 containing this change is available at https://epr.elastic.co/search?package=windows |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current pipeline does not create the "file.hash" field for the new sysmon Event ID 29. As a result, that information is lost and does not end up on the event.
What does this PR do?
It makes sure the file hash information from the new sysmon EID 29 is not lost when the "_temp" field is deleted.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Sample Event
Screenshots