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

Document Type Active Internet-Draft (mile WG)
Last updated 2019-10-28
Replaces draft-banghart-mile-rolie-csirt
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
MILE Working Group                                           S. Banghart
Internet-Draft                                                      NIST
Intended status: Standards Track                                J. Field
Expires: April 30, 2020                                          Pivotal
                                                        October 28, 2019

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

Abstract

   This document extends the Resource-Oriented Lightweight Information
   Exchange (ROLIE) core to add the Indicator and Incident information
   types, relevant categories, and related requirements needed to
   support Computer Security Incident Response Team (CSIRT) use cases.
   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 April 30, 2020.

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

Banghart & Field         Expires April 30, 2020                 [Page 1]
Internet-Draft                 ROLIE CSIRT                  October 2019

   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.  Information-type Extensions . . . . . . . . . . . . . . . . .   4
     3.1.  The "incident" information type . . . . . . . . . . . . .   4
     3.2.  The "indicator" information type  . . . . . . . . . . . .   5
   4.  Data format requirements  . . . . . . . . . . . . . . . . . .   5
     4.1.  Incident Object Description Exchange Format . . . . . . .   6
       4.1.1.  Description . . . . . . . . . . . . . . . . . . . . .   6
       4.1.2.  Requirements  . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Structured Threat Information eXpression (STIX) Format  .   6
       4.2.1.  Description . . . . . . . . . . . . . . . . . . . . .   7
       4.2.2.  Requirements  . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Malware Information Sharing Platform (MISP) Format  . . .   7
       4.3.1.  Creating MISP Event Entries . . . . . . . . . . . . .   8
       4.3.2.  MISP Feeds and Manifests  . . . . . . . . . . . . . .   8
   5.  atom:link Extensions  . . . . . . . . . . . . . . . . . . . .   9
     5.1.  Link relations for the 'incident'
           information-type  . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Link relations for the 'indicator'
           information-type  . . . . . . . . . . . . . . . . . . . .  10
     5.3.  Link relations for both information-types . . . . . . . .  10
   6.  atom:category Extensions  . . . . . . . . . . . . . . . . . .  11
     6.1.  Newly registered category values  . . . . . . . . . . . .  11
     6.2.  Expectation and Impact Classes  . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  information-type registrations  . . . . . . . . . . . . .  12
       7.1.1.  incident information-type . . . . . . . . . . . . . .  12
       7.1.2.  indicator information-type  . . . . . . . . . . . . .  12
     7.2.  atom:category scheme registrations  . . . . . . . . . . .  12
       7.2.1.  category:csirt:iodef:purpose  . . . . . . . . . . . .  13
       7.2.2.  category:csirt:iodef:restriction  . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  15
Show full document text