Adding Wallix PAM via Syslog

Purpose

This guide explains how to forward Wallix Bastion (PAM) events to Logsign USO over syslog and what Logsign does with them. The integration covers proxy authentication events produced by the RDP and SSH proxies, Bastion user authentication events, the session and audit events that the Bastion writes for recorded sessions and administrative changes, and the cron and sudo messages of the Bastion appliance operating system.

Prerequisites

  • A Wallix Bastion administrator account that is allowed to change the log forwarding configuration.
  • Network connectivity from the Bastion to the Logsign USO collector on your syslog port (TCP or UDP 514 by default).
  • The Logsign user account that will add the data source needs access to Settings > Data Collection.

Step 1: Forward Bastion logs to Logsign

Wallix Bastion sends its logs through its own syslog configuration. Menu names differ between Bastion releases, so use the Wallix administration guide for your version to find the log forwarding or remote syslog server settings. In that configuration, add the IP address of the Logsign USO collector and the syslog port, and keep the Bastion default message format.

Logsign reads the key="value" pairs from the message body and does not depend on the syslog header, so both RFC 3164 and RFC 5424 headers are accepted. What matters is that the pairs arrive intact: each event must reach Logsign as a single message, and the quoting around values must be preserved. Do not enable a CEF, LEEF or JSON output on the Bastion for this source, because only the native key/value format is parsed.

Step 2: Add the data source in Logsign USO

Open the Logsign USO web interface and click + Device under Settings > Data Collection. Choose Syslog as the collection method, select Wallix as the vendor and PAM as the product, and enter the IP address of the Bastion as the host. Click Save. Once the Bastion starts sending, events appear under Search.

Supported message format

Every Wallix Bastion message carries a bracketed source tag such as [rdpproxy], [sshproxy], [wabauth], [wabaudit] or [RDP Session], followed by key="value" pairs. Three typical events look like this (anonymized):

1 2026-09-16T11:27:52+02:00 wallix rdpproxy 1208735 - - [rdpproxy] psid="5733451208734" user="test_user" type="AUTHENTICATION_SUCCESS" method="Password"

1 2026-09-16T11:27:52+02:00 wallix WAB(root) 1208735 - - [wabauth] type="UserAuth" action="authentify" user="test_user" client_ip="192.0.2.10" status="success" infos="diagnostic [Authentication success: identified with local(LOCAL), authenticated with: LDAP_AUTH(LDAP).]"

1 2023-09-12T12:04:38+03:00 pam rdpproxy 9821 - - [RDP Session] session_id="18a889374c7c086a00505681868a" client_ip="192.0.2.20" target_ip="10.2.9.85" user="jdoe@example.com" device="SAPGUI" service="APP" account="jdoe@example.com" type="TITLE_BAR" source="Probe" window="ABAP Debugger(1)"

Values that contain spaces have to stay inside double quotes. Key names are used exactly as the Bastion writes them, so a renamed or lower cased key is not recognized.

Appliance operating system messages (cron and sudo)

The Bastion can also forward the syslog messages of its own operating system. Logsign recognizes these messages by the application name CRON, cron or sudo in the RFC 5424 header. They do not carry a bracketed source tag or key="value" pairs. Logsign reads them in a separate way:

  • A sudo command line, for example root : PWD=/root ; USER=wabuser ; COMMAND=/usr/bin/id. Optional parts such as TTY= are accepted.
  • A cron job line, for example (root) CMD (cd / && run-parts --report /etc/cron.hourly).
  • A PAM session line, for example pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) or session closed for user wabuser.
  • Any other cron or sudo line, for example pam_unix(sudo:auth): authentication failure; ... user=kadir. Logsign reads the key=value pairs in the text, such as user.
1 2026-10-27T14:50:01+01:00 wallix sudo 1812315 - - wabadmin : TTY=pts/0 ; PWD=/home/wabadmin ; USER=root ; COMMAND=/usr/bin/id

1 2026-10-27T14:17:01+01:00 wallix CRON 1812771 - - (root) CMD (cd / && run-parts --report /etc/cron.hourly)

What gets collected

Logsign fills the following fields from the Bastion key/value pairs. A field only appears on an event when the corresponding key is present in that message.

Logsign fieldWallix key
Event.Typetype
Event.Actionaction
Event.Statusstatus
Event.Resultresult
Event.Methodmethod
Event.Infotext
Event.Descriptioninfos
Source.UserNameuser
Source.IP, Source.City, Source.Countryclient_ip, otherwise host
Source.Portport
Source.Datadata
Source.Unitchannel_name
Source.Vaultvault
Source.DisplayNamedisplay_name
Destination.IP, Destination.City, Destination.Country, Destination.Locationtarget_ip
Target.UserNametarget
Subject.AccountNameaccount
Session.ID, Session.Duration, Session.Descriptionsession_id, duration, session
Device.Namedevice
Service.Nameservice
Data.SourceNamesource
Object.Name, Object.Size, Object.SHA256, Object.IDfile_name, size, sha256, object
Process.Namewindow
Process.IDpid, otherwise psid. When command_line contains Processid:{...}, the value inside the braces is used as pid.
Process.CommandLinecommand_line
Classification.Nameclass_name
Call.Channelchannel_name

