Tenable Vulnerability Management - Create Exclusion

Tenable Vulnerability Management - Create Exclusion creates an exclusion in Tenable Vulnerability Management for:

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

📘

Note

Required Fields

These fields must be configured to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - 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.

  • Exclusion Name - The name of the exclusion to create in Tenable Vulnerability Management.

  • 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.

💡

Connection and Credentials

When 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 server.

  • Access API key and Secret API key - These values must be created in the Tenable Vulnerability Management console. To generate an API key, see Generate API Keys.

  • Verify SSL (Optional) (default: enabled) - Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings. This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting.)

  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

  • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

  • Gateway Name - Select the Gateway through which to connect to perform the action.

  • Description - An optional description for the exclusion.
  • Use public IP addresses - Include public IP addresses from Axonius assets in the exclusion members list.
  • Use private IP addresses - Include private IP addresses from Axonius assets in the exclusion members list.
  • Add Hostnames - Include hostnames from Axonius assets in the exclusion members list.
  • Exclude IPv6 addresses - When enabled, excludes IPv6 addresses and only includes IPv4 addresses.
  • CIDRs exclude list - A comma-separated list of CIDR blocks to exclude from the exclusion members list.

APIs

Axonius uses the Tenable Vulnerability Management API - POST /exclusions

Required Ports

Axonius must be able to communicate via the following ports:

  • TCP port 443

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

The following permissions and requirements are needed:

  • A Tenable Vulnerability Management account with a minimum of Basic User [16] permission level.
  • Scan Manager [40] or Administrator [64] permission level is recommended.

For more details about other enforcement actions available, see Action Library.


Did this page help you?