Tenable Vulnerability Management - Restart Agent

Tenable Vulnerability Management - Restart Agent restarts unhealthy Tenable agents 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


Prerequisites

To successfully run this Enforcement Set, the following API endpoints and permissions are required:

API Endpoint: POST /scanners/null/agents/_bulk/directive

Permissions:

• Scan Manager [40] user role OR Administrator [64] user role

Required Ports

• TCP 443 (outbound) - HTTPS to cloud.tenable.com • UDP 53 (outbound) - DNS resolution

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 (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 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](https://docs.axonius.com/docs/tenableio) adapter connection.

  • 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 hostname of the Tenable.io server.

  • Access API Key and Secret API Key - An API Key associated with a user account that has permission to perform this Enforcement Action.

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

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



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