Definition of ROLIE CSIRT Extension
draft-ietf-mile-rolie-csirt-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

MILE Working Group                                           S. Banghart
Internet-Draft                                                      NIST
Intended status: Informational                                  J. Field
Expires: September 27, 2019                                      Pivotal
                                                          March 26, 2019

                  Definition of ROLIE CSIRT Extension
                     draft-ietf-mile-rolie-csirt-02

Abstract

   This document extends the Resource-Oriented Lightweight Information
   Exchange (ROLIE) core to add the information type categories and
   related requirements needed to support Computer Security Incident
   Response Team (CSIRT) use cases.  The indicator and incident
   information types are defined as ROLIE extensions.  Additional
   supporting requirements are also defined that describe the use of
   specific formats and link relations pertaining to the new information
   types.

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 September 27, 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

Banghart & Field       Expires September 27, 2019               [Page 1]
Internet-Draft                 ROLIE CSIRT                    March 2019

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Additional Requirements for the Atom Publishing Protocol  . .   4
     3.1.  Use of HTTP requests  . . . . . . . . . . . . . . . . . .   4
       3.1.1.  / (forward slash) Resource URL  . . . . . . . . . . .   4
   4.  Information-type Extensions . . . . . . . . . . . . . . . . .   4
     4.1.  The "incident" information type . . . . . . . . . . . . .   4
     4.2.  The "indicator" information type  . . . . . . . . . . . .   5
   5.  Data format requirements  . . . . . . . . . . . . . . . . . .   5
     5.1.  Incident Object Description Exchange Format . . . . . . .   6
       5.1.1.  Description . . . . . . . . . . . . . . . . . . . . .   6
       5.1.2.  Requirements  . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Structured Threat Information eXpression (STIX) Format  .   7
       5.2.1.  Description . . . . . . . . . . . . . . . . . . . . .   7
       5.2.2.  Requirements  . . . . . . . . . . . . . . . . . . . .   7
     5.3.  Malware Information Sharing Platform (MISP) Format  . . .   7
       5.3.1.  Creating MISP Event Entries . . . . . . . . . . . . .   8
       5.3.2.  MISP Feeds and Manifests  . . . . . . . . . . . . . .   8
   6.  atom:link Extensions  . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Link relations for the 'incident'
           information-type  . . . . . . . . . . . . . . . . . . . .   9
     6.2.  Link relations for the 'indicator'
           information-type  . . . . . . . . . . . . . . . . . . . .  10
     6.3.  Link relations for both information-types . . . . . . . .  11
   7.  atom:category Extensions  . . . . . . . . . . . . . . . . . .  11
     7.1.  Newly registered category values  . . . . . . . . . . . .  12
     7.2.  Expectation and Impact Classes  . . . . . . . . . . . . .  12
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  information-type registrations  . . . . . . . . . . . . .  12
       8.1.1.  incident information-type . . . . . . . . . . . . . .  13
       8.1.2.  indicator information-type  . . . . . . . . . . . . .  13
     8.2.  atom:category scheme registrations  . . . . . . . . . . .  13
       8.2.1.  category:csirt:iodef:purpose  . . . . . . . . . . . .  13
       8.2.2.  category:csirt:iodef:restriction  . . . . . . . . . .  13
     8.3.  rolie:property name registrations . . . . . . . . . . . .  14