Tenable Vulnerability Management - Launch WAS Scan

Tenable Vulnerability Management - Launch WAS Scan launches a web application scan for:

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

APIs

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

API Endpoint: POST /was/v2/configs/{config_id}/scans

Permissions

• Can Execute [32] scan permission
• Scan Operator [24] user role or WAS.SCAN_WAS.MANAGE custom role privilege
  • if you're using a Tenable-provided scan template, you must have the WAS.SCAN_WAS_SYSTEM_TEMPLATE.USE custom role privilege.

Required Fields

These fields must be configured to run the Enforcement Set.

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

• Scan Configuration ID - Provide the ID of the scan configuration (string).

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

APIs

Axonius uses the Tenable API.

Required Ports

Axonius must be able to communicate via the following ports:

• 80
• 443