RFC 5425: Transport Layer Security (TLS) Transport Mapping for Syslog
In plain English — editorial summary, not part of the RFC
This document describes the use of Transport Layer Security (TLS) to provide a secure connection for the transport of syslog messages. This document describes the security threats to syslog and how TLS can be used to counter such threats.
Document record
- Document ID
- RFC5425
- Published
- March 2009
- Authors
- F. Miao; Y. Ma; J. Salowey
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
- Updated by:
- RFC 9662
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5424The Syslog ProtocolCurrent
March 2009
- RFC 5426Transmission of Syslog Messages over UDPCurrent
March 2009
- RFC 5427Textual Conventions for Syslog ManagementCurrent
March 2009
- RFC 5433Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) MethodCurrent
February 2009
- RFC 5409Using the Boneh-Franklin and Boneh-Boyen Identity-Based Encryption Algorithms with the Cryptographic Message Syntax (CMS)Current
January 2009
- RFC 5408Identity-Based Encryption Architecture and Supporting Data StructuresCurrent
January 2009
- RFC 5387Problem and Applicability Statement for Better-Than-Nothing Security (BTNS)Current
November 2008
- RFC 5386Better-Than-Nothing Security: An Unauthenticated Mode of IPsecCurrent
November 2008
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?