Login
    Contents x
    Cherwell IT Service Management - Create Incident
    • 03 Apr 2023
    • 5 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Cherwell IT Service Management - Create Incident

    • Updated on 03 Apr 2023
    • 5 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article Summary

    Cherwell IT Service Management - Create Incident (Create Cherwell Incident) creates an incident in Cherwell for the entities retrieved from the saved query supplied as a trigger (or devices that have been selected in the asset table).

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

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

    NOTE
    • To use this option, you must successfully configure a Cherwell IT Service Management adapter connection.
    • The user name and the password used for the adapter connection must be user with permissions to create new incidents.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    1. Incident description - Specify an incident description.
      Priority (required, default: 5) - Specify the incident priority.
      Instance Name - 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.

    1. Cherwell Domain - The hostname or IP address of the Cherwell server.

      NOTE
      If Use stored credentials from the Cherwell adapter is disabled, this field is required.

    2. User Name and Password - The user name and the password of a user with permissions to create new incidents.

      NOTE
      If Use stored credentials from the Cherwell adapter is disabled, this field is required.

    3. Client ID - Enter the client ID created in the CSM Administrator. For details, see Cherwell - Obtaining API Client IDs.

      NOTE
      If Use stored credentials from the Cherwell adapter is disabled, this field is required.

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

    5. HTTPS Proxy - A proxy to use when connecting to the value supplied in Cherwell Domain. When not supplied, Axonius will connect directly to the value supplied in Cherwell Domain.

    6. Short description - Specify the incident title.

    7. Add default incident description - Select whether to send the incident description to Cherwell.

      • If enabled, Axonius will include the default incident description (mentioned below) in the Cherwell incident.
      • If disabled, Axonius will not include the default incident description (mentioned below) in the Cherwell incident.

      Message example:
      Alert - "test" for the following query has been triggered: Missing Sophos

      Alert Details
      The alert was triggered because: The number of entities is above 0
      The number of devices returned by the query:4
      The previous number of devices was:4

      You can view the query and its results here: https://demo-latest.axonius.com/devices?view=Missing Sophos

    8. Customer display name - Specify the customer display name.

    9. Multiple optional incident related settings :

      1. Source
      2. Service
      3. Category
      4. Subcategory
      5. Incident type
      6. Status
      NOTE
      Since the valid values of the different parameters are customer specific, Axonius does not validate any of those parameters values. You must make sure inserted values are correct, otherwise, the request might fail.

    10. Additional fields (optional, default: empty) - 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.
      • If not supplied, Axonius will not add any additional fields to the created incident.

    11. Send CSV data - Select to include a CSV file with the query results in the issue created.

    Additional CSV Settings

    1. Split by asset entities - Select to create a CSV file where each asset on a device is shown as a separate row. This separates each asset as the 'expand' option in the application. It separates each asset by its entity. For example, you will be able to know which values were fetched from each adapter connection.
      a. If supplied, each value on a device or user is shown as a separate row.
      b. If not supplied all values on a device are in the same cell on the CSV file.
    2. Split by field values - Choose field value - For complex fields and lists you can create a CSV file where the values of complex fields and lists are represented as separate rows in the file. From the drop-down box select the value that you want to display in the file, 'Tags' for instance. Only fields that have been discovered are available. For example, if you export by Installed Software, you will be able to see each installed Software name and its version.
    3. Don't split complex objects into columns - When selected, complex objects appear in a single column in JSON format. By default, each field in a complex object is split into a separate column in the CSV file.
    4. Export CSV delimiter to use for multi-value fields (default: Export CSV delimiter to use for multi-value fields field under the System Settings section in the GUI Settings) - Specify a delimiter to separate between values within the same field of an exported CSV file, otherwise the delimiter defined in Export CSV delimiter to use for multi-value fields is used.
    5. Maximum rows (default: 1048500) - Specify the maximum number of rows to be included in the CSV file. When you set a value here the generated CSV file will include the top x rows, based on the specified values. Otherwise, the generated CSV file will include the default maximum rows, set as 1048500.
    6. Include associated devices (only for Vulnerabilities and Software) - For Software and Vulnerabilities queries. Select this option to include the associated devices with the preferred hostname as a predefined field for each software or vulnerability. When you create a CSV file with associated devices (for Vulnerabilities or Software), if the exported query results are larger than the value set under Maximum rows (or the default value of 1048500), an appropriate notice is displayed at the end of the CSV file.

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

    What's Next
    Change password!
    Changing your password will log you out immediately. Use the new password to log back in.
    Change profile
    Success!
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.
    Logout