OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti-cybox message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [cti-cybox] Formalizing Consensus - CybOX


Yes, if you could have a simple JSON example for each of the items under "Review" in preparation of them becoming Draft.   That would be really helpful.  

Further thinking, maybe we should add that to the requirements of something becoming draft status... It needs to have an example.  


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 May 4, 2016, at 10:34, Kirillov, Ivan A. <ikirillov@mitre.org> wrote:

Do you mean a JSON example? E.g., for the Image File extension:

{
   
"type": "file-object",
   
"id": "file-object--1",
   
"hashes": {"md5": "B4D33B0C7306351B9ED96578465C5579"},
   
"extended_properties": {"image-file-extension": {
       
"image_is_compressed": true,
       
"exif_tags": {
           
"make": "Nikon",
           
"model": "D7000",
           
"xresolution": 4928,
           
"yresolution": 3264
       
}
   
}}
}

Regards,
Ivan

From:  <cti-cybox@lists.oasis-open.org> on behalf of Bret Jordan <bret.jordan@bluecoat.com>
Date: Wednesday, May 4, 2016 at 10:24 AM
To: Ivan Kirillov <ikirillov@mitre.org>
Cc: "cti-cybox@lists.oasis-open.org" <cti-cybox@lists.oasis-open.org>
Subject: Re: [cti-cybox] Formalizing Consensus - CybOX

It might help if each of these had a simple example following the properties table to show how this might be used.  It is kind of hard to understand what each of these mean in a bigger context. 


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 May 4, 2016, at 09:29, Kirillov, Ivan A. <ikirillov@mitre.org> wrote:

All,

Following in the footsteps of STIX, we’d like to move towards a more formal process of gaining consensus on CybOX entities. Thus, we’ve used the STIX status concepts as a baseline and came up with the following:
  • Content coming into the document starts as a Concept
  • Once the community begins to work on the topic it will move to the Development phase. During this phase, the group will flesh out the design and come up with normative text.  
  • As the group comes to general consensus it will move to a Review phase. As co-chairs, we will send a note to the list stating that a topic is ready for formal review. Any comments received during this phase will be discussed via email or during the Thursday CybOX working session.
  • A topic will move into its final Draft phase, based on the views of the co-chairs on having formal consensus, to include receiving no comments/objections. If this cannot be established, a formal motion for a ballot will be made on the email list; however, we’d like to avoid this if at all possible due to the large number of CybOX entities. Draft status doesn’t mean that the text cannot change. Editorial changes can be made throughout the process without going back to earlier phases, however, if material changes are needed, the topic under review would move back to the Development phase and start again.  
Based on this, we’ve gone through the CybOX 3.0 specification and marked each entity accordingly.

Accordingly, we welcome your feedback and comments on the items currently ready for Review :


Regards,
Ivan


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]