Skip to main content

CrowdStrike FDR Host Inventory Source

thumbnail icon

The CrowdStrike FDR Host Inventory Source provides a secure endpoint to receive device data from the CrowdStrike Host-And-Host-Group-Management-APIs. It securely stores the required authentication, scheduling, and state tracking information.


The CrowdStrike API documentation is not public and can only be accessed by partners or customers.


To collect device data from the CrowdStrike platform, you must have an authorized CrowdStrike account. CrowdStrike APIs use an OAuth 2.0 authorization token to make authorized API calls. CrowdStrike API Client is required to get the OAuth 2.0 authorization token. To define a CrowdStrike API client, you must be designated as a CrowdStrike Falcon Administrator role.

Data sources

CrowdStrike FDR Host Inventory retrieves device information every 24 hours. The source will fetch device information that was seen in the last 30 days for the first time. Afterward, it will only fetch information about devices that have been modified.

Device data from this source could be used to augment AID data from the CrowdStrike FDR source via a lookup table

Metadata Field

If you've configured your integration with the Cloud SIEM forward option, metadata fields will be set. See Metadata Fields table below:

_siemProductFDR Host Inventory

Setup and Configuration

In this configuration, you will set up the CrowdStrike FDR account and configure it to be authorized and authenticated to use device information from CrowdStrike FDR API. To obtain the auth token, you will need the following parameters.

API Client and API Secret

The API security token is used to authenticate with CrowdStrike FDR API. After successfully creating the API client, you will get the Client Id, Client Secret, and Base URL. To get the CrowdStrike API Client, follow the steps below:

  1. Access the CrowdStrike FDR Platform.
  2. Log in using your email address and password. After you've completed the two-factor authentication, you'll be directed to the application dashboard.
  3. From the CrowdStrike FDR Console, on the left-hand panel of the dashboard, locate the Menu option and click on it.
  4. Select the Support and resources option from the menu.
  5. Navigate to and click on API clients and keys. You can then view existing clients or add new API clients from there.
  6. Click Add new API client. You will be prompted to give a descriptive name and select the appropriate API scopes.
  7. Provide a proper name and description and select the Read Hosts Scope. Click on ADD to complete the process.
  8. After you click on ADD a dialogue box will appear with the Client ID, Client Secret and Base URL. Copy and paste the Client Id, Client Secret and Base URL to a folder location because you will need them when creating the CrowdStrike FDR Host Inventory Source.


  1. Identify your Region based on your Base URL. The region can be selected from the list below.

    RegionBase URL


A CrowdStrike FDR Host Inventory Source tracks errors, reports its health, and start-up progress. You’re informed, in real-time, if the Source is having trouble connecting, if there's an error requiring user action, or if it is healthy and collecting by utilizing Health Events.

A CrowdStrike FDR Host Inventory Source goes through the following states when created:

  1. Pending. Once the Source is submitted, it is validated, stored, and placed in a Pending state.
  2. Started. A collection task is created on the Hosted Collector.
  3. Initialized. The task configuration is complete in Sumo Logic.
  4. Authenticated. The Source successfully authenticated with CrowdStrike FDR.
  5. Collecting. The Source is actively collecting data from CrowdStrike FDR.

If the Source has any issues during any one of these states, it is placed in an Error state.

When you delete the Source, it is placed in a Stopping state. When it has successfully stopped, it is deleted from your Hosted Collector.

On the Collection page, the Health and Status for Sources is displayed. Use Health Events to investigate issues with collection. You can click the text in the Health column, such as Error, to open the issue in Health Events to investigate.

Set up CrowdStrike FDR Host Inventory Source

When you create a CrowdStrike FDR Host Inventory Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector.

To configure the CrowdStrike FDR Host Inventory API:

  1. In Sumo Logic, select Manage Data > Collection > Collection
  2. On the Collectors page, click Add Source next to a Hosted Collector.
  3. Select CrowdStrike FDR Host Inventory icon.
  4. Enter a Name to display for the Source in the Sumo Logic web application. The description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM Enterprise as inventory. When configured with the Forward to SIEM option the following metadata fields are set:
  • _siemVendor: CrowdStrike
  • _siemProduct: FDR Host Inventory
  • _siemDataType: Inventory
  1. (Optional) Fields. Click the +Add Field link to define the fields you want to associate. Each field needs a name (key) and value.
    • green check circle.png A green circle with a check mark is shown when the field exists in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored, known as dropped.
  2. In Region, choose the region as per your Base URL. See Region section to know your region.
  3. In Client ID, enter the Client ID you generated and secured from the API Client section.
  4. In Client Secret, enter the Client Secret you generated and secured from the API Secret section.
  5. When you are finished configuring the Source, click Save.

Error types

When Sumo Logic detects an issue, it is tracked by Health Events. The following table shows three possible error types. It tells the reason for the error, if the source attempts to retry, and the name of the event log in the Health Event Index.

TypeReasonRetriesRetry BehaviorHealth Event Name
ThirdPartyConfigNormally due to an invalid configuration. You'll need to review your Source configuration and make an update.No retries are attempted until the Source is updated.Not applicableThirdPartyConfigError
ThirdPartyGenericNormally due to an error communicating with the third-party service APIs.YesThe Source will retry indefinitely.ThirdPartyGenericError
FirstPartyGenericNormally due to an error communicating with the internal Sumo Logic APIs.YesThe Source will retry indefinitely.FirstPartyGenericError

Restarting your Source

If your Source encounters ThirdPartyConfig errors, you can restart it from either the Sumo Logic UI or Sumo Logic API.


To restart your source in the Sumo Logic platform, follow the steps below:

  1. Open the Collection page, and go to Manage Data > Collection > Collection.
  2. Select the source and click the information icon on the right side of the row.
  3. The API usage information popup is displayed. Click the Restart Source button on the bottom left.
  4. Click Confirm to send the restart request.
  5. The bottom left of the platform will provide a notification informing you the request was successful.


To restart your source using the Sumo Management API, follow the instructions below:

  • Method: POST
  • Example endpoint:{collector_id}/sources/{source_id}/action/restart

Sumo Logic endpoints like are different in deployments outside us1. For example, an API endpoint in Europe would begin A service endpoint in us2 (Western U.S.) would begin For more information, see Sumo Logic Endpoints.

JSON configuration

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details. 

configJSON ObjectYesContains the configuration-parameters of the
schemaRefJSON ObjectYesUse {"type":"CrowdStrike FDR Host Inventory"} for CrowdStrike FDR Host Inventory Source.not modifiable
sourceTypeStringYesUse Universal for CrowdStrike FDR Host Inventory Source.not modifiable

Config Parameters

nameStringYesType the desired name of the Source and it must be unique per Collector. This value is assigned to the metadata field _sourcemodifiable
descriptionStringNoType the description of the Source.modifiable
categoryStringNoType the category of the source. This value is assigned to the metadata field _sourceCategory.modifiable
fieldsJSON ObjectNoJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.modifiable
regionStringYesThe Region of your CrowdStrike account.modifiable
clientIDStringYesThe CrowdStrike Client ID you want to use to authenticate collection requests.modifiable
clientSecretStringYesThe CrowdStrike Client Secret you want to use to authenticate collection requests.modifiable

JSON example

"name": "crowdstrike-fdr",
"description": "crowdstrike-fdr-inventory",
"region": "US-1",
"clientID": "client id",
"clientSecret": "client secret",
"type":"CrowdStrike FDR Host Inventory Source"
Privacy Statement
Terms of Use

Copyright © 2023 by Sumo Logic, Inc.