Crowdstrike Falcon Data Replicator V2 (using Azure Functions) connector for Microsoft Sentinel

The Crowdstrike Falcon Data Replicator connector provides the capability to ingest raw event data from the Falcon Platform events into Microsoft Sentinel. The connector provides ability to get events from Falcon Agents which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.

Connector attributes

Connector attribute Description
Azure function app code https://aka.ms/sentinel-CrowdstrikeReplicatorV2-functionapp
Kusto function alias CrowdstrikeReplicator
Log Analytics table(s) CrowdStrike_Additional_Events_CL
ASimNetworkSessionLogs
ASimDnsActivityLogs
ASimAuditEventLogs
ASimFileEventLogs
ASimAuthenticationEventLogs
ASimProcessEventLogs
ASimRegistryEventLogs
ASimUserManagementActivityLogs
CrowdStrike_Secondary_Data_CL
Data collection rules support Not currently supported
Supported by Microsoft Corporation

Query samples

Data Replicator - All Activities

CrowdStrikeReplicatorV2 

| sort by TimeGenerated desc

Prerequisites

To integrate with Crowdstrike Falcon Data Replicator V2 (using Azure Functions) make sure you have:

  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions.
  • SQS and AWS S3 account credentials/permissions: AWS_SECRET, AWS_REGION_NAME, AWS_KEY, QUEUE_URL is required. See the documentation to learn more about data pulling. To start, contact CrowdStrike support. At your request they will create a CrowdStrike managed Amazon Web Services (AWS) S3 bucket for short term storage purposes as well as a SQS (simple queue service) account for monitoring changes to the S3 bucket.

Vendor installation instructions

This connector uses Azure Functions to connect to the AWS SQS / S3 to pull logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.

(Optional Step) Securely store API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.

Prerequisites

  1. Configure FDR in CrowdStrike - You must contact the CrowdStrike support team to enable CrowdStrike FDR.
    • Once CrowdStrike FDR is enabled, from the CrowdStrike console, navigate to Support --> API Clients and Keys.
    • You need to Create new credentials to copy the AWS Access Key ID, AWS Secret Access Key, SQS Queue URL and AWS Region.
  2. Register AAD application - For DCR to authentiate to ingest data into log analytics, you must use AAD application.
    • Follow the instructions here (steps 1-5) to get AAD Tenant Id, AAD Client Id and AAD Client Secret.
    • For AAD Principal Id of this application, access the AAD App through AAD Portal and capture Object Id from the application overview page.

Deployment Options

Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the Crowdstrike Falcon Data Replicator connector V2 using an ARM Tempate.

  1. Click the Deploy to Azure button below.

    Deploy To Azure

  2. Provide the required details such as Microsoft Sentinel Workspace, CrowdStrike AWS credentials, Azure AD Application details and ingestion configurations NOTE: Within the same resource group, you can't mix Windows and Linux apps in the same region. Select existing resource group without Windows apps in it or create new resource group. It is recommended to create a new Resource Group for deployment of function app and associated resources.

  3. Mark the checkbox labeled I agree to the terms and conditions stated above.

  4. Click Purchase to deploy.

Option 2 - Manual Deployment of Azure Functions

Use the following step-by-step instructions to deploy the Crowdstrike Falcon Data Replicator connector manually with Azure Functions (Deployment via Visual Studio Code).

1. Deploy DCE, DCR and Custom Tables for data ingestion

  1. Deploy the required DCE, DCR(s) and the Custom Tables by using the Data Collection Resource ARM template
  2. After successful deployment of DCE and DCR(s), get the below information and keep it handy (required during Azure Functions app deployment).

2. Deploy a Function App

  1. Download the Azure Function App file. Extract archive to your local development computer.
  2. Follow the function app manual deployment instructions to deploy the Azure Functions app using VSCode.
  3. After successful deployment of the function app, follow next steps for configuring it.

3. Configure the Function App

  1. Go to Azure Portal for the Function App configuration.

  2. In the Function App, select the Function App Name and select Configuration.

  3. In the Application settings tab, select ** New application setting**.

  4. Add each of the following application settings individually, with their respective string values (case-sensitive):

    • AWS_KEY
    • AWS_SECRET
    • AWS_REGION_NAME
    • QUEUE_URL
    • USER_SELECTION_REQUIRE_RAW //True if raw data is required
    • USER_SELECTION_REQUIRE_SECONDARY //True if secondary data is required
    • MAX_QUEUE_MESSAGES_MAIN_QUEUE // 100 for consumption and 150 for Premium
    • MAX_SCRIPT_EXEC_TIME_MINUTES // add the value of 10 here
    • AZURE_TENANT_ID
    • AZURE_CLIENT_ID
    • AZURE_CLIENT_SECRET
    • DCE_INGESTION_ENDPOINT
    • NORMALIZED_DCR_ID
    • RAW_DATA_DCR_ID
    • EVENT_TO_TABLE_MAPPING_LINK // File is present on github. Add if the file can be accessed using internet
    • REQUIRED_FIELDS_SCHEMA_LINK //File is present on github. Add if the file can be accessed using internet
    • Schedule //Add value as '0 */1 * * * *' to ensure the function runs every minute.
  5. Once all application settings have been entered, click Save.

Next steps

For more information, go to the related solution in the Azure Marketplace.