Get a DemoStart Free TrialSign In


Ship ESET logs to logstash

Follow this step by step guide to get 'logs' from your system to

Step 1 - Configuring ESET

The use of ESET Admin Console, which is a locally installed management console, is recommended for organizations that need to send logs to a Syslog server.

Please note that the cloud management console does not support this functionality and is not compatible with the Syslog server integration.

Step 1 - Install the ESET certificate

sends data in an encrypted format.

You need to install the certificate on your Filebeat server.

sudo mkdir /etc//certificates
sudo openssl req -newkey rsa:2048 -nodes \
-keyout /etc/filebeat/certificates/.key -x509 \
-days 365 \
-out /etc/filebeat/certificates/.crt

Step 2 - Install Filebeat

To get started first follow the steps below:

  • Install
  • Root access
  • Verify the required port is open

Older versions can be found here 7, 6, 5

Step 3 - Configure Filebeat.yml

The configuration file below is pre-configured to send data to your Stack.

Copy the configuration file below and overwrite the contents of the Filebeat configuration file typically located at /etc/filebeat/filebeat.yml

# ============================== Filebeat inputs ===============================

- type: tcp
  max_message_size: 10MiB
  host: ""
  enabled: true

  fields_under_root: true
  encoding: utf-8
  ignore_older: 12h

# ================================== Outputs ===================================
    hosts: ["your-logstash-host:your-ssl-port"]
    loadbalance: true
    ssl.enabled: true

If you’re running Filebeat 7, add this code block to the end. Otherwise, you can leave it out.

# ... For Filebeat 7 only ...
filebeat.registry.path: /var/lib/filebeat

If you’re running Filebeat 6, add this code block to the end.

# ... For Filebeat 6 only ...
registry_file: /var/lib/filebeat/registry

It’s a good idea to run the configuration file through a YAML validator to rule out indentation errors, clean up extra characters, and check if your YAML file is valid. is a great choice.

Step 4 - Start filebeat

Start or restart to apply the configuration changes.

Step 5 - Configure ESET to output to syslog

To configure ESET to send logs to your Syslog server, follow these steps:

  • Open the ESET Admin Console on the Security Management Center
  • In the left side menu choose the ellipsis ... next to Server Settings
  • Expand the Advanced Settings
  • Find the Server Settings section
  • Choose to enable the Syslog server in the SYSLOG SERVER section

Enter the details for your server

  • Host: Enter the host ip address
  • Port: Enter the port 6515 (unless you have changed the default)
  • Format: Select BSD
  • Transport: Select TLS

Scroll down to the LOGGING section

  • Ensure Export logs to Syslog is enabled
  • Choose JSON as the Exported logs format

Step 7 - Check for your logs

Now you should view your data:

View my data

If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.

Step 8 - how to diagnose no data in Stack

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Step 9 - ESET Logging Overview

ESET is an endpoint security solution that offers complete protection against various cyber threats, including malware, ransomware, and other forms of attacks. To effectively monitor and analyze endpoint activity, it's essential to have a dependable and efficient log management solution. ESET generates logs that contain information on endpoint activity, threats, and user behavior.

To manage these logs efficiently, organizations can utilize Filebeat, a log shipping tool that is open-source, to send logs from ESET to multiple destinations such as Elasticsearch, Logstash, and OpenSearch, as it's both reliable and easy to use. Filebeat is widely employed for sending logs from ESET to various destinations, providing organizations with a centralized platform for collecting, processing, and visualizing security-related data.

To send ESET logs to Filebeat, organizations can set up ESET to forward logs to a syslog server and then use Filebeat to collect and forward log data to Elasticsearch or other destinations. This process includes configuring a syslog server to receive the logs, setting up ESET to send logs to the syslog server, and configuring Filebeat to collect and forward the logs from the syslog server to Elasticsearch or other destinations.

In conclusion, using Filebeat to send ESET logs to various destinations, such as Elasticsearch, Logstash, and Kibana or OpenSearch, provides an effective and reliable log management solution. By configuring ESET to forward logs to a syslog server and using Filebeat to collect and forward the logs to Elasticsearch or other destinations, organizations can gain insights into endpoint activity, threats, and user behavior and take appropriate measures to safeguard their networks against cyber threats.

If you need any further assistance with migrating your log data to we're here to help you get started. Feel free to get in contact with our support team by sending us a message via live chat & we'll be happy to assist.

Return to Search
Sign Up

© 2023 Ltd, All rights reserved.