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

Document Type Active Internet-Draft (individual)
Last updated 2019-01-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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: August 4, 2019                               LookingGlass Cyber
                                                                J. Verma
                                                           Cisco Systems
                                                        January 31, 2019

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

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 August 4, 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 August 4, 2019                 [Page 1]
Internet-Draft                    CACAO                     January 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 (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

Jordan, et al.           Expires August 4, 2019                 [Page 2]
Internet-Draft                    CACAO                     January 2019

   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
Show full document text