S1 - Fixed operator logic to perform "contains" searches #182
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.
This is limited to SentinelOne Product. The logic for S1 powerquery queries being built was using the "in" operator which would not perform a full contains match on fields. The code was updated to use the "contains" operator instead which works with the rest of the logic and can still support searching multiple values. After testing all queries work as expected and expected results are now properly returned.
Example:
src.process.name contains ('megasync', 'rclone')
src.process.name in ('megasync', 'rclone')
"in" logic does not match a src.process.name of "rclone.exe", but using contains it now will match this event.