This guide gives you a copy-and-paste Linux (rsyslog) configuration for Log forwarding (rsyslog tls siem mutual auth), plus the rationale behind each line and a free SafeCadence analyzer that scores your existing config against this same best-practice template.
What this snippet does
This Linux (rsyslog) template implements rsyslog forward to SIEM over TLS (mutual auth). It’s been distilled from vendor documentation, NIST SP 800-41 / SP 800-53, and CISA hardening guidance — and battle-tested by SafeCadence on real production engagements.
The configuration template
You can browse and copy the live snippet (with one-click copy + citations) from the SafeCadence Config Templates Library:
▶ Open the live template (with copy button)
Why this matters
- Encrypts logs in transit so credentials don’t leak via syslog.
- Mutual TLS prevents log injection from rogue hosts.
- Aligns with PCI DSS req. 10, SOC 2 CC6.6, HIPAA §164.312.
How to validate your config
Copy your existing Linux (rsyslog) running-config and paste it into the matching SafeCadence analyzer. The analyzer will tell you exactly which best-practice checks pass, which fail, and the per-finding fix:
Need help applying this in production?
SafeCadence offers paid engagements for Linux (rsyslog) hardening — change windows, validation, rollback, and knowledge transfer. Free 30-minute scoping consult.