Ballot Details: Approve STIX 2.0 Working Draft 1 as a Committee Specification Draft (CLOSED) |
|||||||||
Ballot Question | Do you approve STIX 2.0 Working Draft 1 and all associated artifacts packaged together as a Committee Specification Draft (CSD) and designate the Microsoft™ Word version as authoritative? | ||||||||
Ballot Description | The .zip file containing the Multi-part CSD is provided here: https://www.oasis-open.org/committees/document.php?document_id=59847&wg_abbrev=cti The Five Parts of the Multi-Part CSD are as follows: 1. stix-v2.0-wd01-part1-stix-core 2. stix-v2.0-wd01-part2-stix-objects 3. stix-v2.0-wd01-part3-cyber-observable-core 4. stix-v2.0-wd01-part4-cyber-observable-objects 5. stix-v2.0-wd01-part5-stix-patterning |
||||||||
Ballot Options |
VOTING CLOSED: Friday, 3 February 2017 @ 8:00 pm EST
|
||||||||
Open Date | Friday, 20 January 2017 @ 8:00 pm EST | ||||||||
Close Date | Friday, 3 February 2017 @ 8:00 pm EST | ||||||||
Ballot Type | Official, as defined by organization policies and procedures |
Number of votes cast (excluding abstentions) | 38 | |
Eligible members who have voted | 39 of 59 | 66.102% |
Eligible members who have not voted | 20 of 59 | 33.898% |
Options with highest number of votes are bold | ||
Option | # Votes | % of Total |
---|---|---|
Yes | 38 | 100% |
No | 0 | 0% |
Abstain | 1 |
Voter Name | Company |
Vote
![]() |
Time (UTC) | Comments |
---|---|---|---|---|
![]() |
IBM | Yes | 2017-01-26 17:37:00 | |
![]() |
NC4 | Yes | 2017-01-23 12:56:00 | |
![]() |
Mitre Corporation | Yes | 2017-01-23 21:13:00 | |
![]() |
Mitre Corporation | Yes | 2017-01-23 12:35:00 | |
![]() |
US Department of Defense (DoD) | Yes | 2017-02-02 14:32:00 | |
![]() |
GDS | Yes | 2017-01-23 10:55:00 | |
![]() |
NC4 | Yes | 2017-01-23 13:51:00 | |
![]() |
Intel Corporation | Yes | 2017-01-26 18:14:00 | |
![]() |
VeriSign | Yes | 2017-01-27 02:08:00 | |
![]() |
Kingfisher Operations, sprl | Yes | 2017-01-21 10:18:00 | |
![]() |
NC4 | Yes | 2017-01-23 12:50:00 | |
![]() |
Cyber Threat Intelligence Network, Inc. (C... | Yes | 2017-01-21 01:12:00 | |
![]() |
New Context Services, Inc. | Yes | 2017-02-01 23:25:00 | |
![]() |
New Context Services, Inc. | Yes | 2017-01-26 16:59:00 | |
![]() |
Symantec Corp. | Yes | 2017-01-21 01:11:00 | |
![]() |
NEC Corporation | Yes | 2017-01-26 16:26:00 | |
![]() |
US Department of Defense (DoD) | Yes | 2017-01-23 20:19:00 | |
![]() |
IBM | Yes | 2017-01-21 01:12:00 | |
![]() |
Center for Internet Security (CIS) | Yes | 2017-01-23 13:05:00 | |
![]() |
Mitre Corporation | Yes | 2017-01-23 17:44:00 | |
![]() |
Mitre Corporation | Yes | 2017-01-26 17:03:00 | |
![]() |
Individual | Yes | 2017-01-22 20:41:00 | |
![]() |
Wapack Labs LLC | Yes | 2017-01-23 18:09:00 | |
![]() |
Fujitsu Limited | Yes | 2017-01-27 04:57:00 | |
![]() |
FireEye, Inc. | Yes | 2017-02-02 22:44:00 | |
![]() |
Mitre Corporation | Yes | 2017-01-22 15:12:00 | |
![]() |
Kaiser Permanente | Yes | 2017-01-26 16:03:00 | |
![]() |
New Context Services, Inc. | Yes | 2017-01-27 02:19:00 | |
![]() |
U.S. Bank | Yes | 2017-01-26 16:58:00 | |
![]() |
New Context Services, Inc. | Yes | 2017-01-21 01:20:00 | |
![]() |
DHS Office of Cybersecurity and Communicat... | Yes | 2017-01-23 21:30:00 | |
![]() |
NC4 | Yes | 2017-01-23 13:26:00 | |
![]() |
LookingGlass | Yes | 2017-01-21 15:08:00 | |
![]() |
LookingGlass | Yes | 2017-01-23 15:40:00 | |
![]() |
Dell | Yes | 2017-01-25 23:32:00 | |
![]() |
IBM | Yes | 2017-01-26 19:55:00 | |
![]() |
LookingGlass | Yes | 2017-01-23 12:59:00 | |
![]() |
Mitre Corporation | Yes | 2017-01-21 01:13:00 | |
![]() |
DHS Office of Cybersecurity and Communicat... | Abstain | 2017-01-30 21:46:00 | 1 |
![]() |
Difi-Agency for Public Management and eGov... | -- | ||
![]() |
GDS | -- | ||
![]() |
Mitre Corporation | -- | ||
![]() |
Perch | -- | ||
![]() |
Bank of America | -- | ||
![]() |
Mitre Corporation | -- | ||
![]() |
Individual | -- | ||
![]() |
US Department of Defense (DoD) | -- | ||
![]() |
VeriSign | -- | ||
![]() |
GDS | -- | ||
![]() |
Hitachi, Ltd. | -- | ||
![]() |
FireEye, Inc. | -- | ||
![]() |
NC4 | -- | ||
![]() |
TELUS | -- | ||
![]() |
Yanna Technologies LLC | -- | ||
![]() |
Hewlett Packard Enterprise (HPE) | -- | ||
![]() |
GDS | -- | ||
![]() |
Hitachi, Ltd. | -- | ||
![]() |
Australia and New Zealand Banking Group (A... | -- | ||
![]() |
GDS | -- |
Submitter | Vote ![]() |
Comment |
---|---|---|
Taylor, Marlon DHS Office of Cybersecurity and Communicat... |
Abstain | STIX Objects are organized into "SDO"s and "SRO"s. SROs are limited in the fact they can not be used as a "source" or "target" of a relationship. The working draft doesn't provide rules for determining what factors go in to considering whether an object should be a SDO or SRO. As the list of STIX Objects extends upon this version, the question of "whether an object should is (or should be) an SDO or SRO?" will continue to arise and we as a technical committee should provide clear documentation to explain how objects are categorized. Without doing so now, while we have already categorized objects and claimed unique features for each category, we leave ourselves open to inconsistencies. We should provide clear documentation for determining SDO or SRO categorization and ensure our existing objects align accordingly. |