Integration: Kaseya MDR and CrowdStrike

Kaseya MDR

NAVIGATION  At the partner level: Settings > Integrations > + New Integration > choose organization > Next > CrowdStrike

NAVIGATION  At the organization level: Organizations > Edit Organization (pencil icon) > + New Application > CrowdStrike

PERMISSIONS  Permission to manage integrations or organization applications in Kaseya MDR

CrowdStrike

NAVIGATION  Support > API Clients and Keys.

PERMISSIONS  CrowdStrike Falcon account with permissions to create OAuth 2.0 API clients

To generate the API credentials required for the integration, complete the following steps:

1. Sign in to the CrowdStrike Falcon console.

2. Navigate to Support > API Clients and Keys.

   

3. Click Add new API client.

   

4. Configure the API client:

   • Client Name (for example, Kaseya MDR)

   • Optional description

   • Any API client settings required by your CrowdStrike environment

     

5. Select Add.

6. The API client created form is displayed.Copy the Client ID, Client Secret, and Base URL and store them in a secure location.

   

IMPORTANT  CrowdStrike displays the Client Secret only once when it is created. If the secret is lost, a new API client or secret must be generated.

1. In Kaseya MDR, navigate to Settings > Integrations.

   

2. Click + New Integration.

   

3. Select the organization that will receive CrowdStrike telemetry and click Next.

   • To create a new organization and use it for the integration, click Create New Organization and use.

   

4. Under Endpoint Security, locate CrowdStrike and click Connect.

   

5. In the CrowdStrike Connection Wizard, enter:

   • API Base URL

   • Client ID

   • Client Secret

     

6. Click Next.

7. Complete the Organization Mapping step and save the integration.

When configured at the partner level, CrowdStrike appears in Settings > Integrations and displays the associated organization.

1. In Kaseya MDR, navigate to Organizations.

   

2. Click Edit Organization (pencil icon) for the organization you want to connect.

   

3. Click + New Application.

   

4. Under Endpoint Security, locate CrowdStrike and click Connect.

   

5. In the CrowdStrike Connection Wizard, enter:

   • API Base URL

   • Client ID

   • Client Secret

6. Click Next.

7. Complete the Organization Mapping step and save the integration.

When configured at the organization level, the CrowdStrike application appears under the organization's Applications tab.

During setup, follow the organization-mapping steps presented in the wizard.

Organization mapping determines:

• Which organizations receive CrowdStrike telemetry

• How endpoint activity is scoped for investigation and correlation

• Where alerts and activity appear in the SIEM experience

For an overview of how integrations are associated with organizations, see Connecting data sources and integrations.

After the integration is connected:

• The CrowdStrike tile should reflect an active or connected status.

• Endpoint‑related telemetry from CrowdStrike may become available for investigation, depending on configuration and available data.

• CrowdStrike activity may appear alongside other endpoint, network, or SaaS sources during investigations.

Alerts generated from ingested telemetry can be delivered to external systems such as PSAs, depending on your notification and PSA configuration. For more information, see Notifications, PSA, and external communications.

To disable the integration:

1. Navigate to the CrowdStrike integration.

   • If configured at the partner level, go to Settings > Integrations, locate CrowdStrike, and select View details.

   • If configured at the organization level, go to Organizations, select the organization, and open the Applications tab.

2. Select Disconnect Application.

3. Confirm the action.

   Results

   • CrowdStrike telemetry is no longer associated with organizations in Kaseya MDR.

   • Existing CrowdStrike Falcon deployments and configurations remain unchanged.

   • If CrowdStrike is configured at the partner level, disconnecting it affects all organizations mapped to that connection.

   • The integration can be reconnected later using the same workflow if needed.

If expected activity is not visible:

• Verify that the CrowdStrike tenant region entered in Kaseya MDR matches your Falcon environment.

• If credentials change or are regenerated, update the Client Secret in the Kaseya MDR integration settings.