m365_defender: fix message ID handling #12546
Merged
Conversation
This file contains 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
efd6
added
Integration:m365_defender
The current data flow for the fields changed here is NetworkMessageId[1] → m365_defender.event.network.message_id → email.message_id and InternetMessageId[1] → m365_defender.event.internet_message_id → email.local_id, but the definition of email.message_id is that it represents the RFC5322 Message-ID[2], corresponding to the Defender InternetMessageId value, and email.local_id[3] is the non-persistent identifier, reasonably corresponding to the Defender NetworkMessageId value. Also add m365_defender.event.internet_message_id to final remove processor. [1]https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-emailevents-table#:~:text=NetworkMessageId,sending%20email%20system [2]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-message-id [3]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-local-id
efd6
force-pushed
the
12530-m365_defender
branch
from
23baf99 to
0e6b438
Compare
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @efd6 |
|
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
kcreddy
approved these changes
Jan 31, 2025
|
Package m365_defender - 2.21.1 containing this change is available at https://epr.elastic.co/package/m365_defender/2.21.1/ |
harnish-elastic
pushed a commit
to harnish-elastic/integrations
that referenced
this pull request
Feb 4, 2025
The current data flow for the fields changed here is NetworkMessageId[1] → m365_defender.event.network.message_id → email.message_id and InternetMessageId[1] → m365_defender.event.internet_message_id → email.local_id, but the definition of email.message_id is that it represents the RFC5322 Message-ID[2], corresponding to the Defender InternetMessageId value, and email.local_id[3] is the non-persistent identifier, reasonably corresponding to the Defender NetworkMessageId value. Also add m365_defender.event.internet_message_id to final remove processor. [1]https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-emailevents-table#:~:text=NetworkMessageId,sending%20email%20system [2]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-message-id [3]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-local-id
qcorporation
pushed a commit
that referenced
this pull request
Feb 4, 2025
The current data flow for the fields changed here is NetworkMessageId[1] → m365_defender.event.network.message_id → email.message_id and InternetMessageId[1] → m365_defender.event.internet_message_id → email.local_id, but the definition of email.message_id is that it represents the RFC5322 Message-ID[2], corresponding to the Defender InternetMessageId value, and email.local_id[3] is the non-persistent identifier, reasonably corresponding to the Defender NetworkMessageId value. Also add m365_defender.event.internet_message_id to final remove processor. [1]https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-emailevents-table#:~:text=NetworkMessageId,sending%20email%20system [2]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-message-id [3]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-local-id
harnish-elastic
pushed a commit
to harnish-elastic/integrations
that referenced
this pull request
Feb 5, 2025
The current data flow for the fields changed here is NetworkMessageId[1] → m365_defender.event.network.message_id → email.message_id and InternetMessageId[1] → m365_defender.event.internet_message_id → email.local_id, but the definition of email.message_id is that it represents the RFC5322 Message-ID[2], corresponding to the Defender InternetMessageId value, and email.local_id[3] is the non-persistent identifier, reasonably corresponding to the Defender NetworkMessageId value. Also add m365_defender.event.internet_message_id to final remove processor. [1]https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-emailevents-table#:~:text=NetworkMessageId,sending%20email%20system [2]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-message-id [3]https://www.elastic.co/guide/en/ecs/current/ecs-email.html#field-email-local-id
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.
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots