[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] Open Question to the CTI Community
Sean,
Well said... "
"
- this 'analogy' better fits with my understanding and usage to convert non-STIX/CybOX sources to native (standards based) STIX/CybOX.
As well as starting to embrace "test mechanism" to handle native format (to encapsulate other standards) such as SNORT and YARA.
From: cti@lists.oasis-open.org <cti@lists.oasis-open.org> on behalf of Barnum, Sean D. <sbarnum@mitre.org>
Sent: Wednesday, August 19, 2015 10:46 AM To: Jacobsen, Jasen W.; cti@lists.oasis-open.org Subject: Re: [cti] Open Question to the CTI Community I would very much agree with Jasen here.
Trying to stay as simple as possible, I would characterize it as:
To use an analogy, think of:
I would think (hope) there is less confusion here on STIX/CybOX being languages for expressing the relevant information.
I think there is likely some confusion in some parts of the community on the distinction between the STIX/CybOX languages and any specific binding implementations but we hope to address
that confusion soon with the publication of the initial OASIS versions of the STIX language specs along with the initial STIX XML Binding spec as an exemplar.
I think there is more confusion around exactly what TAXII should be and where the scoping boundary lies between being a framework to support exchange of information and constraining
or implementing specific exchange use cases. I am glad to see this being discussed and would encourage the entire TC community to engage in the discussion as the effects of such decisions have potential implications beyond just TAXII.
Sean Barnum
From: <cti@lists.oasis-open.org> on behalf of "Jacobsen, Jasen W." <jasenj1@mitre.org>
Date: Wednesday, August 19, 2015 at 9:30 AM To: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] Open Question to the CTI Community As one who has been part of implementing the TAXII Java libraries let me throw a few cents on the table.
"(2) All of these combined somehow form an information repository (how things are racked, stacked, and found in the warehouse) and TAXII is the "Amazon"."
To me, TAXII is the interface into the "Amazon". It is the API, not the implementation.
TAXII tries to solve two use cases:
So TAXII is both the FedEx store/post office, and the library reference desk. Implementors determine what kind of trucks they want to use, and how to build their library, but TAXII provides a common entry point.
- Jasen.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]