> 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/d-j-integrations/exabeam/exabeam-threat-center-setup-for-workbench.md).

# Exabeam Threat Center Setup for Workbench

## Prerequisites

* You must have admin access in Workbench to set up this integration.
* To create and manage users and API keys in Exabeam, you must be an administrator with full access to your Exabeam subscription.

## Step 1: Create Exabeam API Credentials for Expel

1. Log in to the Exabeam Security Operations Platform and in the left navigation, select **Settings > Developer > API Keys**.
2. Do one of the following depending on whether there are existing API keys:
   * If there are no existing API keys, in the center of the page, select **New API Keys**.
   * If there are existing API keys, select **New Keys**.<br>

     <div align="left"><figure><img src="/files/9d8y9JyooBq4s1Kz4kBS" alt="+ New Keys button above the API key list." width="375"><figcaption></figcaption></figure></div>
3. Configure your new API key:
   * **Key Name** - enter "Expel Key".
   * **Permissions** - select **Threat Center.**<br>

     <div align="left"><figure><img src="/files/hl8ulNq66YFlPtH2pTqt" alt="A New API Key is named Expel Key and has the Threat Center permission assigned." width="375"><figcaption></figcaption></figure></div>
4. Select **Create**. A confirmation message appears noting your key was created successfully.&#x20;
5. **Copy and save the Key ID and Key Secret in a safe place**, as you will need them to complete a later section.<br>

   <div align="left"><figure><img src="/files/RHipe6jOQtLn0nFhy3d2" alt="Message reads Expel Key created successfully! Copy the KEY IS and KEY Secret into your secrets manager or your preferred workflow. The Key ID and Key Secret are provided below." width="375"><figcaption></figcaption></figure></div>
6. Select **Ok, great!**. The API Keys list displays again, now including your new API key.

## Step 2: Create an Exabeam User for Console Access

Expel requires console access to allow analysts to perform investigation and triage. Without this additional level of information, alerts cannot be verified by our analysts and an investigation cannot be initiated. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).

1. In the Exabeam Security Operations Platform left navigation, select **Settings > Teams > Users**.
2. Select **New User**.
3. On the Invite User screen, configure the fields 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>".
4. **Roles** - select **Tier 3 Analyst** and **Tier 3 Analyst (Advanced Analytics)**.<br>

   <div align="left"><figure><img src="/files/u8kWETGrngSER0VpMcMY" alt="Invite User page indicates that the &#x22;Invitiation will be sent to the provided email address&#x22; and asks you to input Names, Email, and Roles." width="375"><figcaption></figcaption></figure></div>
5. Select **Invite**. Expel will receive the account activation email and set a new password.

## Step 3: Add Exabeam Threat Center as a Security Device in Workbench

Now that you have the necessary credentials, you can configure the integration 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 “Exabeam” and then select the **Exabeam Threat Center** integration.<br>

   <div align="left"><figure><img src="/files/r7uI7mTYrNe0wZEhJ9be" alt="Exabeam Threat Center security device setup in Workbench." width="329"><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 Exabeam Threat Center”; 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.
   * **Exabeam API base URL** - select the base URL for your deployment region. [Learn more about selecting the appropriate base URL](https://developers.exabeam.com/exabeam/docs/exabeam-api-base-urls).
   * **API key ID** - enter the API Key ID you generated in [Step 1](#step-1-create-exabeam-api-credentials-for-expel).
   * **API key secret** - enter the API Key Secret you generated in [Step 1](#step-1-create-exabeam-api-credentials-for-expel).
6. Select **Save**.
7. On the console access screen, select **Set up later** from the dropdown, as Expel will complete console access configuration.
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 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).

## Reference

### Exabeam API Routes Expel Uses

| Route                                | Permission                      |
| ------------------------------------ | ------------------------------- |
| /regional\_base\_ur/auth/v1/token    | <p>Administrator</p><p><br></p> |
| /regional\_base\_ur/v1/search/alerts | <p>Administrator</p><p><br></p> |
| /regional\_base\_ur/v1/search/cases  | <p>Administrator</p><p><br></p> |
| /regional\_base\_ur/audit/v1/events  | <p>Administrator</p><p><br></p> |


---

# 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/d-j-integrations/exabeam/exabeam-threat-center-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.