CrowdStrike Falcon
The CrowdStrike integration brings detections and audit activity from CrowdStrike Falcon into UTMStack through the Falcon Event Streams API. You create an API client in Falcon, and UTMStack streams events with its credentials. Nothing is installed on your endpoints or in Falcon by UTMStack.
How it works
UTMStack connects to the Falcon Event Streams API of your CrowdStrike cloud region with an OAuth2 API client (a Client ID and secret that let a program get an access token) that has the Event streams: Read scope.
The stream is continuous: events arrive in UTMStack seconds to minutes after Falcon creates them. UTMStack keeps its position in each stream, so after a restart it continues where it stopped.
UTMStack stores only events created after collection started. Earlier detections and audit events are not imported.
Events are stored with the data type
crowdstrikeand parsed by the shipped pipelinecrowdstrike/crowdstrike.yaml(version 1.3.1). UTMStack v12 ships 17 detection rules for this data type; see CrowdStrike in the Rules tab.
Before you start
The Event Streams API is often disabled by default. You may need to contact CrowdStrike Support to turn it on before the integration can work.
In Falcon, you need permission to create API clients.
In UTMStack, you need the Administrator role (the
integrations.writepermission). Configuration is saved in the tenant you are working in.The UTMStack server must be able to reach the CrowdStrike API over HTTPS (outbound port 443).
Step 1: Create an API client in Falcon
- 1
Open API clients and keys
In the Falcon console, open the menu (the icon at the top left) and go to Support and resources > API clients and keys.
- 2
- 3
Name the client and grant the Event Streams scope
Enter a descriptive client name, for example
UTMStack_SIEM_Connector. Select the Event streams scope with Read access, then click Create. - 4
Record the credentials
Copy the Client ID, the Client Secret and the Base URL shown for your CrowdStrike region.
Falcon shows the Client Secret only once. If you lose it, you must create a new secret.
Step 2: Connect CrowdStrike in UTMStack
Each API client connection is a config group. You can add more than one, for example one per Falcon tenant.
- 1
- 2
Fill in the form
Field What to enter Config group name A name for this connection, for example acme-prod. It cannot be changed later, and it becomes the data source name on the Data Sources page.App name A descriptive name for this API client, for example utmstack-falcon.Client ID The Client ID from Step 1. Client Secret The Client Secret from Step 1. Base URL (cloud region) The Base URL of your CrowdStrike region (see the table below). All fields are required.
- 3
Save
Click Add config group. UTMStack signs in to CrowdStrike and checks access to Event Streams before it saves the credentials. When the check passes, you see "Config group created successfully."
| CrowdStrike 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 |
If the save fails
When the check fails, the config group is not saved and a message starting with "credential verification failed:" explains why.
| Message | What to check |
|---|---|
| Invalid Client ID or Client Secret | The Client ID or secret is wrong, or the secret was reset. |
| Client ID does not have permission to authenticate | The API client is disabled, or it has no scopes. |
| Client ID does not have permission to access Event Streams / CrowdStrike API returned a permission error | Add the Event streams: Read scope to the API client in Falcon. |
| Cannot access CrowdStrike Event Streams | The scope is missing, or the Event Streams API is not turned on for your Falcon account (see the note at the top). |
| Unrecognized CrowdStrike Cloud Region / Invalid CrowdStrike Cloud Region | Use one of the Base URLs in the table above. You can also enter the region code, for example us-1. |
| Cannot resolve CrowdStrike API host / Connection to CrowdStrike timed out | The Base URL is wrong, or the UTMStack server cannot reach it on port 443. |
Check that events arrive
- 1
Create some activity in Falcon
Do something Falcon records in its event stream, for example sign in to the Falcon console or change a setting. Detections also appear in the stream as they happen.
- 2
Open the logs in UTMStack
Open the Crowdstrike card again and click View logs. Log Explorer opens with the
crowdstrikedata type for the last 24 hours. Events usually appear within a few minutes. - 3
Check the data source
Go to Configure > Data Sources and open the Integrations tab. Your config group is listed by its name. The row is created when you save, and turns Live after the first events are counted, which can take up to 20 minutes.
Troubleshooting
Errors that happen after the config group is saved, for example a deleted API client, do not appear in the web interface. They are written to the logs of the UTMStack event processor on the server, where the integration runs.
| Symptom | Likely cause | Fix |
|---|---|---|
| The save fails with a permission message | The API client lacks Event streams: Read, or Event Streams is not turned on for your account. | Edit the API client in Falcon and add the scope. Ask CrowdStrike Support to turn on the Event Streams API if needed. |
Saved, but no crowdstrike events | No activity happened since you saved; UTMStack does not import earlier events. | Create activity (Step 1 of this check) and wait a few minutes. |
| Events stopped | The API client was deleted, or its secret was reset. | Create a new secret in Falcon, then edit the config group and paste it. |
| Events arrive from the wrong Falcon tenant | The API client was created in another Falcon CID (customer ID). | Create the API client inside the Falcon tenant you want to monitor, and add one config group per tenant. |
| The Integrations row shows Offline although events arrive | The data source's "last seen" time is updated from the ingestion counts, which can take up to about 20 minutes. | Wait 20 minutes and click Refresh. |
Manage config groups
Add more connections: save one config group per API client.
Edit: click the pencil icon next to a config group. The name cannot be changed. The client secret shows a masked value; leave it as it is to keep the stored secret. Click Update config group.
Delete: click the bin icon. The config group is deleted at once, without a confirmation, and collection stops. The data source it created stays on the Data Sources page; delete it there if you no longer need it.