RFC 4766: Intrusion Detection Message Exchange Requirements
In plain English — editorial summary, not part of the RFC
The purpose of the Intrusion Detection Exchange Format Working Group (IDWG) 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 the high-level requirements for such a communication mechanism, including the rationale for those requirements where clarification is needed. Scenarios are used to illustrate some requirements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4766
- Published
- March 2007
- Authors
- M. Wood; M. Erlinger
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 25
- 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 4765The Intrusion Detection Message Exchange Format (IDMEF)Current
March 2007
- RFC 4768Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 NamingCurrent
December 2006
- RFC 4752The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) MechanismCurrent
November 2006
- RFC 4785Pre-Shared Key (PSK) Ciphersuites with NULL Encryption for Transport Layer Security (TLS)Updated
January 2007
- RFC 4738MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)Current
November 2006
- RFC 4809Requirements for an IPsec Certificate Management ProfileCurrent
February 2007
- RFC 4716The Secure Shell (SSH) Public Key File FormatUpdated
November 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?