Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | CrowdStrikeFalconAdversaryIntelligence |
| Publisher | CrowdStrike |
| Used in Solutions | CrowdStrike Falcon Endpoint Protection |
| Collection Method | Azure Function (TI Upload API) |
| Connector Definition Files | CrowdStrikeFalconAdversaryIntelligence_FunctionApp.json |
| Ingestion API | STIX 2.0 Upload Indicators API — Connector code references STIX 2.0 Upload Indicators API endpoint (matched 'threatintelligenceindicators:upload') |
| Microsoft Learn | View on Learn |
The CrowdStrike Falcon Indicators of Compromise connector retrieves the Indicators of Compromise from the Falcon Intel API and uploads them Microsoft Sentinel Threat Intel.
This connector ingests data into the following tables:
| Table | Selection Criteria | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|---|
ThreatIntelIndicators |
SourceSystem == "CrowdStrike Falcon Adversary Intelligence" |
✓ | ✓ | ✗ |
ThreatIntelObjects |
✓ | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ 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.
STEP 1 - Generate CrowdStrike API credentials.
Make sure 'Indicators (Falcon Intelligence)' scope has 'read' selected
STEP 2 - Register an Entra App with client secret.
Provide the Entra App principal with 'Microsoft Sentinel Contributor' role assignment on the respective log analytics workspace. How to assign roles on Azure.
STEP 3 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function
IMPORTANT: Before deploying the CrowdStrike Falcon Indicator of Compromise connector, have the Workspace ID (can be copied from the following).
WorkspaceIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
6. Option 1 - Azure Resource Manager (ARM) Template
Use this method for automated deployment of the CrowdStrike Falcon Adversary Intelligence connector connector using an ARM Tempate.
Click the Deploy to Azure button below.
Provide the following parameters: CrowdStrikeClientId, CrowdStrikeClientSecret, CrowdStrikeBaseUrl, WorkspaceId, TenantId, Indicators, AadClientId, AadClientSecret, LookBackDays
7. Option 2 - Manual Deployment of Azure Functions
Use the following step-by-step instructions to deploy the CrowdStrike Falcon Adversary Intelligence connector manually with Azure Functions (Deployment via Visual Studio Code).
1. Deploy a Function App
NOTE: You will need to prepare VS code for Azure function development.
Download the Azure Function App file. Extract archive to your local development computer.
Start VS Code. Choose File in the main menu and select Open Folder.
Select the top level folder from extracted files.
Choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose the Deploy to function app button. If you aren't already signed in, choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose Sign in to Azure If you're already signed in, go to the next step.
Provide the following information at the prompts:
a. Select folder: Choose a folder from your workspace or browse to one that contains your function app.
b. Select Subscription: Choose the subscription to use.
c. Select Create new Function App in Azure (Don't choose the Advanced option)
d. Enter a globally unique name for the function app: Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. CrowdStrikeFalconIOCXXXXX).
e. Select a runtime: Choose Python 3.12.
f. Select a location for new resources. For better performance and lower costs choose the same region where Microsoft Sentinel is located.
Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
Go to Azure Portal for the Function App configuration.
2. Configure the Function App
📄 Source: [CrowdStrike Falcon Endpoint Protection\Data Connectors\CrowdStrikeFalconAdversaryIntelligence\README.md](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/CrowdStrike Falcon Endpoint Protection\Data Connectors\CrowdStrikeFalconAdversaryIntelligence\README.md)
This Microsoft Sentinel data connector enables ingestion of threat intelligence indicators from the CrowdStrike Falcon Intelligence API. It fetches indicators of compromise (IOCs), converts them to STIX 2.1 format, and uploads them to the Microsoft Sentinel threat intelligence store.
The connector runs as an Azure Function App on a 10-minute timer trigger, giving security teams continuously updated, high-confidence threat intelligence to power analytics, hunting, and incident detection.
malicious_confidence (high/medium/low) to STIX confidence scores (85/60/30).indicators:read API scope.indicators:read scope.| Region | Base URL |
|---|---|
| US-1 | https://api.crowdstrike.com |
| US-2 | https://api.us-2.crowdstrike.com |
| EU-1 | https://api.eu-1.crowdstrike.com |
| US-GOV-1 | https://api.laggar.gcw.crowdstrike.com |
When deploying the connector, you'll provide the following parameters:
| Parameter | Required | Description |
|---|---|---|
FunctionName |
Yes | A name for the deployed Function App. |
CrowdStrikeClientId |
Yes | CrowdStrike API client ID. |
CrowdStrikeClientSecret |
Yes | CrowdStrike API client secret. |
CrowdStrikeBaseUrl |
Yes | Region-specific CrowdStrike API base URL (see table above). |
WorkspaceId |
Yes | Microsoft Sentinel workspace ID. |
TenantId |
Yes | Azure AD tenant ID. |
AadClientId |
Yes | Azure AD application client ID. |
AadClientSecret |
Yes | Azure AD application client secret. |
Indicators |
Yes | Comma-separated indicator types to ingest (e.g. url,hash_md5,domain,ip_address). |
LookBackDays |
No | Time window (in days) used on the first run only. Default 1, maximum 60. |
The Indicators parameter accepts any combination of the following types:
hash_md5, hash_sha256, hash_sha1, url, domain, ip_address, mutex_name, password, file_name, email_address, username, persona_name, ip_address_block, coin_address, bitcoin_address.
These can be set as Application Settings on the Function App after deployment:
| Setting | Default | Description |
|---|---|---|
VALIDUNTIL |
20m |
Duration string (m, h, or d — e.g. 20m, 2h, 7d) that sets the STIX valid_until field on uploaded indicators. |
By default the Function App and its storage account are publicly accessible. For a network-isolated deployment, the ARM template can provision a Virtual Network, integrate the Function App with it, and route storage access through private endpoints. Set EnableVNetIntegration to true to enable this; all other VNet parameters are ignored when it is false. Be aware that this will increase your Azure costs through private endpoints and a new consumption plan.
| Parameter | Default | Description |
|---|---|---|
EnableVNetIntegration |
false |
Set to true to deploy a VNet and integrate the Function App with it. When false, VNet resources are skipped and storage remains publicly accessible. |
VNetAddressPrefix |
10.0.0.0/16 |
Address space for the Virtual Network in CIDR notation. |
SubnetName |
snet-functionapp |
Name of the subnet delegated to the Function App for VNet integration. |
SubnetAddressPrefix |
10.0.0.0/24 |
Address prefix for the Function App integration subnet. Must be within the VNet address space. Minimum /28. |
PrivateEndpointSubnetName |
snet-privateendpoints |
Name of the subnet used for storage private endpoints. Must not be delegated. |
PrivateEndpointSubnetAddressPrefix |
10.0.1.0/24 |
Address prefix for the private endpoint subnet. Must be within the VNet address space and not overlap with the Function App subnet. |
UseExistingDnsZones |
false |
Set to true when the private DNS zones and their VNet links already exist (e.g. from a prior deployment). Skips creating DNS zones and VNet links to avoid conflicts. |
On the connector page, complete the configuration steps:
IMPORTANT: Before deploying, copy your Workspace ID from the connector page.
CrowdStrikeClientId, CrowdStrikeClientSecret, CrowdStrikeBaseUrl, WorkspaceId, TenantId, Indicators, AadClientId, AadClientSecret, LookBackDays.Confirm indicators are flowing into Microsoft Sentinel:
ThreatIntelIndicators
| where SourceSystem == "CrowdStrike Falcon Adversary Intelligence"
| take 10
Note: The first run uses
LookBackDaysto establish a starting window. Subsequent runs ingest only new, high-confidence indicators newer than the last persisted marker.
indicators:read scope is granted.Indicators list contains valid, subscribed indicator types.Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