Connecting CrowdStrike Falcon Next-Gen SIEM (NGSIEM)
The CrowdStrike connector runs search jobs against the base_sensor repository, correlating running processes with DNS activity to identify which process on which host reached a given API or MCP endpoint, and surfaces AI agents, automation frameworks, and MCP servers across the licensed fleet. It sees network egress per process, not request contents, so it cannot see a model name carried inside a TLS payload.
RSA Agent ID combines this connector with other data sources to build device- and process-level visibility; it is not an authoritative agent registry on its own.
Before you begin
Ensure you have the following:
- A Falcon Administrator role, or a custom role permitted to create API clients and assign scopes
- An active Falcon Next-Gen SIEM subscription (or the 10 GB entitlement bundled with Falcon Insight XDR)
- Every host to be discovered licensed with Falcon Insight XDR or a bundle that includes it (for example, Falcon Enterprise or Falcon Complete Next-Gen MDR). Antivirus-only tiers, such as Falcon Go or Falcon Pro, do not write the process/DNS events this connector needs.
- The tenant's Falcon cloud region: US-1, US-2, EU-1, or US-GOV-1. It determines the API base URL. Next-Gen SIEM is offered across the commercial clouds and US-GOV-1, but entitlement is set by subscription rather than by region, so confirm NGSIEM is enabled on the tenant before creating the API client.
Required Permissions
Scope | Access | Purpose |
|---|---|---|
| NGSIEM | Read & Write | The connector requires NGSIEM Read and Write permissions but does not modify data. It submits a read-only CQL query for ProcessRollup2 and DnsRequest events through /humio/api/v1/repositories/{view}/queryjobs. Submitting the query creates a temporary server-side search job and returns a job ID, which the connector polls for results. Because StartSearchV1 creates this temporary job, CrowdStrike requires the Write permission. |
| Hosts | Read | Resolves agent IDs (aid) to host name, OS, and platform, so that process and DNS rows attach to the right device. |
CrowdStrike-side Setup
Procedure
- Sign in to the Falcon console for the tenant's region and go to Support and resources > API clients and keys.
- Click Create API client and enter a recognizable name, such as agent-discovery-ngsiem. Add a description if your policy requires one.
- Grant the NGSIEM scope the Read & Write permission (the connector submits a temporary search job and reads its results) and the Hosts scope the Read permission (resolves agent IDs to host name, OS, and platform).
- Click Create, then copy the Client ID, Client Secret, and Base URL from the confirmation dialog. The secret is shown only once and cannot be recovered after you close the dialog.
See the following table for the API Base URL for each region.
Region | API 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 |
Agent ID Setup
Procedure
On the Connectors page, click Add source, then click Connect on the CrowdStrike NGSIEM card.
Enter a Connection name and select a Falcon cloud region.
Enter the API Client ID and API Client Secret, and leave NG-SIEM repository blank to use base_sensor.
Click Test connection, confirm it succeeds, then click Save and start discovery.
Success means the base URL, Client ID, and Client Secret are valid and that NGSIEM Read is present. Note that Test Connection does not exercise the NGSIEM Write scope, which is only tested when the first search job runs.
Troubleshooting
Could not get a token.
Recheck the client ID/secret and the region-specific base URL.
Test passes but the first scan returns nothing.
Grant NGSIEM Read & Write (the search job cannot start on Read alone).
Some hosts never appear.
Check whether they are licensed with an antivirus-only tier that does not write to base_sensor.
Search returns zero rows on every query.
Confirm NGSIEM licensing and that the base_sensor repository is populated.
Host names are blank.
Add the Hosts scope Read and rescan.
Connector worked, then stopped.
API client secret expired. Reset the secret and update the connector.
Related Articles
CrowdStrike Falcon Next-Gen SIEM – RSA Ready Implementation Guide 27Number of Views RSA Agent ID Installation, Deployment, and Administration Guide 5Number of Views CrowdStrike Falcon Next-Gen SIEM - Authentication Manager - RSA Ready Implementation Guide 14Number of Views CrowdStrike Falcon Identity Protection - RSA Ready Implementation Guide 38Number of Views Connecting Discovery Data Sources 1Number of Views