| navigation_title | Create cases | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| mapped_pages | |||||||||||||
| applies_to |
|
||||||||||||
| products |
|
||||||||||||
| description | Create cases to track incidents, attach alerts and files, assign team members, and push updates to external systems. |
To create a new case:
-
Find Cases using the global search field, then select Create case.
:::{note} Cases are scoped by solution. On {{stack}}, search for
Security/CasesorObservability/Cases, or go to {{stack-manage-app}} → Cases. On {{serverless-short}}, search forCasesin {{elastic-sec}} or {{observability}}. ::: -
(Optional) Select a template to pre-fill values.
- {applies_to}
stack: ga 9.5+{applies_to}serverless: gaCreate and manage templates on the Templates page. Refer to Case templates. - {applies_to}
stack: ga 9.0-9.4Create and manage templates in case settings.
- {applies_to}
-
Enter a name, severity, and description. Optionally add a category, assignees, tags, and additional fields.
- {applies_to}
stack: ga 9.5+{applies_to}serverless: gaAdditional fields come from the field library. - {applies_to}
stack: ga 9.0-9.4Additional fields are custom fields configured in case settings.
- {applies_to}
-
(Optional) Adjust sync and extraction options, or leave the defaults:
-
Sync alert status syncs alert statuses with the case status (on by default).
-
Auto-extract observables extracts observables from attached alerts (on by default, requires appropriate subscription). {applies_to}
stack: ga 9.5Auto-extraction can also run for cases created through the Cases API or automations. For details, refer to Auto-extract observables.:::{note} Auto-extracting observables is only available in {{sec-serverless}} and {{elastic-sec}} 9.2+. :::
-
-
(Optional) Select a connector to send the case to an external system. When you create the case, it's pushed to that system automatically.
-
Select Create case.
After creating a case, attach objects such as alerts, files, observables, and visualizations. To notify users when they're assigned to a case, set up email notifications.
Set up email notifications to alert users when they're assigned to a case, so they can respond promptly.
:::::{tab-set}
:::{tab-item} {{ecloud}}
Add the email domains to the notifications domain allowlist.
You do not need to configure an email connector or update {{kib}} user settings. The preconfigured Elastic-Cloud-SMTP connector is used by default.
:::
:::{tab-item} Self-managed
-
Create a preconfigured email connector.
::::{note} Email notifications support only preconfigured email connectors, which are defined in the
kibana.ymlfile. For examples, refer to Email connectors and Configure email accounts for well-known services. :::: -
Set the
notifications.connectors.default.email{{kib}} setting to the name of your email connector.notifications.connectors.default.email: 'mail-dev' xpack.actions.preconfigured: mail-dev: name: preconfigured-email-notification-maildev actionTypeId: .email config: service: other from: from address host: host name port: port number secure: true/false hasAuth: true/false
-
If you want the email notifications to contain links back to the case, configure the server.publicBaseUrl setting.
:::
:::::
A case created in one solution is only visible within that solution:
- {{stack-manage-app}} cases are not visible in {{observability}} or {{elastic-sec}}
- {{observability}} cases are not visible in {{stack-manage-app}} or {{elastic-sec}}
- {{elastic-sec}} cases are not visible in {{stack-manage-app}} or {{observability}}
Alerts also can't cross solution boundaries. You can only attach alerts from the same solution to cases. For example, you can't attach {{observability}} alerts to an {{elastic-sec}} case.