[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-cybox] Network flow object suggestions
There are at minimum 3 cases to be considered which we see very often in the real world:
Which is what the multiplicity in the STIX sighting relationship object is for. We should keep the network flow object for recording one flow, and use the sighting for saying 'and other stuff like this'.
Cheers
Terry MacDonald
Cosive
On 26/08/2016 22:13, "Jason Keirstead" <Jason.Keirstead@ca.ibm.com> wrote:
From: | "Jordan, Bret" <bret.jordan@bluecoat.com> |
To: | "Terry MacDonald" <terry.macdonald@cosive.com> |
Cc: | cti-cybox@lists.oasis-open.org |
Date: | Thu, Aug 25, 2016 7:16 PM |
Subject: | Re: [cti-cybox] Network flow object suggestions |
Hi all
I have some questions about the network flow object.
----
The first is about the multiplicity of the source_refs.
Multicast traffic always so comes from a single source. So does a network broadcast. So is there any reason to have the source as a list when there is always just one source? Am I missing something?
We should really change its name to src_ref, and restrict it to one object-ref.
----
The second is around the list of options in the protocols field. We should probably provide an open vocabulary taken from both the IANA protocol list and the IANA services list to provide people a list of common options they should use. Otherwise we'll hit problems like people putting in 'ip' rather than ipv4 or ipv6, which is ambiguous.
Cheers
Terry MacDonald
Cosive
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]