RFC 4765: The Intrusion Detection Message Exchange Format (IDMEF)
In plain English — editorial summary, not part of the RFC
The purpose of the Intrusion Detection Message Exchange Format (IDMEF) is to define data formats and exchange procedures for sharing information of interest to intrusion detection and response systems and to the management systems that may need to interact with them. This document describes a data model to represent information exported by intrusion detection systems and explains the rationale for using this model. An implementation of the data model in the Extensible Markup Language (XML) is presented, an XML Document Type Definition is developed, and examples are provided. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4765
- Published
- March 2007
- Authors
- H. Debar; D. Curry; B. Feinstein
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 157
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4767The Intrusion Detection Exchange Protocol (IDXP)Current
March 2007
- RFC 5910Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)Current
May 2010
- RFC 3504Internet Open Trading Protocol (IOTP) Version 1, ErrataCurrent
March 2003
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 2802Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)Current
April 2000
- RFC 4671RADIUS Accounting Server MIB for IPv6Current
August 2006
- RFC 4670RADIUS Accounting Client MIB for IPv6Current
August 2006
- RFC 4669RADIUS Authentication Server MIB for IPv6Current
August 2006
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?