Re: [Cacao] Proposed Charter Text

<mohamed.boucadair@orange.com> Tue, 11 December 2018 13:11 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: cacao@ietfa.amsl.com
Delivered-To: cacao@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9784128A6E for <cacao@ietfa.amsl.com>; Tue, 11 Dec 2018 05:11:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9VMU3cOJnmeX for <cacao@ietfa.amsl.com>; Tue, 11 Dec 2018 05:11:26 -0800 (PST)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CD97127332 for <cacao@ietf.org>; Tue, 11 Dec 2018 05:11:26 -0800 (PST)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 43DgLh5ZTPz8tWw; Tue, 11 Dec 2018 14:11:24 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.60]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 43DgLh4WLYzBrLT; Tue, 11 Dec 2018 14:11:24 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0415.000; Tue, 11 Dec 2018 14:11:22 +0100
From: mohamed.boucadair@orange.com
To: Bret Jordan <jordan.ietf@gmail.com>, "cacao@ietf.org" <cacao@ietf.org>
CC: JACQUENET Christian TGI/OLN <christian.jacquenet@orange.com>
Thread-Topic: [Cacao] Proposed Charter Text
Thread-Index: AQHUjSKiK1uLheoim0uzETVcqIl3kaV5iszg
Date: Tue, 11 Dec 2018 13:11:21 +0000
Message-ID: <7f5c77db-96e6-4ea5-af0a-75d7a7e58e30@OPEXCLILM7F.corporate.adroot.infra.ftgroup>
References: <B0A1DA88-8E3A-45CA-9669-6CC3CE6A0354@gmail.com> <800D200B-C838-48DE-9776-801F3332773D@gmail.com>
In-Reply-To: <800D200B-C838-48DE-9776-801F3332773D@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: multipart/alternative; boundary="_000_7f5c77db96e64ea5af0a75d7a7e58e30OPEXCLILM7Fcorporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cacao/5mQLWF9ydOSxwTNaBCyf7XENsus>
Subject: Re: [Cacao] Proposed Charter Text
X-BeenThere: cacao@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Collaborative Automated Course of Action Operations <cacao.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cacao>, <mailto:cacao-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cacao/>
List-Post: <mailto:cacao@ietf.org>
List-Help: <mailto:cacao-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cacao>, <mailto:cacao-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2018 13:11:35 -0000

Hi Bret,

Thank you for drafting and sharing a proposed charter.

I don’t have a gmail account, so I cannot modify the text online.

FWIW, please find our proposed modifications and comments to this proposed charter, both doc and pdf version are included:

doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/cacao-proposed%20charter-rev%2011122018a.docx
pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/cacao-proposed%20charter-rev%2011122018a.pdf

Cheers,
Med

De : Cacao [mailto:cacao-bounces@ietf.org] De la part de Bret Jordan
Envoyé : jeudi 6 décembre 2018 06:15
À : cacao@ietf.org
Objet : Re: [Cacao] Proposed Charter Text

Any comments or suggestions for changes to this proposed charter?

Bret
Sent from my Commodore 128D


PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

On Dec 2, 2018, at 9:50 AM, Bret Jordan <jordan.ietf@gmail.com<mailto:jordan.ietf@gmail.com>> wrote:
All,

Here is some proposed charter text for this working group.  Please send me any suggestions or changes you would like to see.  You can see the live version as a Google Doc here: https://docs.google.com/document/d/1Kh7HEWeqj4-zWuPNDflDkKNJUaqZAOmUl9pBJBRjvv8/edit#<https://docs.google.com/document/d/1Kh7HEWeqj4-zWuPNDflDkKNJUaqZAOmUl9pBJBRjvv8/edit>

I am also attached it in IETF draft document form, not sure which was I should do it. The text is below…




Problem
Threat Actors and Intrusion Sets are advancing at an increasing rate relative to cyber defense. Further, cyber defenders typically have to manually identify and process prevention, mitigation, and remediation steps in order to protect their systems, networks, data, and users.

Due to this increase and sophistication of cyber attacks the need for a secure mechanism that would enable system and network operators to respond to threats in machine relevant time has raised significantly. While some attacks may be well known to certain security experts and cyber researchers they are often not documented in a way that would enable automated mitigation or remediation.. A documented language for describing prevention, mitigation, and remediation actions is critical for cyber defenders to respond more quickly and reduce the exposure from an attack.


Working Group
To enable and assist cyber defense, the Collaborative Automated Course of Action Operations (CACAO) for Cyber Security working group will focus on creating a solution to securely document and share the actions needed to prevent, mitigate, and remediate threats. This effort will focus on providing an information model, data serialization, and transport for defining, sharing, and processing Collaborative Automated Course of Action Operations (CACAO).

Each collaborative course of action will consist of a sequence of cyber defense actions that can be coordinated and deployed across a set of heterogeneous cyber security systems such that both the actions requested and the resultant outcomes may be monitored and verified.

The primary focus of this proposed working group will be the definition and the distribution of the sequence of actions (perhaps in a tree or graph). Where possible we will leverage existing efforts that *may* define the atomic actions to be included in a process or sequence.


Goals
This working group has the following major goals:
* Identify and document the use cases and requirements

* Create an information and data model that can capture and enable collaborative courses of action (sometimes called playbooks) that can be used to automate some parts of cyber defense

* Identify and document the system functions and roles that must exist with associated protocols to exchange information between those system functions

* Identify and document the configuration for a series of protocols that can be used to distribute courses of action in both direct delivery and publish-subscribe methods

* Define and create a series of tests and documents to assist with interoperability

Deliverables
The working group plans to create informational and standards track draft documents some of which may be published through the IETF RFC stream.

Within the first year, the working group aims to:
1. Identify a solution for capturing and distributing multiple sequenced atomic actions, whether they be manual or automated.
2. Publish a standards track draft solution that can be used by organizations and vendors to create and distribute Courses of Action / Playbooks.


<draft-jordan-cacao-charter-00.txt>

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."