> 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/more-features/expel-vulnerability-prioritization/tenable-vulnerability-management-setup-for-workbench.md).

# Tenable Vulnerability Management Setup for Workbench

The following topic describes how to configure an API connection between Workbench and the Tenable Vulnerability Management (VM) platform.

{% hint style="warning" %}
Expel only supports Tenable Vulnerability Management (cloud version, previously called Tenable.io). Tenable.sc (on-premises version) is not currently supported.
{% endhint %}

### Step 1: Get API Credentials from Tenable VM

1. Open Tenable.
2. From the menu in the upper left, select **Settings**.

<div align="left"><figure><img src="/files/vMTSSgYp9WO87vNtSNQw" alt="Image of the settings option in the main menu." width="208"><figcaption></figcaption></figure></div>

3. Select **Access Control**.
4. Select **Create User**.

<div align="left"><figure><img src="/files/aLj60JnUoKu5SPDall4B" alt="Image of the Users tab showing the Create User option." width="289"><figcaption></figcaption></figure></div>

5. Create an **Admin user**.

{% hint style="info" %}
**This user is for API access.** The user must belong to your domain, so reflect that in the username. For example, you can name the user `soc+admin@yourdomain.com` or `soc+api@yourdomain.com`.
{% endhint %}

<div align="left"><figure><img src="/files/OujfEue19jUjRtY9Dol7" alt="Image of the new user screen and its fields." width="532"><figcaption></figcaption></figure></div>

6. Log in with the account that was just created.
7. Create a **second Admin user** and provide the credentials to Expel (our support team will finish setting up the 2FA). This account should be using 2FA with either TOTP authentication or authentication via a SOC hotline.

{% hint style="info" %}
**This user is for for** [**console access**](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md)**.** The user must also belong to your domain, so reflect that in the username just as you did for the first Admin user. For example, you can name the user `soc+console@yourdomain`; if Tenable configured it, you can use the `@expel.io` domain.
{% endhint %}

8. From the menu in the upper left, select **Settings**.
9. Select **My Account**.
10. Select **API KEYS**.

<div align="left"><figure><img src="/files/lupQDma2yfjPBVAccEoH" alt="Image of the API Keys option in the menu." width="150"><figcaption></figcaption></figure></div>

11. Select **Generate**.
12. Copy the **Access Key** and the **Secret Key**. You will need them when you set up the security device in Workbench.

### Step 2: Add Tenable Vulnerability Management 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**. If you have multiple organizations, you must select the appropriate organization name from the list.
3. Select **Add Security Device**.
4. In the search box, enter “Tenable” and then select the Tenable Vulnerability Management integration.
5. Complete the fields as follows:
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Tenable”; 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.
   * **Access Key** - provide the key that was generated in Step 1.
   * **Secret** - provide the secret that was generated in Step 1.
6. Select **Save**.
7. Select **Set up later** from the console access dropdown (Expel will set up console access).
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).


---

# 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/more-features/expel-vulnerability-prioritization/tenable-vulnerability-management-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.
