[Enhancement] Add ".caseless" fields to process events#10533
Merged
Conversation
w0rk3r
commented
Jul 18, 2024
🚀 Benchmarks reportTo see the full report comment with |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform) |
andrewkroh
approved these changes
Jul 19, 2024
AndersonQ
approved these changes
Jul 24, 2024
Contributor
|
@w0rk3r this PR is now in conflict |
|
💚 Build Succeeded
History
cc @w0rk3r |
Contributor
|
@w0rk3r We are now good to go, thanks |
|
Package system - 1.60.0 containing this change is available at https://epr.elastic.co/search?package=system |
|
Package windows - 1.47.0 containing this change is available at https://epr.elastic.co/search?package=windows |
This was referenced Sep 5, 2024
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
[Enhancement] Add ".caseless" fields to process events
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
… EDR data sources (elastic#11019) Uses a field alias to map the process integrity field to the one used in the rules based on our Elastic Defend for more straightforward rule conditions. Adds caseless versions of process.name and process.executable as done in elastic#10533.
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
[Enhancement] Add ".caseless" fields to process events
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
… EDR data sources (elastic#11019) Uses a field alias to map the process integrity field to the one used in the rules based on our Elastic Defend for more straightforward rule conditions. Adds caseless versions of process.name and process.executable as done in elastic#10533.
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
6 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.
Summary
Clean version of #9850, reopening this as the discussion in ECS suggests this may be the best way to proceed.
Proposed commit message
This PR adds
.caselessfields for the process name and executable to improve compatibility with our Elastic Defend integration. This enables us to handle language limitations in KQL more effectively.I'm also specifying the
.textfield as it was being removed from the markdown file otherwise.Elastic Defend Mapping:
Checklist
changelog.ymlfile.How to test this PR locally
Build the integration, ingest sysmon or windows security logs.
Related issues
Screenshots