From ce3b31a15a73b67b10f56eceb7ebc4915f2d7e19 Mon Sep 17 00:00:00 2001 From: vg-svitla <131353512+vg-svitla@users.noreply.github.com> Date: Wed, 5 Jun 2024 15:59:41 +0300 Subject: [PATCH] Update docs/xdr/features/collect/integrations/endpoint/eset_protect.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Sébastien Quioc --- .../features/collect/integrations/endpoint/eset_protect.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/xdr/features/collect/integrations/endpoint/eset_protect.md b/docs/xdr/features/collect/integrations/endpoint/eset_protect.md index 0924be1d5e..f4bd9ff69b 100644 --- a/docs/xdr/features/collect/integrations/endpoint/eset_protect.md +++ b/docs/xdr/features/collect/integrations/endpoint/eset_protect.md @@ -16,6 +16,11 @@ This setup guide will show you how to enable log export in ESET Protect using sy Only events from the following log categories are being exported to Syslog server: Detection, Firewall, HIPS, Audit and ESET Inspect. +### Prerequisites + +An internal syslog concentrator is required to collect and forward events to Sekoia.io. + +### Enable syslog forwarding To enable Syslog server in ESET Protect, follow the steps below: 1. In admin console go to `More` > `Settings`.