Add threat-hunt-* object set for structured threat hunt sharing - #528
Merged
Conversation
Member
|
Thank you very much for the contributions! |
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
2 participants
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.
Why
MISP has hundreds of object templates but nothing for the narrative arc of a hunt itself. You can express an indicator, a Sigma rule, or a course of action, but there's no object for "here's a hypothesis I tested" or "here's what I found and why it matters." Without one, a shared hunt either gets flattened into raw IOC attributes (the reasoning behind them lost) or written up as a free-text Event Report (structure and queryability both lost). These four objects fill that gap.
Companion taxonomy
Paired with the HUNT-EX taxonomy proposed in MISP/misp-taxonomies#345. HUNT-EX answers "can I run this, should I care, did anyone find anything, what happens next" from the tag list. These objects are what you get when you open the event.