[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Initial stab at grouping-context-ov values based on real-world use cases
A couple of weeks ago on the working call I took an action item to provide an initial minimal stab at grouping-context-ov values based on real-world use cases. I got busy and did not follow through. So, at the F2F last week we had a small side discussion where I provided an initial minimal stab at grouping-context-ov values based on real-world use cases that we see and then we discussed which ones we
might have consensus on as a small initial set, which ones might make longer term sense but not have consensus for an initial set and which ones might be considered a bit more esoteric and considerable for future versions if real-world use proved out their
value. To reiterate for clarity, the purpose of the Grouping object is to convey that a specific set of STIX content shares some context.
It is not intended to be the first choice for sharing any set of related STIX content and is not intended to replace CTI domain-relevant objects.
It is the generalized last resort for specifying this sort of thing when there is no STIX domain-relevant object already available for the given type of context (e.g. STIX content that describes the structure
or behavior of a piece of malware would utilize the Malware object, STIX content that characterizes details of infrastructure would utilize the Infrastructure object, etc). The context property of the Grouping object is intended to convey the nature of context that the referenced content shares.
The intent of the grouping-context-ov is to provide consistently defined values for common cases of Grouping context while also leaving open the option of specifying values not defined by the standard. Values of grouping-context-ov fall below the threshold required (at least for now) for defining a new SDO for that sort of context but above the threshold for uncommon or highly specialized forms of grouping
context. Here is the initial stab that resulted from the discussion at the F2F:
A set of STIX content related to a particular suspicious activity event.
(Answers question: what do we know about what happened in this suspicious activity/attack?)
A set of STIX Sightings for a given Indicator.
(Answers question: what sightings are known for this indicator?)
A set of STIX objects related to a given object along with any relevant Relationship objects.
(Answers question: what objects are related to this specific object (embedded/external relationship from this object, embedded/external relationship to this object)?)
A set of STIX content from a malware analysis action (sandbox execution, structural analysis, etc).
A set of STIX content related to a given Malware object. **It should be noted that this is not details of the malware which would
be conveyed in a Malware object but rather other STIX content related to the Malware object
A set of STIX content related to a given ThreatActor object. **It should be noted that this is not details of the threat actor which
would be conveyed in a ThreatActor object but rather other STIX content related to the ThreatActor object
A set of STIX content related to a given Campaign object. **It should be noted that this is not details of the campaign which
would be conveyed in a Campaign object but rather other STIX content related to the Campaign object
A set of STIX content related to a given IntrusionSet object. **It should be noted that this is not details of the intrusion set which
would be conveyed in a IntrusionSet object but rather other STIX content related to the IntrusionSet object
A set of STIX content related to a given Identity object. **It should be noted that this is not details of the identity which
would be conveyed in an Identity object but rather other STIX content related to the Identity object
A set of STIX content related to a given Location object. **It should be noted that this is not details of the location which
would be conveyed in a Location object but rather other STIX content related to the Location object
A set of STIX content related to a given Tool object. **It should be noted that this is not details of the tool which
would be conveyed in a Tool object but rather other STIX content related to the Tool object
A set of STIX content related to a given Vulnerability object. **It should be noted that this is not details of the vulnerability which
would be conveyed in a Vulnerability object but rather other STIX content related to the Vulnerability object
A set of STIX content related to a given Observable object. **It should be noted that this is not details of the observable which
would be conveyed in an Observable object but rather other STIX content related to the Observable object
A set of STIX activity content that occurred within a given time window
A set of STIX content created within a given time window
A set of STIX content that matches a specific selector pattern
Please feel free to offer your thoughts. Do you disagree with including any of these values? Do you think that we should start with only the suggested values? Do you think we should also include any/all of the “common case” or “outlier” values? Sean Barnum Principal Architect FireEye M: 703.473.8262 E: sean.barnum@fireeye.com |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]