Contents x
    Ivanti Security Controls - Patch Group
    • 02 Jul 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Ivanti Security Controls - Patch Group

    • Updated on 02 Jul 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Ivanti Security Controls - Patch Group adds CVEs to the Patch Group or updates the Patch Group CVEs from:
    * Vulnerabilities that match the results of the selected saved query, and match the Enforcement Action Dynamic Value statement, if defined, or vulnerabilities selected on the Vulnerabilities page.
    The CVEs in the Patch Group determine what patches are applicable on the devices.

    See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

    General Settings

    • Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
    • Add description - Add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
    • Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
    • Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
    • 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 Vulnerabilities.

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

    • Patch Group ID - The ID of the Patch Group.

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

    When Use stored credentials from the Ivanti Security Controls adapter is toggled Off, these fields are required:

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

    • Verify SSL - 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 - Connect the adapter to a proxy instead of directly connecting it to the domain.

    • HTTPS Proxy User Name - The user name to use when connecting to the server using the  HTTPS Proxy.

    • HTTPS Proxy Password - The password to use when connecting to the server using the  HTTPS Proxy.

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

    APIs

    Axonius uses the Patch Deployments 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 vulnerabilities.

    • 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