---
title: Open and manage cases in Elastic Security
description: You can create and manage cases using the UI or the cases API. Open a new case to keep track of security issues and share their details with colleagues...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/security/investigate/open-manage-cases
products:
  - Elastic Cloud Serverless
  - Elastic Security
---

# Open and manage cases in Elastic Security
You can create and manage cases using the UI or the [cases API](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-cases).

## Open a new case

Open a new case to keep track of security issues and share their details with colleagues.
1. Find **Cases** in the navigation menu or search for `Security/Cases` by using the [global search field](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/find-and-organize/find-apps-and-objects), then click **Create case**. If no cases exist, the Cases table will be empty and you’ll be prompted to create one by clicking the **Create case** button inside the table.
2. `stack: preview` `serverless: preview` If you defined [templates](/elastic/docs-content/pull/4236/solutions/security/investigate/configure-case-settings#cases-templates), you can optionally select one to use its default field values.
3. Give the case a name, assign a severity level, and provide a description. You can use [Markdown](https://www.markdownguide.org/cheat-sheet) syntax in the case description.
   <note>
   If you do not assign your case a severity level, it will be assigned **Low** by default.
   </note>
   <tip>
   You can insert a Timeline link in the case description by clicking the Timeline icon (![Timeline icon](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-add-timeline-button.png "title")).
   </tip>
4. Optionally, add a category, assignees and relevant tags. You can add users only if they meet the necessary [prerequisites](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/security/investigate/cases-requirements).
5. `stack: preview` `serverless: preview` If you defined [custom fields](/elastic/docs-content/pull/4236/solutions/security/investigate/configure-case-settings#cases-ui-custom-fields), they appear in the **Additional fields** section.
6. Choose if you want alert statuses to sync with the case’s status after they are added to the case. This option is turned on by default, but you can turn it off after creating the case.
7. `stack: ga 9.2` With the appropriate [Elastic Stack subscription](https://www.elastic.co/pricing) or [Serverless project feature tier](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/deploy-manage/deploy/elastic-cloud/project-settings), you can choose to automatically extract observables from alerts that you're adding to the case. This option is turned on by default. You can turn it off after creating the case by toggling **Auto-extract observables** on the case's **Observables** tab.
8. From **External incident management**, select a [connector](/elastic/docs-content/pull/4236/solutions/security/investigate/configure-case-settings#cases-ui-integrations). If you’ve previously added one, that connector displays as the default selection. Otherwise, the default setting is `No connector selected`.
9. Click **Create case**.
   <note>
   If you’ve selected a connector for the case, the case is automatically pushed to the third-party system it’s connected to.
   </note>


## Add email notifications

You can configure email notifications that occur when users are assigned to cases.
For Kibana on Elastic Cloud:
1. Add the email domains to the [notifications domain allowlist](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/alerts-cases/alerts).
   You do not need to take any more steps to configure an email connector or update Kibana user settings, since the preconfigured Elastic-Cloud-SMTP connector is used by default.

For self-managed Kibana:
1. Create a preconfigured email connector.
   <note>
   At this time, email notifications support only [preconfigured email connectors](https://docs-v3-preview.elastic.dev/elastic/kibana/tree/main/reference/connectors-kibana/pre-configured-connectors), which are defined in the [`kibana.yml`](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/deploy-manage/stack-settings) file.
   </note>
2. Set the `notifications.connectors.default.email` Kibana setting to the name of your email connector.
3. If you want the email notifications to contain links back to the case, you must configure the [server.publicBaseUrl](https://docs-v3-preview.elastic.dev/elastic/kibana/tree/main/reference/configuration-reference/general-settings#server-publicbaseurl) setting.

When you subsequently add assignees to cases, they receive an email.

## Manage existing cases

From the Cases page, you can search existing cases and filter them by attributes such as assignees, categories, severity, status, and tags. You can also select multiple cases and use bulk actions to delete cases or change their attributes. General case metrics, including how long it takes to close cases, are provided above the table.
To explore a case, click on its name. You can then:
- [Review the case summary](#cases-summary)
- [Add and manage comments](#cases-manage-comments)
  <tip>
  Comments can contain Markdown. For syntax help, click the Markdown icon (![Click markdown icon](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-markdown-icon.png "title")) in the bottom right of the comment.
  </tip>
- Examine [alerts](#cases-examine-alerts), [indicators](/elastic/docs-content/pull/4236/solutions/security/investigate/indicators-of-compromise#review-indicator-in-case), and `stack: ga 9.2.0` [events](#cases-examine-events) attached to the case
- [Add files](#cases-add-files)
- [Add a Lens visualization](#cases-lens-visualization)
- Modify the case’s description, assignees, category, severity, status, and tags.
- [Manage connectors](/elastic/docs-content/pull/4236/solutions/security/investigate/configure-case-settings#cases-ui-integrations) and send updates to external systems (if you’ve added a connector to the case)
- [Add observables](#cases-add-observables)
- [Copy the case UUID](#cases-copy-case-uuid)
- Refresh the case to retrieve the latest updates


### Review the case summary

Click on an existing case to access its summary. The case summary, located under the case title, contains metrics that summarize alert information and response times. These metrics update when you attach additional unique alerts to the case, add connectors, or modify the case’s status:
- **Total alerts**: Total number of unique alerts attached to the case
- **Associated users**: Total number of unique users that are represented in the attached alerts
- **Associated hosts**: Total number of unique hosts that are represented in the attached alerts
- **Total connectors**: Total number of connectors that have been added to the case
- **Case created**: Date and time that the case was created
- **Open duration**: Time elapsed since the case was created
- **In progress duration**: How long the case has been in the `In progress` state
- **Duration from creation to close**: Time elapsed from when the case was created to when it was closed


### Manage case comments

To edit, delete, or quote a comment, select the appropriate option from the **More actions** menu (**…**).
![Shows you a summary of the case](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-cases-manage-comments.png)


### Examine alerts attached to a case

To explore the alerts attached to a case, click the **Alerts** tab. In the table, alerts are organized from oldest to newest. To [view alert details](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/security/detect-and-alert/view-detection-alert-details), click the **View details** button.
![Shows you the Alerts tab](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-cases-alert-tab.png)

<note>
  Each case can have a maximum of 1,000 alerts.
</note>


### Examine events attached to a case

```
stack: ga 9.2
```

After adding events to cases from the Events table (which you can access from the **Events** tab on the **Hosts**, **Network**, or **Users** pages) or from Timeline, you can examine them in the case's **Events** tab. Within the tab, events are organized from newest to oldest. Click the **View details** button to find out more about the event.

### Add files

To upload files to a case, select the **Files** tab, then click **Add files**. You can set file types and sizes by configuring your [Kibana case settings](https://docs-v3-preview.elastic.dev/elastic/kibana/tree/main/reference/configuration-reference/cases-settings).
<note>
  There is a 10 MiB size limit for images. For all other MIME types, the limit is 100 MiB.
</note>

To download or delete the file, or copy the file hash to your clipboard, open the **Actions** menu (**…**). The available hash functions are MD5, SHA-1, and SHA-256.
When you add a file, a comment is added to the case activity log. To view an image, click its name in the activity or file list.

### Add a Lens visualization

<warning>
  This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
</warning>

Add a Lens visualization to your case to portray event and alert data through charts and graphs.
![Shows how to add a visualization to a case](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-add-vis-to-case.gif)

To add a Lens visualization to a comment within your case:
1. Click the **Visualization** button. The **Add visualization** dialog appears.
2. Select an existing visualization from your Visualize Library or create a new visualization.
   <important>
   Set an absolute time range for your visualization. This ensures your visualization doesn’t change over time after you save it to your case, and provides important context for others managing the case.
   </important>
3. Save the visualization to your Visualize Library by clicking the **Save to library** button (optional).
   1. Enter a title and description for the visualization.
2. Choose if you want to keep the **Update panel on Security** activated. This option is activated by default and automatically adds the visualization to your Visualize Library.
4. After you’ve finished creating your visualization, click **Save and return** to go back to your case.
5. Click **Preview** to show how the visualization will appear in the case comment.
6. Click **Add Comment** to add the visualization to your case.

Alternatively, while viewing a [dashboard](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/security/dashboards) you can open a panel’s menu then click **More actions (…) → Add to existing case** or **More actions (…) → Add to new case**.
After a visualization has been added to a case, you can modify or interact with it by clicking the **Open Visualization** option in the case’s comment menu.
![Shows where the Open Visualization option is](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-cases-open-vis.png)


### Add observables

<admonition title="Requirements">
  Ensure you have the appropriate [Elastic Stack subscription](https://www.elastic.co/pricing) or [Serverless project feature tier](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/deploy-manage/deploy/elastic-cloud/project-settings).
</admonition>

An observable is a piece of information about an investigation, for example, a suspicious URL or a file hash. Use observables to identify correlated events and better understand the severity and scope of a case.
To create an observable:
1. Click the **Observables** tab, then click **Add observable**.
   <note>
   Each case can have a maximum of 50 observables.
   </note>
2. Provide the necessary details:
   - **Type**: Select a type for the observable. You can choose a preset type or a [custom one](/elastic/docs-content/pull/4236/solutions/security/investigate/configure-case-settings#cases-observable-types).
- **Value**: Enter a value for the observable. The value must align with the type you select.
- **Description** (Optional): Provide additional information about the observable.
3. Click **Add observable**.

After adding an observable to a case, you can remove or edit it by using the **Actions** menu (**…**).
<tip>
  Go to the **Similar cases** tab to access other cases with the same observables.
</tip>


### Copy the case UUID

Each case has a universally unique identifier (UUID) that you can copy and share. To copy a case’s UUID to a clipboard, go to the Cases page and select **Actions** → **Copy Case ID** for the case you want to share. Alternatively, go to a case’s details page, then from the **More actions** menu (…), select **Copy Case ID**.
![Copy Case ID option in More actions menu](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-cases-copy-case-id.png)


## Export and import cases

Cases can be [exported](#cases-export) and [imported](#cases-import) as saved objects using the Kibana [Saved Objects](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/find-and-organize/saved-objects) UI.
<important>
  Before importing Lens visualizations, Timelines, or alerts into a space, ensure their data is present. Without it, they won’t work after being imported.
</important>


### Export a case

Use the **Export** option to move cases between different Elastic Security instances. When you export a case, the following data is exported to a newline-delimited JSON (`.ndjson`) file:
- Case details
- User actions
- Text string comments
- Case alerts
- Lens visualizations (exported as JSON blobs).

<note>
  The following attachments are *not* exported:
  - **Case files**: Case files are not exported. However, they are accessible from **Files** (find **Files** in the navigation menu or by using the [global search field](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/find-and-organize/find-apps-and-objects)) to download and re-add.
  - **Alerts**: Alerts attached to cases are not exported. You must re-add them after importing cases.
</note>

To export a case:
1. Find **Saved Objects** in the navigation menu or by using the [global search field](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/find-and-organize/find-apps-and-objects).
2. Search for the case by choosing a saved object type or entering the case title in the search bar.
3. Select one or more cases, then click the **Export** button.
4. Click **Export**. A confirmation message that your file is downloading displays.
   <tip>
   Keep the **Include related objects** option enabled to ensure connectors are exported too.
   </tip>

![Shows the export saved objects workflow](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/solutions/images/security-cases-export-button.png)


### Import a case

To import a case:
1. Find **Saved Objects** in the navigation menu or by using the [global search field](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/find-and-organize/find-apps-and-objects).
2. Click **Import**.
3. Select the NDJSON file containing the exported case and configure the import options.
4. Click **Import**.
5. Review the import log and click **Done**.
   <important>
   Be mindful of the following:
   - If the imported case had connectors attached to it, you’ll be prompted to re-authenticate the connectors. To do so, click **Go to connectors** on the **Import saved objects** flyout and complete the necessary steps. You can also access connectors from the **Connectors** page (find **Connectors** in the navigation menu or by using the [global search field](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/find-and-organize/find-apps-and-objects)).
   - If the imported case had attached alerts, verify that the alerts' source documents exist in the environment. Case features that interact with alerts (such as the Alert details flyout and rule details page) rely on the alerts' source documents to function.
   </important>