Ballot Details: Resolution for the Formation of the Actuator Profile Subcommittee under the OpenC2 Technical Committee (CLOSED) |
|||||||||
Ballot Question | Shall we form the Actuator Profile Subcommittee | ||||||||
Ballot Description | Resolution to form the OpenC2 Actuator Profile Subcommittee of the OpenC2 Technical Committee Preamble: Whereas the OpenC2 Technical Committee * was chartered to address matters as they pertain to command and control of cyber defense technologies, and * the charter defined the drafting of documents, specifications, lexicons and other artifacts to fulfill the needs of cyber security command and control as being within the scope of the work, and * the charter acknowledges that the standard will require the integration of existing and future technologies, and * it is not pragmatic for a single language description document to encompass all aspects of the cyber defense industry, Then be it resolved: A subcommittee known as the Actuator Profile Subcommittee (SC) shall be formed with two co-equal chairs and any number of secretaries, document editors, and other support as deemed appropriate by the chairs; using working methods agreed to by the SC; with the Statement of Purpose per the attached. The SC shall create and deliberate actuator profiles which identify the actions, targets and modifiers that are meaningful to a given cyber defense function. The SC shall present each actuator profile to the committee as a whole for consideration as an addition to the repository of OpenC2 artifacts. OpenC2 Actuator Profile Subcommittee co-chairs The initial OpenC2 Actuator Profile SC co-chairs, as voted at the inaugural meeting of the OpenC2 Technical Committee, shall be: *Kemp, David and *Verma, Jyoti --------------------- Attachment ------------------------ Statement of Purpose The Actuator Profile Subcommittee is responsible for creating and maintaining actuator profiles which define the OpenC2 message elements applicable to specific cyber defense functions. The OpenC2 language description is intended to be relatively stable as technology and product capabilities evolve. Profiles are intended both to segment the function space so that developers need not be concerned with message elements that do not apply to a specific actuator function, and to define the message elements needed to accommodate new functions. A profile will define the actions, targets, actuator specifiers, and modifiers that are mandatory to implement in order to claim conformance with the profile, as well as optional elements that are meaningful in the context of the profile. All interested parties are welcome to participate in evolving OpenC2 as members of the Actuator Profile Subcommittee. List of Deliverables * A template for actuator profiles * A list of actuator profiles and their status (planned, in-progress, complete) * Draft and completed actuator profile documents |
||||||||
Ballot Options |
VOTING CLOSED: Monday, 3 July 2017 @ 11:00 am EDT
|
||||||||
Open Date | Monday, 26 June 2017 @ 11:00 am EDT | ||||||||
Close Date | Monday, 3 July 2017 @ 11:00 am EDT | ||||||||
Ballot Type | Official, as defined by organization policies and procedures |
Number of votes cast (excluding abstentions) | 29 | |
Eligible members who have voted | 29 of 53 | 54.717% |
Eligible members who have not voted | 24 of 53 | 45.283% |
Options with highest number of votes are bold | ||
Option | # Votes | % of Total |
---|---|---|
Yes | 29 | 100% |
No | 0 | 0% |
Abstain | 0 |
Voter Name | Company |
Vote
![]() |
Time (UTC) | Comments |
---|---|---|---|---|
![]() |
Moviri SPA | Yes | 2017-07-03 07:00:00 | |
![]() |
Individual | Yes | 2017-06-30 17:15:00 | |
![]() |
NIST | Yes | 2017-06-30 14:48:00 | |
![]() |
National Security Agency | Yes | 2017-06-27 12:08:00 | |
![]() |
New Context Services, Inc. | Yes | 2017-06-27 07:05:00 | |
![]() |
NC4 | Yes | 2017-07-01 01:37:00 | |
![]() |
Moviri SPA | Yes | 2017-07-01 07:07:00 | |
![]() |
National Security Agency | Yes | 2017-06-26 20:27:00 | |
![]() |
Anomali | Yes | 2017-06-26 20:50:00 | |
![]() |
National Security Agency | Yes | 2017-06-30 14:41:00 | |
![]() |
Nteligen, LLC | Yes | 2017-06-30 14:57:00 | |
![]() |
New Context Services, Inc. | Yes | 2017-06-29 22:21:00 | |
![]() |
Individual | Yes | 2017-06-26 20:43:00 | |
![]() |
NEC Corporation | Yes | 2017-06-30 07:05:00 | |
![]() |
G2 | Yes | 2017-06-27 16:02:00 | |
![]() |
Wapack Labs LLC | Yes | 2017-06-26 21:53:00 | |
![]() |
FireEye, Inc. | Yes | 2017-07-02 15:56:00 | |
![]() |
FireEye, Inc. | Yes | 2017-06-30 17:55:00 | |
![]() |
ThreatConnect, Inc. | Yes | 2017-06-30 15:29:00 | |
![]() |
Individual | Yes | 2017-06-30 20:58:00 | |
![]() |
National Security Agency | Yes | 2017-06-27 02:57:00 | |
![]() |
Northrop Grumman | Yes | 2017-06-26 20:37:00 | |
![]() |
sFractal Consulting LLC | Yes | 2017-06-28 23:31:00 | |
![]() |
New Context Services, Inc. | Yes | 2017-06-30 17:17:00 | |
![]() |
Fornetix | Yes | 2017-06-28 20:11:00 | |
![]() |
NC4 | Yes | 2017-06-30 20:10:00 | |
![]() |
LookingGlass | Yes | 2017-06-26 21:14:00 | |
![]() |
Cisco Systems | Yes | 2017-06-30 20:35:00 | |
![]() |
Bank of America | Yes | 2017-06-30 14:17:00 | |
![]() |
FireEye, Inc. | -- | ||
![]() |
Swimlane, LLC | -- | ||
![]() |
North American Energy Standards Board | -- | ||
![]() |
University of North Carolina at Chapel Hill | -- | ||
![]() |
Cyber Threat Intelligence Network, Inc. (C... | -- | ||
![]() |
Lumeta Corporation | -- | ||
![]() |
IBM | -- | ||
![]() |
New Context Services, Inc. | -- | ||
![]() |
Syncurity | -- | ||
![]() |
Symantec Corp. | -- | ||
![]() |
NEC Corporation | -- | ||
![]() |
National Security Agency | -- | ||
![]() |
Mitre Corporation | -- | ||
![]() |
McAfee | -- | ||
![]() |
McAfee | -- | ||
![]() |
ViaSat | -- | ||
![]() |
Centripetal Networks | -- | ||
![]() |
Symantec Corp. | -- | ||
![]() |
Financial Services Information Sharing and... | -- | ||
![]() |
New Context Services, Inc. | -- | ||
![]() |
SailPoint Technologies | -- | ||
![]() |
Phantom | -- | ||
![]() |
Electric Power Research Institute (EPRI) | -- | ||
![]() |
NIST | -- |