Adding Netwrix Endpoint Protector (CoSoSys) via Syslog

Purpose

This guide explains how to forward Netwrix Endpoint Protector events to Logsign USO over syslog, and what Logsign does with those events once they arrive. Endpoint Protector was originally a CoSoSys product and is now sold by Netwrix, so the source is still registered in Logsign under the vendor name CoSoSys and the product name Endpoint Protector. The integration covers Device Control events (file read, write, copy, rename and delete on monitored devices and network shares, device connect and disconnect, block and unblock), Content Aware Protection events (content threat detections on email, network shares and other exit points) and System Logs (client policy delivery, administrator actions, license information).

Prerequisites

  • An Endpoint Protector server (the appliance or virtual appliance that hosts the reporting and administration console) and an administrator account that can change its logging or SIEM export settings.
  • Network connectivity from the Endpoint Protector server to the Logsign USO collector on your syslog port, TCP or UDP 514 by default.
  • A Logsign USO release that includes the updated CoSoSys Endpoint Protector plugin, if your Endpoint Protector server sends the RFC 5424 header with fractional seconds and a Z offset (see Supported Message Formats). Earlier releases only recognize the two older header forms.
  • A Logsign USO release that includes support for the Endpoint Protector 2608 field names, if your Endpoint Protector server runs version 2608 or later (see Supported Message Formats). On earlier Logsign releases these events are still received and classified, but the source, device and file fields stay empty.

Step 1: Enable syslog export on the Endpoint Protector server

Syslog export is configured entirely on the Endpoint Protector side. Menu labels differ noticeably between Endpoint Protector 5.x and current Netwrix releases, so use the SIEM integration or syslog section of the Netwrix Endpoint Protector documentation for your exact version. Whatever the menu is called, you need to set three things:

  1. The destination address, which is the IP address of your Logsign USO collector.
  2. The destination port and protocol, matching the syslog listener on the Logsign side (TCP or UDP 514 by default).
  3. The event categories to export. Enable Device Control, Content Aware Protection and System Logs to get the full coverage described in this article.

Keep the default syslog output. The Logsign plugin reads the plain text [Key] Value layout that Endpoint Protector produces natively, and it does not parse CEF, LEEF or JSON output.

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 CoSoSys as the vendor and Endpoint Protector as the product, and enter the IP address of the Endpoint Protector server as the host. Click Save.

The host you enter must be the address the syslog messages actually come from, which is the Endpoint Protector server itself, not the individual endpoints. The client computer that generated each event is carried inside the message and ends up in Source.HostName.

Supported Message Formats

Every message has a syslog header, then the category and event name, then the event body as [Key] Value pairs separated by | . Three header forms are recognized.

RFC 5424 with a UTC timestamp and fractional seconds, which is what current Endpoint Protector releases send:

<14>1 2026-09-17T08:33:01.000000Z eppserver EPP-10.22.215.100 - - - EPP IP - 10.22.102.120 - Device Control - File Read-Write: [Log ID] 687c79755f45626a42d805f76317aff1 | [Event Name] File Read-Write | [Client Computer] NTMK-HR-CHINLQ | [IP Address] 10.22.22.189 | [MAC Address] f4-6b-8c-87-d8-12 | [Client User] chi.nlq | [Device Type] Network Share | [File Name] //ntmk-svr-file02/personal$/chi.nlq/scan/08092026133113.pdf | [File Type] Adobe Acrobat Document | [File Size] 373098

RFC 5424 with a numeric UTC offset, sent by Endpoint Protector 5.9 and similar releases:

1 2025-02-13T16:08:55+03:00 eppserver EPP-10.1.2.28 1327925 - - EPP IP - 10.1.2.27 - Content Aware Protection - Content Threat Detected: [Log ID] 6b402f9377f5401e5bb16699c20d8c93 | [Client Computer] BRN1-URT | [IP Address] 10.1.4.4 | [Content Policy] General | [Destination Type] Network Share

The older RFC 3164 header, with a month, day and time instead of an ISO 8601 timestamp:

