Skip to main content

IODEF Usage Guidance
draft-pkampana-iodef-guidance-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Panos Kampanakis
Last updated 2014-04-21 (Latest revision 2013-10-18)
Replaced by draft-ietf-mile-iodef-guidance
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mile-iodef-guidance
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The Incident Object Description Exchange Format [RFC5070] defines a data representation that provides a framework for sharing information commonly exchanged by Computer Security Incident Response Teams (CSIRTs) about computer security incidents. Since the IODEF model includes a wealth of available options that can be used to describe a security incident or issue, it can be challenging for implementers to develop tools that can Leverage IODEF for incident sharing. This document provides guidelines for IODEF implementers. It will also address how common security indicators can be represented in IODEF. The goal of this document is to make IODEF's adoption by vendors easier and encourage faster and wider adoption of the model by Computer Security Incident Response Teams (CSIRTs) around the world.

Authors

Panos Kampanakis

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)