RFC 5848: Signed Syslog Messages
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to add origin authentication, message integrity, replay resistance, message sequencing, and detection of missing messages to the transmitted syslog messages. This specification is intended to be used in conjunction with the work defined in RFC 5424, "The Syslog Protocol". [STANDARDS-TRACK]
Document record
- Document ID
- RFC5848
- Published
- May 2010
- Authors
- J. Kelsey; J. Callas; A. Clemm
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9662Updates to the Cipher Suites in Secure SyslogCurrent
October 2024
- RFC 5676Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) NotificationsCurrent
October 2009
- RFC 5675Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG MessagesCurrent
October 2009
- RFC 5674Alarms in SyslogCurrent
October 2009
- RFC 6587Transmission of Syslog Messages over TCPCurrent
April 2012
- RFC 5840Wrapped Encapsulating Security Payload (ESP) for Traffic VisibilityCurrent
April 2010
- RFC 5836Extensible Authentication Protocol (EAP) Early Authentication Problem StatementCurrent
April 2010
- RFC 5868Problem Statement on the Cross-Realm Operation of KerberosCurrent
May 2010
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?