-
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
enhancement: add hostname to Microsoft 365 defender ingest pipeline #29863
enhancement: add hostname to Microsoft 365 defender ingest pipeline #29863
Conversation
This pull request does not have a backport label. Could you fix it @hinchliff? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
x-pack/filebeat/module/microsoft/m365_defender/ingest/pipeline.yml
Outdated
Show resolved
Hide resolved
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
/test |
I have some better advice; the hosts can be appended only into the My understanding is that there is no mapping for |
This pull request is now in conflicts. Could you fix it? 🙏
|
…-hostname-ms-365-defender
This pull request is now in conflicts. Could you fix it? 🙏
|
…ostname-ms-365-defender
This pull request is now in conflicts. Could you fix it? 🙏
|
…ostname-ms-365-defender
/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 for your patience.
What does this PR do?
The events from Defender ATP include the fields host.name and host.hostname, but these fields were missing from the 365 Defender events.
This PR adds parsing/extraction of
host.name
andhost.hostname
field from the 365 Defender events, using thejson.alerts.devices.deviceDnsName
from the source.Why is it important?
In order to use Elastic Security, host.name is a required field
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
How to test this PR locally
Related issues
Use cases
Screenshots
Logs