setup

CrowdStrike Falcon

Purpose

Imports Falcon hosts and their sensor versions, plus Spotlight vulnerabilities if your Falcon subscription includes Spotlight. Hosts are matched to the same devices from your MDM and identity integrations, so endpoint and vulnerability data sits next to your cloud and identity data.

Subimage reads from CrowdStrike's Hosts API and Spotlight Vulnerabilities API. The integration is read-only.

tip

Secret fields below accept either an AWS Secrets Manager ARN or a value pasted directly into Subimage's managed vault. See Secrets for details.

important

If your CrowdStrike API endpoint is restricted to a private network, set tailscale_hostname and run the collector from a Subimage Outpost.

Required Fields

Field Secret? Description
crowdstrike_client_id No Falcon API client ID
crowdstrike_client_secret Yes Falcon API client secret
crowdstrike_api_url No API base URL for your Falcon cloud. See API URL.
tailscale_hostname No (Optional) Internal hostname resolved via Outpost

Setup Steps

  1. In Falcon, open the API clients page. The menu depends on your console version: Support and resources → API clients and keys, Support and resources → Client Management, or Support Apps → API Clients on older consoles.
  2. Create a new API client, for example named SubImage, and grant Hosts: Read. If your subscription includes Spotlight, also grant Vulnerabilities: Read. Leave every other scope off.
  3. Copy the Client ID and Secret. Falcon shows the secret only once.
  4. In Subimage, fill in the fields above and save the module. crowdstrike_client_secret takes the secret or its AWS Secret ARN.
  5. Run a manual sync to check the connection.

API URL

Set crowdstrike_api_url to the API URL of the Falcon cloud your tenant is on. Your console address tells you which one: for example, falcon.us-2.crowdstrike.com is US-2.

Falcon cloud crowdstrike_api_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
US-GOV-2 https://api.us-gov-2.crowdstrike.mil

What each scope unlocks

Scope Data
Hosts: Read (required) Host inventory and sensor versions. Hosts are matched by serial number to the same device from your MDM and identity integrations (Jamf, Kandji, Intune, and others), so you can see which managed devices run Falcon.
Vulnerabilities: Read (optional) Open and reopened Spotlight vulnerabilities and their CVEs, each linked to the host it was found on. Vulnerabilities that close drop out at the next sync. Only Falcon tenants with Spotlight can grant this scope.

Adding a scope to an existing API client takes effect on the next sync. The client ID and secret don't change.

Troubleshooting

  • Sync fails with 403 Forbidden and scope not permitted → the API client is missing Hosts: Read. The error names the refused operation: QueryDevicesByFilterScroll or GetDeviceDetails.
  • Sync succeeds but no vulnerabilities appear, and the sync log says Skipping CrowdStrike Spotlight vulnerabilities → the API client doesn't have Vulnerabilities: Read, or your subscription doesn't include Spotlight. Hosts still sync. Vulnerabilities from earlier syncs are kept but stop updating until the scope is back.
  • Sync fails with 401 Unauthorized → the client ID or secret is wrong or revoked, or crowdstrike_api_url points at a different Falcon cloud. See API URL.
  • Older setup guides mention Detects: Read. It isn't required: the integration doesn't call the Detects API.