Collaborative Automated Course of Action Operations (CACAO) for Cyber Security
draft-jordan-cacao-charter-06

Document Type Active Internet-Draft (individual)
Last updated 2019-06-20
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IETF                                                           B. Jordan
Internet-Draft                                      Symantec Corporation
Intended status: Informational                                A. Thomson
Expires: December 22, 2019                            LookingGlass Cyber
                                                                J. Verma
                                                           Cisco Systems
                                                           June 20, 2019

 Collaborative Automated Course of Action Operations (CACAO) for Cyber
                                Security
                     draft-jordan-cacao-charter-06

Abstract

   This is the charter for the Working Group: Collaborative Automated
   Course of Action Operations (CACAO) for Cyber Security

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 22, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Jordan, et al.          Expires December 22, 2019               [Page 1]
Internet-Draft                    CACAO                        June 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Goals and Deliverables  . . . . . . . . . . . . . . . . . . .   3
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  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 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 or easily share them across organizational
   boundaries and technological solutions.

   This working group will create a standard that implements the course
   of action playbook model for cybersecurity operations.  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.  These courses of actions should be
   referenceable by other cyber threat intelligence that provides
   support for related data such as threat actors, campaigns, intrusion
   sets, malware, attack patterns, and other adversarial techniques,
   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:

   1.  the creation and documentation of course of action playbooks in a
       structured machine-readable format

   2.  organizations to digitally sign course of action playbooks

   3.  the securely sharing and distribution of course of action
       playbooks across organizational boundaries and technological
       solutions

Jordan, et al.          Expires December 22, 2019               [Page 2]
Internet-Draft                    CACAO                        June 2019

   4.  the creation and documentation of processing instructions for
       course of action playbooks in a machine readable format

   .

   This solution will contain at a minimum a data model that can be used
   to specify course of action playbooks; a defined set of functional
Show full document text