You are leaving our website

tcucinieri · 01-29-2020

Description This is a feature that exists to enable connecting to collectors from the supervisor when there is a firewall between the collector and the supervisor. Restricted user 'tunneluser' runs in a restricted shell that lets only that user creat...

tcucinieri · 07-18-2019

PurposeFortiSIEM supports Nessus 7.1.4 and Nessus-8.1.2 nowFollow the steps below to get Nessus Vulnerability Scanner Report in FortiSIEM:1) Deploy Nessus7/Nessus8 server, generate API key, add a target device IP that waiting to be scan2) Add the tar...

tcucinieri · 06-24-2019

DescriptionThis article describes how to update the Operating System of FortiSIEM.FortiSIEM works on CentOS Linux Operating System and CVE fixes are distributed accordingly with the main OS kernel fixes.Once a new update is available, FortiSIEM engin...

tcucinieri · 06-06-2019

DescriptionBeginning with Windows Agent release 3.0:Agents must upload event data to a Collector. Therefore, minimum architecture is one Supervisor Appliance and one Collector Appliance.Collectors must be installed as IPv4 only. Dual stack IPv4/IPv6 ...

tcucinieri · 05-22-2019

DescriptionThis article describes why the installation of FortiSIEM Windows Agent 3.1 on cloned VM Windows Servers may fail.SolutionFortiSIEM Windows Agent 3.1 installation fails because it identifies both servers as one. This situation can happen if...

User Statistics

User Activity

Technical Tip: Disable Hardcoded SSH configuration for tunnel user

Troubleshooting Tip: How to get Nessus Vulnerability Scanner Report in FortiSIEM

Tecnical Tip: FortiSIEM - OS Update HowTo

Technical Tip: Windows Agent 3.x and Collectors installation considerations

Troubleshooting Tip: FortiSIEM Windows Agent 3.1 installation failed on cloned VM Windows Servers

KCS