Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IDEA] Be able to store additional context/data in cache #83

Open
frikilax opened this issue Oct 14, 2019 · 0 comments
Open

[IDEA] Be able to store additional context/data in cache #83

frikilax opened this issue Oct 14, 2019 · 0 comments
Labels
enhancement New feature or request technical

Comments

@frikilax
Copy link
Member

frikilax commented Oct 14, 2019

What is your feature about ?
Be able to store additional context in cache.

Describe what you'd like
When filters store information (aka. certitude currently) to cache, they can't store additional context about the entry they just handled, being able to store additional metadata (in the form of a string/json/whatever) could be great to give more information in logs when entries have a high certitude level.

Additional context
Example : fyara_scan (first version currently on branch split_inspection) returns not only the certitude, but the matching yara rules (when applicable), tags, etc...
The current cache doesn't permit to store anything else than a number (?), so the matching entries will have context in log only once, and then only the certitude next times (even if the entry needs to be exactly the same, but that WILL happen).

@frikilax frikilax added enhancement New feature or request technical labels Oct 14, 2019
@frikilax frikilax assigned frikilax and unassigned frikilax Oct 14, 2019
@frikilax frikilax changed the title [IDEA] Being able to store additional context/data in cache [IDEA] Be able to store additional context/data in cache Oct 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request technical
Projects
None yet
Development

No branches or pull requests

1 participant