An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity Information (RFC7203)
Publication Date: 2014-Apr-22
The IP.com Prior Art Database
T. Takahashi: AUTHOR [+3]
The number of incidents in cyber society is growing day by day. Incident information needs to be reported, exchanged, and shared among organizations in order to cope with the situation. IODEF is one of the tools already in use that enables such an exchange.
Internet Engineering Task Force (IETF) T. Takahashi Request for Comments: 7203 NICT Category: Standards Track K. Landfield ISSN: 2070-1721 McAfee Y. Kadobayashi NAIST April 2014
An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity Information
This document extends the Incident Object Description Exchange Format (IODEF) defined in RFC 5070 to exchange enriched cybersecurity information among security experts at organizations and facilitate their operations. It provides a well-defined pattern to consistently embed structured information, such as identifier- and XML-based information.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7203.
al. Standards Track [Page 1]
RFC 7203 IODEF-SCI April 2014
Copyright (c) 2014 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. 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 ......................