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

# Cisco Umbrella Setup for Workbench

## Step 1: Enable Console Access <a href="#uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26950" id="uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26950"></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).

1. Navigate to **Admin > Accounts** and click **Add**.
2. Add a user with email address "soc+\<Your\_Organization\_Name>@expel.io".
   * For example, if your organization were Acme Corp, the format would be "<soc+acme_corp@expel.io>".
3. Select **Read Only User Role** for the account.
4. Click **Send Invitation**. Expel completes account registration after the registration email is received.

## Step 2: Generate API Credentials <a href="#uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26956" id="uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26956"></a>

1. Use your admin account to create an API Key. This can be found under **Admin > API Keys**.
2. At the prompt, configure the settings as follows:
   * **API Key Name** - set to your organization's preference or something like "Reports Key".
   * **Key Scope** - select the following depending on the type of tenant you have:
     * **Reports > Read-All**: select this, as it is required.
     * **Admin > Customers**: select only if you have a Multi-Organization Umbrella console.
   * **Expiry Date** - set to **Never expire**.&#x20;
3. Copy both the **Key** and the **Secret** provided. Use these to configure your technology in Workbench in the next step.

## Step 3: Add Cisco Umbrella as a Security Device in Workbench <a href="#uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26962" id="uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26962"></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 “Umbrella” and then select the **Cisco Umbrella** integration.
5. Configure these details:

   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Cisco Umbrella”; 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.
   * **Authorization key** - enter the key you received in [Step 2](#uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26950).
   * **Authorization secret**- enter the secret you received in [Step 2](#uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26956).
   * **Organization ID** - enter your [Umbrella organization ID](https://securitydocs.cisco.com/docs/umbrella-dns/gov/olh/154311.dita).

   <div align="left"><figure><img src="/files/gR2ojQ69yX4HGmp43Use" alt="Cisco Umbrella Add a Security Device screen in Workbench." width="333"><figcaption></figcaption></figure></div>
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](#uuid-e0402006-17f2-c4cb-a53f-f5e31cd52f5b_bridgehead-26950).
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/cisco/cisco-umbrella-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.
