> 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/cribl-setup-for-workbench.md).

# Cribl Setup for Workbench

## Prerequisites

1. You must have admin access in Workbench to set up this integration.
2. You must have Admin permissions in Cribl to allow you to manage API credentials and invite Organization Members.

## Step 1: Create an Expel User for Console Access

Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).

1. Log in to [Cribl](https://manage.cribl.cloud/).
2. In the top navigation, select **Products > Organization**.
3. In the left navigation (expand it if needed), select **Members**.
4. Select **Invite Member**.
5. Configure the new user as follows:
   * **First name** - enter "Expel".
   * **Last name** - enter "SOC".
   * **Email** - enter "soc+\<Your\_Organization\_Name>@expel.io".
     * For example, if your organization were Acme Corp, the format would be "<soc+acme_corp@expel.io>".&#x20;
   * **Organization Role** - select **Admin**.
6. Select **Send Invite**.
7. Notify your Customer Success Manager (CSM) or Expel Support that the new Cribl account is created and the invitation email was sent. Expel will create an account and complete console access configuration in Workbench on your behalf.

## Step 2: Generate API Credentials in Cribl

Next you will create API credentials to connect Cribl to Workbench.

{% hint style="info" %}
The Cribl Member who creates these API credentials appears in the audit logs as the creator of any searches executed through Workbench. If you'd prefer the audit logs indicate Expel as the creator of those searches, Expel can create those API credentials after you've sent the invitation to create our console access Member. Notify your CSM if that is the case, and we will complete the integration on your behalf.
{% endhint %}

1. Navigate to the **API Credentials** section in the side navigation.
2. Select **Add Credential**.
3. Configure the credentials as follows:
   * **Name** - enter "Expel key".
   * **Description (optional)** - enter "API credentials to provide Expel access via Workbench".
   * **Enabled** - ensure this is toggled **on**.
   * Organization Permissions - select **User**.
4. Select **Save**.
5. On the next screen, find your newly created credentials in the list. **Copy and save the Client ID and Secret values** in a safe place for use in the next step.<br>

   <div align="left"><figure><img src="/files/ddIywQQ6hRf43qYhCdVy" alt="Use the copy icons to copy and save both the Client ID and Secret." width="375"><figcaption></figcaption></figure></div>
6. Next, use the upper-left menu to select **Products > Search**.
7. To obtain the Server address, select everything in the URL to the left of "/search". The resulting URL should have a format similar to: `https://main-xxxxx-xxx-xxxxx.cribl.cloud`

## Step 3: Add Cribl as a Security Device in Workbench

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 “Cribl” and then select the **Cribl** integration.

   <div align="left"><figure><img src="/files/cFFV4Em9TQtCtrDVPdNX" alt="Cribl Add Security Device screen in Workbench." width="375"><figcaption></figcaption></figure></div>
5. A configuration pane displays. Complete the fields as follows:
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Cribl”; 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.
   * **Server address** - enter the server address you saved in [Step 2](#step-2-generate-api-credentials-in-cribl).
   * **Client ID** - enter the client ID you saved in [Step 2](#step-2-generate-api-credentials-in-cribl).
   * **Password** - enter the client secret you saved in [Step 2](#step-2-generate-api-credentials-in-cribl).
6. Select **Save**.
7. On the console access screen, select **Set up later**.
8. 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.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* If your device does not begin polling within 15 minutes, [contact our support team](/support/how-to-reach-us.md) for help. You must refresh the page to see updates.


---

# 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/cribl-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.
