draft-ietf-mile-rolie-csirt-03.txt   draft-ietf-mile-rolie-csirt-04.txt 
MILE Working Group S. Banghart MILE Working Group S. Banghart
Internet-Draft NIST Internet-Draft NIST
Intended status: Informational J. Field Intended status: Informational J. Field
Expires: January 21, 2020 Pivotal Expires: January 23, 2020 Pivotal
July 20, 2019 July 22, 2019
Definition of ROLIE CSIRT Extension Definition of ROLIE CSIRT Extension
draft-ietf-mile-rolie-csirt-03 draft-ietf-mile-rolie-csirt-04
Abstract Abstract
This document extends the Resource-Oriented Lightweight Information This document extends the Resource-Oriented Lightweight Information
Exchange (ROLIE) core to add the information type categories and Exchange (ROLIE) core to add the information type categories and
related requirements needed to support Computer Security Incident related requirements needed to support Computer Security Incident
Response Team (CSIRT) use cases. The indicator and incident Response Team (CSIRT) use cases. The indicator and incident
information types are defined as ROLIE extensions. Additional information types are defined as ROLIE extensions. Additional
supporting requirements are also defined that describe the use of supporting requirements are also defined that describe the use of
specific formats and link relations pertaining to the new information specific formats and link relations pertaining to the new information
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 21, 2020. This Internet-Draft will expire on January 23, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
4. Data format requirements . . . . . . . . . . . . . . . . . . 5 4. Data format requirements . . . . . . . . . . . . . . . . . . 5
4.1. Incident Object Description Exchange Format . . . . . . . 5 4.1. Incident Object Description Exchange Format . . . . . . . 5
4.1.1. Description . . . . . . . . . . . . . . . . . . . . . 5 4.1.1. Description . . . . . . . . . . . . . . . . . . . . . 5
4.1.2. Requirements . . . . . . . . . . . . . . . . . . . . 6 4.1.2. Requirements . . . . . . . . . . . . . . . . . . . . 6
4.2. Structured Threat Information eXpression (STIX) Format . 6 4.2. Structured Threat Information eXpression (STIX) Format . 6
4.2.1. Description . . . . . . . . . . . . . . . . . . . . . 6 4.2.1. Description . . . . . . . . . . . . . . . . . . . . . 6
4.2.2. Requirements . . . . . . . . . . . . . . . . . . . . 6 4.2.2. Requirements . . . . . . . . . . . . . . . . . . . . 6
4.3. Malware Information Sharing Platform (MISP) Format . . . 7 4.3. Malware Information Sharing Platform (MISP) Format . . . 7
4.3.1. Creating MISP Event Entries . . . . . . . . . . . . . 7 4.3.1. Creating MISP Event Entries . . . . . . . . . . . . . 7
4.3.2. MISP Feeds and Manifests . . . . . . . . . . . . . . 8 4.3.2. MISP Feeds and Manifests . . . . . . . . . . . . . . 8
5. atom:link Extensions . . . . . . . . . . . . . . . . . . . . 9 5. atom:link Extensions . . . . . . . . . . . . . . . . . . . . 8
5.1. Link relations for the 'incident' 5.1. Link relations for the 'incident'
information-type . . . . . . . . . . . . . . . . . . . . 9 information-type . . . . . . . . . . . . . . . . . . . . 9
5.2. Link relations for the 'indicator' 5.2. Link relations for the 'indicator'
information-type . . . . . . . . . . . . . . . . . . . . 9 information-type . . . . . . . . . . . . . . . . . . . . 9
5.3. Link relations for both information-types . . . . . . . . 10 5.3. Link relations for both information-types . . . . . . . . 10
6. atom:category Extensions . . . . . . . . . . . . . . . . . . 10 6. atom:category Extensions . . . . . . . . . . . . . . . . . . 10
6.1. Newly registered category values . . . . . . . . . . . . 10 6.1. Newly registered category values . . . . . . . . . . . . 10
6.2. Expectation and Impact Classes . . . . . . . . . . . . . 11 6.2. Expectation and Impact Classes . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7.1. information-type registrations . . . . . . . . . . . . . 11 7.1. information-type registrations . . . . . . . . . . . . . 11
7.1.1. incident information-type . . . . . . . . . . . . . . 11 7.1.1. incident information-type . . . . . . . . . . . . . . 11
7.1.2. indicator information-type . . . . . . . . . . . . . 12 7.1.2. indicator information-type . . . . . . . . . . . . . 11
7.2. atom:category scheme registrations . . . . . . . . . . . 12 7.2. atom:category scheme registrations . . . . . . . . . . . 12
7.2.1. category:csirt:iodef:purpose . . . . . . . . . . . . 12 7.2.1. category:csirt:iodef:purpose . . . . . . . . . . . . 12
7.2.2. category:csirt:iodef:restriction . . . . . . . . . . 12 7.2.2. category:csirt:iodef:restriction . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9. Normative References . . . . . . . . . . . . . . . . . . . . 13 9. Normative References . . . . . . . . . . . . . . . . . . . . 13
Appendix A. Examples of Use . . . . . . . . . . . . . . . . . . 14 Appendix A. Examples of Use . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
skipping to change at page 6, line 15 skipping to change at page 6, line 15
4.1.2. Requirements 4.1.2. Requirements
For an Entry to be considered as a "IODEF Entry", it MUST fulfill the For an Entry to be considered as a "IODEF Entry", it MUST fulfill the
following conditions: following conditions:
o The information-type of the Entry is "indicator" or "incident". o The information-type of the Entry is "indicator" or "incident".
For a typical Entry, this is derived from the information type of For a typical Entry, this is derived from the information type of
the Feed it is contained in. For a standalone Entry, this is the Feed it is contained in. For a standalone Entry, this is
provided by an "atom:category" element. provided by an "atom:category" element.
o
o The document linked to by the "href" attribute of the o The document linked to by the "href" attribute of the
"atom:content" element is an IODEF document as per [RFC7970] "atom:content" element is an IODEF document as per [RFC7970]
A "IODEF Entry" MUST conform to the following requirements: A "IODEF Entry" MUST conform to the following requirements:
o The value of the "type" attribute of the "atom:content" element o The value of the "type" attribute of the "atom:content" element
MUST be "application/xml". MUST be "application/xml".
o There MUST be at least one "rolie:property" with the "name" o There MUST be at least one "rolie:property" with the "name"
attribute equal to "urn:ietf:params:rolie:property:content-id" and attribute equal to "urn:ietf:params:rolie:property:content-id" and
skipping to change at page 7, line 5 skipping to change at page 6, line 51
4.2.2. Requirements 4.2.2. Requirements
For an Entry to be considered as a "STIX Entry", it MUST fulfill the For an Entry to be considered as a "STIX Entry", it MUST fulfill the
following conditions: following conditions:
o The information-type of the Entry is "indicator" or "incident". o The information-type of the Entry is "indicator" or "incident".
For a typical Entry, this is derived from the information type of For a typical Entry, this is derived from the information type of
the Feed it is contained in. For a standalone Entry, this is the Feed it is contained in. For a standalone Entry, this is
provided by an "atom:category" element. provided by an "atom:category" element.
o
o The document linked to by the "href" attribute of the o The document linked to by the "href" attribute of the
"atom:content" element is a STIX object as per [stix2] "atom:content" element is a STIX object as per [stix2]
A "STIX Entry" MUST conform to the following requirements: A "STIX Entry" MUST conform to the following requirements:
o The value of the "type" attribute of the "atom:content" element o The value of the "type" attribute of the "atom:content" element
MUST be "application/xml" or "application/json". MUST be "application/xml" or "application/json".
o There MUST be at least one "rolie:property" with the "name" o There MUST be at least one "rolie:property" with the "name"
attribute equal to "urn:ietf:params:rolie:property:content-id" and attribute equal to "urn:ietf:params:rolie:property:content-id" and
skipping to change at page 8, line 14 skipping to change at page 8, line 9
o There should be at least one "rolie:property" with the "name" o There should be at least one "rolie:property" with the "name"
attribute equal to "urn:ietf:params:rolie:property:content-id" and attribute equal to "urn:ietf:params:rolie:property:content-id" and
the "value" attribute exactly equal to the "<uuid>" element in the the "value" attribute exactly equal to the "<uuid>" element in the
attached MISP Event . This allows for ROLIE consumers to more attached MISP Event . This allows for ROLIE consumers to more
easily search for MISP Events without needing to download the easily search for MISP Events without needing to download the
document itself. document itself.
o It is also recommended to expose information in the ROLIE Entry o It is also recommended to expose information in the ROLIE Entry
that is required and recommended to expose in the MISP Manifest that is required and recommended to expose in the MISP Manifest
format. THis ensures better compatibility between a ROLIE Feed format. This ensures better compatibility between a ROLIE Feed
and a MISP Manifest and a MISP Manifest
* The following fields are required by the MISP draft: info, * The following fields are required by the MISP draft: info,
Orgc, timestamp, date Orgc, timestamp, date
* The following fields are recommended by the MISP draft: * The following fields are recommended by the MISP draft:
analysis, threat_level_id analysis, threat_level_id
4.3.2. MISP Feeds and Manifests 4.3.2. MISP Feeds and Manifests
skipping to change at page 10, line 48 skipping to change at page 10, line 37
Table 3: Link Relations for Resource-Oriented Lightweight Indicator Table 3: Link Relations for Resource-Oriented Lightweight Indicator
Exchange Exchange
6. atom:category Extensions 6. atom:category Extensions
6.1. Newly registered category values 6.1. Newly registered category values
This document registers two additional registered atom:category This document registers two additional registered atom:category
names: 'urn:ietf:params:rolie:category:csirt:iodef:purpose' and names: 'urn:ietf:params:rolie:category:csirt:iodef:purpose' and
'urn:ietf:params:rolie:category:csirt:iodef:restriction'. These 'urn:ietf:params:rolie:category:csirt:iodef:restriction'. These
categories IODEF content exposure provides valuable metadata for the categories expose important information from inside the attached
searching and organization of IODEF documents. IODEF document. The Purpose and Restriction elements are often used
to sort or cateogrize IODEF documents, and in some use cases,
determine the security and access permissions of the document.
When the name attribute of the category is When the name attribute of the category is
'urn:ietf:params:rolie:category:csirt:iodef:purpose', the value 'urn:ietf:params:rolie:category:csirt:iodef:purpose', the value
attribute SHOULD be constrained as per section 3.2 of IODEF attribute SHOULD be constrained as per section 3.2 of IODEF
[RFC7970], e.g. traceback, mitigation, reporting, or other. [RFC7970], e.g. traceback, mitigation, reporting, or other.
When the name attribute of the category is When the name attribute of the category is
'urn:ietf:params:rolie:category:csirt:iodef:restriction', the value 'urn:ietf:params:rolie:category:csirt:iodef:restriction', the value
attribute SHOULD be constrained as per section 3.2 of IODEF attribute SHOULD be constrained as per section 3.2 of IODEF
[RFC7970], e.g. public, need-to-know, private, default. [RFC7970], e.g. public, need-to-know, private, default.
skipping to change at page 13, line 14 skipping to change at page 13, line 5
When providing a private workspace for closed sharing, it is When providing a private workspace for closed sharing, it is
recommended that the ROLIE repository checks user authorization when recommended that the ROLIE repository checks user authorization when
the user sends a GET request to the service document. If the user is the user sends a GET request to the service document. If the user is
not authorized to send any requests to a given workspace or not authorized to send any requests to a given workspace or
collection, that workspace or collection should be truncated from the collection, that workspace or collection should be truncated from the
service document in the response. In this way the existence of service document in the response. In this way the existence of
unauthorized content remains unknown to potential attackers, unauthorized content remains unknown to potential attackers,
hopefully reducing attack surface. hopefully reducing attack surface.
When sharing IODEF 2 documents using a ROLIE server, care should be
taken to seperate IODEF Entries into different workspaces based on
the "restriction" attribute of the IODEF Document (and therefore the
restriction property in ROLIE). Security and access controls are
most effectively deployed at the workspace level, as such, keeping
private and need-to-know IODEF documents in their own workspace helps
prevent unintended information leakage.
9. Normative References 9. Normative References
[I-D.dulaunoy-misp-core-format] [I-D.dulaunoy-misp-core-format]
Dulaunoy, A. and A. Iklody, "MISP core format", draft- Dulaunoy, A. and A. Iklody, "MISP core format", draft-
dulaunoy-misp-core-format-07 (work in progress), February dulaunoy-misp-core-format-07 (work in progress), February
2019. 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
 End of changes. 10 change blocks. 
13 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/