Ivanti Neurons for ITSM - Create Incident per Asset

Ivanti Neurons for ITSM - Create Incident per Asset creates a new incident in your Ivanti Neurons for ITSM instance for each asset, 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.

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

Note

Required Fields

These fields must be configured to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - 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 Ivanti Neurons for ITSM 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 an Ivanti Neurons for ITSM adapter connection.

  • Required Incident Fields - The Ivanti Neurons for ITSM incident fields required to create the incident. Add a row for each field, and configure the following for each row:

    • Field Name - Select an incident field from the dropdown, or type the name of a custom field. The available fields are Category, Description, ProfileLink, Service, Source, Status, and Symptom.
    • Value - The value to set for the field. Enter static text, or a template that uses placeholders defined in Map Axonius Fields to Template Placeholders. For example, {{hostname}}.
  • 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.

  • Map Axonius Fields to Template Placeholders - Map Axonius fields to placeholder names. Reference a placeholder in the Value of a Required Incident Field or an Additional Field as {{placeholder_name}}, and Axonius replaces it with the value of the mapped field for each asset. For example, map Host Name to hostname, and then enter Missing XDR agent on {{hostname}} as the value of the Description field.

    Note

    • A placeholder that is not mapped to an Axonius field is left as is in the text.
    • If the mapped field has no value for an asset, the placeholder is replaced with an empty string.
    • If the mapped field has multiple values for an asset (for example, MAC addresses from several network interfaces), the placeholder is replaced with the most common value.
  • Additional Fields - Additional Ivanti Neurons for ITSM incident fields to set on the incident. Add a row for each field, and configure the following for each row:

    • Field Name - Select an incident field from the dropdown, or type the name of a custom field. The available fields are CreatedBy, Owner, OwnerTeam, OwnerTeam_Valid, Owner_Valid, Priority, RequestorLink_RecID, and Subject.
    • Value - The value to set for the field. Enter static text, or a template that uses placeholders defined in Map Axonius Fields to Template Placeholders. For example, {{hostname}}.

Note

Fields whose value is empty for an asset are not sent to Ivanti Neurons for ITSM.

Connection Settings

⚠️

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.

  • Host Name or IP Address - The base URL of your Ivanti Neurons for ITSM tenant. Must include the protocol prefix (https://). For example: https://yourtenant.ivanti.com

  • REST API Key - The REST API Key created in Configuration Console > Security Controls > API Keys. This is the Reference ID of the API key.

  • Verify SSL (Optional) (default: enabled) - Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings. This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting.)

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

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

APIs

Axonius uses the Ivanti Neurons for ITSM REST API - POST /api/odata/businessobject/incidents

Required Ports

Axonius must be able to communicate via the following ports:

  • TCP port 443 (HTTPS)

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the necessary permissions to perform this enforcement action.

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

The following permissions and requirements are needed:

  • The REST API Key must have write permissions to the /api/odata/businessobject/incidents endpoint.
  • The API Key user role must have permission to create incidents in Ivanti Neurons for ITSM.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

VersionSupportedNotes
Ivanti Neurons for ITSM 2022+βœ“Current versions

To learn more about Enforcement Actions, see Enforcement Actions.


Did this page help you?