You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When looking for observables of type command line containing special characters, the search does not return results. It also impacts running analytics on these observable.
After investigating, method filter in ArangoYetiConnector class is adding REGEX conditions which requires to escape all special characters. Replacing this condition with conditions.append(f"(CONTAINS(o.@arg{i}_key, @arg{i}_value) OR REGEX_TEST(o.@arg{i}_key, @arg{i}_value, true))") will work for all cases.
The question is, do we want to replace all occurrences of the faulty condition with the suggested ones or should we provide a regex operator in search?
The text was updated successfully, but these errors were encountered:
When looking for observables of type command line containing special characters, the search does not return results. It also impacts running analytics on these observable.
After investigating, method
filter
inArangoYetiConnector
class is adding REGEX conditions which requires to escape all special characters. Replacing this condition withconditions.append(f"(CONTAINS(o.@arg{i}_key, @arg{i}_value) OR REGEX_TEST(o.@arg{i}_key, @arg{i}_value, true))")
will work for all cases.The question is, do we want to replace all occurrences of the faulty condition with the suggested ones or should we provide a regex operator in search?
The text was updated successfully, but these errors were encountered: