SIEMCrowdStrike Falcon NextGen SIEM

CrowdStrike Falcon NextGen SIEM

Configure CrowdStrike Falcon NextGen SIEM integration with RAD Security for unified threat intelligence.

This guide walks you through integrating CrowdStrike Falcon NextGen SIEM with RAD Security for unified security event management and threat intelligence, enabling bi-directional data flow between the platforms.

CrowdStrike Falcon NextGen SIEM provides advanced threat detection, investigation, and response capabilities with native threat intelligence integration.

Prerequisites

Before you begin, ensure you have:

  • Admin access to CrowdStrike Falcon Console
  • CrowdStrike NextGen SIEM subscription
  • Access to RAD Security workspace with integration permissions

Administrative Privileges Required: You must have administrative privileges in CrowdStrike Console to create API clients and configure data connections.


Understanding Integration Components

CrowdStrike NextGen SIEM integration supports two data flow directions:

Both Scopes Needed: The NGSIEM client requires both Read and Write scopes. Write is needed to create search queries, and Read is needed to retrieve the query results.


Step 1: Create OAuth Client

Log in to CrowdStrike Console

Log in to your CrowdStrike Falcon Console with administrative privileges

Navigate to API Clients

Open the main menu and go to:

Support and resources > Resources and tools > API clients and keys

Create New Client

Click the Create API client button

Configure Client Settings

In the modal dialog:

  1. Client name: Enter a descriptive name (e.g., "RAD Security SIEM Integration")
  2. Description: (Optional) Add details about this integration

Select API Scopes

Under NGSIEM section, select both:

  • ☑️ Read
  • ☑️ Write

Both scopes are required! Write scope is needed to create search queries, and Read scope is needed to read the query results. The integration will not function properly without both.

Create Client

Click the Create button

Copy Credentials

The modal will display your new credentials. Copy these immediately:

  • Client ID
  • Client Secret
  • Base URL

Save these values now! You will not be able to view the Client Secret again. Store them securely in a password manager or secrets vault.

Adjusting Scopes Later: If you need to modify scopes, click the three dots (⋮) to the right of the client listing on the API clients and keys page.


Step 2: Generate HEC Credentials (Optional)

This step is only necessary if you plan to ingest RAD Security events into CrowdStrike NextGen SIEM.

Skip this step if you only need to query CrowdStrike data. Configure this if you want to send RAD Security events to CrowdStrike.

Navigate to Data Connectors

Open the main menu and go to:

Data connectors > Data connections

Add New Connection

In the Connections section, click the + Add connection button

Filter for HTTP Connector

  1. Click the Filter by connector name dropdown
  2. Type "HTTP"
  3. Click Apply

Select HEC Connector

  1. Find HEC / HTTP Event Connector in the filtered list
  2. Click on it to select
  3. Click the Configure button

Configure Connector

Fill in the form with the following values:

FieldValue
Data sourceYour desired data source name (e.g., "RAD Security")
Data TypeJSON
Connector NameYour desired connector name (e.g., "RAD Security HEC")
Parsersjson (Generic Source)

The JSON parser is required to properly parse RAD Security events in CrowdStrike.

Accept Terms

Check the box to affirm your adherence to the CrowdStrike Terms and Conditions

Save Configuration

Click Save

Wait for Setup

  1. A modal will appear indicating the connector is being set up
  2. Close the modal
  3. Wait for the connector setup to finish
  4. You'll see a notification bar at the top when ready

Connector setup typically takes 1-2 minutes. Wait for the "ready to receive data" notification before proceeding.

Generate API Key

Once the connector is ready, click the Generate API Key button on the right side of the notification bar

Copy HEC Credentials

A modal will appear with your credentials. Copy these immediately:

  • API URL (HEC endpoint)
  • API Key (HEC credential)

Store these values securely. You'll need them for the integration configuration.


Step 3: Configure in RAD Security

Navigate to your RAD Security workspace and configure the CrowdStrike Falcon NextGen SIEM integration with the appropriate parameters:

Configuration Scenarios

Use Case: Pull CrowdStrike threat intelligence and events into RAD Security

ParameterDescriptionExample
URLBase URL from Step 1https://api.crowdstrike.com
ClientIdClient ID from Step 1abc123def456...
ClientSecretClient Secret from Step 1xyz789abc123...

This configuration allows querying CrowdStrike data but does not send RAD Security events to CrowdStrike.

Regional Base URLs

Your Base URL will vary by region. Common CrowdStrike regions:

RegionBase URL
US-1https://api.crowdstrike.com
US-2https://api.us-2.crowdstrike.com
EU-1https://api.eu-1.crowdstrike.com
US-GOV-1https://api.laggar.gcw.crowdstrike.com

Verify Integration

After completing the setup, verify your integration is working:

Verify Query Capability

  1. Run a test query from RAD Security
  2. Verify CrowdStrike threat data appears correctly
  3. Check that results are properly formatted

Verify Data Ingestion

  1. Trigger a test event in RAD Security
  2. Search for the event in CrowdStrike NextGen SIEM
  3. Verify the event appears with correct JSON formatting

Your CrowdStrike Falcon NextGen SIEM integration is now configured! RAD Security can query CrowdStrike threat intelligence and/or send events based on your configuration.

What Data is Synced

Use Cases

Unified Threat Intelligence Correlate CrowdStrike's threat intelligence with RAD Security's runtime insights for comprehensive threat detection.

Cross-Platform Detection Detect threats that span endpoints and containerized infrastructure using unified data sources.

Enhanced Investigation Leverage CrowdStrike's investigation tools with RAD Security's container runtime context.

Centralized SIEM Use CrowdStrike as a central SIEM for all security events including container and cloud workloads.

Troubleshooting

Security Best Practices

Rotate Credentials Regularly Periodically rotate OAuth client secrets and HEC API keys as part of security hygiene.

Least Privilege Scopes Only grant the NGSIEM scopes. Avoid adding unnecessary additional scopes to the client.

Secure Credential Storage Store Client Secrets and API Keys in a secure password manager or secrets vault.

Monitor API Usage Regularly review API client activity in CrowdStrike to detect anomalous behavior.

Dedicated Connectors Create separate HEC connectors for different data sources to simplify management and troubleshooting.

Audit Client Access Periodically review OAuth clients and ensure unused clients are removed.

Additional Resources

Next Steps