-
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
[Winlogbeat] Add subdomain value for sysmon module #22999
[Winlogbeat] Add subdomain value for sysmon module #22999
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
Test | Results |
---|---|
Failed | 0 |
Passed | 17359 |
Skipped | 1373 |
Total | 18732 |
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.
Good idea to update the processor.
I noticed there is a dns.question.top_level_domain
field. I guess. that. could go in there too. https://www.elastic.co/guide/en/ecs/current/ecs-dns.html#field-dns-question-top-level-domain
Opened an issue to track circling back and adding "top_level_domain" handling: #23005 |
* [Winlogbeat] Add subdomain value for sysmon module * Add changelog entry * Add target_subdomain_field to docs example (cherry picked from commit d38a5d0)
What does this PR do?
This adds
subdomain
to the event in the sysmon module. To make it a bit more reusable I added an optionaltarget_subdomain_field
to theregistered_domain
processor that different modules in winlogbeat and filebeat use for parsing out theregistered_domain
value.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues