> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/a-c-integrations/corelight-open-ndr-via-collector-setup-for-workbench.md).

# Corelight Open NDR (via Collector) Setup for Workbench

## Prerequisites

* You must have a [Splunk Collector](/connect-your-technology/q-z-integrations/splunk/splunk-collector-setup-for-workbench.md) available as a Security Device in Expel Workbench before onboarding Corelight.
* Also ensure you have your **Collector query string**, as you will need to enter it in Workbench. If you don't have it yet, please [contact Expel support](/support/how-to-reach-us.md) to request it.

## Add Corelight as a Security Device in Workbench

Please ensure you have met the [prerequisites](#prerequisites) before proceeding with this step.

1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. In the search box, type “Corelight” and then select the **Corelight (via Collector)** integration.
5. A configuration pane displays. Complete the fields as follows:
   * **SIEM** - select **Splunk Collector** from the dropdown.
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Corelight”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
   * **Location** - enter the location of your integration, for example “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
   * **Collector query** - enter the query string provided by Expel Support.
6. Select **Save**.

Your device should be created successfully within a few seconds. A few reminders:

* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).

## Troubleshooting

Please ensure you have onboarded and selected the correct Splunk integration for the **SIEM** field in Step 1.5. It should be the one that reads "Splunk Collector."

<div align="left"><figure><img src="/files/Yk5F7ZoOOLjuzkWcHmjg" alt="" width="375"><figcaption></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.expel.io/connect-your-technology/a-c-integrations/corelight-open-ndr-via-collector-setup-for-workbench.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.