[microsoft_defender_endpoint, m365_defender] extract process.name from process.command_line#15226
Merged
efd6 merged 4 commits intoelastic:mainfrom Sep 10, 2025
Merged
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Some pipelines already contain logic to parse process.executable and process.name. The script will only be used when either of these fields is missing to set the process.name.
🚀 Benchmarks reportTo see the full report comment with |
efd6
reviewed
Sep 9, 2025
packages/m365_defender/data_stream/event/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/m365_defender/data_stream/alert/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/m365_defender/data_stream/incident/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/microsoft_defender_endpoint/data_stream/log/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
Optimize initializing process ECS
💚 Build Succeeded
History
|
|
Contributor
|
I have manually tested this on a problematic sample and it behaves as wanted. |
|
Package m365_defender - 4.0.1 containing this change is available at https://epr.elastic.co/package/m365_defender/4.0.1/ |
|
Package microsoft_defender_endpoint - 3.0.1 containing this change is available at https://epr.elastic.co/package/microsoft_defender_endpoint/3.0.1/ |
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
… process.command_line (elastic#15226) * m365_defender: updated process.name ECS mapping in alert, event, and incident data streams to extract the process name from process.command_line instead of relying on file.name. * microsoft_defender_endpoint: updated process.name ECS mapping in log data stream to extract the process name from process.command_line. M365 Defender: * Alert – If process.name already exists, leave it as is. Otherwise, extract it from process.command_line(since process.executable is not available here). * Event – Some pipelines already contain logic to parse process.executable and process.name. The script to set process.name from command_line will only be used when either of these fields is missing. * Incident – Both process.name and process.executable are not available. Therefore, the script must be used to parse and populate process.name. Microsoft Defender Endpoint: * log - Both process.name and process.executable are not available. Therefore, the script must be used to parse and populate process.name.
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
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.How to test this PR locally
To test integration
Clone integrations repo.
Install the elastic package locally.
Start the elastic stack using the elastic package.
Move to integrations/packages/<integration_name> directory.
Run the following command to run tests.
elastic-package test -vNOTE: To test individual integrations, replace <integration_name> with one of the following: m365_defender or microsoft_defender_endpoint.
Related issues
SDH 6382