Re: [cti] Statements of Use

On Fri, Jun 19, 2020 at 3:25 PM Allan Thomson <athomson@lookingglasscyber.com> wrote:

Chet â my SoU was not shared broadly (yet). It was only shared with the CTI co-chairs and OASIS.

Â

Not sure what the plan is in terms of making public but I donât see any big concern about making it more public if that is the plan.

Â

Allan Thomson

CTO (+1-408-331-6646)

LookingGlass Cyber Solutions

Â

From: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> on behalf of Chet Ensign <chet.ensign@oasis-open.org>
Date: Friday, June 19, 2020 at 12:18 PM
To: "Taylor, Marlon" <Marlon.Taylor@cisa.dhs.gov>
Cc: Bret Jordan <bret.jordan@broadcom.com>, "cti@lists.oasis-open.org" <cti@lists.oasis-open.org>
Subject: Re: [cti] Statements of Use

Â

THIS EMAIL ORIGINATES FROM OUTSIDE OF LOOKINGGLASS

Hi Marlon,Â

Â

Not by our rules. You simply assert that you made an implementation of the CS and then the TC gets to decide whether to accept it or request more information or etc. If you have done interop testing, you are certainly free to explain that. More detail as in Allan's SoU certainly gives more meat to your statement and more confidence to those reading it. But it isn't required.Â

Â

/chet

Â

On Fri, Jun 19, 2020 at 2:59 PM Taylor, Marlon <Marlon.Taylor@cisa.dhs.gov> wrote:

Hi Chet and CTI TC Leadership,

Â

Is interop testing with other implementations required as a prerequisite to providing a Statement of Use?

Â

Thanks for your guidance,

Â

-Marlon

Â

From: cti@lists.oasis-open.org <cti@lists.oasis-open.org> On Behalf Of Chet Ensign
Sent: Friday, June 19, 2020 11:13 AM
To: Bret Jordan <bret.jordan@broadcom.com>
Cc: OASIS CTI TC Discussion List <cti@lists.oasis-open.org>
Subject: Re: [cti] Statements of Use

Â

CAUTION: This email originated from outside of DHS. DO NOT click links or open attachments unless you recognize and/or trust the sender. Contact your component SOC with questions or concerns.

Â

All, here is a sample, minimal template you can fill in. You can always add more detail:ÂÂ

Â

<statement provider> has successfully implemented <committee spec title> Version ## Committee Specification ## (<url to cs if you wish>) approved on <date> in accordance with the conformance clauses defined in Section ## <or state a subset of the clauses>.
This use of the specification includes interoperation with other independent implementations.

Â

On Thu, Jun 18, 2020 at 11:11 AM Bret Jordan <bret.jordan@broadcom.com> wrote:

All,

On this morning's call I took an action item to get a list of statements of use as examples. This should help those organizations that are looking to produce them for STIX 2.1 and TAXII 2.1. We need a minimum of three, but the more the better.

Here are those examples.

SARIF statements of use;
- IBM: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/202001/msg00005.html

- Microsoft: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201911/msg00044.html
- SAP: https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201911/msg00037.html

TOSCA Simple Profile in YAML;
- Jheronimus Academy of Data Sciences - https://lists.oasis-open.org/archives/tosca/201910/msg00026.html
- Ubicity Corp. - https://lists.oasis-open.org/archives/tosca/201910/msg00031.html
- XLAB d.o.o. - https://lists.oasis-open.org/archives/tosca/201910/msg00032.html
- Tal Liron - https://lists.oasis-open.org/archives/tosca/201910/msg00039.html

KMIP;
Cryptsoft: https://www.oasis-open.org/committees/download.php/65609/KMIP-SOU-Cryptsoft-10-Jul-2019.pdf
P6R: https://www.oasis-open.org/committees/download.php/65613/KMIP-SOU-P6R-12-July-2019.pdf
Semper Fortis: https://www.oasis-open.org/committees/download.php/65652/KMIP%20SOU-SFS-17-July-2019.pdf

Â

Thanks,

Bret

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."

Â

--

/chetÂ
----------------

Chet Ensign

Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society
http://www.oasis-open.org

Mobile: +1 201-341-1393Â

Â

--

/chetÂ
----------------

Chet Ensign

Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society
http://www.oasis-open.org

Mobile: +1 201-341-1393Â

cti message