Re: [cti-cybox] Network flow object suggestions

["Jason Keirstead" <Jason.Keirstead@ca.ibm.com>]

Multiple sources and dests is not to handle multicast. It is an encoding optimization to handle DDOS and port scan attempts. Without it, to encode a DDOS you may have 100,000 duplicate objects.

Sent from IBM Verse

Jordan, Bret --- Re: [cti-cybox] Network flow object suggestions ---

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

---

Good catch, I have not really gotten to that object yet...  So yes, I would agree, I am not sure why we would allow a list for the source/src/initiator 

Thanks,

Bret

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." 

On Aug 25, 2016, at 15:24, Terry MacDonald <terry.macdonald@cosive.com> wrote:

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