ESET

Ship ESET logs to Logstash

Follow the steps below to send your observability data to Logit.io

Logs

Send your ESET logs to logit.io via logstash using the instructions below and begin searching your data.

Install Integration

Please click on the Install Integration button to configure your stack for this source.

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.

Install the ESET certificate

ESET sends data in an encrypted format.

You need to install the ESET certificate on your Filebeat server.

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

Install Filebeat

To get started you will need to install filebeat. To do this you have two main options:

Choose the filebeat (opens in a new tab) ZIP file (Windows ZIP x86_64) or
Choose the Microsoft Software Installer MSI (opens in a new tab) file (Windows MSI x86_64 (beta))

To successfully install filebeat and set up the required Windows service you will need to have administrator access.

If you have chosen to download the zip file:

Extract the contents of the zip file into C:\Program Files.
Rename the extracted folder to filebeat
Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
From the PowerShell prompt, run the following commands to install filebeat as a Windows service:

cd 'C:\Program Files\filebeat'

.\install-service-filebeat.ps1

If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example:

PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1

For more information about Powershell execution policies see here (opens in a new tab).

If you have chosen to download the filebeat.msi file:

double-click on it and the relevant files will be downloaded.

At the end of the installation process you'll be given the option to open the folder where filebeat has been installed.

Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
From the PowerShell prompt, change directory to the location where filebeat was installed and run the following command to install filebeat as a Windows service:

.\install-service-filebeat.ps1

If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example:

PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1

For more information about Powershell execution policies see here (opens in a new tab).

Configure Filebeat.yml

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

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

####################### Logit.io Filebeat Configuration ########################
# ============================== Filebeat inputs ===============================
filebeat.inputs:
- type: udp
  max_message_size: 10MiB
  host: "0.0.0.0:514"
  enabled: true
 
  fields:
    type: eset
  fields_under_root: true
  encoding: utf-8
  ignore_older: 12h
 
# ================================== Outputs ===================================
output.logstash:
  hosts: ["@logstash.host:@logstash.sslPort"]
  loadbalance: true
  ssl.enabled: true

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. Yamllint.com (opens in a new tab) is a great choice.

Start filebeat

To start Filebeat, run in Powershell:

Start-Service filebeat

Configure ESET to output to syslog

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

Check Logit.io for your logs

Data should now have been sent to your Stack.

View My Data

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

How to diagnose no data in Stack

If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.

Cisco Meraki 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 Logit.io 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.

Erlang etcd