Definition of the ROLIE Vulnerability Extension
draft-ietf-mile-rolie-vuln-01

Document Type Active Internet-Draft (mile WG)
Last updated 2019-07-21
Replaces draft-banghart-mile-rolie-vuln
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html 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: Informational                             July 20, 2019
Expires: January 21, 2020

            Definition of the ROLIE Vulnerability Extension
                     draft-ietf-mile-rolie-vuln-01

Abstract

   This document extends the Resource-Oriented Lightweight Information
   Exchange (ROLIE) core to add the information type categories and
   related requirements needed to support Vulnerability use cases.
   Additional categories, properties, and requirements based on content
   type enables a higher level of interoperability between ROLIE
   implementations, and richer metadata for ROLIE consumers.  In
   particular, usage of the Common Vulnerability Enumeration (CVE) [cve]
   format is discussed.

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 January 21, 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                Expires January 21, 2020                [Page 1]
Internet-Draft                 ROLIE Vuln                      July 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The "vulnerability" information type  . . . . . . . . . . . .   3
   4.  Common Vulnerability Enumeration (CVE) Format . . . . . . . .   4
     4.1.  Description . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Link relations for the 'vulnerability'
       information-type  . . . . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  information-type registrations  . . . . . . . . . . . . .   6
       6.1.1.  vulnerability information-type  . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   As our software becomes more complex and interconnected, the number
   of software vulnerabilities exploitable by actors with mal-intent has
   skyrocketed.  Huge amounts of resources have been poured into the
   preemptive discovery, description, and remediation of these
   vulnerabilities, but it is often a challenge to share and communicate
   the results of these efforts.  While bad-actors have vast
   collaboration networks that enable widespread knowledge of any
   vulnerability, the defensive community at large has no sharing
   consortium as prevalent.  If we are to keep up with the rising
   difficulty of defending our systems, we must increase our ability to
   quickly, efficiently, and automatically share information about
   vulnerabilities.

   The Resource-Oriented Lightweight Information Exchange (ROLIE)
   [RFC8322] provides a means to share computer security information
   with an eye towards automation and efficiency.  By utilizing ROLIE to
   share vulnerability data, we get one step closer to establishing
   automated communication between each party involved in fighting
   vulnerabilities.  A security researcher can send a newly discovered
   vulnerability to a vulnerability repository, where it is
   automatically retrieved and consumed by enterprise systems.  At this
   final stage, the enterprise can cross-reference against their
   enterprise wide software load to begin mitigating the issue.

Banghart                Expires January 21, 2020                [Page 2]
Show full document text