url is optional, you can use
name, which is also optional – you just have to use one of them
From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org]
On Behalf Of Jordan, Bret
Sent: Wednesday, February 03, 2016 11:24 AM
To: Wunder, John A. <jwunder@mitre.org>
Cc: cti@lists.oasis-open.org
Subject: Re: [cti] Top-Level Object Properties
Well then I do not think we have consensus on the external_ids object... I thought this was going to be just an array of string values. Why does it need an "id" and why would we every make data field be a "url".
External_Ids are going to be populated by internal systems or vendor products. These solutions will give a name like "malware foo xyz" for example, this is not a URL.
Bret Jordan CISSP
Director of Security Architecture and Standards | Office of the CTO
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."
The syntax means that those fields are a sub-object nested under the parent. So that would be one of the keys within the objects in the external_ids
array.
I do not believe we have consensus on all of the items in the consensus section. Namely, what are the "----" field all about?
Example
|
----id (required)
|
IDFormat
|
The external ID itself
|
Bret Jordan CISSP
Director of Security Architecture and Standards | Office of the CTO
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."
There’s a new topic to think about! As discussed at the face to face, each top-level object in STIX and CybOX will inherit from a core set of properties…things
like ID, etc. We haven’t quite agreed on what all of those fields are, though.
Take a look at this writeup: https://github.com/STIXProject/specifications/wiki/Active-Issue:-IDable-Construct-Properties.
It has a set of fields that we have general agreement on, a list of fields we haven’t really discussed, and then a couple proposals (from Sean and from the twigs team). Feel free to either add your own proposal to that wiki page or discuss on the mailing lists
and slack. The key question to consider: what fields should be available on *all* top-level objects?
|