Cherry-pick #18381 to 7.x: Improve ECS field mappings in Sysmon module. (#18381) #18519
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.
Cherry-pick #18381 to 7.x branch. Original message:
What does this PR do?
Improve ECS field mappings in Sysmon module.
Why is it important?
Sysmon module was not reporting some fields and was reporting others in a namespace that was not aligned with ECS. This adds changes to improve the ECS field mapping for it.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
NOTES:
process.parent.hash
is not present in any event (you can check here), so nothing was done for it.rule.name
has been added to all events that can have it according to the previous schema, but will be ignored if empty or its value is-
.hash
object will not be removed until 8.0 since it is a breaking change.Related issues
Closes #18364