> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/tenable.md).

# Tenable

Integration with Tenable Vulnerability Management for asset inventory, vulnerability analysis and exports, scan launches, and finding-change polling.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication   |
| --------- | ---------------- |
| Tenable   | API key or token |

### Tenable

Connect to Tenable Vulnerability Management to inventory assets, review and export vulnerability findings, and launch existing scans.

#### Set up in Tenable

1. Prepare the Tenable account or service that the workflow will access. Grant access to the required resources and operations.
2. **Access Key:** The access key generated for your Tenable user. Generate the access key and secret key together; creating a new pair invalidates the previous pair.
3. **Secret Key:** The secret key generated with this access key. Tenable does not refresh these keys, so generate a new pair and reconnect if either value is lost or rotated.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Tenable**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                                           |
| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Access Key    | Yes      | The access key generated for your Tenable user. Generate the access key and secret key together; creating a new pair invalidates the previous pair. [Provider instructions](https://developer.tenable.com/docs/authorization).          |
| Secret Key    | Yes      | The secret key generated with this access key. Tenable does not refresh these keys, so generate a new pair and reconnect if either value is lost or rotated. [Provider instructions](https://developer.tenable.com/docs/authorization). |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Tenable** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### List assets

List scanned assets for coverage, exposure, and stale-asset analysis.

#### Inputs

| Field          | Type    | Required | Description                                                                         |
| -------------- | ------- | -------- | ----------------------------------------------------------------------------------- |
| Maximum assets | integer | No       | Maximum number of asset records to return. Minimum: 1. Maximum: 5000. Default: 100. |

#### Outputs

| Field     | Type          | Description                                    |
| --------- | ------------- | ---------------------------------------------- |
| Assets    | object\_array | Structured Tenable asset records.              |
| Total     | integer       | Total asset records reported by Tenable.       |
| Truncated | boolean       | Whether additional asset records were omitted. |

### List workbench assets

Find asset IDs accepted by Tenable's per-asset vulnerability workbench.

#### Inputs

| Field           | Type    | Required | Description                                                                            |
| --------------- | ------- | -------- | -------------------------------------------------------------------------------------- |
| Days to include | integer | No       | Number of days through today to consider. Minimum: 1. Default: 30.                     |
| Maximum assets  | integer | No       | Maximum number of workbench assets to return. Minimum: 1. Maximum: 5000. Default: 100. |

#### Outputs

| Field     | Type          | Description                                       |
| --------- | ------------- | ------------------------------------------------- |
| Assets    | object\_array | Structured Tenable workbench asset records.       |
| Total     | integer       | Total workbench assets reported by Tenable.       |
| Truncated | boolean       | Whether additional workbench assets were omitted. |

### List Vulnerabilities

List discovered vulnerabilities and rank the returned groups by VPR.

#### Inputs

| Field                   | Type    | Required | Description                                                                                |
| ----------------------- | ------- | -------- | ------------------------------------------------------------------------------------------ |
| Days to include         | integer | No       | Number of days through today to include. Minimum: 1. Maximum: 450. Default: 30.            |
| Minimum VPR             | number  | No       | Only return vulnerability groups at or above this VPR. Minimum: 0.1. Maximum: 10.0.        |
| Maximum vulnerabilities | integer | No       | Maximum number of vulnerability groups to return. Minimum: 1. Maximum: 5000. Default: 100. |

#### Outputs

| Field                 | Type          | Description                                                       |
| --------------------- | ------------- | ----------------------------------------------------------------- |
| Vulnerabilities       | object\_array | Structured vulnerability groups ordered by VPR.                   |
| Total vulnerabilities | integer       | Total vulnerabilities reported by Tenable before local filtering. |
| Results truncated     | boolean       | Whether filtering or the output limit omitted provider results.   |

### Get asset vulnerabilities

Get vulnerability groups for one asset and rank them by VPR.

#### Inputs

| Field                   | Type            | Required | Description                                                                                |
| ----------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------ |
| Asset                   | select (string) | Yes      | The Tenable workbench asset to investigate. Options load from the selected connection.     |
| Days to include         | integer         | No       | Number of days through today to include. Minimum: 1. Maximum: 450. Default: 30.            |
| Minimum VPR             | number          | No       | Only return vulnerability groups at or above this VPR. Minimum: 0.1. Maximum: 10.0.        |
| Maximum vulnerabilities | integer         | No       | Maximum number of vulnerability groups to return. Minimum: 1. Maximum: 5000. Default: 100. |

#### Outputs

| Field                 | Type          | Description                                            |
| --------------------- | ------------- | ------------------------------------------------------ |
| Vulnerabilities       | object\_array | Structured vulnerability groups for the asset.         |
| Total vulnerabilities | integer       | Total vulnerabilities Tenable reported for the asset.  |
| Results truncated     | boolean       | Whether filtering or the output limit omitted results. |

### Export Vulnerabilities

Bulk-export vulnerability findings for trend and exposure analysis.

#### Inputs

| Field                        | Type                      | Required | Description                                                                                                         |
| ---------------------------- | ------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
| Observed since               | datetime                  | No       | Only include findings observed, reopened, or fixed since this time.                                                 |
| Finding states               | multiple\_select (string) | No       | Finding states to include. Available values: Open, Reopened, Fixed. Default: \["OPEN", "REOPENED"].                 |
| Severities                   | multiple\_select (string) | No       | Severity levels to include; leave empty for all. Available values: Info, Low, Medium, High, Critical. Default: \[]. |
| Show advanced fields         | boolean                   | No       | Reveal VPR, payload, chunk-size, and wait controls. Default: false.                                                 |
| Minimum VPR                  | number                    | No       | Only export findings at or above this VPR. Minimum: 0.1. Maximum: 10.0.                                             |
| Include plugin output        | boolean                   | No       | Include detailed scanner plugin output in each finding. Default: false.                                             |
| Include unlicensed assets    | boolean                   | No       | Include findings from unlicensed assets. Default: false.                                                            |
| Include software attribution | boolean                   | No       | Include affected software-package details. Default: false.                                                          |
| Assets per chunk             | integer                   | No       | Number of assets Tenable should group into each export chunk. Minimum: 50. Maximum: 5000. Default: 50.              |
| Maximum findings             | integer                   | No       | Maximum number of finding records to return. Minimum: 1. Maximum: 5000. Default: 1000.                              |
| Wait timeout                 | integer                   | No       | Maximum time to wait for Tenable to finish the export. Minimum: 10. Maximum: 300. Default: 120.                     |

#### Outputs

| Field             | Type          | Description                                         |
| ----------------- | ------------- | --------------------------------------------------- |
| Findings          | object\_array | Structured exported vulnerability findings.         |
| Export ID         | string        | Tenable identifier for the export job.              |
| Export status     | string        | Final Tenable export status.                        |
| Results truncated | boolean       | Whether the finding limit omitted exported records. |
| Chunks downloaded | integer       | Number of export chunks downloaded.                 |

### List scans

List scans that the connected Tenable user can view and launch.

#### Inputs

| Field                 | Type    | Required | Description                                                  |
| --------------------- | ------- | -------- | ------------------------------------------------------------ |
| Launchable scans only | boolean | No       | Only return scans that can be launched. Default: true.       |
| Maximum scans         | integer | No       | Maximum number of scans to return. Minimum: 1. Default: 100. |

#### Outputs

| Field             | Type          | Description                             |
| ----------------- | ------------- | --------------------------------------- |
| Scans             | object\_array | Structured Tenable scan configurations. |
| Returned scans    | integer       | Number of scans returned.               |
| Results truncated | boolean       | Whether the output limit omitted scans. |

### Launch scan

Launch an existing Tenable vulnerability scan.

#### Inputs

| Field                | Type            | Required | Description                                                                     |
| -------------------- | --------------- | -------- | ------------------------------------------------------------------------------- |
| Scan                 | select (string) | Yes      | The existing Tenable scan to launch. Options load from the selected connection. |
| Show advanced fields | boolean         | No       | Reveal target override and rollover controls. Default: false.                   |
| Alternate targets    | string          | No       | Targets to scan instead of the scan's configured targets. Default: .            |
| Rollover scan        | boolean         | No       | Only scan targets missed after a previous timeout. Default: false.              |

#### Outputs

| Field       | Type   | Description                           |
| ----------- | ------ | ------------------------------------- |
| Scan run ID | string | Identifier for the launched scan run. |

## Triggers

A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger.

### Vulnerability changed

Poll every 15 minutes for newly observed, reopened, or fixed Tenable vulnerability findings.

Optionally limit the trigger to severity levels or a minimum VPR score.

#### Configuration

| Field       | Type   | Required | Description                                                               |
| ----------- | ------ | -------- | ------------------------------------------------------------------------- |
| Severities  | string | No       | Only fire for these severity levels; leave empty for all. Default: .      |
| Minimum VPR | number | No       | Only fire for findings at or above this VPR. Minimum: 0.1. Maximum: 10.0. |

#### Event inputs

| Field     | Type   | Required | Description                                            |
| --------- | ------ | -------- | ------------------------------------------------------ |
| Finding   | object | Yes      | The vulnerability finding whose state changed.         |
| Event key | string | Yes      | Stable key used to deduplicate the finding transition. |

#### Outputs

| Field     | Type   | Description                                            |
| --------- | ------ | ------------------------------------------------------ |
| Finding   | object | The vulnerability finding whose state changed.         |
| Event key | string | Stable key used to deduplicate the finding transition. |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/tenable.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
