Configuring CrowdStrike (Hosts Only) Connectors (4.3.0 - 4.3.4)

This version of Stellar Cyber's CrowdStrike connector uses API calls to collect Host data and perform response actions (and contain or hide hosts). If you also want to collect Detection Summary Events, you may use the instructions in the topic for CrowdStrike's Falcon SIEM Connector.

Use the table below to determine which configuration options to use for your deployment, based on your Stellar Cyber software version.

CrowdStrike Data Type	Configuration Procedure	Purpose
Hosts	Stellar Cyber's CrowdStrike (Hosts Only) Connector (this topic) (Uses CrowdStrike's OAuth2 API)	For v.4.3.0-v4.3.4 Use this to ingest host data and enable manual or automated response actions; records are visible in Stellar Cyber Asset Index.
Incident Detections (Detection Summary Event Logs)	CrowdStrike's Falcon SIEM Connector (Uses CrowdStrike's streaming API)	For v.4.3.0-v4.3.4 Use this for mapping CrowdStrike incidents (after deduplication and enrichment) to Stellar Cyber's kill chain and alert index. Records are also visible in the SYSLOG index;
Hosts Detection Summary Events Audit and other events	Stellar Cyber's CrowdStrike Connector (Uses both CrowdStrike's OAuth2 API and their Streaming SIEM Connector API)	For v.4.3.5 and later Use this connector for ingestion and response actions on a variety of data and map CrowdStrike detection summary events to Alerts.

This connector uses CrowdStrike's Oauth2 API for collecting host/asset information to handle response actions only.

To add a CrowdStrike connector:

1. Generate the CrowdStrike Falcon API key
2. Add the connector in Stellar Cyber
3. Test the connector
4. Verify that assets are received from CrowdStrike

Generating the CrowdStrike Falcon API Key

With streaming APIs enabled, you can generate the CrowdStrike Falcon API key:

Use our example as a guideline, as you might be using a different software version.

1. Log in to CrowdStrike Falcon at https://falcon.crowdstrike.com/ .

2. Click API Clients and Keys.

   

   The API Clients and Keys page appears.

3. Click Add new API client.

   

   The Add new API client window appears.

4. Enter the Client Name.

5. Enable Read and Write for Hosts to contain or hide hosts.

   

6. Click Add. The API client created window appears.

   

7. Copy the Client ID and Secret. You will need these later.

Adding the Connector in Stellar Cyber

With the configuration information handy, you can add the CrowdStrike connector in Stellar Cyber:

1. Log in to Stellar Cyber.

2. Click System | Integration | Connectors. The Connector Overview appears.

   

3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

   

4. Choose Endpoint Security from the Category drop-down.

5. Choose CrowdStrike from the Type drop-down.

6. Choose the Function. If you want to collect logs, click the Collect check-box. If you want to contain or hide hosts, click the Respond check-box.

7. Enter a Name. This field is required, and does not accept multibyte characters.

8. Choose a Tenant Name. The Interflow records created by this connector include this tenant name.

9. Choose the device on which to run the connector.

   • Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.

   • If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.

10. Click Next. The Configuration tab appears.

    

11. Enter the Base URL. This is the URL of your CrowdStrike portal, and can be:

    • US: api.crowdstrike.com

    • US-GOV-1: api.laggar.gcw.crowdstrike.com

    • EU-1: api.eu-1.crowdstrike.com

    • US-2: api.us-2.crowdstrike.com

    For release versions prior to v4.3.4, ensure the URL does not include a trailing "/" symbol.

12. Enter the Client ID you copied earlier.

13. Enter the Client Secret you copied earlier.

14. Enter the Interval (min) if you chose Collect. This is how often the logs are collected.

15. Choose the Content Type you would like to collect. The logs for Host are supported.

    This connector uses CrowdStrike's Oauth2 API for collecting host/asset information to handle response actions only. Stellar Cyber intentionally disabled the ability to use that API for CrowdStrike incident detections because CrowdStrike's Falcon SIEM connector leverages a streaming API that includes specific content not available in their OAuth2 API.

16. Click Next. The final confirmation tab appears.

    

17. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

18. If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.

    • This prompt only occurs during the initial create connector process when Collect is enabled.

    • Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.

    • The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.

    The Connector Overview appears.

The new connector is immediately active. You can now contain or hide hosts from the event display, and view or edit those actions on the Endpoint Actions page.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

1. Click System | Integrations | Connectors. The Connector Overview appears.

   

2. Locate the connector that you added, or modified, or that you want to test.

3. Click Test at the right side of that row. The test runs immediately.

   Note that you may run only one test at a time.

Display sample messages...

Success !

Failure with summary of issue: Show More example detail:

 

Verifying Received Assets

To verify Stellar Cyber is receiving assets from CrowdStrike:

1. Click Investigate | Asset Analytics.

2. Click the MAC-Identified Assets tab.

3. Enter crowdstrike in the Search field. The results list is updated.