Knowledge obtained from the implementation experience of an IODEF- capable incident response management system
draft-daisuke-iodef-experiment-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daisuke Miyamoto , Takeshi Takahashi | ||
| Last updated | 2014-08-16 (Latest revision 2014-02-12) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document explains our observation on the usability of IODEF [RFC5070], based on our experiments. We aim at developing an IODEF- capable incident response management systems in order to facilitate incident response activities. We started to design and implement the system for our university CERT, however, there are several technical issues while implementing and operating the system. This document shares the observation from our proto-type implementation and provides new sight from operational aspects.
Authors
Daisuke Miyamoto
Takeshi Takahashi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)