Contents x
    Ivanti Security Controls - Add Machine to Machine Group
    • 22 Sep 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Ivanti Security Controls - Add Machine to Machine Group

    • Updated on 22 Sep 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Ivanti Security Controls - Add Machine to Machine Group adds to an existing or new Machine Group within Ivanti:
    * Devices that match the results of the selected saved query, and match the Enforcement Action Dynamic Value statement, if defined, or devices selected on the Devices 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.

    Note:

    This action runs on Devices.

    • Use stored credentials from Ivanti Security Controls adapter - Select this option to use the Ivanti Security Controls connected adapter credentials.

      • When you select this option, the Select Adapter Connection dropdown is available, and you can choose which adapter connection to use for this Enforcement Action.

      • When not enabled, see Connection Parameters.

    Note:

    To use this option, you must successfully configure an Ivanti Security Controls adapter connection.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Group Name - The name (string) of the Machine Group that machines will be added to.

    • 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 fields are required to create the connection, while other fields are optional.

    • Host Name or IP Address - The hostname or IP address of the Ivanti Security Controls server that Axonius can communicate with via the Required Ports.
    • Port (default: 3121) - The port on the on-prem server that is connected to the Ivanti Security Controls application.
    • User Name and Password - The credentials for a user account that has the Required Permissions to perform this 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.
    • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the  HTTPS Proxy.
    • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the  HTTPS Proxy.

    • Create Group (default: disabled) - Enable this option to create a new group based on Group’s name and assign machines to it.

    • Use public IP addresses (default: disabled) - Enable this option to add public IP addresses. This option is useful for scanning IP addresses from cloud providers, such as AWS.

    • Use private IP addresses (default: disabled) - Enable this option to add private IP addresses.

    • Exclude IPv6 addresses (default: disabled) - Enable this option so that Axonius adds only IPv4 addresses to Ivanti Group and not IPv6 addresses. Otherwise, both IPv4 and IPv6 addresses are added.

    • Gateway Name - Select the Gateway through which to connect to perform the action.

    APIs

    Axonius uses the Machine Groups API.

    Learn more on how to use the REST API.

    Required Ports

    Axonius must be able to communicate with the value supplied in Hostname or IP Address via the designated port (default: 3121).

    Required Permissions

    The value supplied in User Name must have read access to devices.

    • The user must be a local or domain admin.

    The values supplied in Connection Settings above must have Read permissions.

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


    Was this article helpful?
    What's Next