Nessus - Add IPs to Scan

Article summary

Did you find this summary helpful?

Thank you for your feedback

Nessus - Add IPs to Scan adds the IP addresses to an existing Nessus scan for:

Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.

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

General Settings

Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
Add description - Add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories 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.
Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
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 Nessus adapter - Select this option to use the the first connected Nessus adapter credentials.
NOTE
To use this option, you must successfully configure a Tenable.io adapter connection.

These fields must be configured to run the Enforcement Set.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

These fields are optional.

Use public IP addresses - Select to add public IP addresses. This option is useful when needing to scan IP addresses from cloud providers, like AWS.
Use private IP addresses - Select to only add private IP addresses.
Use hostnames - Hostnames from query results will be sent to scan in Nessus.
Exclude IPv6 addresses - When enabled, Axonius will add only IPv4 addresses. Otherwise, both IPv4 and IPv6 addresses will be added.
Scan ID - Scan ID created on Nessus.
Source Adapter - Specify an adapter name as it appears in Axonius to send specific adapter IP data. For example, for the Tenable Nessus adapter, enter nessus_adapter. When specified, the Enforcement Action will send adapter IP data only from the specific adapter listed. Otherwise, IP data from all adapters is sent. To find the adapter name, click to go to the Adapters page, view the page for the relevant adapter and in the page URL will be the adapter name in the format <adaptername>-adapter.

If Use stored credentials from the Tenable Nessus Adapter is disabled, these fields are required:

Host Address - The address of the Nessus host.
Port - The port to use to connect to the Nessus host.
User Name and Password - The credentials for a user account that has the required permissions to add IP addresses.
Access API key and Secret API key - These values must be created in the Tenable.io console. To generate an API key in the Tenable.io console, see Generate an API Key (Tenable Nessus 10.7).
Verify SSL - 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.

Axonius uses the pyTenable 1.4.22 API.

Axonius must be able to communicate with the values supplied in Connection Parameters via the following ports:

The values supplied in Connection Parameters above must have permission to write. See Tenable Permissions for more information.

For more details about other Enforcement Actions available, see Action Library.

Was this article helpful?

Table of contents