Plasma Protected IODEF
draft-schaad-mile-iodef-plasma-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jim Schaad | ||
| Last updated | 2014-08-15 (Latest revision 2014-02-11) | ||
| 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
The Incident Object Description Exchange Format (IODEF) defines a XML representation for information about computer security incidents. The driver for the standardization effort for IODEF is the desire to share the information as part of the cybersecurity response. As the security considerations of RFC5070 notes, the data can be sensitive and should only be disclosed to appropriate parties. This document describes how to use the Plasma policy enforcement model to ensure access to the IODEF data follows the appropriate policies in a distributed environment and independent of the transports used to share the information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)