implementing-syslog-centralization-with-rsyslog

Configure rsyslog for centralized log collection with TLS encryption, custom templates, and log rotation. Generates server and client configuration files with GnuTLS stream drivers, x509 certificate authentication, per-host log segregation, and reliable queue settings for high-availability syslog infrastructure.

Jump to install

Repository: xalgord/xalgorix
Last source activity: June 6, 2026 at 16:41
Detected SKILL.md language: English
Stars: 813
Forks: 146

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/xalgord/xalgorix --skill implementing-syslog-centralization-with-rsyslog

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

exploiting-http-request-smuggling

Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.

2026-07-20

exploiting-oauth-misconfiguration

Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations including redirect URI manipulation, token leakage, and authorization code theft during security assessments.

2026-07-20

exploiting-subdomain-takeover-vulnerabilities

Identifying and exploiting dangling DNS records pointing to unclaimed cloud services, enabling subdomain takeover for phishing, cookie stealing, and authentication bypass during authorized penetration tests.

2026-06-19

View all from this repository

Implementing Syslog Centralization with Rsyslog

When to Use

When deploying or configuring implementing syslog centralization with rsyslog capabilities in your environment

When establishing security controls aligned to compliance requirements

When building or improving security architecture for this domain

When conducting security assessments that require this implementation

Common Misconfigurations & Verification

UDP (514) silently drops under load: @host (single @) sends UDP with no delivery guarantee; messages are lost on congestion with zero error. Use TCP/TLS (@@ / omfwd protocol="tcp") plus disk-assisted queues so spikes spool instead of vanishing.

"TLS configured" but actually plaintext: imtcp/omfwd without StreamDriver="gtls" + StreamDriverMode="1" falls back to cleartext on 6514. Confirm with openssl s_client -connect server:6514 returning a cert, and tcpdump -A port 6514 showing ciphertext rather than readable log lines.

Auth mode anon = any client accepted: StreamDriverAuthMode="anon" trusts any cert. Use x509/name with a permittedPeer list so only known clients forward; verify a client with the wrong CN is rejected.

Queue not disk-assisted = restart loss: without queue.type="LinkedList" + queue.filename + queue.saveonshutdown="on", in-memory queues drop on rsyslog restart. Confirm a .qi/spool file exists under the queue path.

Confirm delivery end to end: logger -n server -P 6514 -T "rsyslog-test" from a client, then verify the line lands in the per-host file (/var/log/remote/<host>/...). A reachable port is not the same as a stored log.

Prerequisites

Familiarity with security operations concepts and tools

Access to a test or lab environment for safe execution

Python 3.8+ with required dependencies installed

Appropriate authorization for any testing activities

Instructions

Install dependencies: pip install jinja2 paramiko

Generate TLS certificates for rsyslog server and clients using OpenSSL.