Nov 23 07:48:18 eppserver EPP-10.0.0.81: EPP-IP - 10.0.2.13 - Device Control - File Read: [Event Name] File Read | [Client Computer] HALISEMIRZA | [IP Address] 10.34.4.35 | [Client User] halisemirza | [File Name] F:/Projects/plan.dwg | [File Type] .dwg file | [File Size] 1099776

For the two ISO 8601 forms, the syslog version digit has to be present in front of the timestamp. Both <14>1 2026-09-17T08:33:01.000000Z and 1 2025-02-13T16:08:55+03:00 are accepted, the leading priority value is optional, but a bare timestamp with no version digit is not recognized.

Endpoint Protector 2608 and later keeps the same header but names the keys in the event body after its internal database columns, for example machine_name instead of Client Computer and file_name instead of File Name. Netwrix documents this as a side effect of its database migration, and there is no setting on the Endpoint Protector side to switch back to the readable names. Logsign accepts both naming styles, and both end up in the same Logsign fields. 

A Device Control event in the 2608 format looks like this (shortened):

<129>1 2026-11-09T15:27:01+03:00 eppserver EPP-10.0.0.70 1089091 - - EPP IP - 10.0.0.26 - Device Control - File Rename: [event_name] File Rename | [machine_name] WS-03 | [os_type_name] Windows | [ip] 10.0.7.77 | [client_name] user.three | [device_type_name] Network Share | [device_name] 10.0.0.52 (Network Share) | [serial_no] 10.0.0.52 | [file_type] Microsoft Word Document | [file_name] \\10.0.0.52\share\common\2026\form.docx | [file_size] 1024 | [file_hash] d90fbeab5b56ac689bf57852c41826a3 | [os_version] Windows 11 Pro x64 25H2 (26200.9711) | [Log ID] 7897f66e4bf21f3323968741bfa51d2f

Each event is a single line. If you copy a sample from a screen or a ticket that wraps long lines, join it back into one line before you paste it into the plugin test page, otherwise every wrapped line is tested as a separate message and none of them parse.

What Gets Collected

Field names in the left column are the normalized Logsign fields you search on. The right column is the key in the Endpoint Protector message. Where Endpoint Protector 2608 and later uses a different key, it is shown after the readable name.

Logsign FieldEndpoint Protector Field
Time.GeneratedThe timestamp in the syslog header, not Date/Time(Server) (see Notes and Limits)
Event.CategoryThe category in the header, for example Device Control, Content Aware Protection or System Logs
Event.InfoThe event name in the header, for example File Read-Write or Content Threat Detected
Event.IDLog ID
Event.ActionAction Type
Event.AdditionalInformationSection
Event.DetailDestination Details or destination_details, which holds the recipient list on email events
Event.NoteMessage
Source.HostNameClient Computer or machine_name
Source.UserNameClient User or client_name, or Administrator on System Logs events
Source.IP, Source.IPV6, Source.City, Source.Country, Source.LocationIP Address or ip, which accepts both IPv4 and IPv6 values
Source.MACMAC Address
Source.OSOS or os_version, falling back to os_type_name when neither is present
Object.Name, Object.PathFile Name or file_name, split at the last forward slash or backslash into the file name and its directory. This covers Unix style paths, drive letter paths such as D:\Reports\2026\list.xls and UNC paths such as \\server\share\form.docx.
Object.TypeFile Type or file_type
Object.SizeFile Size or file_size
Object.HashFile Hash or file_hash
Object.PipeNameItem Details or item_details
Device.TypeDevice Type or device_type_name, for example Network Share or Serial ATA Controller
Device.NameDevice or device_name, falling back to the client computer name
Device.SerialNumberSerial Number or serial_no
Policy.Name, Policy.TypeContent Policy or content_policy, Content Policy Type
Destination.Attribute, Destination.InterfaceDestination Type or destination_type, Destination or destination
Mail.TO, Mail.SubjectEmail Sender or email_sender, Email Subject or email_subject
Configuration.Old, Configuration.NewBefore, After, which carry the previous and new settings on administrator changes

Every event is recorded with Vendor CoSoSys, Product Endpoint Protector, EventSource Type Security System, EventSource Category DLP, EventSource PrefixID 4066 and Event.VendorID 1.

Event Classification

