TERENA'S Incident Object Description and Exchange Format Requirements
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 17
- Abstract
- 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.
- Publication Date
- 2001-02-01
- Status Note
- Informational
- DOI
10.17487/RFC3067- Link
- https://doi.org/10.17487/RFC3067
- Author(s)
- Jimmy ArvidssonAndrew CormackYuri DemchenkoJan Meijer
- Keyword(s)
- Data, Archive
Latest version of IETF RFC 3067
Document Versions — IETF RFC 3067
-
▶ IETF RFC 3067 (2001-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- NIST.SP.800-3 — 8 EXTERNAL
- Best Current Practice of incident classification and reporting schemes currently used by active CSIRTs. - http://www.terena.nl/task-forces/tf-csirt/i- taxonomy/docs/BCPreport1.rtf EXTERNAL
- Intrusion Detection Exchange Format Requirements by Wood, M. - December 2000, Work in Progress. EXTERNAL
- Guidelines for Evidence Collection and Archiving by Dominique Brezinski, Tom Killalea - July 2000, Work in Progress. EXTERNAL
- Incident Taxonomy and Description Working Group Charter - http://www.terena.nl/task-forces/tf-csirt/i-taxonomy/ EXTERNAL
- A Common Language for Computer Security Incidents by John D. Howard and Thomas A. Longstaff. - Sandia Report: SAND98-8667, Sandia National Laboratories - http://www.cert.org/research/taxonomy_988667.pdf EXTERNAL
- Intrusion Detection Message Exchange Format Extensible Markup Language (XML) Document Type Definition by D. Curry, H. Debar - February 2001, Work in Progress. EXTERNAL
- Handbook for Computer Security Incident Response Teams (CSIRTs), Moira J. West-Brown, Don Stikvoort, Klaus-Peter Kossakowski. - CMU/SEI-98-HB-001. - Pittsburgh, PA: Carnegie Mellon University, 1998. EXTERNAL
- Taxonomy of the Computer Security Incident related terminology - http://www.terena.nl/task-forces/tf-csirt/i-taxonomy/docs/i- taxonomy_terms.html EXTERNAL
- Multilingual Support in Internet/IT Applications. - http://www.terena.nl/projects/multiling/ EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 2350 [Active*]
- IETF RFC 2828 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3067.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3067, TERENA'S Incident Object Description and Exchange Format Requirements. Available at https://doi.org/10.17487/RFC3067
Snippet:
IETF RFC 3067, TERENA'S Incident Object Description and Exchange Format Requirements. Available at https://doi.org/10.17487/RFC3067
HTML (ISO 690 compliant)
Preview:
IETF RFC 3067, TERENA'S Incident Object Description and Exchange Format Requirements. Available at https://doi.org/10.17487/RFC3067
Snippet:
<span class="citation"><cite>IETF RFC 3067</cite>, TERENA'S Incident Object Description and Exchange Format Requirements. Available at <a href="https://doi.org/10.17487/RFC3067" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3067</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3067, TERENA'S Incident Object Description and Exchange Format Requirements
doi: 10.17487/RFC3067
url: https://doi.org/10.17487/RFC3067
doi: 10.17487/RFC3067
url: https://doi.org/10.17487/RFC3067
Snippet:
<li> <cite id="bib-rfc3067">IETF RFC 3067</cite>, TERENA'S Incident Object Description and Exchange Format Requirements <span class="doi">10.17487/RFC3067</span> </li>
Referenced By
- IETF RFC 7416 [Active*]