Configure case settings

To change case closure options, add custom fields, templates, and connectors for external incident management systems, and create custom observable types, find Cases in the navigation menu or search for Security/Cases by using the global search field, then click Settings.

Shows the case settings page

Note

To view and change case settings, you must have the appropriate Kibana feature privileges. Refer to Cases requirements.

Case closures ¶

If you close cases in your external incident management system, the cases will remain open in Elastic Security until you close them manually.

To close cases when they are sent to an external system, select Automatically close cases when pushing new incident to external system.

External incident management systems ¶

You can push Elastic Security cases to these third-party systems:

  • {sn-itsm}
  • {sn-sir}
  • Jira (including Jira Service Desk)
  • {ibm-r}
  • {swimlane}
  • {hive}
  • {webhook-cm}

To push cases, you need to create a connector, which stores the information required to interact with an external system. After you have created a connector, you can set Elastic Security cases to automatically close when they are sent to external systems.

Important

To create connectors and send cases to external systems, you need the appropriate license, and your role needs All privileges for the Action and Connectors feature. For more information, refer to Cases requirements.

To create a new connector:

  1. From the Incident management system list, select Add new connector.
  2. Select the system to send cases to: ServiceNow, Jira, IBM Resilient, Swimlane, TheHive, or Webhook - Case Management.
  3. Enter your required settings. For connector configuration details, refer to:

To change the settings of an existing connector:

  1. Select the required connector from the incident management system list.
  2. Click Update <connector name>.
  3. In the Edit connector flyout, modify the connector fields as required, then click Save & close to save your changes.

To change the default connector used to send cases to external systems, select the required connector from the incident management system list.

Mapped case fields ¶

When you export an Elastic Security case to an external system, case fields are mapped to existing fields in the external system. For example, the case title is mapped to the short description in ServiceNow and the summary in Jira incidents. Case tags are mapped to labels in Jira. Case comments are mapped to work notes in ServiceNow.

When you use a Webhook - Case Management connector, case fields can be mapped to custom or existing fields.

When you push updates to external systems, mapped fields are either overwritten or appended, depending on the field and the connector.

Retrieving data from external systems is not supported.

Custom fields ¶

You can add optional and required fields for customized case collaboration.

  1. In the Custom fields section, click Add field. :::{image} ../../../images/security-cases-add-custom-field.png
    :alt: Add a custom field in case settings
    :class: screenshot
    :::
  2. You must provide a field label and type (text or toggle). You can optionally designate it as a required field and provide a default value.

When you create a custom field, it’s added to all new and existing cases. In existing cases, new custom text fields initially have null values.

You can subsequently remove or edit custom fields on the Settings page.

Templates ¶

Warning

This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.

You can make the case creation process faster and more consistent by adding templates. A template defines values for one or all of the case fields (such as severity, tags, description, and title) as well as any custom fields.

To create a template:

  1. In the Templates section, click Add template. :::{image} ../../../images/security-cases-add-template.png
    :alt: Add a template in case settings
    :class: screenshot
    :::
  2. You must provide a template name and case severity. You can optionally add template tags and a description, values for each case field, and a case connector.

When users create cases, they can optionally select a template and use its values or override them.

Note

If you update or delete templates, existing cases are unaffected.

Observable types ¶

Requirements

To use observables, you must have a Platinum subscription or higher.

Create custom observable types for enhanced case collaboration.

  1. In the Observable types section, click Add observable type.
  2. Enter a descriptive label for the observable type, then click Save.

After creating a new observable type, you can remove or edit it from the Settings page.

Note

You can create up to 10 custom observable types.

Important

Deleting a custom observable type deletes all instances of it.

Add an observable type in case settings