The EventMap classification and the severity come from the event name in the message header. This works the same way for the 2608 key names.

Event nameEventMapSeverity
File Read, File Read-WriteObject / File / Accessinformation
File Write, File Copy, File RenameObject / File / Changeinformation
File DeleteObject / File / Deletewarning
Content Threat DetectedSecurity / Scan / Detectcritical
Client Integrity FailSecurity / Other / Errorwarning
Connected, Disconnected, Blocked, UnblockedSecurity / Other / Infoinformation
User LoginIdentity / User / Logininformation
User LogoutIdentity / User / Logoutinformation
Policies ReceivedSystem / Policy / Infoinformation
Endpoint LicensesSystem / License / Infoinformation

Any other event name is still parsed and searchable, but it gets no EventMap values and its severity defaults to information. If you build correlation rules on event types that are not in the table, filter on Event.Category and Event.Info instead of EventMap.

Notes and Limits

  • Time.Generated is taken from the syslog header, not from the Date/Time(Server) value inside the message, and the header time is used as it is without being converted to the appliance time zone. On the RFC 5424 UTC format this means Time.Generated is a UTC time. For a server running at UTC+7, an event the Endpoint Protector console shows at 15:33:01 is recorded in Logsign as 08:33:01 on the same day. Keep that offset in mind when you compare the two consoles or build time based searches.
  • Fractional seconds in the header are dropped, so events are recorded with one second resolution.
  • Only the native [Key] Value output is parsed. If the Endpoint Protector server is configured to send CEF, LEEF or JSON, the messages are not recognized by this integration.
  • An event has to arrive as a single syslog message. If something in the path splits it at the pair separator, the parts are not recognized.
  • These keys are parsed but are not mapped to a normalized field: Event Name (the header event name is used instead), Date/Time(Server), Date/Time(Client), Date/Time(Server UTC), Date/Time(Client UTC), Matched Item, Justification, Time Interval, EPP Client Version, Device VID, Device PID and Device Serial. They remain visible in the raw message.
  • In the 2608 format, only the keys shown in the What Gets Collected table are mapped. Other keys such as event_id, event_name, timestamp, event_time_local, machine_id, domain, department_name, device_type_id, vid, pid, epp_client_version and ur_justification are parsed but not mapped to a normalized field, and they remain visible in the raw message.
  • The 2608 key names for Content Aware Protection events follow the Netwrix field reference. Logsign has not yet checked them against a real Content Aware Protection event in the 2608 format. If Source, Policy or Destination fields stay empty on these events while Device Control events look correct, send a raw sample line to Logsign Support.
  • Mail.TO carries the Email Sender value, not the recipients. The recipient list of an email event is in Event.Detail, from Destination Details.
  • System Logs administrator events (event name Admin Action) are collected with Event.Action set from Action Type and the old and new settings in Configuration.Old and Configuration.New, but they are not given EventMap values. Search them with Event.Category System Logs.
  • A file name that contains a closing bracket followed by a space, for example [SHS] Private Placement Bonds IM_v3.docx, is handled correctly and does not affect the fields that follow it in the message.

Verification

After both sides are saved, one file operation on a monitored device or share is enough to check the integration end to end.

  • In Logsign USO, open Settings > Data Collection and confirm that the CoSoSys Endpoint Protector source is receiving data.
  • Open or copy a file on a monitored network share or removable device from a machine that runs the Endpoint Protector client. In Logsign USO, go to Search and look for events with Vendor CoSoSys and Product Endpoint Protector. The operation should appear with your client computer in Source.HostName, the user in Source.UserName, the file in Object.Name and Object.Path, and an EventMap of Object / File / Access or Object / File / Change.
  • If the source is receiving data but no events show Vendor CoSoSys, the messages are not in a format this integration recognizes. Check that the syslog output is the native [Key] Value format, and compare the header of a raw message against the three forms in Supported Message Formats.
  • If events show Vendor CoSoSys and the correct EventMap, but Source.HostName, Source.UserName, Device and Object fields are empty, look at the raw message. Keys such as [machine_name] and [file_name] mean the server runs Endpoint Protector 2608 or later, and your Logsign USO release does not yet include support for the 2608 field names.
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.