Nessus - Delete Account
  • 22 Sep 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Nessus - Delete Account

  • Dark
    Light
  • PDF

Article summary

Nessus - Delete Account deletes a user account from an existing Tenable Nessus group for users that match the parameters 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.

Note:

General Settings

  • 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 the the first connected Nessus adapter credentials.
    NOTE
    To use this option, you must successfully configure a Tenable Nessus adapter connection.

Required Fields

These fields must be configured to run the Enforcement Set.

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 values supplied in Connection Parameters above must have permission to write.


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


Was this article helpful?