Definition of ROLIE CSIRT Extension
draft-banghart-mile-rolie-csirt-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
MILE Working Group                                              J. Field
Internet-Draft                                                   Pivotal
Intended status: Informational                               S. Banghart
Expires: May 4, 2017                                                NIST
                                                        October 31, 2016

                  Definition of ROLIE CSIRT Extension
                   draft-banghart-mile-rolie-csirt-00

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.

Contributing to this document

   The source for this draft is being maintained in GitHub.  Suggested
   changes should be submitted as pull requests at
   <https://github.com/CISecurity/ROLIE>.  Instructions are on that page
   as well.  Editorial changes can be managed in GitHub, but any
   substantial issues need to be discussed on the MILE mailing list.

Status of This Memo

   This Internet-Draft is submitted to IETF 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 http://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 May 4, 2017.

Field & Banghart           Expires May 4, 2017                  [Page 1]
Internet-Draft                 ROLIE CSIRT                  October 2016

Copyright Notice

   Copyright (c) 2016 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
   (http://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  New information-types . . . . . . . . . . . . . . . . . . . .   4
     3.1.  The "incident" information type . . . . . . . . . . . . .   4
     3.2.  The "indicator" information type  . . . . . . . . . . . .   5
   4.  Usage of CSIRT Information Types in the Atom       Publishing
       Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  / (forward slash) Resource URL  . . . . . . . . . . . . .   5
   5.  Usage of CSIRT Information Types in the atom:feed element . .   5
   6.  Usage of CSIRT Information Types in an atom:entry . . . . . .   5
     6.1.  Use of the atom:link element  . . . . . . . . . . . . . .   6
       6.1.1.  Link relations for the 'incident'
               information-type  . . . . . . . . . . . . . . . . . .   6
       6.1.2.  Link relations for the 'indicator'
               information-type  . . . . . . . . . . . . . . . . . .   6
       6.1.3.  Link relations for both information-types . . . . . .   7
     6.2.  Use of the rolie:format element . . . . . . . . . . . . .   7
       6.2.1.  IODEF Format  . . . . . . . . . . . . . . . . . . . .   8
       6.2.2.  STIX Format . . . . . . . . . . . . . . . . . . . . .   8
     6.3.  Additional requirements for use of IODEF  . . . . . . . .   8
       6.3.1.  The IODEF Document  . . . . . . . . . . . . . . . . .   8
       6.3.2.  Category Element  . . . . . . . . . . . . . . . . . .   9
       6.3.3.  Entry Elements  . . . . . . . . . . . . . . . . . . .   9
       6.3.4.  User Authorization  . . . . . . . . . . . . . . . . .  10
       6.3.5.  Expectation and Impact Classes  . . . . . . . . . . .  10
       6.3.6.  Search  . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  incident information-type . . . . . . . . . . . . . . . .  11
     7.2.  indicator information-type  . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
Show full document text