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

 


Help: OASIS Mailing Lists Help | MarkMail Help

cyber-council message

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


Subject: [OASIS Issue Tracker] (CYBERCOUNC-2) Business Justification for OpenC2


     [ https://issues.oasis-open.org/browse/CYBERCOUNC-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duncan Sparrell updated CYBERCOUNC-2:
-------------------------------------

    Description: 
Sounil Yu gave an excellent presentation to the Standards Council on Monday Nov 6, 2017. At the meeting, one of the attendees (someone tell me who and I'll fill in their name) asked that someone give the business reasons behind OpenC2. He mentioned he was a Board member for a bank and he'd like to know about the business justification and what OpenC2 will mean to Board members - ie at a plane above the technical level of the TC.

There are several reasons for creating this issue:
1. to provide fodder for the other issue on 'what are the rules for issues' (CYBERCOUNC-1) so we'd have a concrete example
2. part of work plan is to figure out exactly what is the role of the Standards Council. If we accept this issue, work it, and it seems useful - this issue might model a standard role for the Council. Ie TC's work the technical details and Standards Council works the business reasoning justifying when to use or not use, the various cybersecurity standards within the Council scope (STIX, TAXII, OpenC2, KIMP, ....).
3. to answer his question

  was:
Sounil Yu gave an excellent presentation to the Standards Council on Monday Nov 6, 2017. At the meeting, one of the attendees (someone tell me who and I'll fill in their name) asked that someone give the business reasons behind OpenC2. He mentioned he was a Board member for a bank and he'd like to know about the business justification and what OpenC2 will mean to Board members - ie at a plane above the technical level of the TC.

There are several reasons for creating this issue:
1. to provide fodder for the other issue on 'what are the rules for issues' so we'd have a concrete example
2. part of work plan is to figure out exactly what is the role of the Standards Council. If we accept this issue, work it, and it seems useful - this issue might model a standard role for the Council. Ie TC's work the technical details and Standards Council works the business reasoning justifying when to use or not use, the various cybersecurity standards within the Council scope (STIX, TAXII, OpenC2, KIMP, ....).
3. to answer his question


> Business Justification for OpenC2 
> ----------------------------------
>
>                 Key: CYBERCOUNC-2
>                 URL: https://issues.oasis-open.org/browse/CYBERCOUNC-2
>             Project: Cyber Standards Council
>          Issue Type: Task
>            Reporter: Duncan Sparrell
>
> Sounil Yu gave an excellent presentation to the Standards Council on Monday Nov 6, 2017. At the meeting, one of the attendees (someone tell me who and I'll fill in their name) asked that someone give the business reasons behind OpenC2. He mentioned he was a Board member for a bank and he'd like to know about the business justification and what OpenC2 will mean to Board members - ie at a plane above the technical level of the TC.
> There are several reasons for creating this issue:
> 1. to provide fodder for the other issue on 'what are the rules for issues' (CYBERCOUNC-1) so we'd have a concrete example
> 2. part of work plan is to figure out exactly what is the role of the Standards Council. If we accept this issue, work it, and it seems useful - this issue might model a standard role for the Council. Ie TC's work the technical details and Standards Council works the business reasoning justifying when to use or not use, the various cybersecurity standards within the Council scope (STIX, TAXII, OpenC2, KIMP, ....).
> 3. to answer his question



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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