OASIS Cyber Threat Intelligence (CTI) TC

 View Only

  • 1.  CTI TC Working Calls Kickoff July 19, 2024

    Posted 07-11-2024 14:05

    Hi TC,

     

    I am thrilled to announce a new series of sessions focused on exploring and advancing emerging efforts within our vibrant community CTI TC Working Call July 19, 2024 from 08:30 to 09:30 (ET). These sessions will provide an invaluable platform for collaboration, innovation, and sharing of ideas that will help shape the future of our work. We'll focus on broad topics related to our core focus to include:

    - Advancement and interoperability of STIX and TAXII

    - Extensions and support for other standards

    - Innovative ideas you bring to the table!

     

    Your participation and contributions are crucial to the success of these sessions. By sharing your knowledge and collaborating with others, you will help drive innovation and ensure that our projects remain at the forefront of technological advancements. There are several ways you can contribute to these sessions such as:

    1. Joining the Sessions: Mark your calendars and participate actively in the discussions.

    2. Proposing Topics: Have a topic you're passionate about? Submit your ideas to be included in the agenda.

    3. Leading a Session: Volunteer to lead a session or present your expertise on a specific topic.

     

    Kickoff Session RSVP: CTI TC Working Call July 19, 2024 from 08:30 to 09:30 (ET)

     

    Please register for the sessions, submit your topics, and volunteer as a session leader!

     

    Let's come together to explore new horizons and drive our community forward. I look forward to your enthusiastic participation and valuable contributions.

     

    -Marlon



  • 2.  RE: CTI TC Working Calls Kickoff July 19, 2024

    Posted 07-11-2024 16:08
    Marlon/Bret/Jeff - I'm unable to attend the July 19th meeting otherwise I would make the following point in person.

    I'm all for improving standards, especially if they are impractical, hard to implement, hard to use ...etc. 

    One of the critical items that must drive (any) standards at OASIS is a strong business use case that justifies the development of the standard or the improvement of the standard in the case of STIX 2.1/TAXII 2.1.

    Just because we can do something doesn't mean we should do something.

    Ultimately, interoperability and use of the standard is paramount over whether something is elegant or not. Companies or organizations will not invest in a new standard if it doesn't solve a problem that they care to solve. Or the existing standard is "good enough" that allows them to not invest in the new standard.

    So I would encourage the TC to consider business use cases/priorities/sponsors that are concrete, that clearly identify why any technical innovation or improvement of the CTI specs is needed.

    Otherwise a lot of work may go into specifying a great spec that no one implements or uses.

    Regards

    Allan T.

    On Jul 11, 2024, at 11:05 AM, Marlon Taylor via OASIS <Mail@mail.groups.oasis-open.org> wrote:





    Original Message


  • 3.  RE: CTI TC Working Calls Kickoff July 19, 2024

    Posted 07-12-2024 14:35

    Allan,

    I wholly agree that we should have strong business use cases and requirements.  However, apparently there was not much of a "strong business use case" for AI use until recently...even when it was easily available back in the 2000s.  This has more to do with perception than reality..."keeping up with the Joneses".

    I would also counter that just because we have some things doesn't mean we have nice things.  I opine that a "great spec" should include an easy path to implementation so that it is used.

    I also think there is a lot of room to develop solutions that are both interoperable and elegant.  But those concepts are subjective to the individual and their environment

    As an aside, was there ever an XML Schema or JSON Schema developed to help implementers use STIX bundle documents?



    ------------------------------
    Keven Ates
    US Federal Bureau of Investigation
    Washington DC
    ------------------------------

    Original Message


Related Content