Skip to main content

CollectorsCloud Collectors Administration Guide

CrowdStrike Context Cloud Collector

Prerequisites to Configure the CrowdStrike Context Cloud Collector

Before you configure the CrowdStrike Context cloud collector you must complete the following prerequisites:

  • Complete any vendor-specific requirements necessary to obtain the URLs and credentials you will need to access the data source.

  • Contact CrowdStrike support to obtain the cloud endpoint API gateway assigned to your API client.

    Note

    CrowdStrike assigns a cloud endpoint, also called an API gateway, to each API client. For example: https://api.crowdstrike.com or https://api.us-2.crowdstrike.com.

  • Obtain the client ID and client secret for the OAuth2 authentication method.

Obtain the Client ID and the Client Secret

CrowdStrike APIs are authenticated using application keys. You must obtain the client ID and client secret to use while configuring the CrowdStrike collector.

To obtain an application key:

  1. Log in to the CrowdStrike console as an administrator.

  2. In the left pane, navigate to Support > API Clients and Keys.

  3. In the upper right corner of the page that displays existing clients, click Add new API clients.

  4. In the Add new API client dialog box, specify a name and enter a description for the new client that will need access to the detection API in read-only mode.

  5. In the API Scopes, select Hosts (Read) to define the required API capabilities for retrieving host information.

  6. Click Add.

  7. Record the values for Client ID and Client Secret. The values are represented by a string of letters and numbers. You will need these values when you configure the cloud collector.

  8. Click Done.

  9. Proceed to Configure the CrowdStrike Context Cloud Collector.

Configure the CrowdStrike Context Cloud Collector

Set up the CrowdStrike Context Cloud Collector to continuously ingest device data from a CrowdStrike source. You can then create a corresponding CrowdStrike context table in the Context Management application to store the data.

In the context table, the CrowdStrike device data is normalized so that it can be mapped to Exabeam target attributes based on a common information model. This model defines standardized objects for security content across Exabeam products. The mapped data is used to enrich security content that can be leveraged by downstream services such as Search, Correlation Rules, and Dashboards. For more information about the context table and mapped attributes, see CrowdStrike Context Tables, in the Context Management Guide.

To configure the CrowdStrike Context Cloud Collector:

Note

Only one CrowdStrike Context Cloud Collector can be created per Exabeam subscription. So, if a CrowdStrike Context Cloud Collector already exists, you will not be able to create another one.

  1. Complete the prerequisites to configure the CrowdStrike Context Cloud Collector.

  2. Log in to the New-Scale Security Operations Platform with your registered credentials as an administrator.

  3. Navigate to Collectors > Cloud Collectors.

  4. Click New Collector.

  5. Click CrowdStrike Context.

    Crowdstrike_Context_3.png

  6. Enter the following information for the cloud collector:

    • NAME – Specify a name for the CrowdStrike Context Cloud Collector.

    • CLIENT ID – Enter the Client ID that you obtained while completing the prerequisites.

    • CLIENT SECRET – Enter the Client Secret that you obtained while completing the prerequisites.

    • CLOUD ENDPOINT – For Cloud Endpoint, enter the API gateway URL. For example: https://api.crowdstrike.com or https://api.us-2.crowdstrike.com.

    • DATA SOURCES – Select a data source for the collector. The available option is Devices for the CrowdStrike Context Cloud Collector.

  7. (Optional) SITE – Select an existing site or to create a new site with a unique ID, click manage your sites. Adding a site name helps you to ensure efficient management of environments with overlapping IP addresses.

    By entering a site name, you associate the logs with a specific independent site. A sitename metadata field is automatically added to all the events that are going to be ingested via this collector. For more information about Site Management, see Define a Unique Site Name.

  8. (Optional) TIMEZONE – Select a time zone applicable to you for accurate detections and event monitoring.

    By entering a time zone, you override the default log time zone. A timezone metadata field is automatically added to all events ingested through this collector.

    Timezone_sitename_site_management_1.png

  9. To confirm that the New-Scale Security Operations Platform communicates with the service, click Test Connection. 

  10. Click Install.

    AWS_S3_2.png

    A confirmation message informs you that the new collector is created.

  11. To create a corresponding CrowdStrike context table, navigate to the Context Management service in the New-Scale Security Operations Platform and create a CrowdStrike context table. For more information, see CrowdStrike Context Tables, in the Context Management Guide.

    Note

    The CrowdStrike cloud collector must be created before the corresponding context table. If you previously onboarded a CrowdStrike context table and you want to integrate with the this cloud collector for CrowdStrike data ingestion, you must delete the context table and recreate it after the cloud collector is created and running.