🚫 🔍 [Deprecated] CrowdStrike Falcon Endpoint Protection via AMA

🚫 Deprecated: This connector has been deprecated and may be removed in future versions.

🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Connectors Index

Attribute Value
Connector ID CrowdStrikeFalconEndpointProtectionAma
Publisher CrowdStrike
Used in Solutions CrowdStrike Falcon Endpoint Protection
Collection Method AMA
Connector Definition Files template_CrowdStrikeFalconEndpointProtectionAma.json

The CrowdStrike Falcon Endpoint Protection connector allows you to easily connect your CrowdStrike Falcon Event Stream with Microsoft Sentinel, to create custom dashboards, alerts, and improve investigation. This gives you more insight into your organization's endpoints and improves your security operation capabilities.

NOTE: This data connector has been deprecated, consider moving to the CCP data connector available in the solution which replaces ingestion via the deprecated HTTP Data Collector API.

Additional Information

🛠️ Device Configuration: Follow these instructions to deploy the SIEM Collector and forward syslog.

Tables Ingested

This connector ingests data into the following tables:

Table Selection Criteria Transformations Ingestion API Lake-Only
CommonSecurityLog DeviceProduct == "FalconHost"
DeviceVendor == "CrowdStrike"		 ✓ ✓ ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions: - Workspace (Workspace): read and write permissions are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias Crowd Strike Falcon Endpoint Protection and load the function code or click here, on the second line of the query, enter the hostname(s) of your CrowdStrikeFalcon device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update. 1. Kindly follow the steps to configure the data connector

Step A. Configure the Common Event Format (CEF) via AMA data connector

Note:- CEF logs are collected only from Linux Agents

  1. Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .

  2. Search for 'Common Event Format (CEF) via AMA' data connector and open it.

  3. Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule)

    Note:- It is recommended to install minimum 1.27 version of AMA agent Learn more and ensure there is no duplicate DCR as it can cause log duplicacy

  4. Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine

Step B. Forward CrowdStrike Falcon Event Stream logs to a Syslog agent

Deploy the CrowdStrike Falcon SIEM Collector to forward Syslog messages in CEF format to your Microsoft Sentinel workspace via the Syslog agent. 1. Follow these instructions to deploy the SIEM Collector and forward syslog 2. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address.

Step C. Validate connection

Follow the instructions to validate your connectivity:

Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.

It may take about 20 minutes until the connection streams data to your workspace.

If the logs are not received, run the following connectivity validation script:

  1. Make sure that you have Python on your machine using the following command: python -version

  2. You must have elevated permissions (sudo) on your machine - Run the following command to validate your connectivity:: sudo wget -O Sentinel_AMA_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/Syslog/Sentinel_AMA_troubleshoot.py&&sudo python Sentinel_AMA_troubleshoot.py --cef

2. Secure your machine

Make sure to configure the machine's security according to your organization's security policy

Learn more >

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Connectors Index