Workbench Filters

In the Tenable Vulnerability Management user interface, "workbenches" are default dashboards that, unlike user-defined dashboards, cannot be customized. Workbenches provide you with an overview of actionable insights into assets and vulnerability management, which you can then use to prioritize vulnerabilities and manage assets and scan coverage in your organization's network. The workbenches API provides extended capabilities for retrieving asset and vulnerability data from the workbenches.

Use filter query parameters to refine the asset and vulnerability data that the workbenches API endpoints return.

For more information, see:

Filter Parameters

For each filter you want to apply to workbench data, you must specify the following query parameters:

filter..filterThe name of the filter to apply to the returned data.
filter..qualityThe operator of the filter to apply to the returned data.
filter..valueThe value of the filter to apply to the returned data.

To specify a single filter, use '0' as the value in each filter parameter name.

To specify multiple filters:

  1. Increment the portion of each filter parameter name. For example:
  1. (Optional) Include the filter.search_type query parameter. This parameter specifies whether to use the AND or the OR logical operator when matching data to the specified filters. If you omit the filter.search_type parameter, Vulnerability Management uses AND by default.



You cannot specify more than 10 filters or 50 filter values per filter. A 400 Bad Request error is returned if you exceed this limit.

Supported Filters

Commonly-used Filters

The table below lists parameters for commmonly-used filters for assets and vulnerabilities.

User Interface Labelfilter..filterfilter..qualityfilter..value
Asset Assessedasset_assessedeqtrue, false
Hostname/IP Addresshost.targeteq, neq, match, nmatchString
IPv4 Addressipv4eqString
Is Licensed (VM)is_licensedeqtrue, false
Severityseverityeq, neqNone, Low, Medium, High, Critical



If a POST /vulns/exports request contains a filter, Vulnerability Management parses the filter into asset identifiers, which it then matches to vulnerabilities. Vulnerability Management can support parsing the filter up to a maximum of 1,024 asset identifiers. If the filter parsing exceeds this limit, Vulnerability Management returns a 400 error response. To resolve this error state, refine the values specified for the filter to minimize returned results.

Example: Filter by Installed Software

Your organization might distribute remediation responsibility based on network segments or, commonly, based on the type of software installed on the network assets. For example, you might be responsible for patching only Apple vulnerabilities for your organization. You can use the API to retrieve a list of only those assets where a specific version of Apple Quicktime is installed.

In this case, your query parameters might include the following:


Example: Filter by Asset Assessed

Vulnerability Management can discover assets without scanning them for vulnerabilities. After discovery, you may want to identify these unassessed assets to target them for vulnerability scanning. For more information, see Manage Unassessed Assets.

In this case, your query parameters include the following: