[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-taxii] The need (or no need) for TAXII to support Query
Thanks for the insight in to what you all need. I think your view is very similar to what I would like to see. Structurally I am just calling it something different... <me personally, not as co-chair> I would like to see three work products be delivered out of the TAXII SC. 1) TAXII Specification for transporting CTI HTTPS REST HTTP Basic + JWT Extension Points for other authentication system And possible a few other minor things here and there 2) A Query Specification that plugs in to the TAXII REST API HTTPS REST 3) Build a getting started guide to add some context around how you might build a storage repository for TAXII. Most of this would be implementation or deployment specific and not specification related, but I think it would be good to help people understand from those of us that think about TAXII all day long, how we envision it working. Query would be Optional to implement. However, if you do implement it, it would look and feel like it belongs, not like it was patched in as a secondary after thought. </off soap box> What something like this be acceptable to everyone? Please push back. Thanks, Bret 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."
|
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]