Security Advisory Format
draft-debeaupuis-saf-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tristan Debeaupuis | ||
| Last updated | 1999-05-19 | ||
| 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 memo describes a format for security advisories. An advisory is a document describing a vulnerability of a program, an operating system or, more generally, a software or hardware component of the information system. This specification tries to minimize changes in issuer and readers current practices (messages style), and by trying to help a program re-read the advisory tries also to keep advisories easily and friendly readable by humans. It focuses on structure of documents. This specification is primarily useful for advisories issuers such as CSIRTs [RFC2350] and users and is linked with intrusion detection.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)