Encrypted (TLS) syslog is now available in MX Security & SD-WAN Appliances running MX26.1.1 or higher firmware.
Why is Encrypted Syslog important?
More and more often, network administrators are taking advantage of “as a service” syslog solutions. In order to deliver syslog messaging to these services, encryption should be used to safeguard these logs across the public Internet.
What is the implementation?
This feature follows the architecture described in RFC 5425 for TLS Transport Mapping for Syslog. This allows for TLS encryption over TCP.
Template Support
Encrypted Syslog is fully supported in Configuration Templates as of March 6, 2026.
Note that if Encrypted Syslog is deployed via a Configuration Templates prior to that date, it may not forward messages, encrypted or unencrypted. To resolve this, please delete and re-add your Encrypted Syslog configuration to the Configuration Template.
Additional Syslog enhancements
In addition to encryption, MX26.1.1 introduces these additional syslog features:
- TCP transport of syslog (encrypted and unencrypted) is now supported where it was previously UDP only
- Fully qualified domain names (FQDNs) can be used for syslog server configuration
Getting started
Refer to the Encrypted Syslog Documentation for more details on configuration and operation of Encrypted Syslog.
