[M365 Defender] Improve response action support in event dataset. #13769
Conversation
This file contains hidden or 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
reviewed
May 4, 2025
packages/m365_defender/data_stream/event/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
Changes to version numbers, formatting corrections, and fields. Co-authored-by: Dan Kortschak <[email protected]>
Contributor
|
/test |
Contributor
|
You'll need to regenerate the pipeline test expectations. For example |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
A prior commit had set the field `cloud.instance.id'`. This removes the inadvertant single quote from the field name.
Contributor
|
/test |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
|
efd6
approved these changes
May 19, 2025
|
Package m365_defender - 3.4.0 containing this change is available at https://epr.elastic.co/package/m365_defender/3.4.0/ |
anupratharamachandran
pushed a commit
to anupratharamachandran/integrations
that referenced
this pull request
Jun 2, 2025
…astic#13769) This PR copies the value, when present, from m365_defender.event.device.id to cloud.instance.id. The value will not be copied if the device ID is null or cloud.instance.id is already set. Setting this field addresses one of the solutions in elastic/kibana#218756 The M365 Defender response action is available on alerts with the following fields: microsoft_defender_endpoint: [ 'm365_defender.alerts.entities.deviceId', 'm365_defender.alerts.devices.mdatpDeviceId', 'm365_defender.incident.alert.evidence.mde_device_id', 'cloud.instance.id', ], Currently, any alert generated from the m365_defender.event dataset will not have a response action available. Once cloud.instance.id is set, it is possible to isolate/release a host via the connector. The alternative/supplemental solution, adding m365_defender.event.device.id to the constant, microsoft_defender_endpoint would require an update to Kibana, making the approach here a more immediate fix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
This PR copies the value, when present, from
m365_defender.event.device.idtocloud.instance.id. The value will not be copied if the device ID is null orcloud.instance.idis already set.Setting this field addresses one of the solutions in elastic/kibana#218756
The M365 Defender response action is available on alerts with the following fields:
Presently, any alerts generated from the
m365_defender.eventdataset will not have a response action available. Oncecloud.instance.idis set, it is possible to isolate/release a host via the connector.The alternative/supplemental solution, adding
m365_defender.event.device.idto the constant,microsoft_defender_endpointwould require an update to Kibana, making this a more immediate fix.Checklist
changelog.ymlfile.Related issues