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

# Tenable: Remove Sprinto Access

Remove the access Sprinto was given in Tenable. Covers every way Sprinto can be connected to Tenable and the steps to take in Tenable for each.

Use this guide to remove the access you gave Sprinto in Tenable. These steps are done in Tenable, not in Sprinto. To connect Tenable to Sprinto again later, see [Tenable VM Integration](https://docs.sprinto.com/integrations/overview/tenable-vm-integration.md).

## Which connection method did you use?

Sprinto can be connected to Tenable in 2 ways. Find the method you used, then follow the steps in that section.

| Connection method                                                         | How to tell                                                                                                                           |
| ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| [Access review connection (API keys)](#access-review-connection-api-keys) | Connected from Sprinto's access review integrations (Tenable user list) by entering an access key and secret key in a sign-in window. |
| [Vulnerability connection (API keys)](#vulnerability-connection-api-keys) | Connected from the Tenable VM tile under vulnerability scanners in Sprinto by pasting an API key and secret key.                      |

***

## Access review connection (API keys) <a href="#access-review-connection-api-keys" id="access-review-connection-api-keys"></a>

**Who must do this:** Tenable Vulnerability Management Administrator (or the key owner for their own keys)

**What gets removed:** The Tenable access and secret key pair used to read Tenable users and groups, or the API-only user that owned it.

### Steps

1. If you created a dedicated API user just for Sprinto: as an Administrator go to **Settings** → **Access Control** → **Users**, open that user's row menu and disable the user, then click **Disable** to confirm (Tenable requires this before deleting).
2. In the same row menu click **Delete**, choose who receives the user's objects in Select **New Object Owner**, click **Delete**, then click **Delete** again to confirm.
3. If the keys belong to a regular user you keep: that user clicks the profile icon → **My Account** → **API Keys** → **Generate**, then **Continue**. Tenable has no delete for this key; resetting permanently invalidates the key Sprinto holds.
4. If that user has left or can't sign in: an Administrator opens **Settings** → **Access Control** → **Users**, clicks the user's name, and in the **API Keys** section clicks Generate API Keys → **Replace & Generate**.
5. Optional: delete any saved copies of the old access and secret keys, and don't store the new keys unless you need them.

### Confirm it's removed

The dedicated user no longer appears under Users, or the user's API keys were regenerated so the old pair is unauthorized.

{% hint style="warning" %}
Tenable allows one key pair per user. Regenerating breaks every other app using that user's keys, including the Sprinto Tenable vulnerability connection if it used the same keys. User deletion can't be undone.
{% endhint %}

**Official guide:** [Tenable docs](https://docs.tenable.com/vulnerability-management/Content/Settings/access-control/manage-users.htm)

***

## Vulnerability connection (API keys) <a href="#vulnerability-connection-api-keys" id="vulnerability-connection-api-keys"></a>

**Who must do this:** Tenable Vulnerability Management Administrator (or the key owner for their own keys)

**What gets removed:** The Tenable access and secret key pair Sprinto used, or the API-only user that owned it.

### Steps

1. If you created a dedicated API user just for Sprinto: as an Administrator go to **Settings** → **Access Control** → **Users**, open that user's row menu and disable the user, then click **Disable** to confirm (Tenable requires this before deleting).
2. In the same row menu click **Delete**, choose who receives the user's objects in Select **New Object Owner**, click **Delete**, then click **Delete** again to confirm.
3. If the keys belong to a regular user you keep: that user clicks the profile icon → **My Account** → **API Keys** → **Generate**, then **Continue**. Tenable has no delete for this key; resetting permanently invalidates the key Sprinto holds.
4. If that user has left or can't sign in: an Administrator opens **Settings** → **Access Control** → **Users**, clicks the user's name, and in the **API Keys** section clicks Generate API Keys → **Replace & Generate**.
5. Optional: delete any saved copies of the old access and secret keys, and don't store the new keys unless you need them.

### Confirm it's removed

The dedicated user no longer appears under Users, or the user's API keys were regenerated so the old pair is unauthorized.

{% hint style="warning" %}
Tenable allows one key pair per user. Regenerating breaks every other app using that user's keys, including a Sprinto Tenable access review connection if it used the same keys. User deletion can't be undone.
{% endhint %}

**Official guide:** [Tenable docs](https://docs.tenable.com/vulnerability-management/Content/Settings/access-control/manage-users.htm)


---

# 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.sprinto.com/integrations/remove-integration-access/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.
