[crowdstrike,m365_defender,microsoft_defender_endpoint,trend_micro_vision_one] map source-specific fields to process.* ECS fields - #13984
Merged
Conversation
mohitjha-elastic
added
enhancement
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
…add_ecs_for_data_analyzer Conflicts: packages/crowdstrike/changelog.yml packages/crowdstrike/data_stream/alert/sample_event.json packages/crowdstrike/data_stream/falcon/sample_event.json packages/crowdstrike/docs/README.md packages/m365_defender/changelog.yml packages/m365_defender/data_stream/alert/sample_event.json packages/m365_defender/data_stream/incident/sample_event.json packages/m365_defender/docs/README.md packages/microsoft_defender_endpoint/changelog.yml packages/microsoft_defender_endpoint/data_stream/log/sample_event.json packages/microsoft_defender_endpoint/docs/README.md
Contributor
🚀 Benchmarks reportTo see the full report comment with |
efd6
changed the title
efd6
reviewed
May 25, 2025
Comment on lines
+298
to
+309
| - convert: | ||
| field: process.pid | ||
| tag: convert_process_pid_to_string | ||
| target_field: process.entity_id | ||
| type: string | ||
| ignore_missing: true | ||
| - convert: | ||
| field: process.parent.pid | ||
| tag: convert_process_parent_pid_to_string | ||
| target_field: process.parent.entity_id | ||
| type: string | ||
| ignore_missing: true |
Contributor
There was a problem hiding this comment.
Leave as numbers and note numeric keyword in the test definition.
Comment on lines
+110
to
+121
| - convert: | ||
| field: process.pid | ||
| tag: convert_process_pid_to_string | ||
| target_field: process.entity_id | ||
| type: string | ||
| ignore_missing: true | ||
| - convert: | ||
| field: process.parent.pid | ||
| tag: convert_process_parent_pid_to_string | ||
| target_field: process.parent.entity_id | ||
| type: string | ||
| ignore_missing: true |
| if (!processParentPid.isEmpty()) { | ||
| ctx.process.parent.pid = convertToOrderedArray(processParentPid); | ||
| } | ||
| - foreach: |
Comment on lines
+237
to
+248
| - convert: | ||
| field: process.pid | ||
| tag: convert_process_pid_to_string | ||
| target_field: process.entity_id | ||
| type: string | ||
| ignore_missing: true | ||
| - convert: | ||
| field: process.parent.pid | ||
| tag: convert_process_parent_pid_to_string | ||
| target_field: process.parent.entity_id | ||
| type: string | ||
| ignore_missing: true |
| field: process.pid | ||
| copy_from: trend_micro_vision_one.detection.process.pid | ||
| ignore_failure: true | ||
| - convert: |
|
💚 Build Succeeded
History
|
efd6
changed the title
efd6
approved these changes
May 26, 2025
efd6
left a comment
efd6
left a comment
Contributor
There was a problem hiding this comment.
Suggest commit message body:
* crowdstrike: add process.entity_id and process.parent.entity_id ECS
mappings in alert and falcon data streams.
* m365_defender: add process.entity_id and process.parent.entity_id ECS
mappings in all data streams.
* microsoft_defender_endpoint: add process.entity_id and
process.parent.entity_id ECS mappings in log data stream.
* trend_micro_vision_one: add process.entity_id ECS mapping in detection
data stream.
These mappings align the data streams with ECS standards and ensure
consistency across ingested data, supporting reliable analyzer
development.
Contributor
|
Package crowdstrike - 1.71.0 containing this change is available at https://epr.elastic.co/package/crowdstrike/1.71.0/ |
Contributor
|
Package m365_defender - 3.6.0 containing this change is available at https://epr.elastic.co/package/m365_defender/3.6.0/ |
Contributor
|
Package microsoft_defender_endpoint - 2.36.0 containing this change is available at https://epr.elastic.co/package/microsoft_defender_endpoint/2.36.0/ |
Contributor
|
Package trend_micro_vision_one - 2.1.0 containing this change is available at https://epr.elastic.co/package/trend_micro_vision_one/2.1.0/ |
anupratharamachandran
pushed a commit
to anupratharamachandran/integrations
that referenced
this pull request
Jun 2, 2025
…sion_one] map source-specific fields to process.* ECS fields (elastic#13984) * crowdstrike: add process.entity_id and process.parent.entity_id ECS mappings in alert and falcon data streams. * m365_defender: add process.entity_id and process.parent.entity_id ECS mappings in all data streams. * microsoft_defender_endpoint: add process.entity_id and process.parent.entity_id ECS mappings in log data stream. * trend_micro_vision_one: add process.entity_id ECS mapping in detection data stream. These mappings align the data streams with ECS standards and ensure consistency across ingested data, supporting reliable analyzer development.
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
3 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
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: crowdstrike, m365_defender, microsoft_defender_endpoint, or trend_micro_vision_one.
Related issues