Use CrowdStrike Falcon Streaming v2 integration to connect to CrowdStrike Falcon stream and fetch events as incidents to demisto.
Define CrowdStrike API client
In order to use the integration, an API client need to be defined, and its ID and secret should be configured in the integration instance.
Follow this article in order to get access to CrowdStrike API, and generate client ID and client secret.
The required scope is Event streams.
Configure CrowdStrike Falcon Streaming v2 on Demisto
- Navigate to Settings > Integrations > Servers & Services.
- Search for CrowdStrike Falcon Streaming v2
- Click Add instance to create and configure a new integration instance.
- Name: a textual name for the integration instance.
- Cloud Base URL (e.g. https://api.crowdstrike.com)
- Client ID
- Client Secret
- Application ID
- Event type to fetch
- Offset to fetch events from
- Stream client read timeout
- Incident type
- Store sample events for mapping
- Trust any certificate (not secure)
- Use system proxy settings
- Click Test to validate the URLs, token, and connection.
If you're using Falcon's commercial cloud, use the default value of the Cloud base URL. If you use another CrowdStrike cloud environment, use one of the following:
Offset to fetch events from should have an integer value, in order to fetch all events set it to 0 (as the default value).
Only events starting from this offset will be fetched
For example, if set to 10: the event with offset 9 will not be fetched, and events with offsets 10 and 11 will be fetched.
Event type to fetch parameter accepts multiple values, so choose as many as you want to fetch.
In order to fetch all events of all types, you can leave it empty.
You can also add event type that is not listed, by entering it in the parameter value.
In order to run multiple clients (stream consumers) simultaneously, each integration instance should have unique application ID. The application ID can be of length up to 32 characters.
Fetched Incidents Data
Event metadata will be fetched as the incident details, which contain the following:
- Creation time
- Used ID
- Service Name
- Detection Name
- Detection Description
Mapping incoming events
Because this is a push-based streaming integration, it cannot fetch sample events in the mapping wizard.
In order to view sample events, enable events storage by selecting the checkbox of the integration parameter Store sample events for mapping.
The last events (maximum of 20) are fetched every 1 minute. Allow the integration to run for at least 5 minutes before running the command. After you finish mapping, it is recommended to turn off the Store sample events for mapping to reduce performance overhead.
For Cortex XSOAR version 6.0 and above, you will be able to fetch samples in the mapping wizard
For earlier versions, you should run the
The command output is as follows:
You can now upload that JSON file to the mapping wizard and continue as usual.