CrowdStrike Threat Intel Source

Beta

CrowdStrike is the leader in next-generation endpoint protection, threat intelligence, and response services. CrowdStrike’s core technology, the Falcon platform, stops breaches by preventing and responding to all types of attacks — both malware and malware-free. The CrowdStrike Threat Intel integration ingests the indicator data from CrowdStrike Combined API and sends it to Sumo Logic as normalized threat indicator information.

info

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

Data collected

Polling Interval	Data
1 hour	Indicator data

Setup

Vendor configuration

Prerequisites

To collect vulnerability 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.

In this configuration, you will set up the CrowdStrike Threat Intel and configure it to be authorized and authenticated to use indicator information from CrowdStrike Threat Intel 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 Threat Intel 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. Sign in to CrowdStrike Platform.
2. Sign 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 console, select the Support and resources option from the menu.
   
4. In the Resources and tools section, select the API clients and keys option. You can then view existing clients or add new API clients from there.
   
5. Click Add new API client. You will be prompted to give a descriptive name and select the appropriate API scopes.
   
6. Provide a proper name and description and select the indicators(Falcon Intelligence):read scope scope. Click on ADD to complete the process.
7. After you click on ADD a dialogue box will appear with the Client ID, Client Secret, and Base URL. Copy and save the Client Id, Client Secret, and Base URL to a folder location because you will need them for the source configuration.
   

Region

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

Region	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

Source configuration

When you create a CrowdStrike Threat Intel 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 Threat Intel Source:

1. Classic UI. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
   New UI. In the Sumo Logic top menu select Configuration, and then under Data Collection select Collection. You can also click the Go To... menu at the top of the screen and select Collection.
2. On the Collectors page, click Add Source next to a Hosted Collector.
3. Search for and select CrowdStrike Threat Intel 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. (Optional) Fields. Click the +Add Field link to define the fields you want to associate. Each field needs a name (key) and value.
   •  A green circle with a check mark is shown when the field exists in the Fields table schema.
   •  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.
7. In Region, choose the region as per your Base URL. See Region section to know your region.
8. In Client ID, enter the Client ID you generated and secured from the API Client section.
9. In Client Secret, enter the Client Secret you generated and secured from the API Secret section.
10. In Sumo Logic Threat Intel Source ID, enter the Sumo Logic namespace in which the indicators are stored.
11. (Optional) In Mallicious Confidence, enter the type of confidence to collect data from. Possible values: high, medium,low, or unverified.
12. The Polling Interval is set for one hour by default, you can adjust it based on your needs. This sets how often the integration will fetch complete vulnerability instance data that has been updated within most recent polling interval duration.
13. When you are finished configuring the Source, click Save.

JSON schema

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

Parameter	Type	Value	Required	Description
schemaRef	JSON Object	{"type":"Crowdstrike Threat Intel"}	Yes	Define the specific schema type.
sourceType	String	"Universal"	Yes	Type of source.
config	JSON Object	Configuration object	Yes	Source type specific values.

Configuration Object

Parameter	Type	Required	Default	Description	Example
name	String	Yes	null	Type a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source.	"mySource"
description	String	No	null	Type a description of the source.	"Testing source"
category	String	No	null	Type a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details.	"mySource/test"
fields	JSON Object	No	null	JSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.	{"_siemForward": false, "fieldA": "valueA"}
baseURL	String	Yes	US-1	The Region of your CrowdStrike account.
clientID	String	Yes	null	The CrowdStrike Client ID you want to use to authenticate collection requests.
clientSecret	String	Yes	null	The CrowdStrike Client Secret you want to use to authenticate collection requests.
userSourceID	String	Yes	null	The Sumo Logic namespace in which the indicators will be stored.
pollingInterval	Integer	No	1 hour	This sets how often the Source checks for new data.
maliciousConfidence	String	No	null	Type of confidence to collect data from. Possible values: high, medium,low, or unverified.

JSON example

{
	"api.version": "v1",
	"source": {
		"config": {
  				"name": "Crowdstrike TI",
  				"baseURL": "https://api.crowdstrike.com",
  				"clientId": "8e094xxxxxxxxxxxx2b1nu36x2d2",
  				"clientSecret": "***********",
  				"pollingIntervalHour": 1,
				"userSourceID": "id1",
  				"maliciousConfidence": [
    					"high",
    					"medium",
    					"low",
    					"unverifed"
  				]
            },    
		"schemaRef": {
            		"type": "Crowdstrike Threat Intel"
        	},
        	"sourceType": "Universal"
    }
}

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "crowdstrike-threat-intel" {
  collector_id = sumologic_collector.collector.id
  schema_ref = {
    type = "CrowdStrike Threat Intel"
  }
  config = jsonencode({
  				"name": "Crowdstrike TI",
  				"baseURL": "https://api.crowdstrike.com",
  				"clientId": "8e094xxxxxxxxxxxx2b1nu36x2d2",
  				"clientSecret": "***********",
  				"pollingIntervalHour": 1,
				"userSourceID": "id1",
  				"maliciousConfidence": [
    					"high",
    					"medium",
    					"low",
    					"unverifed"
  				]
  })
}
resource "sumologic_collector" "collector" {
  name        = "my-collector"
  description = "Just testing this"
}

Download example

FAQ

info

Click here for more information about Cloud-to-Cloud sources.