For cron and sudo messages of the appliance operating system, Logsign fills these fields from the message text:

Logsign fieldValue
Application.NameApplication name from the syslog header: CRON, cron or sudo
Event.InfoFull message text after the syslog header
Source.UserNameUser that runs the sudo command, user in brackets of a cron job, user of a PAM session line, or the user= value of other lines
Source.CommandCOMMAND= value of a sudo line, or the command inside CMD (...) of a cron line
Target.UserNameUSER= value of a sudo line
Process.PathPWD= value of a sudo line (working directory)
Event.Actionsession opened or session closed for PAM session lines

Every event is recorded with Vendor Wallix, Product PAM, EventSource Type Security System, EventSource Category Access Control and EventSource PrefixID 4392.

Event classification

Authentication events are classified from type and status. The proxy events written by [rdpproxy] and [sshproxy] have no status key, so the type alone decides the result. Bastion user authentication events written by [wabauth] carry type="UserAuth" and are classified by their status.

EventEventMapEventMap.ID
type="AUTHENTICATION_SUCCESS" (rdpproxy, sshproxy)Identity / User / Login10101
type="AUTHENTICATION_FAILURE" (rdpproxy, sshproxy)Identity / User / Deny10102
type="UserAuth" with status="success" (wabauth)Identity / User / Login10101
type="UserAuth" with status="failure" (wabauth)Identity / User / Deny10102
type="UserAuth" with status="started" (wabauth)Identity / User / Info10111
Appliance operating system messages from CRON, cron or sudoSystem / Command / Info71401
Every other Wallix PAM eventNetwork / Connection / Info60901

A single interactive login usually produces both a [wabauth] pair and a proxy event. The Bastion writes status="started" when the authentication attempt begins and follows it with status="success" or status="failure" for the same attempt. The started event is deliberately classified as Identity / User / Info instead of a login, so that one login is not counted twice in login rules and reports.

Notes and limits

  • Session activity and audit events, for example [RDP Session] events such as TITLE_BAR, KBD_INPUT and FOREGROUND_WINDOW_CHANGED, and [wabaudit] configuration events, stay on Network / Connection / Info (60901). Use Event.Type and Event.Action to filter them.
  • All cron and sudo messages are classified as System / Command / Info (71401). This includes PAM session lines and pam_unix(sudo:auth) authentication failures. A failed sudo authentication does not appear as Identity / User / Deny. Use Application.Name and Event.Info to filter these events.
  • If your authentication events still arrive as Network / Connection / Info, the appliance is running an older version of the Wallix PAM plugin. The classification table above applies from the plugin update that introduced it. Contact Logsign support to confirm the version you need. The same applies if cron and sudo messages arrive as Network / Connection / Info.
  • Wallix messages do not carry a time_generated key, so Time.Generated is set when Logsign processes the message. For events that are delayed on the way, use the timestamp in the raw log to reconstruct the exact Bastion time.
  • The event severity comes from the syslog priority of the incoming message, not from a field inside the Wallix event.

Verification

After both sides are saved, one login through the Bastion is enough to check the integration end to end.

  • In Logsign USO, open Settings > Data Collection and confirm that the Wallix PAM source is receiving data.
  • Log in through the Bastion to generate a test event. In Search, look for events with Vendor Wallix and Product PAM. The login should appear with EventMap Identity / User / Login and your user name in Source.UserName.
  • Enter a wrong password once. That attempt should appear as Identity / User / Deny with Event.Type AUTHENTICATION_FAILURE, or as a [wabauth] event with status="failure".
  • If the Bastion forwards its operating system messages, look for events with Application.Name CRON or sudo. They should appear with EventMap System / Command / Info and the executed command in Source.Command.
  • If the source is receiving data but no events show Vendor Wallix, the messages are not in a format this integration recognizes. Check that the Bastion is sending its native key/value format and that quoted values are not being split or rewritten on the way.
Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
Become a Certified Logsign User/Administrator
Sign-up for Logsign Academy and take the courses to learn about Logsign USO Platform in detail. Enjoy the courses, and get your badges and certificates. In these courses, you'll learn how to use Logsign in your work and add value to your career.
Visit Our Blog
Our Logsign USO Platform illustrate our expertise. So do the blog. Through our blog posts, deepen your knowledge on various SecOps topics or get updated about important news & modern approaches for cybersecurity. Get into the habit of reading valuable information provided by Logsign. Be a step ahead.