Forescout Host Property Monitor (Push Connector via Codeless Connector Framework)

1. Create ARM Resources and Provide the Required Permissions

This connector receives data from external security systems that push logs to Microsoft Sentinel. The external system must be configured to send raw event data to the Microsoft Sentinel Ingestion API. Clicking on **Deploy** will trigger the creation of Log Analytics tables and a Data Collection Rule (DCR). It will then create an Entra application, link the DCR to it, and set the entered secret in the application. This setup enables data to be sent securely to the DCR using an Entra token. [Learn more about the connector setup process](https://review.learn.microsoft.com/azure/sentinel/create-push-codeless-connector)

Deploy Forescout Host Property Monitor connector resources (Multi-Stream)

Tenant ID (Directory ID)

Entra App Registration Application ID

Entra App Registration Secret

Data Collection Endpoint Url

Data Collection Rule Immutable ID

Stream Name (ForescoutHostProperties)

Stream Name (ForescoutPolicyStatus)

Stream Name (ForescoutComplianceStatus)

Keep these values secure. You will need them to configure your external security system.

2. Configure your external system to push logs

Use the following parameters to configure your external security system to send logs to the workspace. ### Configuration Steps 1. Access your external security system's configuration interface. 2. Navigate to the data forwarding, integration, or SIEM settings. 3. Select **Azure Monitor** or **Microsoft Sentinel** as the destination. 4. Select **Data Collection Endpoint** as the authentication method. 5. Configure the required fields using the values from the previous step: - **Tenant ID**: Copy from above - **Application (Client) ID**: Copy from above - **Client Secret**: Copy from above - **Data Collection Endpoint**: Copy from above - **Data Collection Rule Immutable ID**: Copy from above - **Stream Name**: Copy the appropriate stream name from above 6. Save the configuration and enable/start the forwarder. ### Validation > **Note**: Data will appear in the following tables in your Log Analytics workspace within a few minutes: > - **ForescoutHostProperties** > - **ForescoutPolicyStatus** > - **ForescoutComplianceStatus** To verify data is being received, run the following queries in your Log Analytics workspace: **Table 1: ForescoutHostProperties** ```kusto ForescoutHostProperties | where TimeGenerated > ago(1h) | take 10 ``` **Table 2: ForescoutPolicyStatus** ```kusto ForescoutPolicyStatus | where TimeGenerated > ago(1h) | take 10 ``` **Table 3: ForescoutComplianceStatus** ```kusto ForescoutComplianceStatus | where TimeGenerated > ago(1h) | take 10 ``` **All Tables Combined:** ```kusto union ForescoutHostProperties, ForescoutPolicyStatus, ForescoutComplianceStatus | where TimeGenerated > ago(1h) | take 10 ``` ### Troubleshooting If data is not appearing: - Verify the configuration values are correct - Check that the forwarder/integration is enabled and running - Review logs in your external security system for any errors - Ensure network connectivity from your system to Azure - Verify the Entra application has the correct permissions

Uninstall connector

Disconnect from all sources and delete the connector instances.