Subject: [Cacao] Updated Charter version 03

From: Bret Jordan <[email-masked]>
Date: Thu, 31 Jan 2019 16:53:46 -0700

All,

Thanks for all of the great feedback on the charter text.  We have updated the document to address all comments that we have received and are releasing a new version of the text.  You can see it here: https://datatracker.ietf.org/doc/draft-jordan-cacao-charter/ <https://datatracker.ietf.org/doc/draft-jordan-cacao-charter/> and copied below.

### BEGIN

# 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 based on current industry best practices for cybersecurity. 

This solution will specifically enable:

 1. the creation and documentation of COAs in a structured machine-readable format
 2. organizations to perform attestations on COAs
 3. the sharing and distribution of COAs across organizational boundaries and technology stacks
 4. the verification of deployed COAs. 

This solution will contain (at a minimum) a standard JSON based data model, a defined set of functional capabilities and associated interfaces, and a mandatory to implement protocol. This solution will also provide a data model for actuators to confirm the status of the COA execution, however, it will be agnostic of how the COA is implemented by the actuator.

Each collaborative course of action 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 connected data structure like the OASIS STIX V2 model that provides support for connected data such as threat actors, campaigns, intrusion sets, malware, attack patterns, and other adversarial techniques, tactics, and procedures (TTPs). 

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. Some of the deliverables may be published through the IETF RFC stream as informational or standards track documents.

 - 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
   - Identify and document the requirements to effectively report and alert on the deployment of CACAO actions and the potential threat response to those actions
 - 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 as RFCs. That decision will be made during the lifetime of the working group. 

### END

Thanks,
Bret
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."