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] TAXII Protocol Shortlist


I would also offer my support toward HTTP for the same reasons outlined below, as well as one other - most companies with threat sharing APIs are already using HTTP for their proprietary APIs (example see Facebook, most threat stream vendors...).

If we want them to standardize on TAXII, keeping at least the transport protocol makes that a much easier pill to swallow, since it will be easier to integrate into their product suite in a backward compatible fashion.

-
Jason Keirstead
Product Architect, Security Intelligence, IBM Security Systems
www.ibm.com/security | www.securityintelligence.com

Without data, all you are is just another person with an opinion - Unknown


Inactive hide details for "Davidson II, Mark S" ---2015/08/27 03:31:27 PM---Just to throw another thought into the mix – HTTP "Davidson II, Mark S" ---2015/08/27 03:31:27 PM---Just to throw another thought into the mix – HTTP does not preclude messaging backends. In fact, man

From: "Davidson II, Mark S" <mdavidson@mitre.org>
To: "Jordan, Bret" <bret.jordan@bluecoat.com>, "Wunder, John A." <jwunder@mitre.org>, "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org>
Date: 2015/08/27 03:31 PM
Subject: RE: [cti-taxii] TAXII Protocol Shortlist
Sent by: <cti-taxii@lists.oasis-open.org>





Just to throw another thought into the mix – HTTP does not preclude messaging backends. In fact, many messaging products have HTTP interfaces.

-Mark



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