ServiceNow - Create Incident per Asset

ServiceNow - Create Incident per Asset creates an incident in ServiceNow for each entity that matches the parameters of the saved query supplied as a trigger (or from the entities selected in the asset table).

General Settings

Use stored credentials from ServiceNow adapter - Select this option to use the ServiceNow connected adapter credentials.

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

Required Fields

These fields must be configured to run the Enforcement Set.

• Incident short description - Specify the incident title.
• Message severity (default: info) - Select the message severity: info, warning or error.

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

• Split by field values - Select a field to split assets by in the Assets table. Each incident will be split into multiple rows where each row lists a single field value - for example, a row with an incident per vulnerability per device.

• Retry Count (default: 1) - If the action fails, Axonius will retry to execute it this many times for each device.

• Incident description and Map Axonius fields to fields in the description - These fields allow you to create custom incident descriptions.

  • In Incident description, enter a description template that includes field placeholders for field mapping. The placeholder is enclosed by double {{ }}.
  • Then, in Map Axonius fields to fields in the description, enter the field placeholder in Placeholder text fields on the left and select an Axonius field in Axonius fields on the right. The value of the Axonius field is populated into the description in place of the placeholder text.

  In the example below, the template in Incident description maps the fields selected under Axonius fields into the placeholders dev_hostname, dev_ip, and dev_serial. Each asset that matches the query parameters will have its data added to the incident description.

  

• Multiple optional incident related settings:

  1. Incident Type
  2. Caller ID
  3. Requested for
  4. Symptom
  5. Assignment group
  6. Category
  7. Subcategory
  NOTE

  Since the valid values of these parameters are customer specific, Axonius does not validate any of these parameter's values. You must make sure inserted values are correct, otherwise, the request might fail.

• Additional fields - Specify additional fields to be added as part of the incident as key/value pairs in a JSON format.
  For example:

  {"field1": "value1", "field2": "value2"}.
  

  • If supplied, Axonius will add the specified fields and values to the created incident. If one of the specified fields is invalid, the request might fail.

• Table name (default: incident) - Specify the ServiceNow table name in which the incident will be created.

  • If supplied, the incident will be created in the specified table name.
  • If not supplied, the incident will be created in the 'incident' table.

• Link created task to another new table record - Link this new task to another table with the following parameters:

  • Name of table to populate into (default: sc_req_item)
  • Field to base a relation on (default: request)
  • JSON entry to send

• Axonius to ServiceNow field mapping - Field mapping allows you to map Axonius fields to the CMDB fields. The input should be key/value pairs in a JSON format.
  For example:

  {"axonius_field1":"servicenow_field1", "axonius_field2":"servicenow_field2"}
  

• Send CSV data (required, default: False)

  • If enabled, the created issue will include an attached CSV file with the query results.
  • If disabled, the created issue will not include an attached CSV file with the query results.