Set up a Tenable Vulnerability Management connector
ConductorOne provides identity governance and just-in-time provisioning for Tenable VM. Integrate your Tenable VM instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.
The Tenable VM connector supports automatic account provisioning and deprovisioning.When a new account is created by ConductorOne, the account’s password will be sent to a vault.When deprovisioning an account, the Tenable connector disables the account, it is not deleted outright. Visit the Tenable documentation on deleting user accounts for more information.The connector also offers the option to opt into enabling existing disabled accounts if new app access is requested and approved.
In the Tenable VM UI, navigate to My Account and click API Keys.
2
Click Generate.
3
The new key is created, and its credentials are shown in the Custom API Keys section of the page. Carefully copy and save the access key and secret key.
That’s it! Next, move on to the connector configuration instructions.
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Tenable VM credentials generated by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
1
In ConductorOne, navigate to Admin > Connectors and click Add connector.
2
Search for Tenable VM and click Add.
3
Choose how to set up the new Tenable VM connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Paste your access key and secret key into the relevant fields.
8
Optional. Click the checkbox if you want to opt into enabling existing disabled accounts if new app access is requested and approved.
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Tenable VM connector is now pulling access data into ConductorOne.
Follow these instructions to use the Tenable VM connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
In ConductorOne, navigate to Connectors > Add connector.
2
Search for Baton and click Add.
3
Choose how to set up the new Tenable VM connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
In the Settings area of the page, click Edit.
7
Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.
# baton-tenable-vm-secrets.yamlapiVersion: v1kind: Secretmetadata: name: baton-tenable-vm-secretstype: OpaquestringData: # ConductorOne credentials BATON_CLIENT_ID: <ConductorOne client ID> BATON_CLIENT_SECRET: <ConductorOne client secret> # Tenable VM credentials BATON_ACCESS_KEY: <Tenable VM access key> BATON_SECRET_KEY: <Tenable VM secret key> # Optional: include if you want ConductorOne to provision access using this connector BATON_PROVISIONING: true # Optional: include if you want to opt into enabling existing disabled accounts if new app access is requested and approved BATON_ENABLE_ON_PROVISION: true
See the connector’s README or run --help to see all available configuration flags and environment variables.
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
2
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Tenable VM connector to. Tenable VM data should be found on the Entitlements and Accounts tabs.
That’s it! Your Tenable VM connector is now pulling access data into ConductorOne.
