OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cti-taxii message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [cti-taxii] RE: Vision Statement for TAXII

I think this proposed language works.
I think it would be better without the bracketed content and I would suggest changing the wording "TAXII reduces the friction ..." To something more like "TAXII focuses on reducing the friction ..."
We should be careful to avoid assertions of success before they occur.

My only other point of potential concern (though less than the other areas) is that the word "protocol" while not inaccurate (like Rich's concern with "technology") has the potential to be misinterpreted in an overly constrained way. Some people may immediately think of it as only a specific transport protocol (http) rather than the services and message flows for the CTI exchange use cases. We don't want people to think we are reinventing any wheels.


Sent with Good (www.good.com)

From: cti-taxii@lists.oasis-open.org <cti-taxii@lists.oasis-open.org> on behalf of Wunder, John A. <jwunder@mitre.org>
Sent: Tuesday, September 15, 2015 11:27:39 AM
To: 'cti-taxii@lists.oasis-open.org'
Subject: Re: [cti-taxii] RE: Vision Statement for TAXII
Just spitballing here:

TAXII is an open protocol that enables rapid, secure, and trusted sharing of cyber threat intelligence between people and systems. With a focus on simple and reusable concepts, TAXII reduces the friction of sharing cyber threat intelligence among disparate tools, organizations, and ecosystems [without prescribing specific trust agreements, governance, or sharing policies].

I’d go either way on the section in the brackets…do people often misunderstand and think that TAXII prescribes trust agreements, governance, sharing policies, etc? If so, maybe include it. Otherwise it’s extraneous and could even sound defensive.


From: <cti-taxii@lists.oasis-open.org> on behalf of "Richard.Struse@HQ.DHS.GOV"
Date: Tuesday, September 15, 2015 at 10:58 AM
To: "'cti-taxii@lists.oasis-open.org'"
Subject: Re: [cti-taxii] RE: Vision Statement for TAXII

The original paragraphs were clearly too verbose and lacked punch. However, the proposed language seems somehow too vague and does read like ad copy.

I'm also not thrilled with talking about TAXII as a "technology". While I think we all know what is meant by that, others might infer that TAXII is a specific thing when it is in fact a series of specifications. I'd urge us to consider making it clear what TAXII is. The original paragraph did that well.

From: Eric Burger [mailto:Eric.Burger@georgetown.edu]
Sent: Tuesday, September 15, 2015 09:22 AM Eastern Standard Time
To: cti-taxii@lists.oasis-open.org <cti-taxii@lists.oasis-open.org>
Subject: Re: [cti-taxii] RE: Vision Statement for TAXII

Looks like it was written by a Mad Men copy writer. Does it say anything?

Sent from my mobile device. Thanks be to LEMONADE: http://www.standardstrack.com/ietf/lemonade
S2ERC: http://s2erc.georgetown.edu/
GCSC: http://gcsc.georgetown.edu/
Me: http://www.cs.georgetown.edu/~ eburger

On Sep 14, 2015 12:06 PM, "Davidson II, Mark S" <mdavidson@mitre.org> wrote:



The statement Bret shared below is intended to be the kind of statement that we can make future decisions around. When a contentious issue comes up, one factor will be how well various options match the vision statement.


When people write articles about TAXII, they are going to use our vision statement – this is our opportunity to get the first word into many TAXII discussions. Having a good vision statement is important.


For comparison, the equivalent text for TAXII 1.0 and TAXII 1.1 was:

TAXII defines a set of services and message exchanges that, when implemented, enable sharing of actionable cyber threat information across organization and product/service boundaries. TAXII defines services, protocols and messages to exchange cyber threat information for the detection, prevention, and mitigation of cyber threats. TAXII is not an information sharing initiative or application and does not attempt to define trust agreements, governance, or non-technical aspects of cyber threat information sharing. Instead, TAXII empowers organizations to achieve improved situational awareness about emerging threats, and enables organizations to easily share the information they choose with the partners they choose all while using a single, common, set of tools.


What do you think? Should we keep the old one? Is the new one better? Would you like to offer a different proposal for consideration?


In an effort to cajole responses out of this subcommittee: I’ll offer to take your silence as complete support of the proposed vision statement and that you have nothing but effusive praise for it. (I’m kidding – but please share your thoughts!).


Let the SC know what you think!


Thank you.



From:cti-taxii@lists.oasis-open.org [mailto:cti-taxii@lists.oasis-open.org] On Behalf Of Jordan, Bret
Sent: Friday, September 11, 2015 8:42 AM
To: cti-taxii@lists.oasis-open.org
Subject: [cti-taxii] Vision Statement for TAXII




During our last call we had a good conversation about the need to establish some top level elements for this subcommittee, these include things like vision, scope, and purpose. We would like to propose the following vision/purpose statement for your review.   


"TAXII is a threat sharing technology that enables rapid, secure, and trusted communications between people and systems through simple, powerful, and reusable concepts. TAXII users have faster response times, better ROI, and more effective cyber defenses."








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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]