CTI STIX Subcommittee

 View Only
Expand all | Collapse all

Re: [cti-stix] STIX 2.1 discussion

  • 1.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-19-2016 18:27
    The OpenC2 spec is mature enough with a proposal for STIX here  complete with the JSON schema and examples. There are reference implementations being built as of now using orchestrators and SDN controllers. I’d be happy to provide an update or answer any questions on behalf of the OpenC2 working group.  Thanks, Jyoti From: < cti-stix@lists.oasis-open.org > on behalf of "Jordan, Bret" < bret.jordan@bluecoat.com > Date: Friday, August 19, 2016 at 9:11 AM To: " cti-stix@lists.oasis-open.org " < cti-stix@lists.oasis-open.org > Subject: [cti-stix] STIX 2.1 discussion Even though STIX 2.0 is just leaving the house, I would like to start work on STIX 2.1...  Here are some of the things I would like to see us do.  Please comment on or add your suggestions.... My Primary Goals for 2.1 1) Flesh out the Malware object 2) Add the Incident object  3) Add the Infrastructure object   4) Solve the problem of not being able to track when a victim was being targeted. 5) Flesh out Course of Action and add support for OpenC2 Stretch Goals 2.1 1) Figure out Confidence  2) Figure out a solution for Digital Signatures My Primary Goals for 2.2 1) Confidence 2) Digital Signatures 3) Internationalization  I would also like to propose that we plan to have this done by end of January 2017.  That gives us 5 months - 1 month for holiday time off = 4 months of development work.   If we could have this discussion wrapped up before the end of August, and have the roadmap in place for 2.1 and 2.2 that would be great.  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." 


  • 2.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-19-2016 20:22
    My wish list for 2.1: - Confidence, so that consumers are able to filter out the high confidence intel from the lore confidence (this is the most critical thing we're missing at the moment!) - Opinion object, so that people can show it they agree or disagree with someone else's assertion. - Internationalization, which is critical to gain widespread adoption outside of the US. - incident object, so we can properly show the incidents orgs have responded to. - IEP integration, including the latest version of IEP in the STIX document as an example. For STIX 2.2: - digital signatures - object level encryption Cheers Terry MacDonald Cosive On 20/08/2016 6:27 AM, "Jyoti Verma (jyoverma)" < jyoverma@cisco.com > wrote: The OpenC2 spec is mature enough with a proposal for STIX here  complete with the JSON schema and examples. There are reference implementations being built as of now using orchestrators and SDN controllers. I’d be happy to provide an update or answer any questions on behalf of the OpenC2 working group.  Thanks, Jyoti From: < cti-stix@lists.oasis-open.org > on behalf of "Jordan, Bret" < bret.jordan@bluecoat.com > Date: Friday, August 19, 2016 at 9:11 AM To: " cti-stix@lists.oasis-open.org " < cti-stix@lists.oasis-open.org > Subject: [cti-stix] STIX 2.1 discussion Even though STIX 2.0 is just leaving the house, I would like to start work on STIX 2.1...  Here are some of the things I would like to see us do.  Please comment on or add your suggestions.... My Primary Goals for 2.1 1) Flesh out the Malware object 2) Add the Incident object  3) Add the Infrastructure object   4) Solve the problem of not being able to track when a victim was being targeted. 5) Flesh out Course of Action and add support for OpenC2 Stretch Goals 2.1 1) Figure out Confidence  2) Figure out a solution for Digital Signatures My Primary Goals for 2.2 1) Confidence 2) Digital Signatures 3) Internationalization  I would also like to propose that we plan to have this done by end of January 2017.  That gives us 5 months - 1 month for holiday time off = 4 months of development work.   If we could have this discussion wrapped up before the end of August, and have the roadmap in place for 2.1 and 2.2 that would be great.  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." 


  • 3.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 07:35
    On 20.08.2016 08:22:15, Terry MacDonald wrote: > My wish list for 2.1: > +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4 5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- "All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same." --anonymous Attachment: signature.asc Description: Digital signature


  • 4.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 16:54
    Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no real confidence or opinion as everything could be faked.   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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote: On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same. --anonymous Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 5.  RE: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 17:21
    I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it.   I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.     Sarah Kelley Senior CERT Analyst Center for Internet Security (CIS) Integrated Intelligence Center (IIC) Multi-State Information Sharing and Analysis Center (MS-ISAC) 1-866-787-4722 (7×24 SOC) Email:  cert@cisecurity.org www.cisecurity.org Follow us @CISecurity   From: cti-stix@lists.oasis-open.org [mailto:cti-stix@lists.oasis-open.org] On Behalf Of Jordan, Bret Sent: Monday, August 22, 2016 12:55 PM To: Trey Darley <trey@kingfisherops.com> Cc: Terry MacDonald <terry.macdonald@cosive.com>; Jyoti Verma (jyoverma) <jyoverma@cisco.com>; Fai, Joyce <Joyce.Fai@gd-ms.com>; cti-stix@lists.oasis-open.org; Kemp, David P <dpkemp@nsa.gov>; Brule, Joseph M <jmbrule@radium.ncsc.mil> Subject: Re: [cti-stix] STIX 2.1 discussion   Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no "real" confidence or opinion as everything could be faked.     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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote:   On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- "All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same." --anonymous   This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments. . . .


  • 6.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 17:41




    I also agree on Confidence as a next step. Confidence is something that can be implemented rather quickly within the TC (and vendor products), and have a large benefit to consumers.

     
    Aharon
     

    From:
    <cti-stix@lists.oasis-open.org> on behalf of Sarah Kelley <Sarah.Kelley@cisecurity.org>
    Date: Monday, August 22, 2016 at 1:21 PM
    To: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>
    Subject: RE: [cti-stix] STIX 2.1 discussion


     



    I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence
    field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it.

     
    I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.

     
     

    Sarah Kelley
    Senior CERT Analyst
    Center for Internet Security (CIS)
    Integrated Intelligence Center (IIC)
    Multi-State Information Sharing and Analysis Center (MS-ISAC)
    1-866-787-4722 (7×24 SOC)
    Email:  cert@cisecurity.org
    www.cisecurity.org
    Follow us @CISecurity

     


    From: cti-stix@lists.oasis-open.org [mailto:cti-stix@lists.oasis-open.org]
    On Behalf Of Jordan, Bret
    Sent: Monday, August 22, 2016 12:55 PM
    To: Trey Darley <trey@kingfisherops.com>
    Cc: Terry MacDonald <terry.macdonald@cosive.com>; Jyoti Verma (jyoverma) <jyoverma@cisco.com>; Fai, Joyce <Joyce.Fai@gd-ms.com>; cti-stix@lists.oasis-open.org; Kemp, David P <dpkemp@nsa.gov>; Brule, Joseph M <jmbrule@radium.ncsc.mil>
    Subject: Re: [cti-stix] STIX 2.1 discussion


     
    Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no "real" confidence or opinion as everything could be faked.  







     


    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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote:

     


    On 20.08.2016 08:22:15, Terry MacDonald wrote:




    My wish list for 2.1:


    +1 for Terry's list of STIX 2.1/2.2 priorities

    --
    Cheers,
    Trey
    ++--------------------------------------------------------------------------++
    Kingfisher Operations, sprl
    gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D
    ++--------------------------------------------------------------------------++
    --
    "All systems, regardless of composition, do one of three things: blow
    up, oscillate, or stay about the same." --anonymous




     
    This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited.
    Please notify the sender immediately and permanently delete the message and any attachments.

    . . .








  • 7.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 18:36
    I agree on the "confidence" as well because, while digital signatures are important to eventually get to, we also need to ackgnoledge the fact that the vast majority of threat intelligence is currently shared in private trust groups and other siloed communities, where a "confidence factor" can actually have meaning, and they don't have to worry much about information being "faked" inside that community. - Jason Keirstead STSM, 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 Aharon Chernin ---08/22/2016 02:41:12 PM---I also agree on Confidence as a next step. Confidence is something that can be implemented rather qu From: Aharon Chernin <achernin@soltra.com> To: Sarah Kelley <Sarah.Kelley@cisecurity.org>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> Date: 08/22/2016 02:41 PM Subject: Re: [cti-stix] STIX 2.1 discussion Sent by: <cti-stix@lists.oasis-open.org> I also agree on Confidence as a next step. Confidence is something that can be implemented rather quickly within the TC (and vendor products), and have a large benefit to consumers. Aharon From: <cti-stix@lists.oasis-open.org> on behalf of Sarah Kelley <Sarah.Kelley@cisecurity.org> Date: Monday, August 22, 2016 at 1:21 PM To: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> Subject: RE: [cti-stix] STIX 2.1 discussion I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it. I would also push for incident (for our use) and also for internationalization for the sake of increased adoption. Sarah Kelley Senior CERT Analyst Center for Internet Security (CIS) Integrated Intelligence Center (IIC) Multi-State Information Sharing and Analysis Center (MS-ISAC) 1-866-787-4722 (7? SOC) Email: cert@cisecurity.org www.cisecurity.org Follow us @CISecurity From: cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ] On Behalf Of Jordan, Bret Sent: Monday, August 22, 2016 12:55 PM To: Trey Darley <trey@kingfisherops.com> Cc: Terry MacDonald <terry.macdonald@cosive.com>; Jyoti Verma (jyoverma) <jyoverma@cisco.com>; Fai, Joyce <Joyce.Fai@gd-ms.com>; cti-stix@lists.oasis-open.org; Kemp, David P <dpkemp@nsa.gov>; Brule, Joseph M <jmbrule@radium.ncsc.mil> Subject: Re: [cti-stix] STIX 2.1 discussion Confidence does not really make sense before we have digital signatures, neither does the opinion object.. Without digital signatures first, there is no "real" confidence or opinion as everything could be faked. 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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote: On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4 5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- "All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same." --anonymous This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments. . . .




  • 8.  RE: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 18:37




    My +1 for confidence.  I understand the eventual need to tie this to a producer identity and signature, but for producers like us, this is a concept already
    well understood and currently in use, either natively or via STIX 1.x.
     


    From: cti-stix@lists.oasis-open.org [mailto:cti-stix@lists.oasis-open.org]
    On Behalf Of Aharon Chernin
    Sent: Monday, August 22, 2016 1:41 PM
    To: Sarah Kelley; cti-stix@lists.oasis-open.org
    Subject: Re: [cti-stix] STIX 2.1 discussion


     
    I also agree on Confidence as a next step. Confidence is something that can be implemented rather quickly within the TC (and vendor products), and have a large benefit to
    consumers.
     
    Aharon
     

    From:
    < cti-stix@lists.oasis-open.org > on behalf of Sarah Kelley < Sarah.Kelley@cisecurity.org >
    Date: Monday, August 22, 2016 at 1:21 PM
    To: " cti-stix@lists.oasis-open.org " < cti-stix@lists.oasis-open.org >
    Subject: RE: [cti-stix] STIX 2.1 discussion


     



    I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x.
    We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence
    on it.
     
    I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.

     
     

    Sarah Kelley
    Senior CERT Analyst
    Center for Internet Security (CIS)
    Integrated Intelligence Center (IIC)
    Multi-State Information Sharing and Analysis Center (MS-ISAC)
    1-866-787-4722 (7×24 SOC)
    Email:  cert@cisecurity.org
    www.cisecurity.org
    Follow us @CISecurity

     


    From:
    cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ]
    On Behalf Of Jordan, Bret
    Sent: Monday, August 22, 2016 12:55 PM
    To: Trey Darley < trey@kingfisherops.com >
    Cc: Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >; Fai, Joyce < Joyce.Fai@gd-ms.com >;
    cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil >
    Subject: Re: [cti-stix] STIX 2.1 discussion


     
    Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no "real" confidence or opinion as everything could be faked.  







     


    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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote:

     


    On 20.08.2016 08:22:15, Terry MacDonald wrote:



    My wish list for 2.1:


    +1 for Terry's list of STIX 2.1/2.2 priorities

    --
    Cheers,
    Trey
    ++--------------------------------------------------------------------------++
    Kingfisher Operations, sprl
    gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D
    ++--------------------------------------------------------------------------++
    --
    "All systems, regardless of composition, do one of three things: blow
    up, oscillate, or stay about the same." --anonymous




     
    This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited.
    Please notify the sender immediately and permanently delete the message and any attachments.

    . . .








  • 9.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 21:36




    +1 for Confidence as well. 

     
     
    Paul Patrick
     
     

    From:
    <cti-stix@lists.oasis-open.org> on behalf of "Coderre, Robert" <rcoderre@verisign.com>
    Date: Monday, August 22, 2016 at 2:37 PM
    To: Aharon Chernin <achernin@soltra.com>, Sarah Kelley <Sarah.Kelley@cisecurity.org>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>
    Subject: RE: [cti-stix] STIX 2.1 discussion


     




    My +1 for confidence.  I understand the eventual need to tie this to a producer identity and signature, but for producers like us, this is a concept already well understood
    and currently in use, either natively or via STIX 1.x.
     


    From: cti-stix@lists.oasis-open.org [mailto:cti-stix@lists.oasis-open.org]
    On Behalf Of Aharon Chernin
    Sent: Monday, August 22, 2016 1:41 PM
    To: Sarah Kelley; cti-stix@lists.oasis-open.org
    Subject: Re: [cti-stix] STIX 2.1 discussion


     
    I also agree on Confidence as a next step. Confidence is something that can be implemented rather quickly within the TC (and vendor products), and have a large benefit to consumers.

     
    Aharon
     

    From:
    < cti-stix@lists.oasis-open.org > on behalf of Sarah Kelley < Sarah.Kelley@cisecurity.org >
    Date: Monday, August 22, 2016 at 1:21 PM
    To: " cti-stix@lists.oasis-open.org " < cti-stix@lists.oasis-open.org >
    Subject: RE: [cti-stix] STIX 2.1 discussion


     



    I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence
    field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it.

     
    I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.

     
     

    Sarah Kelley
    Senior CERT Analyst
    Center for Internet Security (CIS)
    Integrated Intelligence Center (IIC)
    Multi-State Information Sharing and Analysis Center (MS-ISAC)
    1-866-787-4722 (7×24 SOC)
    Email:  cert@cisecurity.org
    www.cisecurity.org
    Follow us @CISecurity

     


    From:
    cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ]
    On Behalf Of Jordan, Bret
    Sent: Monday, August 22, 2016 12:55 PM
    To: Trey Darley < trey@kingfisherops.com >
    Cc: Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >; Fai, Joyce < Joyce.Fai@gd-ms.com >;
    cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil >
    Subject: Re: [cti-stix] STIX 2.1 discussion


     
    Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no "real" confidence or opinion as everything could be faked.  







     


    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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote:

     


    On 20.08.2016 08:22:15, Terry MacDonald wrote:




    My wish list for 2.1:


    +1 for Terry's list of STIX 2.1/2.2 priorities

    --
    Cheers,
    Trey
    ++--------------------------------------------------------------------------++
    Kingfisher Operations, sprl
    gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D
    ++--------------------------------------------------------------------------++
    --
    "All systems, regardless of composition, do one of three things: blow
    up, oscillate, or stay about the same." --anonymous




     
    This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited.
    Please notify the sender immediately and permanently delete the message and any attachments.

    . . .






    This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited.
    If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.





  • 10.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 19:16
    Sarah, Can you put together a proposal for Confidence?   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 22, 2016, at 11:21, Sarah Kelley < Sarah.Kelley@cisecurity.org > wrote: I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it.     I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.     Sarah Kelley Senior CERT Analyst Center for Internet Security (CIS) Integrated Intelligence Center (IIC) Multi-State Information Sharing and Analysis Center (MS-ISAC) 1-866-787-4722 (7×24 SOC) Email:  cert@cisecurity.org www.cisecurity.org Follow us @CISecurity   From:   cti-stix@lists.oasis-open.org   [ mailto:cti-stix@lists.oasis-open.org ]   On Behalf Of   Jordan, Bret Sent:   Monday, August 22, 2016 12:55 PM To:   Trey Darley < trey@kingfisherops.com > Cc:   Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >; Fai, Joyce < Joyce.Fai@gd-ms.com >;   cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil > Subject:   Re: [cti-stix] STIX 2.1 discussion   Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no real confidence or opinion as everything could be faked.     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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote:   On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities --   Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same. --anonymous   This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments.   . . . Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 11.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-22-2016 23:00
    All: I just wanted to point out this forthcoming article that will be published in Intelligence and National Security that discusses the Admiralty Code.  https://www.hks.harvard.edu/fs/rzeckhau/Evaluating%20Estimative%20Accuracy.pdf Jane Ginn On 8/22/2016 12:15 PM, Jordan, Bret wrote: Sarah, Can you put together a proposal for Confidence?   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 22, 2016, at 11:21, Sarah Kelley < Sarah.Kelley@cisecurity.org > wrote: I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it.     I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.     Sarah Kelley Senior CERT Analyst Center for Internet Security (CIS) Integrated Intelligence Center (IIC) Multi-State Information Sharing and Analysis Center (MS-ISAC) 1-866-787-4722 (7×24 SOC) Email:  cert@cisecurity.org www.cisecurity.org Follow us @CISecurity   From:   cti-stix@lists.oasis-open.org   [ mailto:cti-stix@lists.oasis-open.org ]   On Behalf Of   Jordan, Bret Sent:   Monday, August 22, 2016 12:55 PM To:   Trey Darley < trey@kingfisherops.com > Cc:   Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >; Fai, Joyce < Joyce.Fai@gd-ms.com >;   cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil > Subject:   Re: [cti-stix] STIX 2.1 discussion   Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no real confidence or opinion as everything could be faked.     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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote:   On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities --   Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same. --anonymous   This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments.   . . . -- Jane Ginn, MSIA, MRP CTI-TC Co-Secretary Cyber Threat Intelligence Network, Inc. jg@ctin.us


  • 12.  RE: [cti-stix] STIX 2.1 discussion

    Posted 08-23-2016 00:41




    Hi, Jane,
     
    It seems it is already published in 2014
     
      Why Assessing Estimative Accuracy Is Feasible and Desirable
     

    https://www.hks.harvard.edu/fs/rzeckhau/Assessing%20Estimative%20Accuracy.pdf
     
    Regards,
     
    Ryu
     


    From: cti-stix@lists.oasis-open.org
    [mailto:cti-stix@lists.oasis-open.org] On Behalf Of JG on CTI-TC
    Sent: Tuesday, August 23, 2016 8:00 AM
    To: cti-stix@lists.oasis-open.org
    Subject: Re: [cti-stix] STIX 2.1 discussion


     
    All:
    I just wanted to point out this forthcoming article that will be published in Intelligence and National Security that discusses the Admiralty Code. 

    https://www.hks.harvard.edu/fs/rzeckhau/Evaluating%20Estimative%20Accuracy.pdf
    Jane Ginn
     

    On 8/22/2016 12:15 PM, Jordan, Bret wrote:


    Sarah,

     


    Can you put together a proposal for Confidence?  







     


    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 22, 2016, at 11:21, Sarah Kelley < Sarah.Kelley@cisecurity.org > wrote:

     


    I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already
    in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database
    has a confidence on it.  


     


    I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.


     


     



    Sarah Kelley


    Senior CERT Analyst


    Center for Internet Security (CIS)


    Integrated Intelligence Center (IIC)


    Multi-State Information Sharing and Analysis Center (MS-ISAC)


    1-866-787-4722 (7×24 SOC)


    Email:  cert@cisecurity.org


    www.cisecurity.org


    Follow us @CISecurity



     




    From:   cti-stix@lists.oasis-open.org   [ mailto:cti-stix@lists.oasis-open.org ]   On
    Behalf Of   Jordan, Bret
    Sent:   Monday, August 22, 2016 12:55 PM
    To:   Trey Darley < trey@kingfisherops.com >
    Cc:   Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >;
    Fai, Joyce < Joyce.Fai@gd-ms.com >;   cti-stix@lists.oasis-open.org ;
    Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil >
    Subject:   Re: [cti-stix] STIX 2.1 discussion




     


    Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no "real" confidence
    or opinion as everything could be faked.  








     



    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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote:



     




    On 20.08.2016 08:22:15, Terry MacDonald wrote:





    My wish list for 2.1:



    +1 for Terry's list of STIX 2.1/2.2 priorities

    --  
    Cheers,
    Trey
    ++--------------------------------------------------------------------------++
    Kingfisher Operations, sprl
    gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D
    ++--------------------------------------------------------------------------++
    --
    "All systems, regardless of composition, do one of three things: blow
    up, oscillate, or stay about the same." --anonymous






     

    This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination,
    distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments.  
    . . .



     





    --
    Jane Ginn, MSIA, MRP
    CTI-TC Co-Secretary
    Cyber Threat Intelligence Network, Inc.
    jg@ctin.us






  • 13.  RE: [cti-stix] STIX 2.1 discussion

    Posted 08-23-2016 01:13
    Ryu: Thank you for pointing that out... My main point was really to point out that there have been extensive discussions on this issue on the predecessor list-serve, and on this OASIS channel. For example, Terry McDonald led a conversation on the use of the Admiralty Code well over a year ago.... I don't want us to lose the thread of that institutional memory, or this good work developed by Friedman & Zeckhauser. Jane Ginn, MSIA, MRP Cyber Threat Intelligence Network, Inc. jg@ctin.us


  • 14.  RE: [cti-stix] STIX 2.1 discussion

    Posted 08-29-2016 18:30
    Myself - I would prefer confidence be a numeric code of say 1-100 with an allowed value that maps to "unknown" (perhaps 0 or -1), and leave it up to individual implementers if they want to map that to the admiralty code in their software or not. A numeric code has this large advantage, that it can be easily adapted to match any labelling regime, and any level of granularity. Whereas, if the Admiralty code is adopted, we are "stuck" there - and that regime may be too granular for some organizations, and not granular enough for others. - Jason Keirstead STSM, 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 "Masuoka, Ryusuke" ---08/22/2016 09:41:11 PM---Hi, Jane, It seems it is already published in 2014 From: "Masuoka, Ryusuke" <masuoka.ryusuke@jp.fujitsu.com> To: JG on CTI-TC <jg@ctin.us>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> Date: 08/22/2016 09:41 PM Subject: RE: [cti-stix] STIX 2.1 discussion Sent by: <cti-stix@lists.oasis-open.org> Hi, Jane, It seems it is already published in 2014 Why Assessing Estimative Accuracy Is Feasible and Desirable https://www.hks.harvard.edu/fs/rzeckhau/Assessing%20Estimative%20Accuracy.pdf Regards, Ryu From: cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ] On Behalf Of JG on CTI-TC Sent: Tuesday, August 23, 2016 8:00 AM To: cti-stix@lists.oasis-open.org Subject: Re: [cti-stix] STIX 2.1 discussion All: I just wanted to point out this forthcoming article that will be published in Intelligence and National Security that discusses the Admiralty Code. https://www.hks.harvard.edu/fs/rzeckhau/Evaluating%20Estimative%20Accuracy.pdf Jane Ginn On 8/22/2016 12:15 PM, Jordan, Bret wrote: Sarah, Can you put together a proposal for Confidence? 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 22, 2016, at 11:21, Sarah Kelley < Sarah.Kelley@cisecurity.org > wrote: I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it. I would also push for incident (for our use) and also for internationalization for the sake of increased adoption. Sarah Kelley Senior CERT Analyst Center for Internet Security (CIS) Integrated Intelligence Center (IIC) Multi-State Information Sharing and Analysis Center (MS-ISAC) 1-866-787-4722 (7? SOC) Email: cert@cisecurity.org www.cisecurity.org Follow us @CISecurity From: cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ] On Behalf Of Jordan, Bret Sent: Monday, August 22, 2016 12:55 PM To: Trey Darley < trey@kingfisherops.com > Cc: Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >; Fai, Joyce < Joyce.Fai@gd-ms.com >; cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil > Subject: Re: [cti-stix] STIX 2.1 discussion Confidence does not really make sense before we have digital signatures, neither does the opinion object.. Without digital signatures first, there is no "real" confidence or opinion as everything could be faked. 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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote: On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4 5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- "All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same." --anonymous This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments. . . . -- Jane Ginn, MSIA, MRP CTI-TC Co-Secretary Cyber Threat Intelligence Network, Inc. jg@ctin.us




  • 15.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-29-2016 20:18
    I could get on board with that.   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 29, 2016, at 12:29, Jason Keirstead < Jason.Keirstead@ca.ibm.com > wrote: Myself - I would prefer confidence be a numeric code of say 1-100 with an allowed value that maps to unknown (perhaps 0 or -1), and leave it up to individual implementers if they want to map that to the admiralty code in their software or not. A numeric code has this large advantage, that it can be easily adapted to match any labelling regime, and any level of granularity. Whereas, if the Admiralty code is adopted, we are stuck there - and that regime may be too granular for some organizations, and not granular enough for others. - Jason Keirstead STSM, 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> Masuoka, Ryusuke ---08/22/2016 09:41:11 PM---Hi, Jane, It seems it is already published in 2014 From:     Masuoka, Ryusuke < masuoka.ryusuke@jp.fujitsu.com > To:     JG on CTI-TC < jg@ctin.us >, cti-stix@lists.oasis-open.org < cti-stix@lists.oasis-open.org > Date:     08/22/2016 09:41 PM Subject:     RE: [cti-stix] STIX 2.1 discussion Sent by:     < cti-stix@lists.oasis-open.org > Hi, Jane, It seems it is already published in 2014 Why Assessing Estimative Accuracy Is Feasible and Desirable https://www.hks.harvard.edu/fs/rzeckhau/Assessing%20Estimative%20Accuracy.pdf Regards, Ryu From:   cti-stix@lists.oasis-open.org   [ mailto:cti-stix@lists.oasis-open.org ]   On Behalf Of   JG on CTI-TC Sent:   Tuesday, August 23, 2016 8:00 AM To:   cti-stix@lists.oasis-open.org Subject:   Re: [cti-stix] STIX 2.1 discussion All: I just wanted to point out this forthcoming article that will be published in Intelligence and National Security that discusses the Admiralty Code.   https://www.hks.harvard.edu/fs/rzeckhau/Evaluating%20Estimative%20Accuracy.pdf Jane Ginn On 8/22/2016 12:15 PM, Jordan, Bret wrote: Sarah,   Can you put together a proposal for Confidence?     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 22, 2016, at 11:21, Sarah Kelley < Sarah.Kelley@cisecurity.org > wrote: I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it.   I would also push for incident (for our use) and also for internationalization for the sake of increased adoption. Sarah Kelley Senior CERT Analyst Center for Internet Security (CIS) Integrated Intelligence Center (IIC) Multi-State Information Sharing and Analysis Center (MS-ISAC) 1-866-787-4722 (7? SOC) Email:   cert@cisecurity.org www.cisecurity.org Follow us @CISecurity From:   cti-stix@lists.oasis-open.org   [ mailto:cti-stix@lists.oasis-open.org ]   On Behalf Of   Jordan, Bret Sent:   Monday, August 22, 2016 12:55 PM To:   Trey Darley < trey@kingfisherops.com > Cc:   Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >; Fai, Joyce < Joyce.Fai@gd-ms.com >;   cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil > Subject:   Re: [cti-stix] STIX 2.1 discussion Confidence does not really make sense before we have digital signatures, neither does the opinion object.. Without digital signatures first, there is no real confidence or opinion as everything could be faked.     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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote: On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities --   Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4 5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same. --anonymous This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments.   . . . --   Jane Ginn, MSIA, MRP CTI-TC Co-Secretary Cyber Threat Intelligence Network, Inc. jg@ctin.us Attachment: signature.asc Description: Message signed with OpenPGP using GPGMail


  • 16.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-29-2016 21:38




    Presuming licensing issues, if any, could be worked out,  can we provide direct support for the flexible MISP Machine Tags (Triple Tags)?


    https://github.com/MISP/misp-taxonomies


    I know we've discussed this before, but it's still not clear what the impediments are to subsuming this flexible JSON format and the growing library of community shared taxonomies.

    Patrick Maroney
    President
    Integrated Networking Technologies, Inc.
    Desk: (856)983-0001
    Cell: (609)841-5104
    Email:
    pmaroney@specere.org



    _____________________________
    From: Jason Keirstead < jason.keirstead@ca.ibm.com >
    Sent: Monday, August 29, 2016 2:30 PM
    Subject: RE: [cti-stix] STIX 2.1 discussion
    To: Masuoka, Ryusuke < masuoka.ryusuke@jp.fujitsu.com >
    Cc: < cti-stix@lists.oasis-open.org >, JG on CTI-TC < jg@ctin.us >



    Myself - I would prefer confidence be a numeric code of say 1-100 with an allowed value that maps to "unknown" (perhaps 0 or -1), and leave it up to individual implementers if they want to map that to the admiralty code in their software or not.

    A numeric code has this large advantage, that it can be easily adapted to match any labelling regime, and any level of granularity.

    Whereas, if the Admiralty code is adopted, we are "stuck" there - and that regime may be too granular for some organizations, and not granular enough for others.

    -
    Jason Keirstead
    STSM, 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


    "Masuoka, Ryusuke"
    ---08/22/2016 09:41:11 PM---Hi, Jane, It seems it is already published in 2014

    From: "Masuoka, Ryusuke" < masuoka.ryusuke@jp.fujitsu.com >
    To: JG on CTI-TC < jg@ctin.us >, " cti-stix@lists.oasis-open.org "
    < cti-stix@lists.oasis-open.org >
    Date: 08/22/2016 09:41 PM
    Subject: RE: [cti-stix] STIX 2.1 discussion
    Sent by: < cti-stix@lists.oasis-open.org >





    Hi, Jane,

    It seems it is already published in 2014

    Why Assessing Estimative Accuracy Is Feasible and Desirable
    https://www.hks.harvard.edu/fs/rzeckhau/Assessing%20Estimative%20Accuracy.pdf

    Regards,

    Ryu

    From:
    cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ]
    On Behalf Of JG on CTI-TC
    Sent: Tuesday, August 23, 2016 8:00 AM
    To:
    cti-stix@lists.oasis-open.org
    Subject: Re: [cti-stix] STIX 2.1 discussion

    All:
    I just wanted to point out this forthcoming article that will be published in Intelligence and National Security that discusses the Admiralty Code.

    https://www.hks.harvard.edu/fs/rzeckhau/Evaluating%20Estimative%20Accuracy.pdf
    Jane Ginn

    On 8/22/2016 12:15 PM, Jordan, Bret wrote:


    Sarah,

    Can you put together a proposal for Confidence?

    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 22, 2016, at 11:21, Sarah Kelley < Sarah.Kelley@cisecurity.org > wrote:

    I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts
    some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it.


    I would also push for incident (for our use) and also for internationalization for the sake of increased adoption.


    Sarah Kelley
    Senior CERT Analyst
    Center for Internet Security (CIS)
    Integrated Intelligence Center (IIC)
    Multi-State Information Sharing and Analysis Center (MS-ISAC)
    1-866-787-4722 (7? SOC)
    Email: cert@cisecurity.org
    www.cisecurity.org
    Follow us @CISecurity

    From: cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ]
    On Behalf Of Jordan, Bret
    Sent: Monday, August 22, 2016 12:55 PM
    To: Trey Darley < trey@kingfisherops.com >
    Cc: Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >;
    Fai, Joyce < Joyce.Fai@gd-ms.com >;
    cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >;
    Brule, Joseph M < jmbrule@radium.ncsc.mil >
    Subject: Re: [cti-stix] STIX 2.1 discussion

    Confidence does not really make sense before we have digital signatures, neither does the opinion object.. Without digital signatures first, there is no "real" confidence or opinion as everything could be faked.


    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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com >
    wrote:

    On 20.08.2016 08:22:15, Terry MacDonald wrote:




    My wish list for 2.1:


    +1 for Terry's list of STIX 2.1/2.2 priorities

    --
    Cheers,
    Trey
    ++--------------------------------------------------------------------------++
    Kingfisher Operations, sprl
    gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4 5B9B B30D DD6E 62C8 6C1D
    ++--------------------------------------------------------------------------++
    --
    "All systems, regardless of composition, do one of three things: blow
    up, oscillate, or stay about the same." --anonymous


    This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited.
    Please notify the sender immediately and permanently delete the message and any attachments.

    . . .





    --
    Jane Ginn, MSIA, MRP
    CTI-TC Co-Secretary
    Cyber Threat Intelligence Network, Inc.
    jg@ctin.us










  • 17.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-30-2016 11:31
    The license for MISP is AGPL, that is going to put it out of bounds. To use these taxonomies as-is, we would have to seek out all of the contributors and re-issue the works under a different license to comply with OASIS IPR (and to allow them to be useable by other non-GPL products). - Jason Keirstead STSM, 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 Patrick Maroney ---08/29/2016 06:38:14 PM---Presuming licensing issues, if any, could be worked out, can we provide direct support for the flex From: Patrick Maroney <Pmaroney@Specere.org> To: "Masuoka, Ryusuke" <masuoka.ryusuke@jp.fujitsu.com>, Jason Keirstead/CanEast/IBM@IBMCA Cc: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>, "JG on CTI-TC" <jg@ctin.us> Date: 08/29/2016 06:38 PM Subject: Re: [cti-stix] STIX 2.1 discussion Sent by: <cti-stix@lists.oasis-open.org> Presuming licensing issues, if any, could be worked out, can we provide direct support for the flexible MISP Machine Tags (Triple Tags)? https://github.com/MISP/misp-taxonomies I know we've discussed this before, but it's still not clear what the impediments are to subsuming this flexible JSON format and the growing library of community shared taxonomies. Patrick Maroney President Integrated Networking Technologies, Inc. Desk: (856)983-0001 Cell: (609)841-5104 Email: pmaroney@specere.org _____________________________ From: Jason Keirstead < jason.keirstead@ca.ibm.com > Sent: Monday, August 29, 2016 2:30 PM Subject: RE: [cti-stix] STIX 2.1 discussion To: Masuoka, Ryusuke < masuoka.ryusuke@jp.fujitsu.com > Cc: < cti-stix@lists.oasis-open.org >, JG on CTI-TC < jg@ctin.us > Myself - I would prefer confidence be a numeric code of say 1-100 with an allowed value that maps to "unknown" (perhaps 0 or -1), and leave it up to individual implementers if they want to map that to the admiralty code in their software or not. A numeric code has this large advantage, that it can be easily adapted to match any labelling regime, and any level of granularity. Whereas, if the Admiralty code is adopted, we are "stuck" there - and that regime may be too granular for some organizations, and not granular enough for others. - Jason Keirstead STSM, 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 "Masuoka, Ryusuke" ---08/22/2016 09:41:11 PM---Hi, Jane, It seems it is already published in 2014 From: "Masuoka, Ryusuke" < masuoka.ryusuke@jp.fujitsu.com > To: JG on CTI-TC < jg@ctin.us >, " cti-stix@lists.oasis-open.org " < cti-stix@lists.oasis-open.org > Date: 08/22/2016 09:41 PM Subject: RE: [cti-stix] STIX 2.1 discussion Sent by: < cti-stix@lists.oasis-open.org >
    Hi, Jane, It seems it is already published in 2014 Why Assessing Estimative Accuracy Is Feasible and Desirable https://www.hks.harvard.edu/fs/rzeckhau/Assessing%20Estimative%20Accuracy.pdf Regards, Ryu From: cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ] On Behalf Of JG on CTI-TC Sent: Tuesday, August 23, 2016 8:00 AM To: cti-stix@lists.oasis-open.org Subject: Re: [cti-stix] STIX 2.1 discussion All: I just wanted to point out this forthcoming article that will be published in Intelligence and National Security that discusses the Admiralty Code. https://www.hks.harvard.edu/fs/rzeckhau/Evaluating%20Estimative%20Accuracy.pdf Jane Ginn On 8/22/2016 12:15 PM, Jordan, Bret wrote: Sarah, Can you put together a proposal for Confidence? 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 22, 2016, at 11:21, Sarah Kelley < Sarah.Kelley@cisecurity.org > wrote: I would argue for the confidence as well. I understand that you want it to interact with digital signatures, but I know we’re using it already in STIX 1.x. We use the confidence field as Terry described, to give our analysts some hint how much they should care about something if they see it in traffic or how likely we believe it could be to cause false positives. Every single thing in our database has a confidence on it. I would also push for incident (for our use) and also for internationalization for the sake of increased adoption. Sarah Kelley Senior CERT Analyst Center for Internet Security (CIS) Integrated Intelligence Center (IIC) Multi-State Information Sharing and Analysis Center (MS-ISAC) 1-866-787-4722 (7? SOC) Email: cert@cisecurity.org www.cisecurity.org Follow us @CISecurity From: cti-stix@lists.oasis-open.org [ mailto:cti-stix@lists.oasis-open.org ] On Behalf Of Jordan, Bret Sent: Monday, August 22, 2016 12:55 PM To: Trey Darley < trey@kingfisherops.com > Cc: Terry MacDonald < terry.macdonald@cosive.com >; Jyoti Verma (jyoverma) < jyoverma@cisco.com >; Fai, Joyce < Joyce.Fai@gd-ms.com >; cti-stix@lists.oasis-open.org ; Kemp, David P < dpkemp@nsa.gov >; Brule, Joseph M < jmbrule@radium.ncsc.mil > Subject: Re: [cti-stix] STIX 2.1 discussion Confidence does not really make sense before we have digital signatures, neither does the opinion object.. Without digital signatures first, there is no "real" confidence or opinion as everything could be faked. 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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote: On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++--------------------------------------------------------------------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4 5B9B B30D DD6E 62C8 6C1D ++--------------------------------------------------------------------------++ -- "All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same." --anonymous This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments. . . . -- Jane Ginn, MSIA, MRP CTI-TC Co-Secretary Cyber Threat Intelligence Network, Inc. jg@ctin.us




  • 18.  Re: [cti-stix] STIX 2.1 discussion

    Posted 09-02-2016 15:22
    On 30/08/16 13:30, Jason Keirstead wrote: > The license for MISP is AGPL, that is going to put it out of bounds. Only the MISP software is AGPL. The taxonomies are clearly separated from the MISP software to cover such case and not under the AGPL terms but CC0. > To use these taxonomies as-is, we would have to seek out all of the > contributors and re-issue the works under a different license to comply > with OASIS IPR (and to allow them to be useable by other non-GPL products). Nope. The default license for MISP taxonomies is CCO (public domain)[1] except if one of the author of the taxonomy decided to license it under a different one. For my understanding, public domain is compatible with the OASIS IPR. I hope this clarifies. Cheers. [1] https://creativecommons.org/publicdomain/zero/1.0/ -- Alexandre Dulaunoy CIRCL - Computer Incident Response Center Luxembourg 41, avenue de la gare L-1611 Luxembourg info@circl.lu - www.circl.lu


  • 19.  Re: [cti-stix] STIX 2.1 discussion

    Posted 09-02-2016 15:34
    Alexandre - that is great news, thanks for the clarification. - Jason Keirstead STSM, 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 Alexandre Dulaunoy ---09/02/2016 12:21:41 PM---On 30/08/16 13:30, Jason Keirstead wrote: > The license for MISP is AGPL, that is going to put it ou From: Alexandre Dulaunoy <Alexandre.Dulaunoy@circl.lu> To: cti-stix@lists.oasis-open.org Date: 09/02/2016 12:21 PM Subject: Re: [cti-stix] STIX 2.1 discussion Sent by: <cti-stix@lists.oasis-open.org> On 30/08/16 13:30, Jason Keirstead wrote: > The license for MISP is AGPL, that is going to put it out of bounds. Only the MISP software is AGPL. The taxonomies are clearly separated from the MISP software to cover such case and not under the AGPL terms but CC0. > To use these taxonomies as-is, we would have to seek out all of the > contributors and re-issue the works under a different license to comply > with OASIS IPR (and to allow them to be useable by other non-GPL products). Nope. The default license for MISP taxonomies is CCO (public domain)[1] except if one of the author of the taxonomy decided to license it under a different one. For my understanding, public domain is compatible with the OASIS IPR. I hope this clarifies. Cheers. [1] https://creativecommons.org/publicdomain/zero/1.0/ -- Alexandre Dulaunoy CIRCL - Computer Incident Response Center Luxembourg 41, avenue de la gare L-1611 Luxembourg info@circl.lu - www.circl.lu --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php  


  • 20.  Re: [cti-stix] STIX 2.1 discussion

    Posted 08-23-2016 01:30
      |   view attached
    I would disagree. We had confidence in STIX v1.x without digital signatures, and it worked ok. We urgently need to give content creators the ability to convey how confident they are that their threat intel assertion is true. It is the only way that consumers will be able to make their own decisions about whether to believe the assertion(s) they have received, or to ignore them. This is also critical to enable decisions to be made on how to use the threat intel. Additionally, understanding what the other sharing community members think of particular threat intelligence assertions is key too. Threat Intel Analysts are rare. Not every organization will have access to them. We need to give organizations the ability to receive guidance from other organizations they trust to enable them to better protect themselves. We need the ability for community members to tell others that they think a threat intel assertion is good or bad. Other Organizations with new analysts, or no analysts will then be able to learn from these assertions who to trust... effectively crowdsourcing their knowledge from the opinions of others. If I am a consumer and I see that there are a lot of opinion objects from community members disagreeing with Threat Intel from Vendor A, then I am less likely to trust what they say. If there are opinion objects from community members agreeing with Vendor B's threat intel, then I am more likely to trust what they say. Both Confidence and the Opinion object will have a profound effect on how people will use their threat intel, and on whose threat intel they trust.   If I have received a low confidence domain name indicator associated with a threat actor I care about, but I don't trust the content creator very much, I am not likely to block it on the firewall, but I might be likely to add it to my IDS sensor alert. If I have a high confidence domain name indicator associated with a threat actor I care about, from a content creator I do trust highly, then I am more likely to throw it in my firewall block list, or in my DNS RPZ blocklist. This can all happen without Digital Signatures, as the sharing communities now do the same thing between organizations they trust over email. Digital signatures only become important when we try to do this over open, public, unvetted sharing communities. And while these communities are needed eventually, they are not needed now. Which is why I believe digital signatures can wait for STIX 2.2. Cheers Terry MacDonald   Chief Product Officer M:   +64 211 918 814 E:   terry.macdonald@cosive.com W:   www.cosive.com On Tue, Aug 23, 2016 at 4:54 AM, Jordan, Bret < bret.jordan@bluecoat.com > wrote: Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no "real" confidence or opinion as everything could be faked.   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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote: On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++---------------------------- ------------------------------ ----------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D ++---------------------------- ------------------------------ ----------------++ -- "All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same." --anonymous


  • 21.  Re: [cti-stix] STIX 2.1 discussion

    Posted 09-06-2016 22:16
    Picking up on this thread late, of course, but this sort of argument applies to everything and nothing. Whenever STIX data is transmitted from one entity to another, it is always between authenticated entities, on a cryptographically secure link providing both authentication, integrity, and confidentiality - one hopes. While a mis-trusted peer entity could supply you with bogus confidence objects, it can also suppress actual confidence in existing information, too - which can be just as disruptive, if not more so. It can strip out the information itself, of course. And in both cases, this can be a valid thing to do. So digital signatures add, at best, a mechanism for assuring information that the peer has already decided to pass onto you. One valid reason for stripping the signature (and perhaps re-signing) is to protect the identities involved. Repeatedly, we've found that assured anonymity is a vital part of ensuring that a community's confidence in sharing information safely remains high. While all this is not to say that digital signatures aren't a worthwhile goal, I do repeat - they're far from a panacea, and introduce issues of their own. (On a more pragmatic nature, digital signatures are easy - JOSE and done - the tricky part is key distribution and authentication without introducing a second secured path). Dave. On 22 Aug 2016 17:54, "Jordan, Bret" < bret.jordan@bluecoat.com > wrote: Confidence does not really make sense before we have digital signatures, neither does the opinion object..  Without digital signatures first, there is no "real" confidence or opinion as everything could be faked.   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 22, 2016, at 01:34, Trey Darley < trey@kingfisherops.com > wrote: On 20.08.2016 08:22:15, Terry MacDonald wrote: My wish list for 2.1: +1 for Terry's list of STIX 2.1/2.2 priorities -- Cheers, Trey ++---------------------------- ------------------------------ ----------------++ Kingfisher Operations, sprl gpg fingerprint: 85F3 5F54 4A2A B4CD 33C4  5B9B B30D DD6E 62C8 6C1D ++---------------------------- ------------------------------ ----------------++ -- "All systems, regardless of composition, do one of three things: blow up, oscillate, or stay about the same." --anonymous