Contents x
    Tenable.io - Add IP Addresses to Target Group
    • 20 Feb 2025
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Tenable.io - Add IP Addresses to Target Group

    • Updated on 20 Feb 2025
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Tenable.io - Add IP Addresses to Target Group adds IP addresses to an existing Tenable.io target group or creates a new Tenable.io target group for:

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

    Tenable.io target groups allow you to set permissions for which hosts users can scan. By default, all users can scan all hosts. For more details about Tenable.io target groups, see Tenable.io online documentation.

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

    • Target group name - Specify the Tenable.io target group name to be updated/created.

    • Create new target group - Select to create a new target group in Tenable.io.

      • If enabled, Axonius will create a new target group in Tenable.io.
      • If disabled, Axonius will update the specified target group name in Tenable.io.

    • 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 IP address or hostname of your Tenable.io management server.
    • Access API key and Secret API key (required) - These values must be created in the Tenable.io console. To generate an API key in the Tenable.io console, see Tenable.io - Generate an API Key.
    • 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.
    • Use public IP addresses - Select to add public IP addresses to Tenable.io.
    • Use private IP addresses - Select to add private IP addresses to Tenable.io.
    • Exclude IPv6 addresses - Select to add IPv6 addresses to the Tenable.io scan.
      • If enabled, Axonius will add only IPv4 addresses to Tenable.io.
      • If disabled, Axonius will add both IPv4 and IPv6 addresses to Tenable.io.
    • Override current IP address list - Select to override the current Tenable.sc asset IP list.
      • If enabled, Axonius will override the current Tenable.sc asset IP list.
      • If disabled, Axonius will add IP addresses to the existing Tenable.sc asset IP list.
    • CIDR exclude list - Specify a comma-separated list of CIDRs to be excluded.
      • If supplied, Axonius will not add to Tenable.sc IP addresses in the IP range of the specified CIDRs.
      • If not supplied Axonius will add to Tenable.sc IP addresses in any IP range.
    • Use preferred hostname FQDN - Select this to use the FQDN field as the preferred hostname. Note that this overrides Use AWS Public Dns as hostname.
    • Use AWS Public Dns as hostname - Select this to use the AWS Public DNS field as the preferred hostname. To enable this option, ensure to disable Use preferred hostname FQDN.

    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