↳ GitHub sourceConnector

Forescout

Description

The [Forescout](https://www.forescout.com/) data connector provides the capability to ingest [Forescout events](https://docs.forescout.com/bundle/syslog-3-6-1-h/page/syslog-3-6-1-h.How-to-Work-with-the-Syslog-Plugin.html) into Microsoft Sentinel. Refer to [Forescout documentation](https://docs.forescout.com/bundle/syslog-msg-3-6-tn/page/syslog-msg-3-6-tn.About-Syslog-Messages-in-Forescout.html) for more information.
Declared status
1
Declared author / publisher
Forescout

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Data types

Declared permissions

read and write permissions are required.
Workspace
Workspace

Connector instructions

Content published in the repository. Refer to the original file for all parameters.

>**NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected [**ForescoutEvent**](https://aka.ms/sentinel-forescout-parser) which is deployed with the Microsoft Sentinel Solution.
>**NOTE:** This data connector has been developed using Forescout Syslog Plugin version: v3.6
1. Install and onboard the agent for Linux or Windows
Install the agent on the Server where the Forescout logs are forwarded. > Logs from Forescout Server deployed on Linux or Windows servers are collected by **Linux** or **Windows** agents.
Choose where to install the Linux agent:
Install agent on Azure Linux Virtual Machine
Select the machine to install the agent on and then click **Connect**.
Install agent on a non-Azure Linux Machine
Download the agent on the relevant machine and follow the instructions.
Choose where to install the Windows agent:
Install agent on Azure Windows Virtual Machine
Select the machine to install the agent on and then click **Connect**.
Install agent on a non-Azure Windows Machine
Download the agent on the relevant machine and follow the instructions.
2. Configure the logs to be collected
Configure the facilities you want to collect and their severities. 1. Under workspace advanced settings **Configuration**, select **Data** and then **Syslog**. 2. Select **Apply below configuration to my machines** and select the facilities and severities. 3. Click **Save**.
3. Configure Forescout event forwarding
Follow the configuration steps below to get Forescout logs into Microsoft Sentinel. 1. [Select an Appliance to Configure.](https://docs.forescout.com/bundle/syslog-3-6-1-h/page/syslog-3-6-1-h.Select-an-Appliance-to-Configure.html) 2. [Follow these instructions](https://docs.forescout.com/bundle/syslog-3-6-1-h/page/syslog-3-6-1-h.Send-Events-To-Tab.html#pID0E0CE0HA) to forward alerts from the Forescout platform to a syslog server. 3. [Configure](https://docs.forescout.com/bundle/syslog-3-6-1-h/page/syslog-3-6-1-h.Syslog-Triggers.html) the settings in the Syslog Triggers tab.

Related content

Links established from declared identifiers and solution manifests.

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

Source identifier
Forescout
Additional source files 2Solutions/Forescout (Legacy)/Data Connectors/Forescout_syslog.jsonsource ↗Solutions/Forescout (Legacy)/Data/Solution_Forescout.jsonsolution-membership ↗
GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.