-
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
Add event IDs 4797, 5379, 5380, 5381, and 5382 #34294
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
/test |
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.
Are you able to provide events (as individual evtx) for these event types?
I was able to grab some of them, but they contain sensitive usernames, hostnames, etc. Do you have a location I can send them to you out of the public eye? |
I think we could get around needing the evtx if we start from the XML by exporting this from the event viewer. This would mean that we can include the data in the tree without leaking your secrets if you scrub before letting us have the data. Does that sound reasonable to you? |
Attaching five scrubbed sample events for each of the Event ID's. |
Can we back-port this? |
This is an enhancement, so we will not back-port. |
Tests cases mechanically derived from user-provided XML scrubbed event data.
It looks like there needs to be some additional changes to make sure that things like related.host and related.user are properly updated for these event types. There are hooks in the security.yml file that allow this to be done by adding the appropriate event ID to the filter array. |
/test |
I don't see any processors that would add |
/test |
/test |
@@ -2604,7 +2639,7 @@ processors: | |||
"4750", "4751", "4752", "4753", "4754", "4755", "4756", "4757", | |||
"4758", "4759", "4760", "4761", "4762", "4763", "4764", "4767", | |||
"4781", "4798", "4799", "4817", "4904", "4905", "4907", "4912", | |||
"4648"].contains(ctx.event.code)) { | |||
"4648", "4797"].contains(ctx.event.code)) { |
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.
Is there a reason not to include the other types here? They also appear to have SubjectUserName
fields.
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.
There was not. I had added them to the related user appending, but I forgot to add them to "Copy Subject User from Event Data" script. Since event 4797 also has a TargetUserName, I also just added that one to the "Copy Target User to Target" script.
This pull request is now in conflicts. Could you fix it? 🙏
|
/test |
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.
Thanks
@efd6 could mappings for these events be applied to the system.security pipeline for agent, to ensure alignment between the winlogbeat and agent pipelines? |
@jamiehynds , please see #5085 that mirrors these changes to the |
Thanks @MakoWish, I missed that one. Thanks for all your recent contributions and collaboration! |
Didn't miss it. I created it after your comment. 👍 |
Tests cases mechanically derived from user-provided XML scrubbed event data. Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
Type of change
What does this PR do?
This PR adds event parsing to the Security Ingest Pipeline for Winlogbeat for Event ID's 4797, 5379, 5380, 5381, and 5382.
Why is it important?
These Event ID's are quite common in our environment, so ensuring the correct
event.action
is populated will help identify the nature of the event at a quick glance.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues