Contents x
    Tenable.io - Launch WAS Scan
    • 20 Feb 2025
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Tenable.io - Launch WAS Scan

    • Updated on 20 Feb 2025
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Tenable.io - Launch WAS Scan launches a web application scan 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 Tenable.io 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.
    • 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 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.

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

    Required Permissions

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

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


    Was this article helpful?
    What's Next