metasystema.org
CurrentINFORMATIONALLegacy stream

RFC 3067: TERENA'S Incident Object Description and Exchange Format Requirements

In plain English — editorial summary, not part of the RFC

The purpose of the Incident Object Description and Exchange Format is to define a common data format for the description, archiving and exchange of information about incidents between CSIRTs (Computer Security Incident Response Teams) (including alert, incident in investigation, archiving, statistics, reporting, etc.). This document describes the high-level requirements for such a description and exchange format, including the reasons for those requirements. This memo provides information for the Internet community.

Document record

Document ID
RFC3067
Published
February 2001
Authors
J. Arvidsson; A. Cormack; Y. Demchenko; J. Meijer
Status
INFORMATIONAL
Stream
Legacy
Area
—
Pages
17
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3067-terena-s-incident-object-description-and-exchange-format-requirements