Transport of Incident Detection Message Exchange Format version 2 (IDMEFv2) Messages over HTTPS
draft-poirotte-idmefv2-https-transport-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Francois Poirotte , Thomas Andrejak , Gilles Lehmann | ||
Last updated | 2022-10-15 | ||
Replaced by | draft-lehmann-idmefv2-https-transport | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-lehmann-idmefv2-https-transport | |
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
The Incident Detection Message Exchange Format version 2 (IDMEFv2) provides a way to describe any incidents detected on cyber and/or physical infrastructures. The format is agnostic so it can be used in standalone or combined cyber (SIEM), physical (PSIM) and availability (NMS) monitoring systems. IDMEFv2 can also be used to describe cyber and physical potential threats (CTI/PTI). IDMEF improves situational awareness by facilitating correlation of multiple types of events using the same base format thus enabling efficient detection of complex and combined cyber and physical attacks on critical infrastructures. If approved this document would obsolete RFC4767.
Authors
Francois Poirotte
Thomas Andrejak
Gilles Lehmann
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)