OASIS Cyber Threat Intelligence (CTI) TC

 View Only
  • 1.  RE: [cti] twigs has been merged into STIX Pre-draft Specification Document

    Posted 03-18-2016 03:52
    Great work everyone. Does this mean that now the TC/SC can go through each item in document to discuss/evaluate its rationale to lend into approval/amendments/rejection of the document and/or the items within? -Marlon   From: cti@lists.oasis-open.org on behalf of Piazza, Rich Sent: Tuesday, March 15, 2016 3:09:59 PM To: cti@lists.oasis-open.org Subject: [cti] twigs has been merged into STIX Pre-draft Specification Document As suggested at RSA, the twigs documentation has been merged into the STIX Pre-draft Specification document (see http://stixproject.github.io/stix2.0/ )   This involved merging in only concepts from twigs that were not in the Pre-draft doc already, because consensus had been “reached”. Much of the work of the merge was to format the twigs content as we had agreed on in the existing doc.  Any cv mentioned in the TLOs was added.   If your favorite part of the twigs document wasn’t merged in, it probably wound up in one of the “playgrounds”.   The document was reviewed by Sean, John, Bret and myself – cleaning up the existing comments.   If you haven’t looked at this doc recently, you might want make a pass over it and add any new comments for the team to consider.                   Rich      


  • 2.  RE: [cti] twigs has been merged into STIX Pre-draft Specification Document

    Posted 03-18-2016 14:26
    Anybody and everybody should be encouraged to put comments and suggested changes into the google docs.  Please avoid using the edit mode, otherwise, it is difficult to track changes.   Bret put in a status table for the TLOs in the “cover page” document ( https://docs.google.com/document/d/1yvqWaPPnPW-2NiVCLqzRszcx91ffMowfT5MmE9Nsy_w/edit?usp=sharing ).  As you can see, most TLOs are in the Proposal stage, which means they were just copied over from the twigs strawman doc.  That doesn’t mean you shouldn’t comment on those, but the ones under development probably are the ones to prioritize.   From: Taylor, Marlon [mailto:Marlon.Taylor@hq.dhs.gov] Sent: Thursday, March 17, 2016 11:52 PM To: Piazza, Rich <rpiazza@mitre.org>; cti@lists.oasis-open.org Cc: Marlon (US-CERT) <marlon.taylor@us-cert.gov> Subject: RE: [cti] twigs has been merged into STIX Pre-draft Specification Document   Great work everyone. Does this mean that now the TC/SC can go through each item in document to discuss/evaluate its rationale to lend into approval/amendments/rejection of the document and/or the items within? -Marlon   From: cti@lists.oasis-open.org on behalf of Piazza, Rich Sent: Tuesday, March 15, 2016 3:09:59 PM To: cti@lists.oasis-open.org Subject: [cti] twigs has been merged into STIX Pre-draft Specification Document As suggested at RSA, the twigs documentation has been merged into the STIX Pre-draft Specification document (see http://stixproject.github.io/stix2.0/ )   This involved merging in only concepts from twigs that were not in the Pre-draft doc already, because consensus had been “reached”. Much of the work of the merge was to format the twigs content as we had agreed on in the existing doc.  Any cv mentioned in the TLOs was added.   If your favorite part of the twigs document wasn’t merged in, it probably wound up in one of the “playgrounds”.   The document was reviewed by Sean, John, Bret and myself – cleaning up the existing comments.   If you haven’t looked at this doc recently, you might want make a pass over it and add any new comments for the team to consider.                   Rich