Next in thread → Next in month →

RE: [cti] STIX Subcommittee Nomination

From
Peter F Brown <>
Date
2015-06-19T20:23:40+00:00
ID
Thread
RE: [cti] STIX Subcommittee Nomination
+1

 

From:  [mailto:]
On Behalf Of Barnum, Sean D.

Sent: 18 June, 2015 12:43

To: Joep Gommers; Jordan, Bret; Aharon Chernin

Cc: ; ; 

Subject: Re: [cti] STIX Subcommittee Nomination

 

So, the typical way of doing this would be to have a single STIX SC with multiple work product efforts (e.g. STIX 1.x & STIX 2.0) underway with different editors
 and contributors.

This provides the coordination and communication Aharon describes as well as the separate focus that Bret, et al, describe.

This is true of almost all SDOs and I think still meets the objectives you are all conveying here.

 

sean

 

From:
Joep Gommers <>

Date: Thursday, June 18, 2015 at 3:33 PM

To: "Jordan, Bret" <>, Aharon Chernin <>

Cc: "" <>, "" <>,
 "" <>

Subject: Re: [cti] STIX Subcommittee Nomination

 

I can also see some advantage with regards to focus. Separate work stream with separate cadence, leadership expertise, etc might be helpful. J-

 

From:
"Jordan, Bret" <>

Date: Thursday, June 18, 2015 at 9:26 PM

To: Aharon Chernin <>

Cc: "" <>, "" <>,
 "" <>

Subject: Re: [cti] STIX Subcommittee Nomination

 

The same people may be on both subcommittees.  By breaking them up this allows each subcommittee to focus on different things.  There are some people that will
 not care about STIX 1.3 and some that will not care about STIX 2.0

 

Thanks,

 

Bret

 

 

 

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 62A6 5999 0F7D 0D61 4C66 D59C 2DB5 111D 63BC A303

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

 

On Jun 18, 2015, at 13:23, Aharon Chernin <> wrote:

 

I think a single STIX committee will ensure good communication between the folks working STIX 1.x and STIX 2.x. This may also improve interoperability between
 the two major releases.

 

Aharon Chernin

CTO

SOLTRA |
 An FS-ISAC & DTCC Company

18301 Bermuda green Dr

Tampa, fl 33647

813.470.2173 | 

www.soltra.com

From: 
 <> on behalf of Jordan, Bret <>

Sent: Thursday, June 18, 2015 3:20 PM

To: 

Cc: ;


Subject: Re: [cti] STIX Subcommittee Nomination

 

I am against the idea of creating a single STIX working group.  STIX 1.3 and STIX 2.0 are two totally different animals and we do not want to bog one down
 to work on the other.     

 

I could see Aharon and Sean co-Chairing the STIX 1.3 sub committee.  I would be good with that.  

 

Thanks,

 

Bret

 

 

 

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 62A6 5999 0F7D 0D61 4C66 D59C 2DB5 111D 63BC A303

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

 

On Jun 18, 2015, at 13:10, Tony Rutkowski <> wrote:

 

Yaana seconds the proposal

On 2015-06-18 3:08 PM,  wrote:

Hi All, 

I am submitting a proposal to create a STIX subcommittee and nominate Aharon Chernin & Sean Barnum as co-chairs 

The STIX subcommittee will maintain and steer the future direction of the Structured Threat Information _expression_ language. 

Deliverables: 

Create a roadmap for STIX 1.x

Maintain and enhance STIX 1.x as necessary

Create a roadmap for STIX 2.x

Design and create STIX 2.x 

STIX Documentation

 

Regards, 

Mona Magathan 

Information Security Services   

U.S. Bank 

(206) 225.7519

U.S. BANCORP made the following annotations

---------------------------------------------------------------------

Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary
 in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received
 this communication in error, and then immediately delete it. Thank you in advance for your cooperation.

--------------------------------------------------------------------- 

 

-- 

________________________________ 

Anthony Michael Rutkowski

EVP, Industry Standards & Regulatory Affairs 



+1 703 999 8270

________________________________ 

Yaana Technologies LLC 

 

542 Gibraltar Drive 

Milpitas CA 95035 USA
Next in thread → Next in month →