Connect CrowdStrike
Connect a CrowdStrike Falcon Next-Gen SIEM tenant to a target with an API client.
A CrowdStrike target validates against Falcon Next-Gen SIEM. Nothing is installed in your tenant: Tracemill calls the Falcon API with an API client you create, to list your correlation rules, find the events it delivered, and read the alerts those rules raised.
1. Create a Falcon API client
In the Falcon console, create an API client with these scopes:
| Scope | Access |
|---|---|
| Correlation Rules | Read |
| NGSIEM | Read and Write |
| Alerts | Read |
NGSIEM Write is needed because Tracemill creates search jobs to find the events it delivered. Tracemill does not create or modify rules.
2. Connect the target
Create a target with the CrowdStrike SIEM type, then open Settings › Connection and enter:
| Field | Description |
|---|---|
| API client ID | The client ID from step 1. |
| API client secret | The client secret from step 1. |
| API base URL (optional) | Detected automatically for commercial clouds. Enter it for GovCloud. |
Select Connect. The page shows Connected · CrowdStrike Falcon when the credentials are accepted, and the target's Detections page fills with your correlation rules after the connector's first report.
If the connector never reports, the usual cause is a missing scope. Fix the API client in Falcon and select Re-check permissions.
3. Add a delivery pipeline
The connection only reads from Falcon. Events are delivered separately, through a pipeline into the ingestion path that feeds your Next-Gen SIEM. Add one under Settings › Pipelines; see Pipelines.
Managing the connection
- Replace credentials swaps in a new API client, for example after rotating the secret.
- Disconnect removes the connection. Connect again with an API client to resume validation.
How detections are matched
A Test for CrowdStrike names a correlation rule template, which is the same in every Falcon tenant, and Tracemill matches it to the rule you deployed from that template. See the job schema.