> 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/cybereason-endpoint-detection-and-response-edr-setup-for-workbench.md).

# Cybereason Endpoint Detection and Response (EDR) Setup for Workbench

Cybereason REST APIs use an auth token to make authorized calls to the API. Expel uses Cybereason REST APIs to access resources through URI paths. You need to generate an API key and an Application key.

## Step 1: Generate User Credentials <a href="#uuid-9300ec52-3307-a489-18f9-6919f10c8b51_bridgehead-25991" id="uuid-9300ec52-3307-a489-18f9-6919f10c8b51_bridgehead-25991"></a>

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

1. In the Cybereason UI, navigate to the **User** screen.
2. Click **Create New User**. The Create New User screen appears.
3. Enter the required details:
   * **Username** - enter an email address. Make note of this for later use.
   * **Password** - enter a password. Make note of this for later use.
   * **Change password on next login** - do NOT select this.
   * **Enable Two Factor Authentication (TFA)** - do NOT select this.
   * **Custom roles** - select **Analyst** and **L3**.
   * **Predefined roles** - select **API User**.
4. Click **Add User**.

## Step 2: Add Cybereason EDR as a Security Device in Workbench <a href="#uuid-9300ec52-3307-a489-18f9-6919f10c8b51_bridgehead-idm4544991570753633057878795047" id="uuid-9300ec52-3307-a489-18f9-6919f10c8b51_bridgehead-idm4544991570753633057878795047"></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/).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. Search for and select **Cybereason EDR**.
5. Complete the fields as follows:

   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Cybereason EDR”; 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.
   * **Username** - enter the username created in [Step 1](#uuid-9300ec52-3307-a489-18f9-6919f10c8b51_bridgehead-25991).
   * **Password** - enter the password created in [Step 1](#uuid-9300ec52-3307-a489-18f9-6919f10c8b51_bridgehead-25991).
   * **Server URL** - enter the Cybereason device address.

   <div align="left"><figure><img src="/files/GNR8qk6c1qcD82hioXJs" alt="Cybereason EDR Add a Security Device page in Workbench." width="331"><figcaption></figcaption></figure></div>
6. Click **Save**.
7. On the console access screen, select **Set up now**. 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).
8. In the Console Login area, enter these details:

* **Console URL** - enter the console URL from the Server address in the Connection Settings area above. At the end of the URL, type **/login**.
* **Username** - enter the user name you created previously.
* **Password** - enter the password you created previously.
* **Two-factor secret key (32-character code)** - depending on how your organization enforces log-ins, this field may not apply to you. In these cases, you can leave it blank. This field is optional and if you have questions or concerns, reach out to your Customer Success Manager (CSM) or to support.

9. 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/cybereason-endpoint-detection-and-response-edr-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.
