[mile] I-D Action: draft-ietf-mile-iodef-guidance-10.txt
internet-drafts@ietf.org Mon, 22 May 2017 16:17 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C67B12EB1C; Mon, 22 May 2017 09:17:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: mile@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149546982360.22141.8822534408920138135@ietfa.amsl.com>
Date: Mon, 22 May 2017 09:17:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/c0y6eqz51kNApyuqHPBZAbsJsAA>
Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-10.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2017 16:17:04 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Managed Incident Lightweight Exchange of the IETF. Title : IODEF Usage Guidance Authors : Panos Kampanakis Mio Suzuki Filename : draft-ietf-mile-iodef-guidance-10.txt Pages : 34 Date : 2017-05-22 Abstract: The Incident Object Description Exchange Format v2 [RFC7970] 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 security practitioners to develop tools that can leverage IODEF for incident sharing. This document provides guidelines for IODEF implementers. It also addresses how common security indicators can be represented in IODEF and use-cases of how IODEF is being used. This document aims 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-10 https://datatracker.ietf.org/doc/html/draft-ietf-mile-iodef-guidance-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-mile-iodef-guidance-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [mile] I-D Action: draft-ietf-mile-iodef-guidance… internet-drafts
- Re: [mile] I-D Action: draft-ietf-mile-iodef-guid… Panos Kampanakis (pkampana)
- Re: [mile] I-D Action: draft-ietf-mile-iodef-guid… Charles Eckel (eckelcu)
- Re: [mile] I-D Action: draft-ietf-mile-iodef-guid… Panos Kampanakis (pkampana)