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

Feature request, store the yara rule name #4858

Closed
debernal opened this issue Jul 11, 2019 · 6 comments
Closed

Feature request, store the yara rule name #4858

debernal opened this issue Jul 11, 2019 · 6 comments

Comments

@debernal
Copy link

Hi, this is a feature request.

Currently MISP is able to store the YARA rule content that was used to detect a malicious file. But there is no specific type to only store the yara rule name. This is handy when the actual YARA rule is stored somewhere else, but it is still useful to know the name of the rule that was used to detect a specific file. Based on the description of "Support Tool" category, it seems that it is the best fit for this use case, as an automatic tool detecting files would not immediately know in what phase of the attack this file was used, such as "Payload Delivery, Network Activity", etc.

In this case, would it be possible to add another type on Support Tool category called yara-rule-name, or similar? Thank you

@adulau
Copy link
Member

adulau commented Jul 11, 2019

You can add a yara object in MISP. Let me know if you want an additional field with the yara rule name.

@debernal
Copy link
Author

Hi adulau, yes please, I want an additional field with the yara rule name. And in this case, allow to leave as null the YARA rule body if the yara rule name is set, does this make sense? thx

adulau added a commit to MISP/misp-objects that referenced this issue Jul 11, 2019
@adulau
Copy link
Member

adulau commented Jul 11, 2019

Thank you for the idea. This is now in the yara object template and the object can be expressed with the yara rule or the yara rule name alone.

MISP/misp-objects@ce8d6a9

The objects are also updated in MISP and the documentation.

If you see something else, missing in the object templates don't hesitate.

@adulau adulau closed this as completed Jul 11, 2019
@debernal
Copy link
Author

Thanks very much for your help adulau, should I simply update MISP to apply the new template or is it a file I can search and replace on the server?

@adulau
Copy link
Member

adulau commented Jul 12, 2019

Sure, you can do the following via the cli (or update via the Web interface) :

git pull origin 2.4
git submodule update

then go to the Web interface in Global Action - List Object Templates then you can click on 'Update Objects' in the menu to update the object templates.

@debernal
Copy link
Author

Thanks for your help :D, have a great day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants