Enumeration Reference Format for the Incident Object Description Exchange Format
RFC 7495, “Enumeration Reference Format for the Incident Object Description Exchange Format”, is a Proposed Standard document published in March 2015 by A. Montville, D. Black. The canonical text is published by the RFC Editor.
Abstract
The Incident Object Description Exchange Format (IODEF) is an XML data representation framework for sharing information about computer security incidents. In IODEF, the Reference class provides references to externally specified information such as a vulnerability, Intrusion Detection System (IDS) alert, malware sample, advisory, or attack technique. In practice, these references are based on external enumeration specifications that define both the enumeration format and the specific enumeration values, but the IODEF Reference class (as specified in IODEF v1 in RFC 5070) does not indicate how to include both of these important pieces of information.
This document establishes a stand-alone data format to include both the external specification and specific enumeration identification value, and establishes an IANA registry to manage external enumeration specifications. While this document does not update IODEF v1, this enumeration reference format is used in IODEF v2 and is applicable to other formats that support this class of enumeration references.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7495 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7494 IEEE 802.11 Medium Access Control Profile for Control and Provisioning of Wireless Access Points
- RFC 7496 Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension
- RFC 7493 The I-JSON Message Format
- RFC 7497 Rate Measurement Test Protocol Problem Statement and Requirements
- RFC 7492 Analysis of Bidirectional Forwarding Detection Security According to the Keying and Authentication for Routing Protocols Design Guidelines
- RFC 7498 Problem Statement for Service Function Chaining
- RFC 7491 A PCE-Based Architecture for Application-Based Network Operations
- RFC 7499 Support of Fragmentation of RADIUS Packets