CTI TAXII Subcommittee

 View Only
Expand all | Collapse all

Protocol Shortlist - Add HTTP

  • 1.  Protocol Shortlist - Add HTTP

    Posted 08-25-2015 17:56
    All,   As I mentioned in a previous email, not having a protocol to work with has ended up slowing down prototype work. IMO, a shortlist of protocols needs to be picked for prototyping efforts, and I’d like to start that by proposing HTTP be added to the shortlist. That will unblock me so I can write some code that does something. I think HTTP meets our requirements and also works well with Sergey’s idea of incremental change.   Here’s my take on how HTTP stacks up to the protocol requirements we’ve written down so far [1]:   > 1. Minimal changes to existing firewall deployments AFAIK, just about every FW everywhere let’s HTTP and HTTPS through, so I think this one is met.   > 2. Robust ecosystem of TAXII Server platforms There are lots of platforms (Web Servers, Messaging Products, etc) that support HTTP or have HTTP interfaces. I’d go as far as to say that I don’t think choosing HTTP would preclude any technology stack that I’ve been exposed to.   > 3. Ubiquitous, well supported client libraries. HTTP has libraries in every language on just about every platform that I know about.   > 4. Well understood by the software development community HTTP is IMO the best understood protocol by the development community.   > 5. Supportable in cloud infrastructures HTTP is used widely in cloud infrastructures   > 6. Integration within existing vendor communication channels I can’t really speak to this one – somebody else will have to chime in.   > 7. Ability to push information from a server to a client This is where native HTTP doesn’t work great. Though perhaps a workaround like long polling could be sufficient.   > 8. Protocol efficiency / minimal verbosity I don’t have any experience or information to make an assessment here.   Please note that this does not represent a group consensus, merely that HTTP is being explored further. Absent dissenting opinions, I’ll work on an HTTP-based prototype and share something about it before too long.   Are there other protocols that should be added to the shortlist?   Thank you. -Mark   [1] https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements#protocol-requirements


  • 2.  Re: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-25-2015 18:38
    I have also spent a lot of time thinking through the various options, and Mark and I have discussed them at length on a daily basis..  Here is my take, kind of where I am leaning, but please push back or disagree.  I would love to hear your thoughts.   1) The way I see it, it really comes down to a question of doing something over HTTP or something over a messaging protocol, like AMQP, ZeroMQ, etc....   2) HTTP in my option is probably the best and easiest option for us.  So I would agree to add HTTP to the short list.   i) Does everyone agree with this?   ii) Does anyone think we should be looking at something other than HTTP? 3) The biggest draw back to HTTP is the lack of server push.  But I think we can solve that in a very creative way with long-polling that will also be super easy to implement.   So in regards to a TAXII 2.0 vs TAXII 1.5...  I think the small and important changes we would make will result in a breaking change, thus I think the need for a TAXII 2.0..  However, I do not think we have done a good job thus far marketing our message to the community.  I do not think TAXII 2.0 is as scary and new as it may seem from our discussions... Think of it this way: 1) Data-Collections + Data-Feeds = Channels  2) We add a real security and authentication system to TAXII, thus user authentication, groups, and policies on channels. 3) We simplify the messages and the back and forth that exists in TAXII 1.1 to make TAXII 2.0 easier and faster 4) We define TAXII 2.0 to have some base level functionality that every TAXII server MUST have.  This, I believe, will make it easier for people and vendors to use TAXII... They will know what is there. For example, Soltra had to start shipping their solution with default Data-Collections and such already configured, so that people could use it out of the box.   When we start looking at it like that. Then I think TAXII 2.0 is not so scary and seems a lot more like TAXII 1.1, just better, easier, and faster.  Please spend some time thinking about the idea of continuing to use HTTP as the transport for TAXII and either give your comments on the list or come to the next call in 2 weeks ready to express your options. I would really like to get this initial decision out of the way sooner rather than later as it is will impact a lot of future decisions.   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.   On Aug 25, 2015, at 11:56, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote: All,   As I mentioned in a previous email, not having a protocol to work with has ended up slowing down prototype work. IMO, a shortlist of protocols needs to be picked for prototyping efforts, and I’d like to start that by proposing HTTP be added to the shortlist. That will unblock me so I can write some code that does something. I think HTTP meets our requirements and also works well with Sergey’s idea of incremental change.   Here’s my take on how HTTP stacks up to the protocol requirements we’ve written down so far [1]:   > 1. Minimal changes to existing firewall deployments AFAIK, just about every FW everywhere let’s HTTP and HTTPS through, so I think this one is met.   > 2. Robust ecosystem of TAXII Server platforms There are lots of platforms (Web Servers, Messaging Products, etc) that support HTTP or have HTTP interfaces. I’d go as far as to say that I don’t think choosing HTTP would preclude any technology stack that I’ve been exposed to.   > 3. Ubiquitous, well supported client libraries. HTTP has libraries in every language on just about every platform that I know about.   > 4. Well understood by the software development community HTTP is IMO the best understood protocol by the development community.   > 5. Supportable in cloud infrastructures HTTP is used widely in cloud infrastructures   > 6. Integration within existing vendor communication channels I can’t really speak to this one – somebody else will have to chime in.   > 7. Ability to push information from a server to a client This is where native HTTP doesn’t work great. Though perhaps a workaround like long polling could be sufficient.   > 8. Protocol efficiency / minimal verbosity I don’t have any experience or information to make an assessment here.   Please note that this does not represent a group consensus, merely that HTTP is being explored further. Absent dissenting opinions, I’ll work on an HTTP-based prototype and share something about it before too long.   Are there other protocols that should be added to the shortlist?   Thank you. -Mark   [1]   https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements#protocol-requirements Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 3.  Re: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-25-2015 20:32
    I think HTTP/2.0 should be on the short list as well, as it also meets all the requirements, and enables various additional capabilities. - 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 "Davidson II, Mark S" ---2015/08/25 02:57:00 PM---All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing dow From: "Davidson II, Mark S" <mdavidson@mitre.org> To: "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org> Date: 2015/08/25 02:57 PM Subject: [cti-taxii] Protocol Shortlist - Add HTTP Sent by: <cti-taxii@lists.oasis-open.org> All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing down prototype work. IMO, a shortlist of protocols needs to be picked for prototyping efforts, and I’d like to start that by proposing HTTP be added to the shortlist. That will unblock me so I can write some code that does something. I think HTTP meets our requirements and also works well with Sergey’s idea of incremental change. Here’s my take on how HTTP stacks up to the protocol requirements we’ve written down so far [1]: > 1. Minimal changes to existing firewall deployments AFAIK, just about every FW everywhere let’s HTTP and HTTPS through, so I think this one is met. > 2. Robust ecosystem of TAXII Server platforms There are lots of platforms (Web Servers, Messaging Products, etc) that support HTTP or have HTTP interfaces. I’d go as far as to say that I don’t think choosing HTTP would preclude any technology stack that I’ve been exposed to. > 3. Ubiquitous, well supported client libraries. HTTP has libraries in every language on just about every platform that I know about. > 4. Well understood by the software development community HTTP is IMO the best understood protocol by the development community. > 5. Supportable in cloud infrastructures HTTP is used widely in cloud infrastructures > 6. Integration within existing vendor communication channels I can’t really speak to this one – somebody else will have to chime in. > 7. Ability to push information from a server to a client This is where native HTTP doesn’t work great. Though perhaps a workaround like long polling could be sufficient. > 8. Protocol efficiency / minimal verbosity I don’t have any experience or information to make an assessment here. Please note that this does not represent a group consensus, merely that HTTP is being explored further. Absent dissenting opinions, I’ll work on an HTTP-based prototype and share something about it before too long. Are there other protocols that should be added to the shortlist? Thank you. -Mark [1] https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements#protocol-requirements




  • 4.  Re: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-25-2015 21:21
    I can go with HTTP/2 and that might even solve more of our problems and help us look slightly more progressive without the scary factor.  So as of right now we have two options for a protocol... HTTP/1.1 HTTP/2 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.   On Aug 25, 2015, at 12:21, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: I think HTTP/2.0 should be on the short list as well, as it also meets all the requirements, and enables various additional capabilities. - 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 <graycol.gif> Davidson II, Mark S ---2015/08/25 02:57:00 PM---All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing dow From: Davidson II, Mark S < mdavidson@mitre.org > To: cti-taxii@lists.oasis-open.org < cti-taxii@lists.oasis-open.org > Date: 2015/08/25 02:57 PM Subject: [cti-taxii] Protocol Shortlist - Add HTTP Sent by: < cti-taxii@lists.oasis-open.org > All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing down prototype work. IMO, a shortlist of protocols needs to be picked for prototyping efforts, and I’d like to start that by proposing HTTP be added to the shortlist. That will unblock me so I can write some code that does something. I think HTTP meets our requirements and also works well with Sergey’s idea of incremental change. Here’s my take on how HTTP stacks up to the protocol requirements we’ve written down so far [1]: > 1. Minimal changes to existing firewall deployments AFAIK, just about every FW everywhere let’s HTTP and HTTPS through, so I think this one is met. > 2. Robust ecosystem of TAXII Server platforms There are lots of platforms (Web Servers, Messaging Products, etc) that support HTTP or have HTTP interfaces. I’d go as far as to say that I don’t think choosing HTTP would preclude any technology stack that I’ve been exposed to. > 3. Ubiquitous, well supported client libraries. HTTP has libraries in every language on just about every platform that I know about. > 4. Well understood by the software development community HTTP is IMO the best understood protocol by the development community. > 5. Supportable in cloud infrastructures HTTP is used widely in cloud infrastructures > 6. Integration within existing vendor communication channels I can’t really speak to this one – somebody else will have to chime in. > 7. Ability to push information from a server to a client This is where native HTTP doesn’t work great. Though perhaps a workaround like long polling could be sufficient. > 8. Protocol efficiency / minimal verbosity I don’t have any experience or information to make an assessment here. Please note that this does not represent a group consensus, merely that HTTP is being explored further. Absent dissenting opinions, I’ll work on an HTTP-based prototype and share something about it before too long. Are there other protocols that should be added to the shortlist? Thank you. -Mark [1] https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements#protocol-requirements Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 5.  RE: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-26-2015 11:32




    Dumb question – what has to change in application code if HTTP/2 is used?
     
    Asking the question another way – if I write a Python/Django web app for HTTP/1.1 that runs on Apache, what modifications would I need to make in order to support
    Apache’s HTTP/2 functionality?
     
    Based on what I’ve read, it sounds like application code will have to change very little, if at all. There is a presumption that due to the similarities between
    HTTP/1.1 and HTTP/2, thigs like Django (or the underlying WSGI) won’t need to change their interface very much, and therefore will have minimal impact to application developers.

     
    As I understand it, HTTP/2 adds some new features (Server Push and Stream Prioritization) that will eventually propagate up to the web developer level, and other
    features (e.g., binary encoding) will be handled transparently by the underlying webserver.
     
    This was based on a few minutes of internet searching, so please let me know what I got wrong.
     
    If my assumptions are correct, it seems we can for the most part proceed with a general notion of HTTP and then make a value decision about HTTP/1.1 vs HTTP/2
    later on.
     
    Thank you.
    -Mark
     


    From: Jordan, Bret [mailto:bret.jordan@bluecoat.com]

    Sent: Tuesday, August 25, 2015 5:21 PM
    To: Jason Keirstead <Jason.Keirstead@ca.ibm.com>
    Cc: Davidson II, Mark S <mdavidson@mitre.org>; cti-taxii@lists.oasis-open.org
    Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP


     
    I can go with HTTP/2 and that might even solve more of our problems and help us look slightly more progressive without the scary factor.  So as of right now we have two options for a protocol...

     


               
    HTTP/1.1


               
    HTTP/2


     










     


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









     



    On Aug 25, 2015, at 12:21, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote:

     



    I think HTTP/2.0 should be on the short list as well, as it also meets all the requirements, and enables various additional capabilities.

    -
    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


    <graycol.gif> "Davidson II, Mark S" ---2015/08/25 02:57:00 PM---All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing dow

    From: "Davidson II, Mark S" < mdavidson@mitre.org >
    To: " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org >
    Date: 2015/08/25 02:57 PM
    Subject: [cti-taxii] Protocol Shortlist - Add HTTP
    Sent by: < cti-taxii@lists.oasis-open.org >







    All,

    As I mentioned in a previous email, not having a protocol to work with has ended up slowing down prototype work. IMO, a shortlist of protocols needs to be picked for prototyping efforts, and I’d like to start that
    by proposing HTTP be added to the shortlist. That will unblock me so I can write some code that does something. I think HTTP meets our requirements and also works well with Sergey’s idea of incremental change.

    Here’s my take on how HTTP stacks up to the protocol requirements we’ve written down so far [1]:

    > 1. Minimal changes to existing firewall deployments
    AFAIK, just about every FW everywhere let’s HTTP and HTTPS through, so I think this one is met.

    > 2. Robust ecosystem of TAXII Server platforms
    There are lots of platforms (Web Servers, Messaging Products, etc) that support HTTP or have HTTP interfaces. I’d go as far as to say that I don’t think choosing HTTP would preclude any technology stack that I’ve
    been exposed to.

    > 3. Ubiquitous, well supported client libraries.
    HTTP has libraries in every language on just about every platform that I know about.


    > 4. Well understood by the software development community
    HTTP is IMO the best understood protocol by the development community.

    > 5. Supportable in cloud infrastructures
    HTTP is used widely in cloud infrastructures

    > 6. Integration within existing vendor communication channels
    I can’t really speak to this one – somebody else will have to chime in.

    > 7. Ability to push information from a server to a client
    This is where native HTTP doesn’t work great. Though perhaps a workaround like long polling could be sufficient.

    > 8. Protocol efficiency / minimal verbosity
    I don’t have any experience or information to make an assessment here.

    Please note that this does not represent a group consensus, merely that HTTP is being explored further. Absent dissenting opinions, I’ll work on an HTTP-based prototype and share something about it before too long.

    Are there other protocols that should be added to the shortlist?

    Thank you.
    -Mark

    [1]
    https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements#protocol-requirements




     








  • 6.  RE: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-26-2015 12:10
    There are a number of facilities available in HTTP/2.0 that could be of great use to TAXII - for example, as you mentioned below, server push. If HTTP/2.0 is part of the specification, then these facilities can be assumed to be present and we can utilize them in the TAXII specification. If not, then we are stuck with HTTP/1.1 facilities. The answer to "how much would the application code have to know" also depends. For a protocol like TAXII, it depends very much on how it is written and where it is running. It is not always going to be an option for someone implementing a TAXII service to simply stick an Apache instance in front, for example if it is for example running on an embedded device. - 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 "Davidson II, Mark S" ---2015/08/26 08:32:23 AM---Dumb question – what has to change in application code if HTTP/2 is used? Asking the question anothe From: "Davidson II, Mark S" <mdavidson@mitre.org> To: "Jordan, Bret" <bret.jordan@bluecoat.com>, Jason Keirstead/CanEast/IBM@IBMCA Cc: "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org> Date: 2015/08/26 08:32 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP Sent by: <cti-taxii@lists.oasis-open.org> Dumb question – what has to change in application code if HTTP/2 is used? Asking the question another way – if I write a Python/Django web app for HTTP/1.1 that runs on Apache, what modifications would I need to make in order to support Apache’s HTTP/2 functionality? Based on what I’ve read, it sounds like application code will have to change very little, if at all. There is a presumption that due to the similarities between HTTP/1.1 and HTTP/2, thigs like Django (or the underlying WSGI) won’t need to change their interface very much, and therefore will have minimal impact to application developers. As I understand it, HTTP/2 adds some new features (Server Push and Stream Prioritization) that will eventually propagate up to the web developer level, and other features (e.g., binary encoding) will be handled transparently by the underlying webserver. This was based on a few minutes of internet searching, so please let me know what I got wrong. If my assumptions are correct, it seems we can for the most part proceed with a general notion of HTTP and then make a value decision about HTTP/1.1 vs HTTP/2 later on. Thank you. -Mark From: Jordan, Bret [ mailto:bret.jordan@bluecoat.com ] Sent: Tuesday, August 25, 2015 5:21 PM To: Jason Keirstead <Jason.Keirstead@ca.ibm.com> Cc: Davidson II, Mark S <mdavidson@mitre.org>; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP I can go with HTTP/2 and that might even solve more of our problems and help us look slightly more progressive without the scary factor. So as of right now we have two options for a protocol... HTTP/1.1 HTTP/2 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." On Aug 25, 2015, at 12:21, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: I think HTTP/2.0 should be on the short list as well, as it also meets all the requirements, and enables various additional capabilities. - 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 <graycol.gif> "Davidson II, Mark S" ---2015/08/25 02:57:00 PM---All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing dow From: "Davidson II, Mark S" < mdavidson@mitre.org > To: " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org > Date: 2015/08/25 02:57 PM Subject: [cti-taxii] Protocol Shortlist - Add HTTP Sent by: < cti-taxii@lists.oasis-open.org > All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing down prototype work. IMO, a shortlist of protocols needs to be picked for prototyping efforts, and I’d like to start that by proposing HTTP be added to the shortlist. That will unblock me so I can write some code that does something. I think HTTP meets our requirements and also works well with Sergey’s idea of incremental change. Here’s my take on how HTTP stacks up to the protocol requirements we’ve written down so far [1]: > 1. Minimal changes to existing firewall deployments AFAIK, just about every FW everywhere let’s HTTP and HTTPS through, so I think this one is met. > 2. Robust ecosystem of TAXII Server platforms There are lots of platforms (Web Servers, Messaging Products, etc) that support HTTP or have HTTP interfaces. I’d go as far as to say that I don’t think choosing HTTP would preclude any technology stack that I’ve been exposed to. > 3. Ubiquitous, well supported client libraries. HTTP has libraries in every language on just about every platform that I know about. > 4. Well understood by the software development community HTTP is IMO the best understood protocol by the development community. > 5. Supportable in cloud infrastructures HTTP is used widely in cloud infrastructures > 6. Integration within existing vendor communication channels I can’t really speak to this one – somebody else will have to chime in. > 7. Ability to push information from a server to a client This is where native HTTP doesn’t work great. Though perhaps a workaround like long polling could be sufficient. > 8. Protocol efficiency / minimal verbosity I don’t have any experience or information to make an assessment here. Please note that this does not represent a group consensus, merely that HTTP is being explored further. Absent dissenting opinions, I’ll work on an HTTP-based prototype and share something about it before too long. Are there other protocols that should be added to the shortlist? Thank you. -Mark [1] https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements#protocol-requirements




  • 7.  RE: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-26-2015 12:46




    From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter
    in regard to TAXII.
     
    I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I
    understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png) and the response to that promised request. The rules are:
    ·         
    Promised requests MUST be cacheable
    ·         
    MUST be safe (a.k.a “Read Only”)
    ·         
    MUST NOT include a request body
     
    These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let
    me just go ahead and send those to you before you ask for them”.
     
    In thinking how this might work for messaging, you’d almost have to have a URL structure like this:
    http://hostname/<group>/<channel>/<message-id>, where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/)
    would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context.
     
    I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t
    been discussed yet. We will be able to prove these out with prototypes one way or another.
     
    In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something
    that makes sense for TAXII.
     
    -Mark
    [1] https://httpwg.github.io/specs/rfc7540.html#PushResources
     


    From: cti-taxii@lists.oasis-open.org [mailto:cti-taxii@lists.oasis-open.org]
    On Behalf Of Jason Keirstead
    Sent: Wednesday, August 26, 2015 8:10 AM
    To: Davidson II, Mark S <mdavidson@mitre.org>
    Cc: Jordan, Bret <bret.jordan@bluecoat.com>; cti-taxii@lists.oasis-open.org
    Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP


     
    There are a number of facilities available in HTTP/2.0 that could be of great use to TAXII - for example, as you mentioned below, server push. If HTTP/2.0 is part of the specification, then these facilities can be assumed to be present
    and we can utilize them in the TAXII specification. If not, then we are stuck with HTTP/1.1 facilities.


    The answer to "how much would the application code have to know" also depends. For a protocol like TAXII, it depends very much on how it is written and where it is running. It is not always going to be an option for someone implementing a TAXII service to simply
    stick an Apache instance in front, for example if it is for example running on an embedded device.


    -
    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


    "Davidson
    II, Mark S" ---2015/08/26 08:32:23 AM---Dumb question – what has to change in application code if HTTP/2 is used? Asking the question anothe

    From: "Davidson II, Mark S" < mdavidson@mitre.org >
    To: "Jordan, Bret" < bret.jordan@bluecoat.com >, Jason Keirstead/CanEast/IBM@IBMCA
    Cc: " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org >
    Date: 2015/08/26 08:32 AM
    Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP
    Sent by: < cti-taxii@lists.oasis-open.org >






    Dumb question – what has to change in application code if HTTP/2 is used?

    Asking the question another way – if I write a Python/Django web app for HTTP/1.1 that runs on Apache, what modifications would I need to make in order to support Apache’s HTTP/2 functionality?

    Based on what I’ve read, it sounds like application code will have to change very little, if at all. There is a presumption that due to the similarities between HTTP/1.1 and HTTP/2, thigs like Django
    (or the underlying WSGI) won’t need to change their interface very much, and therefore will have minimal impact to application developers.


    As I understand it, HTTP/2 adds some new features (Server Push and Stream Prioritization) that will eventually propagate up to the web developer level, and other features (e.g., binary encoding) will
    be handled transparently by the underlying webserver.

    This was based on a few minutes of internet searching, so please let me know what I got wrong.

    If my assumptions are correct, it seems we can for the most part proceed with a general notion of HTTP and then make a value decision about HTTP/1.1 vs HTTP/2 later on.

    Thank you.
    -Mark
    From: Jordan, Bret [ mailto:bret.jordan@bluecoat.com ]

    Sent: Tuesday, August 25, 2015 5:21 PM
    To: Jason Keirstead < Jason.Keirstead@ca.ibm.com >
    Cc: Davidson II, Mark S < mdavidson@mitre.org >;
    cti-taxii@lists.oasis-open.org
    Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP

    I can go with HTTP/2 and that might even solve more of our problems and help us look slightly more progressive without the scary factor. So as of right now we have two options for a protocol...

    HTTP/1.1
    HTTP/2


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

    On Aug 25, 2015, at 12:21, Jason Keirstead < Jason.Keirstead@ca.ibm.com >
    wrote:

    I think HTTP/2.0 should be on the short list as well, as it also meets all the requirements, and enables various additional capabilities.

    -
    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


    <graycol.gif> "Davidson II, Mark S" ---2015/08/25 02:57:00 PM---All, As I mentioned in a previous email, not having a protocol to work with has ended up slowing dow

    From: "Davidson II, Mark S" < mdavidson@mitre.org >
    To: " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org >
    Date: 2015/08/25 02:57 PM
    Subject: [cti-taxii] Protocol Shortlist - Add HTTP
    Sent by: < cti-taxii@lists.oasis-open.org >







    All,

    As I mentioned in a previous email, not having a protocol to work with has ended up slowing down prototype work. IMO, a shortlist of protocols needs to be picked for prototyping efforts, and I’d like to start that by proposing HTTP be added to the shortlist.
    That will unblock me so I can write some code that does something. I think HTTP meets our requirements and also works well with Sergey’s idea of incremental change.

    Here’s my take on how HTTP stacks up to the protocol requirements we’ve written down so far [1]:

    > 1. Minimal changes to existing firewall deployments
    AFAIK, just about every FW everywhere let’s HTTP and HTTPS through, so I think this one is met.

    > 2. Robust ecosystem of TAXII Server platforms
    There are lots of platforms (Web Servers, Messaging Products, etc) that support HTTP or have HTTP interfaces. I’d go as far as to say that I don’t think choosing HTTP would preclude any technology stack that I’ve been exposed to.

    > 3. Ubiquitous, well supported client libraries.
    HTTP has libraries in every language on just about every platform that I know about.


    > 4. Well understood by the software development community
    HTTP is IMO the best understood protocol by the development community.

    > 5. Supportable in cloud infrastructures
    HTTP is used widely in cloud infrastructures

    > 6. Integration within existing vendor communication channels
    I can’t really speak to this one – somebody else will have to chime in.

    > 7. Ability to push information from a server to a client
    This is where native HTTP doesn’t work great. Though perhaps a workaround like long polling could be sufficient.

    > 8. Protocol efficiency / minimal verbosity
    I don’t have any experience or information to make an assessment here.

    Please note that this does not represent a group consensus, merely that HTTP is being explored further. Absent dissenting opinions, I’ll work on an HTTP-based prototype and share something about it before too long.

    Are there other protocols that should be added to the shortlist?

    Thank you.
    -Mark

    [1] https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements#protocol-requirements
     
     






  • 8.  RE: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-26-2015 13:14
    Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 "Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: "Davidson II, Mark S" <mdavidson@mitre.org> To: Jason Keirstead/CanEast/IBM@IBMCA Cc: "Jordan, Bret" <bret.jordan@bluecoat.com>, "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org> Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/ <group>/<channel>/<message-id>, where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources




  • 9.  Re: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-26-2015 14:41
    This sounds like a really interesting idea that we need to explore and build code to test.   Does anyone have any objection to moving forward with the two protocols we are discussing? HTTP1/1 HTTP/2 Are there any other protocols we should be looking at?  Please either bring them up on the list or come to the next call prepared to discuss them.  We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems.    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.   On Aug 26, 2015, at 07:01, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 <graycol.gif> Davidson II, Mark S ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: Davidson II, Mark S < mdavidson@mitre.org > To: Jason Keirstead/CanEast/IBM@IBMCA Cc: Jordan, Bret < bret.jordan@bluecoat.com >, cti-taxii@lists.oasis-open.org < cti-taxii@lists.oasis-open.org > Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/ <group>/<channel>/<message-id>, where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 10.  Re: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-27-2015 12:32
    Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks > On 26 Aug 2015, at 16:40, Jordan, Bret <bret.jordan@BLUECOAT.COM> wrote: > > This sounds like a really interesting idea that we need to explore and build code to test. > > Does anyone have any objection to moving forward with the two protocols we are discussing? > > HTTP1/1 > HTTP/2 > > Are there any other protocols we should be looking at? Please either bring them up on the list or come to the next call prepared to discuss them. We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. > > > 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." > >> On Aug 26, 2015, at 07:01, Jason Keirstead <Jason.Keirstead@ca.ibm.com> wrote: >> >> Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. >> >> - >> 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 >> >> >> <graycol.gif>"Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, >> >> From: "Davidson II, Mark S" <mdavidson@mitre.org> >> To: Jason Keirstead/CanEast/IBM@IBMCA >> Cc: "Jordan, Bret" <bret.jordan@bluecoat.com>, "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org> >> Date: 2015/08/26 09:45 AM >> Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP >> >> >> >> >> From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. >> >> I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: >> · Promised requests MUST be cacheable >> · MUST be safe (a.k.a “Read Only”) >> · MUST NOT include a request body >> >> These are clearly optimized for the “I’m sending you a web page with 15 images and 5 javascript/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. >> >> In thinking how this might work for messaging, you’d almost have to have a URL structure like this: >> http://hostname/ <group>/<channel>/<message-id>, where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. >> >> I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. >> >> In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. >> >> -Mark >> [1] https://httpwg.github.io/specs/rfc7540.html#PushResources >> >> > Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 11.  RE: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-27-2015 12:37
    Sergey, Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? -Mark -----Original Message----- From: Sergey Polzunov [ mailto:sergey@intelworks.com ] Sent: Thursday, August 27, 2015 8:32 AM To: Jordan, Bret <bret.jordan@BLUECOAT.COM> Cc: Jason Keirstead <Jason.Keirstead@ca.ibm.com>; Davidson II, Mark S <mdavidson@mitre.org>; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks > On 26 Aug 2015, at 16:40, Jordan, Bret <bret.jordan@BLUECOAT.COM> wrote: > > This sounds like a really interesting idea that we need to explore and build code to test. > > Does anyone have any objection to moving forward with the two protocols we are discussing? > > HTTP1/1 > HTTP/2 > > Are there any other protocols we should be looking at? Please either bring them up on the list or come to the next call prepared to discuss them. We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. > > > 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." > >> On Aug 26, 2015, at 07:01, Jason Keirstead <Jason.Keirstead@ca.ibm.com> wrote: >> >> Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. >> >> - >> 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 >> >> >> <graycol.gif>"Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, >> >> From: "Davidson II, Mark S" <mdavidson@mitre.org> >> To: Jason Keirstead/CanEast/IBM@IBMCA >> Cc: "Jordan, Bret" <bret.jordan@bluecoat.com>, "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org> >> Date: 2015/08/26 09:45 AM >> Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP >> >> >> >> >> From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. >> >> I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: >> · Promised requests MUST be cacheable >> · MUST be safe (a.k.a “Read Only”) >> · MUST NOT include a request body >> >> These are clearly optimized for the “I’m sending you a web page with 15 images and 5 javascript/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. >> >> In thinking how this might work for messaging, you’d almost have to have a URL structure like this: >> http://hostname/ <group>/<channel>/<message-id>, where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. >> >> I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. >> >> In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. >> >> -Mark >> [1] https://httpwg.github.io/specs/rfc7540.html#PushResources >> >> >


  • 12.  Re: [cti-taxii] Protocol Shortlist - Add HTTP

    Posted 08-27-2015 12:49
    yep, looks like it Sergey Polzunov Intelworks > On 27 Aug 2015, at 14:36, Davidson II, Mark S <mdavidson@MITRE.ORG> wrote: > > Sergey, > > Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? > > -Mark > > -----Original Message----- > From: Sergey Polzunov [ mailto:sergey@intelworks.com ] > Sent: Thursday, August 27, 2015 8:32 AM > To: Jordan, Bret <bret.jordan@BLUECOAT.COM> > Cc: Jason Keirstead <Jason.Keirstead@ca.ibm.com>; Davidson II, Mark S <mdavidson@mitre.org>; cti-taxii@lists.oasis-open.org > Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP > > Hey Bret, > > I suggest adding ZMTP ( http://zmtp.org/ ) to the mix > > Thanks, > Sergey Polzunov > Intelworks > > >> On 26 Aug 2015, at 16:40, Jordan, Bret <bret.jordan@BLUECOAT.COM> wrote: >> >> This sounds like a really interesting idea that we need to explore and build code to test. >> >> Does anyone have any objection to moving forward with the two protocols we are discussing? >> >> HTTP1/1 >> HTTP/2 >> >> Are there any other protocols we should be looking at? Please either bring them up on the list or come to the next call prepared to discuss them. We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. >> >> >> 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." >> >>> On Aug 26, 2015, at 07:01, Jason Keirstead <Jason.Keirstead@ca.ibm.com> wrote: >>> >>> Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. >>> >>> - >>> 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 >>> >>> >>> <graycol.gif>"Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, >>> >>> From: "Davidson II, Mark S" <mdavidson@mitre.org> >>> To: Jason Keirstead/CanEast/IBM@IBMCA >>> Cc: "Jordan, Bret" <bret.jordan@bluecoat.com>, "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org> >>> Date: 2015/08/26 09:45 AM >>> Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP >>> >>> >>> >>> >>> From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. >>> >>> I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: >>> · Promised requests MUST be cacheable >>> · MUST be safe (a.k.a “Read Only”) >>> · MUST NOT include a request body >>> >>> These are clearly optimized for the “I’m sending you a web page with 15 images and 5 javascript/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. >>> >>> In thinking how this might work for messaging, you’d almost have to have a URL structure like this: >>> http://hostname/ <group>/<channel>/<message-id>, where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. >>> >>> I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. >>> >>> In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. >>> >>> -Mark >>> [1] https://httpwg.github.io/specs/rfc7540.html#PushResources >>> >>> >> >


  • 13.  TAXII Protocol Shortlist

    Posted 08-27-2015 12:57
    We have three protocols on the short list...   HTTP/1.1 HTTP/2 ZMTP Are there any others we should be actually thinking about or discussing?   If so please suggest them.  I would also like to start hearing pros and cons, discussion / debate about which one to use in the end.  Once we come to a steady state on discussion, we can then proceed to a vote.  Lets take the next few weeks to discuss this.. I really want to hear your opinions.  We will also plan to also discuss this on our next community call, as we stated a few days ago.  We can not really move further on the future of TAXII, as lot of future decisions will be impacted by this one, until this initial decision gets made so lets discuss it and make a decision.  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.   On Aug 27, 2015, at 06:36, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote: Sergey, Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? -Mark -----Original Message----- From: Sergey Polzunov [ mailto:sergey@intelworks.com ] Sent: Thursday, August 27, 2015 8:32 AM To: Jordan, Bret < bret.jordan@BLUECOAT.COM > Cc: Jason Keirstead < Jason.Keirstead@ca.ibm.com >; Davidson II, Mark S < mdavidson@mitre.org >; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks On 26 Aug 2015, at 16:40, Jordan, Bret < bret.jordan@BLUECOAT.COM > wrote: This sounds like a really interesting idea that we need to explore and build code to test. Does anyone have any objection to moving forward with the two protocols we are discussing? HTTP1/1 HTTP/2 Are there any other protocols we should be looking at?  Please either bring them up on the list or come to the next call prepared to discuss them.  We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. 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. On Aug 26, 2015, at 07:01, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 <graycol.gif> Davidson II, Mark S ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: Davidson II, Mark S < mdavidson@mitre.org > To: Jason Keirstead/CanEast/IBM@IBMCA Cc: Jordan, Bret < bret.jordan@bluecoat.com >, cti-taxii@lists.oasis-open.org < cti-taxii@lists.oasis-open.org > Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/<group>/<channel>/<message-id> , where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 14.  Re: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 14:19
    AMQP and potentially MQTT if you want to consider your vision of TAXII Clients on IoT. Sent from Outlook On Thu, Aug 27, 2015 at 5:57 AM -0700, "Jordan, Bret" < bret.jordan@bluecoat.com > wrote: We have three protocols on the short list...   HTTP/1.1 HTTP/2 ZMTP Are there any others we should be actually thinking about or discussing?   If so please suggest them.  I would also like to start hearing pros and cons, discussion / debate about which one to use in the end.  Once we come to a steady state on discussion, we can then proceed to a vote.  Lets take the next few weeks to discuss this.. I really want to hear your opinions.  We will also plan to also discuss this on our next community call, as we stated a few days ago.  We can not really move further on the future of TAXII, as lot of future decisions will be impacted by this one, until this initial decision gets made so lets discuss it and make a decision.  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."  On Aug 27, 2015, at 06:36, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote: Sergey, Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? -Mark -----Original Message----- From: Sergey Polzunov [ mailto:sergey@intelworks.com ] Sent: Thursday, August 27, 2015 8:32 AM To: Jordan, Bret < bret.jordan@BLUECOAT.COM > Cc: Jason Keirstead < Jason.Keirstead@ca.ibm.com >; Davidson II, Mark S < mdavidson@mitre.org >; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks On 26 Aug 2015, at 16:40, Jordan, Bret < bret.jordan@BLUECOAT.COM > wrote: This sounds like a really interesting idea that we need to explore and build code to test. Does anyone have any objection to moving forward with the two protocols we are discussing? HTTP1/1 HTTP/2 Are there any other protocols we should be looking at?  Please either bring them up on the list or come to the next call prepared to discuss them.  We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. 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." On Aug 26, 2015, at 07:01, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 <graycol.gif>"Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: "Davidson II, Mark S" < mdavidson@mitre.org > To: Jason Keirstead/CanEast/IBM@IBMCA Cc: "Jordan, Bret" < bret.jordan@bluecoat.com >, " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org > Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/<group>/<channel>/<message-id> , where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources


  • 15.  RE: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 14:21
    Which version of AMQP? =)   From: cti-taxii@lists.oasis-open.org [mailto:cti-taxii@lists.oasis-open.org] On Behalf Of Patrick Maroney Sent: Thursday, August 27, 2015 10:19 AM To: cti-taxii@lists.oasis-open.org; Jordan, Bret <bret.jordan@bluecoat.com> Subject: Re: [cti-taxii] TAXII Protocol Shortlist   AMQP and potentially MQTT if you want to consider your vision of TAXII Clients on IoT. Sent from Outlook   On Thu, Aug 27, 2015 at 5:57 AM -0700, "Jordan, Bret" < bret.jordan@bluecoat.com > wrote: We have three protocols on the short list...     HTTP/1.1 HTTP/2 ZMTP   Are there any others we should be actually thinking about or discussing?   If so please suggest them.  I would also like to start hearing pros and cons, discussion / debate about which one to use in the end.  Once we come to a steady state on discussion, we can then proceed to a vote.  Lets take the next few weeks to discuss this.. I really want to hear your opinions.  We will also plan to also discuss this on our next community call, as we stated a few days ago.    We can not really move further on the future of TAXII, as lot of future decisions will be impacted by this one, until this initial decision gets made so lets discuss it and make a decision.    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."    On Aug 27, 2015, at 06:36, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote:   Sergey, Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? -Mark -----Original Message----- From: Sergey Polzunov [ mailto:sergey@intelworks.com ] Sent: Thursday, August 27, 2015 8:32 AM To: Jordan, Bret < bret.jordan@BLUECOAT.COM > Cc: Jason Keirstead < Jason.Keirstead@ca.ibm.com >; Davidson II, Mark S < mdavidson@mitre.org >; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks On 26 Aug 2015, at 16:40, Jordan, Bret < bret.jordan@BLUECOAT.COM > wrote: This sounds like a really interesting idea that we need to explore and build code to test. Does anyone have any objection to moving forward with the two protocols we are discussing? HTTP1/1 HTTP/2 Are there any other protocols we should be looking at?  Please either bring them up on the list or come to the next call prepared to discuss them.  We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. 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." On Aug 26, 2015, at 07:01, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 <graycol.gif>"Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: "Davidson II, Mark S" < mdavidson@mitre.org > To: Jason Keirstead/CanEast/IBM@IBMCA Cc: "Jordan, Bret" < bret.jordan@bluecoat.com >, " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org > Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/<group>/<channel>/<message-id> , where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources      


  • 16.  RE: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 14:25
    And I should add SMTP, but I doubt there'll be broad support (perhaps none ;-). However, willing to make arguments for same. Sent from Outlook On Thu, Aug 27, 2015 at 7:20 AM -0700, "Davidson II, Mark S" < mdavidson@mitre.org > wrote: Which version of AMQP? =)   From: cti-taxii@lists.oasis-open.org [mailto:cti-taxii@lists.oasis-open.org] On Behalf Of Patrick Maroney Sent: Thursday, August 27, 2015 10:19 AM To: cti-taxii@lists.oasis-open.org; Jordan, Bret <bret.jordan@bluecoat.com> Subject: Re: [cti-taxii] TAXII Protocol Shortlist   AMQP and potentially MQTT if you want to consider your vision of TAXII Clients on IoT. Sent from Outlook   On Thu, Aug 27, 2015 at 5:57 AM -0700, "Jordan, Bret" < bret.jordan@bluecoat.com > wrote: We have three protocols on the short list...     HTTP/1.1 HTTP/2 ZMTP   Are there any others we should be actually thinking about or discussing?   If so please suggest them.  I would also like to start hearing pros and cons, discussion / debate about which one to use in the end.  Once we come to a steady state on discussion, we can then proceed to a vote.  Lets take the next few weeks to discuss this.. I really want to hear your opinions.  We will also plan to also discuss this on our next community call, as we stated a few days ago.    We can not really move further on the future of TAXII, as lot of future decisions will be impacted by this one, until this initial decision gets made so lets discuss it and make a decision.    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."    On Aug 27, 2015, at 06:36, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote:   Sergey, Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? -Mark -----Original Message----- From: Sergey Polzunov [ mailto:sergey@intelworks.com ] Sent: Thursday, August 27, 2015 8:32 AM To: Jordan, Bret < bret.jordan@BLUECOAT.COM > Cc: Jason Keirstead < Jason.Keirstead@ca.ibm.com >; Davidson II, Mark S < mdavidson@mitre.org >; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks On 26 Aug 2015, at 16:40, Jordan, Bret < bret.jordan@BLUECOAT.COM > wrote: This sounds like a really interesting idea that we need to explore and build code to test. Does anyone have any objection to moving forward with the two protocols we are discussing? HTTP1/1 HTTP/2 Are there any other protocols we should be looking at?  Please either bring them up on the list or come to the next call prepared to discuss them.  We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. 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." On Aug 26, 2015, at 07:01, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 <graycol.gif>"Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: "Davidson II, Mark S" < mdavidson@mitre.org > To: Jason Keirstead/CanEast/IBM@IBMCA Cc: "Jordan, Bret" < bret.jordan@bluecoat.com >, " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org > Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/<group>/<channel>/<message-id> , where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources      


  • 17.  Re: TAXII Protocol Shortlist

    Posted 08-27-2015 14:54
    So the list now is: HTTP/1.1 HTTP/2 ZMTP AMQP (which version??) MQTT SMTP Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks.  Also, if there is no discussion of pros/cons for a given item, then it will be dropped from the list.  No reason for having it on the list if there is no supporting data one way or another for it.  So if you feel strongly about one of the above, or another yet to be added item, please do the research and identify why you think it would be a good option for us to go with and how it would solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki.   https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements 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.   On Aug 27, 2015, at 06:57, Bret Jordan < bret.jordan@bluecoat.com > wrote: We have three protocols on the short list...   HTTP/1.1 HTTP/2 ZMTP Are there any others we should be actually thinking about or discussing?   If so please suggest them.  I would also like to start hearing pros and cons, discussion / debate about which one to use in the end.  Once we come to a steady state on discussion, we can then proceed to a vote.  Lets take the next few weeks to discuss this.. I really want to hear your opinions.  We will also plan to also discuss this on our next community call, as we stated a few days ago.  We can not really move further on the future of TAXII, as lot of future decisions will be impacted by this one, until this initial decision gets made so lets discuss it and make a decision.  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.   On Aug 27, 2015, at 06:36, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote: Sergey, Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? -Mark -----Original Message----- From: Sergey Polzunov [ mailto:sergey@intelworks.com ] Sent: Thursday, August 27, 2015 8:32 AM To: Jordan, Bret < bret.jordan@BLUECOAT.COM > Cc: Jason Keirstead < Jason.Keirstead@ca.ibm.com >; Davidson II, Mark S < mdavidson@mitre.org >; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks On 26 Aug 2015, at 16:40, Jordan, Bret < bret.jordan@BLUECOAT.COM > wrote: This sounds like a really interesting idea that we need to explore and build code to test. Does anyone have any objection to moving forward with the two protocols we are discussing? HTTP1/1 HTTP/2 Are there any other protocols we should be looking at?  Please either bring them up on the list or come to the next call prepared to discuss them.  We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. 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. On Aug 26, 2015, at 07:01, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 <graycol.gif> Davidson II, Mark S ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: Davidson II, Mark S < mdavidson@mitre.org > To: Jason Keirstead/CanEast/IBM@IBMCA Cc: Jordan, Bret < bret.jordan@bluecoat.com >, cti-taxii@lists.oasis-open.org < cti-taxii@lists.oasis-open.org > Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/<group>/<channel>/<message-id> , where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 18.  Re: [cti-taxii] Re: TAXII Protocol Shortlist

    Posted 08-27-2015 15:48
    Re: Which version -- V1.0: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf Patrick Maroney President Integrated Networking Technologies, Inc. Desk: (856)983-0001 Cell: (609)841-5104 Email: pmaroney@specere.org On Thu, Aug 27, 2015 at 7:53 AM -0700, "Jordan, Bret" < bret.jordan@bluecoat.com > wrote: So the list now is: HTTP/1.1 HTTP/2 ZMTP AMQP (which version??) MQTT SMTP Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks.  Also, if there is no discussion of pros/cons for a given item, then it will be dropped from the list.  No reason for having it on the list if there is no supporting data one way or another for it.  So if you feel strongly about one of the above, or another yet to be added item, please do the research and identify why you think it would be a good option for us to go with and how it would solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki.   https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements 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."  On Aug 27, 2015, at 06:57, Bret Jordan < bret.jordan@bluecoat.com > wrote: We have three protocols on the short list...   HTTP/1.1 HTTP/2 ZMTP Are there any others we should be actually thinking about or discussing?   If so please suggest them.  I would also like to start hearing pros and cons, discussion / debate about which one to use in the end.  Once we come to a steady state on discussion, we can then proceed to a vote.  Lets take the next few weeks to discuss this.. I really want to hear your opinions.  We will also plan to also discuss this on our next community call, as we stated a few days ago.  We can not really move further on the future of TAXII, as lot of future decisions will be impacted by this one, until this initial decision gets made so lets discuss it and make a decision.  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."  On Aug 27, 2015, at 06:36, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote: Sergey, Is this the spec for zmtp: http://rfc.zeromq.org/spec:37 ? -Mark -----Original Message----- From: Sergey Polzunov [ mailto:sergey@intelworks.com ] Sent: Thursday, August 27, 2015 8:32 AM To: Jordan, Bret < bret.jordan@BLUECOAT.COM > Cc: Jason Keirstead < Jason.Keirstead@ca.ibm.com >; Davidson II, Mark S < mdavidson@mitre.org >; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] Protocol Shortlist - Add HTTP Hey Bret, I suggest adding ZMTP ( http://zmtp.org/ ) to the mix Thanks, Sergey Polzunov Intelworks On 26 Aug 2015, at 16:40, Jordan, Bret < bret.jordan@BLUECOAT.COM > wrote: This sounds like a really interesting idea that we need to explore and build code to test. Does anyone have any objection to moving forward with the two protocols we are discussing? HTTP1/1 HTTP/2 Are there any other protocols we should be looking at?  Please either bring them up on the list or come to the next call prepared to discuss them.  We would like to come to general consensus on this decision in the next 2 weeks so we can start discussing and thinking through other much more interesting problems. 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." On Aug 26, 2015, at 07:01, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Yes exactly - IE - Client makes a TAXII query that returns 100 documents. Those documents contain references to indicators that live in other documents, that weren't matched in the query (possibly hundreds of such references). Instead of the TAXII client making hundreds of dereference requests and the associated HTTP overhead (as they would have to with 1.1), the server can push the documents down with a promise request. If for some esoteric use case the client would not actually want to de-reference, they can just disable it in the connection, as per HTTP/2 spec. - 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 <graycol.gif>"Davidson II, Mark S" ---2015/08/26 09:45:52 AM---From my perspective, I’d hope that an embedded device can behave like a client and not as a server, From: "Davidson II, Mark S" < mdavidson@mitre.org > To: Jason Keirstead/CanEast/IBM@IBMCA Cc: "Jordan, Bret" < bret.jordan@bluecoat.com >, " cti-taxii@lists.oasis-open.org " < cti-taxii@lists.oasis-open.org > Date: 2015/08/26 09:45 AM Subject: RE: [cti-taxii] Protocol Shortlist - Add HTTP From my perspective, I’d hope that an embedded device can behave like a client and not as a server, and still be able to take all of the actions that might matter in regard to TAXII. I took a quick glance at the section on Server Push [1], and there’s a number of requirements that at first glance seem to be counter to what we’d want. As I understand it, the server can send the client a “promised request” (e.g., I expect you will ask for http://example.com/image.png ) and the response to that promised request. The rules are: · Promised requests MUST be cacheable · MUST be safe (a.k.a “Read Only”) · MUST NOT include a request body These are clearly optimized for the “I’m sending you a web page with 15 images and 5 _javascript_/CSS resources that I know you’re going to ask for next, so let me just go ahead and send those to you before you ask for them”. In thinking how this might work for messaging, you’d almost have to have a URL structure like this: http://hostname/<group>/<channel>/<message-id> , where a message is a resource living at a particular URL. Then a request to the channel (e.g., GET hostname/<group>/<channel>/) would include a list of pointers to messages, THEN the server could send promised requests and the responses (one for each message). I’m not sure how well that kind of setup would work outside of a browser context. I think whether server push can be made to work for TAXII is ultimately an unknown. There’s also other reasons we might choose to go with HTTP/2 that haven’t been discussed yet. We will be able to prove these out with prototypes one way or another. In short, I agree with all Jason’s points. I took a slight detour down the rabbit hole of HTTP/2 server push, and I’m unclear on whether server push is something that makes sense for TAXII. -Mark [1] https://httpwg.github.io/specs/rfc7540.html#PushResources


  • 19.  Re: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 16:14
    Updated.... HTTP/1.1 HTTP/2 ZMTP AMQP 0.9 AMQP 1.0 MQTT SMTP Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks.  Also, if there is no discussion of pros/cons for a given item, then it will be dropped from the list.  No reason for having it on the list if there is no supporting data one way or another for it.  So if you feel strongly about one of the above, or another yet to be added item, please do the research and identify why you think it would be a good option for us to go with and how it would solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki.   https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements 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


  • 20.  Re: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 16:54




    So in the interest of spurring discussion, here are my thoughts:


    HTTP 1.1 would be my preferred option:

    Easy to implement against Well understood Very extensive library support Will go through a firewall Will not freak out security teams
    HTTP 2 is intriguing, I can see how it would be nice. It seems like a trade-off: it’s not as well supported as HTTP 1.1 right now but that should be changing in the (near??) future. So given that it might be worth exploring it, and if nothing else adding
    support or switching over in a future version of TAXII?


    The various messaging protocols:

    I was under the impression that ZeroMQ is specific to a single software platform, which probably means it should not be used? MQTT seems to be optimized for devices and small sensors, not sure that’s the biggest target now? In general, the big cons of these seem to me to be:

    Probably will not go through a corporate firewall without a lot of justification, so bad on the open internet Not an awesome fit for the query model, though it’s doable
    Pros:

    Probably a better fit for lots of small messages (sightings) and publish/subscribe type models Might be worth trying?
    No opinion on AMQP 1.0 vs. 0.9.
    I’m not sure of the reasoning behind SMTP so I can’t really evaluate it.


    John








    From: < cti-taxii@lists.oasis-open.org > on behalf of "Jordan, Bret"
    Date: Thursday, August 27, 2015 at 12:14 PM
    To: " cti-taxii@lists.oasis-open.org "
    Subject: Re: [cti-taxii] TAXII Protocol Shortlist





    Updated....




    HTTP/1.1
    HTTP/2
    ZMTP
    AMQP 0.9
    AMQP 1.0
    MQTT
    SMTP


    Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks.  Also, if there is no discussion of pros/cons for a given item, then it will be dropped from the list.  No reason for having it on
    the list if there is no supporting data one way or another for it.  So if you feel strongly about one of the above, or another yet to be added item, please do the research and identify why you think it would be a good option for us to go with and how it would
    solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki.  


    https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements













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


















  • 21.  RE: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 17:17




    I think all three proposals could be implemented using any of the protocols mentioned so far, so maybe it’s a bit more about the social and political aspects
    of these protocols than anything strictly technical.
     
    For me, the various messaging protocols usually have some combination of the following flaws:
    1)      
    Developers are not familiar with them
    2)      
    Available brokers/servers are hard to extend and write code on top of (e.g., to implement Message Handlers)
    3)      
    Firewalls generally do not let them through, and therefore existing firewall configs would be a barrier to adoption
    4)      
    Adoption is limited and clients are not ubiquitous
     
    Note that none of those flaws are strictly technical – they have to do with the social and political aspects and the ecosystem surrounding the protocol. There’s
    a reason the messaging space is so hard to understand – there’s no clear “winner”.
     
    For me at least right now, I’m leaning toward HTTP as my opinion for moving forward. My key reasons are in line with John’s, though I’ll also add: Vibrant ecosystem
    of platforms, tools, and knowledge for building applications.
     
    Thank you.
    -Mark
     


    From: cti-taxii@lists.oasis-open.org [mailto:cti-taxii@lists.oasis-open.org]
    On Behalf Of Wunder, John A.
    Sent: Thursday, August 27, 2015 12:54 PM
    To: Jordan, Bret <bret.jordan@bluecoat.com>; cti-taxii@lists.oasis-open.org
    Subject: Re: [cti-taxii] TAXII Protocol Shortlist


     


    So in the interest of spurring discussion, here are my thoughts:


     


    HTTP 1.1 would be my preferred option:


    ·         
    Easy to implement against

    ·         
    Well understood

    ·         
    Very extensive library support

    ·         
    Will go through a firewall

    ·         
    Will not freak out security teams

    HTTP 2 is intriguing, I can see how it would be nice. It seems like a trade-off: it’s not as well supported as HTTP 1.1 right now but that
    should be changing in the (near??) future. So given that it might be worth exploring it, and if nothing else adding support or switching over in a future version of TAXII?


     


    The various messaging protocols:


    ·         
    I was under the impression that ZeroMQ is specific to a single software platform, which probably means it should not be used?

    ·         
    MQTT seems to be optimized for devices and small sensors, not sure that’s the biggest target now?

    ·         
    In general, the big cons of these seem to me to be:


    o    
    Probably will not go through a corporate firewall without a lot of justification, so bad on the open internet

    o    
    Not an awesome fit for the query model, though it’s doable

    ·         
    Pros:


    o    
    Probably a better fit for lots of small messages (sightings) and publish/subscribe type models

    o    
    Might be worth trying?

    ·         
    No opinion on AMQP 1.0 vs. 0.9.

    I’m not sure of the reasoning behind SMTP so I can’t really evaluate it.


     


    John



     


    From:
    < cti-taxii@lists.oasis-open.org > on behalf of "Jordan, Bret"
    Date: Thursday, August 27, 2015 at 12:14 PM
    To: " cti-taxii@lists.oasis-open.org "
    Subject: Re: [cti-taxii] TAXII Protocol Shortlist


     




    Updated....


     


     


    HTTP/1.1


    HTTP/2


    ZMTP


    AMQP 0.9


    AMQP 1.0


    MQTT


    SMTP


     


    Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks.  Also, if there is no discussion
    of pros/cons for a given item, then it will be dropped from the list.  No reason for having it on the list if there is no supporting data one way or another for it.  So if you feel strongly about one of the above, or another yet to be added item, please do
    the research and identify why you think it would be a good option for us to go with and how it would solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki.  


     


    https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements


     









     


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










     








  • 22.  Re: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 18:23
    In my opinion: HTTP/1.1  1) Easiest for us to do, as it is what we do today.   2) The change from TAXII 1.1 to TAXII 2.0 will be less scary as it can be made to look relatively the same but with added functionality and improved features 3) Developers are very familiar with it 4) There is nearly ubiquitous support for it 5) Everything can speak HTTP.   This makes it very easy for vendors to do TAXII as they already do HTTP for their updates, for talking with other vendors, and most of their APIs run over HTTP.   6) HTTP also is allowed out the firewall, even when deep packet inspection is enabled.  7) Great library support 8) Allows us to build very light weight clients 9) It can scale nicely behind load balancers that are well understood today, so we can have infinite scalability with tools and technologies that are very common in IT shops today. 10) It will work well with cloud based services 11) Works well over the internet 12) Can be made to work with things like server push, using something like Long-Polling HTTP/2  1) seems neat, very progressive 2) not a lot of support for it today.   3) I would suggest adding support for HTTP/2 in a future release of TAXII, maybe 2.5 Message Queues All of the messaging queue systems generally suffer from these sort of things 1) Developers in generally are not familiar with them 2) You often hear, we need to bring in an expert to talk about them.  That by definition illustrates the problem. 3) There is no clear winner.  There are big vendor versions, and great open source versions and non compatible religious debates within specific versions (AMQP 0.9 vs AMQP 1.0)  4) Firewalls do not allow this traffic out be default, so that is a show stopper 5) Hacking them to run over HTTP is not always easy 6) Client support can be iffy or it requires you to run their client, there is not always a client library to use 7) Adding on top of the MQ can be hard, some times it requires hacking the source of the server to do or adding a lot of extra software packages to do it 8) Some of the best MQ system are PAID products, so requiring people to buy a MQ just to support TAXII is a show stopper 9) A lot of times MQs are designed for the server to be super light weight and have all of the heavy lifting to be done on the end client.  I think this is also a show stopper 10) A lot of cloud based services only allow HTTP type connectivity, so unless the MQ supports HTTP natively, then this is a show stopper.  11) Usually designed for closed systems SMTP 1) Not an option IMO I really like ZeroMQ but based on the requirements listed here:  https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements  ZeroMQ does not meet the majority of them.  Therefor I am also leaning towards HTTP. 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.   On Aug 27, 2015, at 11:17, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote: I think all three proposals could be implemented using any of the protocols mentioned so far, so maybe it’s a bit more about the social and political aspects of these protocols than anything strictly technical.   For me, the various messaging protocols usually have some combination of the following flaws: 1)         Developers are not familiar with them 2)         Available brokers/servers are hard to extend and write code on top of (e.g., to implement Message Handlers) 3)         Firewalls generally do not let them through, and therefore existing firewall configs would be a barrier to adoption 4)         Adoption is limited and clients are not ubiquitous   Note that none of those flaws are strictly technical – they have to do with the social and political aspects and the ecosystem surrounding the protocol. There’s a reason the messaging space is so hard to understand – there’s no clear “winner”.   For me at least right now, I’m leaning toward HTTP as my opinion for moving forward. My key reasons are in line with John’s, though I’ll also add: Vibrant ecosystem of platforms, tools, and knowledge for building applications.   Thank you. -Mark   From:   cti-taxii@lists.oasis-open.org   [ mailto:cti-taxii@lists.oasis-open.org ]   On Behalf Of   Wunder, John A. Sent:   Thursday, August 27, 2015 12:54 PM To:   Jordan, Bret < bret.jordan@bluecoat.com >;   cti-taxii@lists.oasis-open.org Subject:   Re: [cti-taxii] TAXII Protocol Shortlist   So in the interest of spurring discussion, here are my thoughts:   HTTP 1.1 would be my preferred option: ·            Easy to implement against ·            Well understood ·            Very extensive library support ·            Will go through a firewall ·            Will not freak out security teams HTTP 2 is intriguing, I can see how it would be nice. It seems like a trade-off: it’s not as well supported as HTTP 1.1 right now but that should be changing in the (near??) future. So given that it might be worth exploring it, and if nothing else adding support or switching over in a future version of TAXII?   The various messaging protocols: ·            I was under the impression that ZeroMQ is specific to a single software platform, which probably means it should not be used? ·            MQTT seems to be optimized for devices and small sensors, not sure that’s the biggest target now? ·            In general, the big cons of these seem to me to be: o       Probably will not go through a corporate firewall without a lot of justification, so bad on the open internet o       Not an awesome fit for the query model, though it’s doable ·            Pros: o       Probably a better fit for lots of small messages (sightings) and publish/subscribe type models o       Might be worth trying? ·            No opinion on AMQP 1.0 vs. 0.9. I’m not sure of the reasoning behind SMTP so I can’t really evaluate it.   John   From:   < cti-taxii@lists.oasis-open.org > on behalf of Jordan, Bret Date:   Thursday, August 27, 2015 at 12:14 PM To:   cti-taxii@lists.oasis-open.org Subject:   Re: [cti-taxii] TAXII Protocol Shortlist   Updated....     HTTP/1.1 HTTP/2 ZMTP AMQP 0.9 AMQP 1.0 MQTT SMTP   Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks.  Also, if there is no discussion of pros/cons for a given item, then it will be dropped from the list.  No reason for having it on the list if there is no supporting data one way or another for it.  So if you feel strongly about one of the above, or another yet to be added item, please do the research and identify why you think it would be a good option for us to go with and how it would solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki.     https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements     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


  • 23.  RE: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-27-2015 18:31




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


    From: cti-taxii@lists.oasis-open.org [mailto:cti-taxii@lists.oasis-open.org]
    On Behalf Of Jordan, Bret
    Sent: Thursday, August 27, 2015 2:23 PM
    To: Davidson II, Mark S <mdavidson@mitre.org>; Wunder, John A. <jwunder@mitre.org>; cti-taxii@lists.oasis-open.org
    Subject: Re: [cti-taxii] TAXII Protocol Shortlist


     

    In my opinion:


     

    HTTP/1.1 

               
    1) Easiest for us to do, as it is what we do today.  


               
    2) The change from TAXII 1.1 to TAXII 2.0 will be less scary as it can be made to look relatively the same but with added functionality and improved features


               
    3) Developers are very familiar with it


               
    4) There is nearly ubiquitous support for it


               
    5) Everything can speak HTTP.   This makes it very easy for vendors to do TAXII as they already do HTTP for their updates, for talking with other vendors, and most of their APIs run over HTTP.  


               
    6) HTTP also is allowed out the firewall, even when deep packet inspection is enabled. 


               
    7) Great library support


               
    8) Allows us to build very light weight clients


               
    9) It can scale nicely behind load balancers that are well understood today, so we can have infinite scalability with tools and technologies that are very common in IT shops today.


               
    10) It will work well with cloud based services


               
    11) Works well over the internet


               
    12) Can be made to work with things like server push, using something like Long-Polling



     


    HTTP/2 


               
    1) seems neat, very progressive


               
    2) not a lot of support for it today.  


               
    3) I would suggest adding support for HTTP/2 in a future release of TAXII, maybe 2.5


     


    Message Queues


    All of the messaging queue systems generally suffer from these sort of things


               
    1) Developers in generally are not familiar with them


               
    2) You often hear, we need to bring in an expert to talk about them.  That by definition illustrates the problem.


               
    3) There is no clear winner.  There are big vendor versions, and great open source versions and non compatible religious debates within specific versions (AMQP 0.9 vs AMQP 1.0) 


               
    4) Firewalls do not allow this traffic out be default, so that is a show stopper


               
    5) Hacking them to run over HTTP is not always "easy"


               
    6) Client support can be iffy or it requires you to run "their" client, there is not always a client library to use


               
    7) Adding on top of the MQ can be hard, some times it requires hacking the source of the server to do or adding a lot of extra software packages to do it


               
    8) Some of the best MQ system are PAID products, so requiring people to buy a MQ just to support TAXII is a show stopper


               
    9) A lot of times MQs are designed for the server to be super light weight and have all of the heavy lifting to be done on the end client.  I think this is also a show stopper


               
    10) A lot of cloud based services only allow HTTP type connectivity, so unless the MQ supports HTTP natively, then this is a show stopper. 


               
    11) Usually designed for closed systems


               



     


    SMTP


               
    1) Not an option IMO


     








    I really like ZeroMQ but based on the requirements listed here:  https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements  ZeroMQ
    does not meet the majority of them.  Therefor I am also leaning towards HTTP.


     


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









     



    On Aug 27, 2015, at 11:17, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote:

     


    I think all three proposals could be implemented using any of the protocols mentioned so far, so maybe it’s a bit more about the social
    and political aspects of these protocols than anything strictly technical.


     


    For me, the various messaging protocols usually have some combination of the following flaws:


    1)         Developers
    are not familiar with them


    2)         Available
    brokers/servers are hard to extend and write code on top of (e.g., to implement Message Handlers)


    3)         Firewalls
    generally do not let them through, and therefore existing firewall configs would be a barrier to adoption


    4)         Adoption
    is limited and clients are not ubiquitous


     


    Note that none of those flaws are strictly technical – they have to do with the social and political aspects and the ecosystem surrounding
    the protocol. There’s a reason the messaging space is so hard to understand – there’s no clear “winner”.


     


    For me at least right now, I’m leaning toward HTTP as my opinion for moving forward. My key reasons are in line with John’s, though I’ll
    also add: Vibrant ecosystem of platforms, tools, and knowledge for building applications.


     


    Thank you.


    -Mark


     




    From:   cti-taxii@lists.oasis-open.org   [ mailto:cti-taxii@lists.oasis-open.org ]   On
    Behalf Of   Wunder, John A.
    Sent:   Thursday, August 27, 2015 12:54 PM
    To:   Jordan, Bret < bret.jordan@bluecoat.com >;   cti-taxii@lists.oasis-open.org
    Subject:   Re: [cti-taxii] TAXII Protocol Shortlist




     




    So in the interest of spurring discussion, here are my thoughts:




     




    HTTP 1.1 would be my preferred option:



    ·            Easy
    to implement against


    ·            Well
    understood


    ·            Very
    extensive library support


    ·            Will
    go through a firewall


    ·            Will
    not freak out security teams



    HTTP 2 is intriguing, I can see how it would be nice. It seems like a trade-off: it’s not as well supported as HTTP 1.1 right now but that should be
    changing in the (near??) future. So given that it might be worth exploring it, and if nothing else adding support or switching over in a future version of TAXII?




     




    The various messaging protocols:



    ·            I
    was under the impression that ZeroMQ is specific to a single software platform, which probably means it should not be used?


    ·            MQTT
    seems to be optimized for devices and small sensors, not sure that’s the biggest target now?


    ·            In
    general, the big cons of these seem to me to be:


    o       Probably
    will not go through a corporate firewall without a lot of justification, so bad on the open internet


    o       Not
    an awesome fit for the query model, though it’s doable


    ·            Pros:


    o       Probably
    a better fit for lots of small messages (sightings) and publish/subscribe type models


    o       Might
    be worth trying?


    ·            No
    opinion on AMQP 1.0 vs. 0.9.



    I’m not sure of the reasoning behind SMTP so I can’t really evaluate it.




     




    John





     




    From:   < cti-taxii@lists.oasis-open.org >
    on behalf of "Jordan, Bret"
    Date:   Thursday, August 27, 2015 at 12:14 PM
    To:   " cti-taxii@lists.oasis-open.org "
    Subject:   Re: [cti-taxii] TAXII Protocol Shortlist




     






    Updated....




     




     




    HTTP/1.1




    HTTP/2




    ZMTP




    AMQP 0.9




    AMQP 1.0




    MQTT




    SMTP




     




    Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks.  Also, if there is no discussion of
    pros/cons for a given item, then it will be dropped from the list.  No reason for having it on the list if there is no supporting data one way or another for it.  So if you feel strongly about one of the above, or another yet to be added item, please do the
    research and identify why you think it would be a good option for us to go with and how it would solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki.  




     




    https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements




     










     



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















     








  • 24.  RE: [cti-taxii] TAXII Protocol Shortlist

    Posted 08-28-2015 20:00
    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 "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 From: cti-taxii@lists.oasis-open.org [ mailto:cti-taxii@lists.oasis-open.org ] On Behalf Of Jordan, Bret Sent: Thursday, August 27, 2015 2:23 PM To: Davidson II, Mark S <mdavidson@mitre.org>; Wunder, John A. <jwunder@mitre.org>; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] TAXII Protocol Shortlist In my opinion: HTTP/1.1 1) Easiest for us to do, as it is what we do today. 2) The change from TAXII 1.1 to TAXII 2.0 will be less scary as it can be made to look relatively the same but with added functionality and improved features 3) Developers are very familiar with it 4) There is nearly ubiquitous support for it 5) Everything can speak HTTP. This makes it very easy for vendors to do TAXII as they already do HTTP for their updates, for talking with other vendors, and most of their APIs run over HTTP. 6) HTTP also is allowed out the firewall, even when deep packet inspection is enabled. 7) Great library support 8) Allows us to build very light weight clients 9) It can scale nicely behind load balancers that are well understood today, so we can have infinite scalability with tools and technologies that are very common in IT shops today. 10) It will work well with cloud based services 11) Works well over the internet 12) Can be made to work with things like server push, using something like Long-Polling HTTP/2 1) seems neat, very progressive 2) not a lot of support for it today. 3) I would suggest adding support for HTTP/2 in a future release of TAXII, maybe 2.5 Message Queues All of the messaging queue systems generally suffer from these sort of things 1) Developers in generally are not familiar with them 2) You often hear, we need to bring in an expert to talk about them. That by definition illustrates the problem. 3) There is no clear winner. There are big vendor versions, and great open source versions and non compatible religious debates within specific versions (AMQP 0.9 vs AMQP 1.0) 4) Firewalls do not allow this traffic out be default, so that is a show stopper 5) Hacking them to run over HTTP is not always "easy" 6) Client support can be iffy or it requires you to run "their" client, there is not always a client library to use 7) Adding on top of the MQ can be hard, some times it requires hacking the source of the server to do or adding a lot of extra software packages to do it 8) Some of the best MQ system are PAID products, so requiring people to buy a MQ just to support TAXII is a show stopper 9) A lot of times MQs are designed for the server to be super light weight and have all of the heavy lifting to be done on the end client. I think this is also a show stopper 10) A lot of cloud based services only allow HTTP type connectivity, so unless the MQ supports HTTP natively, then this is a show stopper. 11) Usually designed for closed systems SMTP 1) Not an option IMO I really like ZeroMQ but based on the requirements listed here: https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements ZeroMQ does not meet the majority of them. Therefor I am also leaning towards HTTP. 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." On Aug 27, 2015, at 11:17, Davidson II, Mark S < mdavidson@MITRE.ORG > wrote: I think all three proposals could be implemented using any of the protocols mentioned so far, so maybe it’s a bit more about the social and political aspects of these protocols than anything strictly technical. For me, the various messaging protocols usually have some combination of the following flaws: 1) Developers are not familiar with them 2) Available brokers/servers are hard to extend and write code on top of (e.g., to implement Message Handlers) 3) Firewalls generally do not let them through, and therefore existing firewall configs would be a barrier to adoption 4) Adoption is limited and clients are not ubiquitous Note that none of those flaws are strictly technical – they have to do with the social and political aspects and the ecosystem surrounding the protocol. There’s a reason the messaging space is so hard to understand – there’s no clear “winner”. For me at least right now, I’m leaning toward HTTP as my opinion for moving forward. My key reasons are in line with John’s, though I’ll also add: Vibrant ecosystem of platforms, tools, and knowledge for building applications. Thank you. -Mark From: cti-taxii@lists.oasis-open.org [ mailto:cti-taxii@lists.oasis-open.org ] On Behalf Of Wunder, John A. Sent: Thursday, August 27, 2015 12:54 PM To: Jordan, Bret < bret.jordan@bluecoat.com >; cti-taxii@lists.oasis-open.org Subject: Re: [cti-taxii] TAXII Protocol Shortlist So in the interest of spurring discussion, here are my thoughts: HTTP 1.1 would be my preferred option: · Easy to implement against · Well understood · Very extensive library support · Will go through a firewall · Will not freak out security teams HTTP 2 is intriguing, I can see how it would be nice. It seems like a trade-off: it’s not as well supported as HTTP 1.1 right now but that should be changing in the (near??) future. So given that it might be worth exploring it, and if nothing else adding support or switching over in a future version of TAXII? The various messaging protocols: · I was under the impression that ZeroMQ is specific to a single software platform, which probably means it should not be used? · MQTT seems to be optimized for devices and small sensors, not sure that’s the biggest target now? · In general, the big cons of these seem to me to be: o Probably will not go through a corporate firewall without a lot of justification, so bad on the open internet o Not an awesome fit for the query model, though it’s doable · Pros: o Probably a better fit for lots of small messages (sightings) and publish/subscribe type models o Might be worth trying? · No opinion on AMQP 1.0 vs. 0.9. I’m not sure of the reasoning behind SMTP so I can’t really evaluate it. John From: < cti-taxii@lists.oasis-open.org > on behalf of "Jordan, Bret" Date: Thursday, August 27, 2015 at 12:14 PM To: " cti-taxii@lists.oasis-open.org " Subject: Re: [cti-taxii] TAXII Protocol Shortlist Updated.... HTTP/1.1 HTTP/2 ZMTP AMQP 0.9 AMQP 1.0 MQTT SMTP Please submit pros and cons for each of these and any others you think we should look at over the next 2 weeks. Also, if there is no discussion of pros/cons for a given item, then it will be dropped from the list. No reason for having it on the list if there is no supporting data one way or another for it. So if you feel strongly about one of the above, or another yet to be added item, please do the research and identify why you think it would be a good option for us to go with and how it would solve the TAXII problems we have identified and further, how it will meet the protocol requirements we have identified on the wiki. https://github.com/TAXIIProject/TAXII-Specifications/wiki/TAXII-2.0-Requirements 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."