Nessus - Add Agent to Agent Group
  • 01 Dec 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Nessus - Add Agent to Agent Group

  • Dark
    Light
  • PDF

Article summary

Nessus - Add Agent to Agent Group adds an agent to an existing agent group in Tenable Nessus 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.

Note:

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 Nessus 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.io adapter connection.
  • Agent group name - The name of the group to which to add the agent.
  • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius 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.

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

APIs

Axonius uses the pyTenable 1.4.22 documentation API.

Required Ports

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

  • 80
  • 443

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have permission to perform this Enforcement Action.

Version Matrix

This Enforcement Action was tested only 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.

VersionSupportedNotes
Tennable Nessus v5.9 ProYes

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


Was this article helpful?