RFC 8274: Incident Object Description Exchange Format Usage Guidance
In plain English — editorial summary, not part of the RFC
The Incident Object Description Exchange Format (IODEF) v2 (RFC7970) defines a data representation that provides a framework for sharing information about computer security incidents commonly exchanged by Computer Security Incident Response Teams (CSIRTs) . Since the IODEF model includes a wealth of available options that can be used to describe a security incident or issue, it can be challenging for security practitioners to develop tools that leverage IODEF for incident sharing. This document provides guidelines for IODEF implementers. It addresses how common security indicators can be represented in IODEF and use-cases of how IODEF is being used. This document aims to make IODEF's adoption by vendors easier and encourage faster and wider adoption of the model by CSIRTs around the world.
Document record
- Document ID
- RFC8274
- Published
- November 2017
- Authors
- P. Kampanakis; M. Suzuki
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8270Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 BitsCurrent
December 2017
- RFC 8268More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)Current
December 2017
- RFC 8252OAuth 2.0 for Native AppsCurrent
October 2017
- RFC 8248Security Automation and Continuous Monitoring (SACM) RequirementsCurrent
September 2017
- RFC 8247Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2)Updated
September 2017
- RFC 8308Extension Negotiation in the Secure Shell (SSH) ProtocolUpdated
March 2018
- RFC 8314Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and AccessUpdated
January 2018
- RFC 8229TCP Encapsulation of IKE and IPsec PacketsObsoleted
August 2017
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?