Re: [Cacao] Call for CACAO Charter Consensus

On Fri, May 10, 2019 at 6:52 AM <Carolin.Baumgartner@interdiscount.ch>
wrote:

> I am still interested and support the charter. I am not sure what to make
> out of this sentence though
>
>
>
> “The working group may decide to not publish the use cases and
> requirements; and test documents.”
>
>
>

[Joe] Since these documents are informational it is the choice of the
working group and chairs to determine whether they want to spend the
resources to take these documents through the entire IETF process to
publication.   Since they are listed as deliverables the expectation is
that we would get working group consensus on these documents.

> I am willing to review documents
>
>
>
> Carolin
>
>
>
> *From: *Cacao <cacao-bounces@ietf.org> on behalf of Joseph Salowey <
> joe@salowey.net>
> *Date: *Friday, 10 May 2019 at 15:39
> *To: *"cacao@ietf.org" <cacao@ietf.org>
> *Subject: *[Cacao] Call for CACAO Charter Consensus
>
>
>
> At the CACAO meeting at IETF 105 in Prague there was significant interest in the CACAO problem statement.  We want to reach consensus for a charter for a working group.  A draft charter has been posted to the list [1]..
>
> We need to continue this discussion on the email list as well as gauge continued interest in participating in this work.  Please do so by responding to the following questions:
>
>
>
>   1.  Do you support this charter text (full text also provided at the end of email or at [1])?  Please submit objections or blocking concerns to the list.
>
>   2.  Are you willing to author or participate in the development of the drafts of this WG?
>
>   3.  Are you willing to help review the drafts of this WG?
>
>   4.  Are you interested in implementing drafts of this WG?
>
>
>
> Please provide comments including proposed text changes ASAP to provide ample time for discussion.  This call for consensus ends on May 27, 2019.
>
>
>
> Thanks,
>
> Joe & Chris
>
> [1] https://mailarchive.ietf.org/arch/msg/cacao/QKVvohhYvwU46jcsLYyYY1agPTU
>
>
>
> Charter text copied below:
>
> --------------
>
> # Introduction
>
> To defend against threat actors and their tactics, techniques, and procedures, organizations need to manually identify, create, and document prevention, mitigation, and remediation steps. These steps when grouped together into a course of action (COA) / playbook are used to protect systems, networks, data, and users. The problem is, once these steps have been created there is no standardized and structured way to document them, verify they were correctly executed, or easily share them across organizational boundaries and technology stacks.
>
>
>
>
>
> This working group will create a standard that implements the playbook model for cybersecurity operations.
>
>
>
>
>
> This solution will specifically enable:
>
>
>
>
>
>  1. the creation and documentation of COAs in a structured machine-readable format
>
>  2. organizations to perform attestation including verification and authentication  on COAs
>
>  3. the sharing and distribution of COAs across organizational boundaries and technology stacks that may include protocols, apis, interfaces and other related technology to support sharing.
>
>  4. the verification of COA correctness prior to deployment.
>
>  5. the monitoring of COA activity after successful deployment.
>
>
>
>
>
> This solution will contain (at a minimum) a standard JSON based data model, a defined set of functional capabilities and associated interfaces, and a protocol. This solution will also provide a data model for systems to confirm the status of the COA execution, however, it will be agnostic of how the COA is implemented by the system.
>
>
>
>
>
> Each collaborative course of action, such as recommended prevention, mitigation and remediation steps, will consist of a sequence of cyber defense actions that can be executed by the various systems that can act on those actions. Further, these COAs will be coordinated and deployed across heterogeneous cyber security systems such that both the actions requested and the resultant outcomes may be verified. These COA actions will be referenceable in a data structure like the OASIS STIX V2 model that provides support for related data such as threat actors, campaigns, intrusion sets, malware, attack patterns, and other adversarial techniques, tactics, and procedures.
>
>
>
>
>
> Where possible the working group will consider existing efforts, like OASIS OpenC2 and IETF I2NSF that define the atomic actions to be included in a process or sequence. The working group will not consider how shared actions are used/enforced, except where a response is expected for a specific action or step.
>
>
>
>
>
> # Goals and Deliverables
>
> This working group has the following major goals and deliverables
>
>
>
>
>
>  - CACAO Use Cases and Requirements
>
>    - Specify the use cases and requirements
>
>  - CACAO Functional Architecture: Roles and Interfaces
>
>    - Specify the system functions and roles that are needed to enable Collaborative Courses of Action
>
>  - CACAO Protocol Specification
>
>    - Specify and standardize the configuration for at least one protocol that can be used to distribute courses of action in both a direct delivery and publish-subscribe method
>
>  - CACAO Distribution and Response Application Layer Protocol
>
>    - Specify the protocol which may include apis, interfaces and other related technology to support the requirements identified for the protocol.
>
>  - CACAO JSON Data Model
>
>    - Create a JSON data model that can capture and enable collaborative courses of action
>
>  - CACAO Interoperability Test Documents
>
>    - Define and create a series of tests and documents to assist with interoperability of the various systems involved.
>
>
>
>
>
> The working group may decide to not publish the use cases and requirements; and test documents. That decision will be made during the lifetime of the working group.
>
> --
> Cacao mailing list
> Cacao@ietf.org
> https://www.ietf.org/mailman/listinfo/cacao
>