< draft-jordan-cacao-charter-05.txt   draft-jordan-cacao-charter-06.txt >
IETF B. Jordan IETF B. Jordan
Internet-Draft Symantec Corporation Internet-Draft Symantec Corporation
Intended status: Informational A. Thomson Intended status: Informational A. Thomson
Expires: December 14, 2019 LookingGlass Cyber Expires: December 22, 2019 LookingGlass Cyber
J. Verma J. Verma
Cisco Systems Cisco Systems
June 12, 2019 June 20, 2019
Collaborative Automated Course of Action Operations (CACAO) for Cyber Collaborative Automated Course of Action Operations (CACAO) for Cyber
Security Security
draft-jordan-cacao-charter-05 draft-jordan-cacao-charter-06
Abstract Abstract
This is the charter for the Working Group: Collaborative Automated This is the charter for the Working Group: Collaborative Automated
Course of Action Operations (CACAO) for Cyber Security Course of Action Operations (CACAO) for Cyber Security
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 14, 2019. This Internet-Draft will expire on December 22, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Goals and Deliverables . . . . . . . . . . . . . . . . . . . 3 2. Goals and Deliverables . . . . . . . . . . . . . . . . . . . 3
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
To defend against threat actors and their tactics, techniques, and To defend against threat actors and their tactics, techniques, and
procedures, organizations need to manually identify, create, and procedures, organizations need to manually identify, create, and
document prevention, mitigation, and remediation steps. These steps document prevention, mitigation, and remediation steps. These steps
when grouped together into a course of action playbook are used to when grouped together into a course of action playbook are used to
protect systems, networks, data, and users. The problem is, once protect systems, networks, data, and users. The problem is, once
these steps have been created there is no standardized and structured these steps have been created there is no standardized and structured
way to document them or easily share them across organizational way to document them or easily share them across organizational
boundaries and technology stacks. boundaries and technological solutions.
This working group will create a standard that implements the course This working group will create a standard that implements the course
of action playbook model for cybersecurity operations. Each of action playbook model for cybersecurity operations. Each
collaborative course of action, such as recommended prevention, collaborative course of action, such as recommended prevention,
mitigation and remediation steps, will consist of a sequence of cyber mitigation and remediation steps, will consist of a sequence of cyber
defense actions that can be executed by the various systems that can defense actions that can be executed by the various systems that can
act on those actions. These courses of actions should be act on those actions. These courses of actions should be
referenceable by other cyber threat intelligence that provides referenceable by other cyber threat intelligence that provides
support for related data such as threat actors, campaigns, intrusion support for related data such as threat actors, campaigns, intrusion
sets, malware, attack patterns, and other adversarial techniques, sets, malware, attack patterns, and other adversarial techniques,
tactics, and procedures. tactics, and procedures.
It is out of scope of the WG to define or recommend actual
investigation, detection, prevention, mitigation, and remediation
steps for a given threat. The working group will not consider how
shared actions are operationalized on specific systems, except where
it is necessary for those actions to interact with the playbook
including the response expected for a specific action or step.
This solution will specifically enable: This solution will specifically enable:
1. the creation and documentation of course of action playbooks in a 1. the creation and documentation of course of action playbooks in a
structured machine-readable format structured machine-readable format
2. organizations to digitally sign course of action playbooks 2. organizations to digitally sign course of action playbooks
3. the securely sharing and distribution of course of action 3. the securely sharing and distribution of course of action
playbooks across organizational boundaries and technology stacks playbooks across organizational boundaries and technological
solutions
4. the creation and documentation of processing instructions for 4. the creation and documentation of processing instructions for
course of action playbooks in a machine readable format course of action playbooks in a machine readable format
. .
This solution will contain at a minimum a data model specifying the This solution will contain at a minimum a data model that can be used
course of action playbooks; a defined set of functional capabilities to specify course of action playbooks; a defined set of functional
and associated interfaces; and an exchange protocol between products. capabilities and associated interfaces; and an exchange protocol
Where possible the working group may reuse and/or reference existing between products. Where possible the working group may reuse and/or
data models, like OASIS OpenC2 and other IETF standards (e.g., I2NSF, reference existing data models, like OASIS OpenC2 and other IETF
YANG, NETCONF, etc) that define the atomic actions to be included in standards (e.g., NETCONF, RESTCONF, DOTS, I2NSF, etc.) that define
a process or sequence. the atomic actions of a course of action playbook.
2. Goals and Deliverables 2. Goals and Deliverables
This working group has the following major goals and deliverables This working group has the following major goals and deliverables
o CACAO Use Cases and Requirements o CACAO Use Cases and Requirements
* Specify the use cases and requirements * Specify the use cases and requirements
o CACAO Functional Architecture: Roles and Interfaces o CACAO Functional Architecture: Roles and Interfaces
* Specify the system functions and roles that are needed to * Specify the system functions and roles that are needed to
enable Collaborative Courses of Action enable Collaborative Courses of Action
o CACAO Protocol Specification o CACAO Protocol Specification
* Specify and standardize the configuration for at least one * Identify and standardize the configuration for at least one
protocol that can be used to distribute courses of action in protocol that can be used to distribute course of action
both a direct delivery and publish-subscribe method playbooks over the interfaces identified in the CACAO
functional architecture. The WG may choose to use one or more
protocols to address the requirements of both a direct delivery
and publish-subscribe method
o CACAO JSON Data Model o CACAO JSON Data Model
* Create a JSON data model that can capture and enable * Create a JSON data model that can capture and enable
collaborative courses of action collaborative courses of action
o CACAO Interoperability Test Documents o CACAO Interoperability Test Documents
* Define and create a series of tests and documents to assist * Define and create a series of tests and documents to assist
with interoperability of the various systems involved. with interoperability of the various systems involved.
 End of changes. 10 change blocks. 
17 lines changed or deleted 28 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/