Overview
HarfangLab EDR can forward endpoint telemetry (process, network, DNS, URL, PowerShell, driver, USB and authentication events) to an external syslog server. This article explains how to send that telemetry to Logsign Unified SecOps Platform via syslog.
Syslog telemetry is a separate source from the HarfangLab EDR API integration described in HarfangLab EDR Data Collection and Response Integration Guide. The API integration collects alerts and creates incidents. The syslog source described here collects raw endpoint telemetry for search, reporting and correlation. You can use both at the same time. Events from the two sources carry the same vendor and product names (HarfangLab / EDR) and are told apart by EventSource.PrefixID: 4496 for the API source and 4532 for the syslog source.
Prerequisites
- A Logsign version that includes the HarfangLab EDR syslog parser (PrefixID 4532).
- Network access from the HarfangLab EDR Manager to the Logsign collector on the syslog port you use (UDP 514 by default).
- An administrator account on the HarfangLab EDR Manager that can edit the syslog export settings.
Configure On HarfangLab EDR
Unverified: the exact console menu path for the syslog export settings has not been verified against a live HarfangLab EDR Manager. Consult HarfangLab's administration guide for your version.
- In the HarfangLab EDR Manager, open the syslog export settings. On multi-tenant deployments the export is configured per tenant.
- Set the destination host to the IP address of your Logsign collector and the port to the syslog port configured on Logsign.
- Choose the protocol (UDP, TCP or TCP over SSL) that matches the listener on your Logsign collector.
- Set the message format to RFC 5424. The Logsign parser reads the RFC 5424 header (version, timestamp, hostname) followed by the JSON event. Lines sent with an RFC 3164 header, or as bare JSON without a header, are not recognized.
- Select the log types to export. See the "Supported Events" section below for the types that Logsign classifies in detail.
If the HarfangLab EDR API integration is already active, do not select the alert and threat log types in the syslog export. The API integration already collects alerts, and exporting them over syslog as well produces duplicate records.
Add Device in Logsign USO
Open the Logsign Unified SecOps Platform web interface and click the + Device button under Settings > Data Collection. In the Source Type Selection page, choose Syslog as the collection method, select HarfangLab as the vendor, and EDR as the product.
| Field | Description |
|---|---|
| Host | IP address of the HarfangLab EDR Manager sending the logs. |
| Encoding | utf_8 (default). |
| Offset | Time offset in minutes, if the source's clock differs from the collector's. |
| Data Policy | Filter which incoming logs are kept; Default Policy collects everything. |
| Check Health | Enable to monitor whether the source is actively sending logs. |
| Device Name / Tag | A descriptive name and optional tag for the source, used in search and reporting. |
Click Save to add the source. Once HarfangLab EDR is forwarding syslog to the configured host and port, events should begin appearing under Search.
Log Format
Each HarfangLab syslog message is an RFC 5424 header followed by a single JSON document. The example below is for illustration only (not a captured live sample):
<14>1 2026-11-12T19:12:11.103424+00:00 hl-tenant-a hl-tenant-a - - null {"@event_create_date": "2026-11-12T19:14:23.407162Z", "log_type": "process", "tenant": "tenant-a", "agent": {"agentid": "agent-0001", "hostname": "WS-01", "ipaddress": "192.0.2.10", ...}, ...}
The hostname in the syslog header is written to Device.HostName. The tenant name from the JSON body is written to Tenant.ID, so events from different HarfangLab tenants can be filtered in Search. The event time is taken from @event_create_date (or @timestamp when the first is missing), which HarfangLab sends in UTC, and is stored in Time.Generated in the Logsign server's local time.
Every event carries the endpoint agent details: Source.AgentID, Source.HostName, Source.DomainName, Source.OS, Source.OSVersion and, when no event-specific address is present, the agent IP address in Source.IP. Process name, path, PID, GUID and user name are filled where the event provides them.
Verification
- Confirm the source is receiving data under Settings > Data Collection (event count should increase).
- Filter Search by EventSource.PrefixID 4532 or by the source's Device Name/Tag, and confirm that fields such as Event.Category, Source.HostName, Tenant.ID and EventMap.Type are populated.
- If events arrive but are not parsed, check that the HarfangLab export uses the RFC 5424 format.