Skip to main content

CrowdStrike

Visualize Crowdstrike endpoint agents and protected devices, map agents to devices and their respective owners, and monitor changes through queries and alerts.

Installation​

info

You will need to create an API client ID and an API client secret on Crowdstrike. See their documentation for more information.

When creating the API client ID and API client secret, provide (at minimum) read access to the following API Scopes:

  • Hosts
  • Prevention policies

An additional scope is needed for ingesting vulnerabilities (Spotlight Vulnerabilities). Future additions may require additional scopes.

note

The query used to ingest vulnerabilities limits to the date/time of the last successful integration or to the last 30 days for the initial run. Similarly, only crowdstrike_sensors seen by CrowdStrike in the last 30 days will be ingested.

To install the Crowdstrike integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Crowdstrike. Click New Instance to begin configuring your integration.

Creating a configuration requires the following:

  • The Account Name used to identify the Crowdstrike account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your Crowdstrike API client ID and API client secret to authenticate with the CrowdStrike Falcon and Spotlight APIs.

  • Enter the Availability Zone you'd like to use for API calls. Leave blank to use the main API endpoint. For example, entering us-2 as the availability zone will result in the use of a CrowdStrike API endpoint of api.us-2.crowdstrike.com.

Click Create once all values are provided to finalize the integration.

note

The CrowdStrike integration only ingests information on applications that have vulnerabilities. Applications without vulnerabilities will not be ingested into JupiterOne.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.