Before you begin, you’ll need:
- ESET Endpoint Protection Advanced installed
- ESET Admin Console locally installed. (The cloud management console does not support sending logs to a Syslog server and therefore is not supported.)
- Filebeat 7
- Root access
Install the ESET certificate on your Filebeat server
ESET sends encrypted data, so you’ll need to create a dedicated ESET certificate to decrypt the logs by the Filebeat server.
sudo mkdir /etc/filebeat/certificates sudo openssl req -newkey rsa:2048 -nodes \ -keyout /etc/filebeat/certificates/ESET.key -x509 \ -days 365 \ -out /etc/filebeat/certificates/ESET.crt
Download the Logz.io public certificate to your credentials server
For HTTPS shipping, download the Logz.io public certificate to your certificate authority folder.
sudo curl https://raw.githubusercontent.com/logzio/public-certificates/master/AAACertificateServices.crt --create-dirs -o /etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt
Open the Filebeat configuration file (/etc/filebeat/filebeat.yml) with your preferred text editor. Copy and paste the code block below, overwriting the previous contents. (You want to replace the file’s contents with this code block.)
This code block adds ESET as an input and sets Logz.io as the output.
# ... filebeat.inputs: - type: tcp max_message_size: 10MiB host: "0.0.0.0:6514" ssl.enabled: true ssl.certificate: "/etc/filebeat/certificates/ESET.crt" ssl.key: "/etc/filebeat/certificates/ESET.key" ssl.verification_mode: none fields: logzio_codec: plain # Your Logz.io account token. You can find your token at # https://app.logz.io/#/dashboard/settings/manage-accounts token: <<LOG-SHIPPING-TOKEN>> type: eset fields_under_root: true encoding: utf-8 ignore_older: 3h filebeat.registry.path: /var/lib/filebeat processors: - rename: fields: - from: "agent" to: "filebeat_agent" ignore_missing: true - rename: fields: - from: "log.file.path" to: "source" ignore_missing: true # ... output.logstash: hosts: ["<<LISTENER-HOST>>:5015"] ssl: certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']
Replace the placeholders to match your specifics. (They are indicated by the double angle brackets
<<LOG-SHIPPING-TOKEN>>with the token of the account you want to ship to.
<<LISTENER-HOST>>with the host for your region. For example,
listener.logz.ioif your account is hosted on AWS US East, or
listener-nl.logz.ioif hosted on Azure West Europe.
One last validation - make sure Logz.io is the only output and appears only once. If the file has other outputs, remove them.
Start or restart Filebeat for the changes to take effect.
Configure ESET to send logs to Logzio
Open the ESET Admin Console on the Security Management Center.
- In the left side menu, click the ellipsis [⋯] > More > Server Settings.
- Expand the Advanced Settings option.
Scroll down to Server Settings and configure the Syslog server:
In the SYSLOG SERVER section, enable the option to Use Syslog server. Fill in the details:
- Host - Enter your host address.
- Port - Enter your port number. (Port 6514 unless you’ve changed the default)
- Format - Select BSD as the log format.
- Transport - Select the TLS protocol.
In the LOGGING section, enable the option to Export logs to Syslog. Fill in the details:
- Exported logs format - Select the JSON format.
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open Kibana.
If you still don’t see your logs, see log shipping troubleshooting.