Tenable Vulnerability Management - Delete Asset
Tenable Vulnerability Management - Delete Asset deletes assets from Tenable.io for:
- Assets returned by the selected query or assets selected on the relevant asset page.
Tenable Vulnerability Management assets are entities of value on a network, that can be exploited. This includes laptops, desktops, servers, routers, mobile phones, virtual machines, software containers, and cloud instances.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
Note:
- Not all asset types are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Set.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
- Use stored credentials from the Tenable Vulnerability Management Adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
-
When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
-
NOTE
To use this option, you must successfully configure a Tenable Vulnerability Management adapter connection.
-
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.
Additional Fields
These fields are optional.
- Hard delete - Select to completely remove the assets along with all related data. When not selected, only the assets are removed. Related data is kept.
-
Gateway Name - Select the Gateway through which to connect to perform the action.
Connection and CredentialsWhen Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.
Tenable Vulnerability Management domain - The IP address or hostname of your Tenable Vulnerability Management management server.
Access API key and Secret API key (required) - These values must be created in the Tenable Vulnerability Management console. To generate an API key in theTenable Vulnerability Management console, see Generate an API Key.
Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
APIs
Axonius uses the Tenable Bulk Delete Assets API. Use the POST /api/v2/assets/bulk-jobs/delete endpoint.
Required Ports
Axonius must be able to communicate to Tenable Vulnerability Management via the following ports:
- TCP port 80
Required Permissions
The Tenable Vulnerability Management user account must have the Scan Operator [24] user role.
Version Matrix
This Enforcement Action has only been tested with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.
| Version | Supported | Notes |
|---|---|---|
| Tenable Vulnerability Management v5.9 | Yes | |
| Tenable Vulnerability Management | No | API not supported |
For more details about other Enforcement Actions available, see Action Library.
Updated about 11 hours ago
