> 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/broadcom/broadcom-carbon-black-edr-formerly-cb-response-setup-for-workbench.md).

# Broadcom Carbon Black EDR (formerly CB Response) Setup for Workbench

## Step 1: Enable Console Access <a href="#h_01hye97pgv6zq5yaggma7qamax" id="h_01hye97pgv6zq5yaggma7qamax"></a>

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).

### Create an Admin Account <a href="#h_01hye97pgv5xz6peexrqyxb4bt" id="h_01hye97pgv5xz6peexrqyxb4bt"></a>

1. Navigate to the **Users** icon on the left and click **+Add User**.
   * **Username** - enter "expel".
   * **First Name** - enter "Expel".
   * **Last Name** - enter "User."
   * **Email Address** - type "<soc@expel.io>".
   * Enter a **Password**.
   * Assign to - **Administrators**.
   * Select **Global administrator**. Global administrator is required to perform the necessary functions within Carbon Black EDR for pulling process listings, and so on.
2. Click **Save changes**.

### Verify Carbon Black Live EDR is Enabled <a href="#h_01hye97pgv96d1nv3djy92awm3" id="h_01hye97pgv96d1nv3djy92awm3"></a>

This step allows Expel to interact with your endpoints, for example, pull process listings, and so on.

1. Click on the **Sensors** icon on the left side panel and click any host name.
2. In the upper right corner, the button **Go Live** is active if Carbon Black Live EDR is enabled. If it's **active**, this step is complete.\
   \
   If Carbon Black Live EDR is **not enabled** and is hosted **on-prem**:

   * SSH into the CB appliance and perform the command `vi /etc/cb/cb.conf`.
   * Search for `CbLREnabled=False` and change the value from False to True.
   * Restart services for the change to take effect: `service cb-enterprise restart`.<br>

   If Carbon Black Live EDR is **not enabled** and **cloud-hosted**:

   * Submit a request to the Carbon Black Cloud Support team requesting this feature be enabled. You can simply send the request with the following: “Please enable Live EDR and VDI Behavior”.

## Step 2: Generate API Credentials <a href="#h_01hye97pgvv409zbm65b25yfjg" id="h_01hye97pgvv409zbm65b25yfjg"></a>

To integrate the technology with Workbench, you need to create secure credentials to the API.

This step creates an authentication token that allows the Expel Assembler to access the Carbon Black EDR API.

1. Log out of the Carbon Black EDR Console.
2. Log back into the Carbon Black EDR Console as the newly created Expel User.
3. Click **Expel User** on the upper right, then **My Profile**, then **API Token**.
4. Save the **API token** value in a safe place for use in a later step.

## Step 3: Enable Threat Feeds <a href="#h_01hye97pgv3th700e28e4m9025" id="h_01hye97pgv3th700e28e4m9025"></a>

Expel recommends enabling the following Carbon Black threat feeds at a minimum:

* \+ CB Advanced Threat
* \+ CB Community
* \+ CB Suspicious Feed
* \+ CB Tamper Detection
* \+ CB Early Access
* \+ SANS Feed
* \+ Expel (this feed is added and enabled by Expel)

1. Navigate to the Threat Intelligence icon.
2. Select **Enable** and the **Create Alert options** for each of the feeds.

## Step 4: Add Broadcom Carbon Black EDR as a Security Device in Workbench <a href="#h_01hye97pgvc5a5fj82beavhv8g" id="h_01hye97pgvc5a5fj82beavhv8g"></a>

Now that you have the correct access configured and noted the credentials, you can integrate your tech with 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 “Carbon Black” and then select the **Broadcom Carbon Black EDR (formerly CB Response)** integration.
5. Enter the following information:
   * Select **Cloud** or **On-Prem** (on premises) installation.
     * For On-Prem installations only, select an Assembler from the list. Select the assembler you set up in [Add a New Assembler](/connect-your-technology/expel-assembler/add-a-new-assembler.md).
   * **Name** - type the hostname of the Carbon Black EDR device.
   * **Location**- type the geographic location of the appliance.
   * **Server address** - type the Carbon Black EDR device IP or hostname in the following format: `https://10.0.0.10 or https://mycbraddress.com`
   * **API key** - type the API generated in [Step 2](#h_01hye97pgvv409zbm65b25yfjg).
6. Click **Save**.
7. On the console access screen, select **Set up later**. Expel will complete configuration with the user you created in [Step 1](#h_01hye97pgv6zq5yaggma7qamax).
8. Click **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).


---

# 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/broadcom/broadcom-carbon-black-edr-formerly-cb-response-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.