[ESET PROTECT] Make IoC ECS fields compatible with TI integrations - #9459
Closed
kat-does-code wants to merge 14 commits into
Closed
[ESET PROTECT] Make IoC ECS fields compatible with TI integrations#9459kat-does-code wants to merge 14 commits into
kat-does-code wants to merge 14 commits into
Conversation
added 14 commits
March 27, 2024 10:16
|
💚 CLA has been signed |
kat-does-code
marked this pull request as draft
March 28, 2024 09:04
kat-does-code
marked this pull request as ready for review
March 28, 2024 09:04
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.
(Enhancement)
Adjusted ECS fields
file.hash.sha1,threat.indicator.file.hash.sha1andrelated.hashto be lower case, which is more in line with comparable security integrations (including the ESET Threat Intelligence integration). This enhancement should enable compatibility with indicator match rules.Also fixed a grok parsing issue where event data would be incorrectly parsed when
eset_protect.event.object_urihas valuescript.Proposed commit message
Lowercase related hash and indicator hash to support indicator rule matching. Fixed grok parse error when object_uri equals 'script'.
Checklist
changelog.ymlfile.