elastic · nastasha-solomon · Jun 22, 2022 · Jun 8, 2022 · Jun 8, 2022 · Jun 8, 2022
@@ -1,3 +1,5 @@
 include::cases-overview.asciidoc[leveloffset=+1]
 
+include::cases-manage.asciidoc[leveloffset=+2]
+
 include::cases-ui-integrations.asciidoc[]
@@ -0,0 +1,180 @@
+[[cases-open-manage]]
+= Open and manage cases
+
+You can create and manage cases using the UI or the <<cases-api-overview>>.
+
+[float]
+[[cases-ui-open]]
+== Open a new case
+
+Open a new case to keep track of security issues and share their details with
+colleagues.
+
+. Go to *Investigate* -> *Cases*, 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.
+. Give the case a name, add relevant tags, assign a severity level, and provide a description. You can use
+https://www.markdownguide.org/cheat-sheet[Markdown] syntax in the case description.
++
+NOTE: If you do not assign your case a severity level, it will be assigned *Low* by default.
+
++
+TIP: You can insert a Timeline link in the case description by clicking the Timeline icon (image:images/add-timeline-button.png[Timeline icon,17,17]).
+
+. Choose if you want alert statuses to sync with the case's status after they are added to the case. This option is enabled by default, but you can turn it off after creating the case.
+. From *External incident management*, select a <<cases-ui-integrations, connector>>. If you’ve previously added one, that connector displays as the default selection. Otherwise, the default setting is `No connector selected`.
+. 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.
+
+
+[role="screenshot"]
+image::images/cases-ui-open.png[Shows an open case]
+
+[float]
+[[cases-ui-manage]]
+== Manage existing cases
+
+From the Cases page, you can search existing cases and filter them by severity, tags, reporter, and status: `Open`, `In progress`, or `Closed`. General case metrics, including how long it takes to close cases, are provided above the table.
+
+[role="screenshot"]
+image::images/cases-home-page.png[Case UI Home]
+
+To explore a case, click on its name. You can then:
+
+* <<cases-summary>>
+* Add and <<cases-manage-comments, manage comments>>
++
+TIP: Comments can contain Markdown. For syntax help, click the Markdown icon (image:images/markdown-icon.png[Click markdown icon,17,17]) in the bottom right of the comment.
+
+* <<cases-examine-alerts, Examine alerts attached to the case>>
+* <<cases-lens-visualization>>
+* Modify the case's description
+* <<cases-ui-integrations, Manage connectors>> and send updates to external systems (if you've added a connector to the case)
+* Close the case or reopen it
+* Edit tags
+* Update the case's severity
+* Refresh the case to retrieve the latest updates
+
+[float]
+[[cases-summary]]
+=== 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
+
+[role="screenshot"]
+image::images/cases-summary.png[Shows you a summary of the case]
+
+[float]
+[[cases-manage-comments]]
+=== Manage case comments
+To edit, delete, or quote a comment, select the appropriate option from the *More actions* menu (*…*).
+
+[role="screenshot"]
+image::images/cases-manage-comments.png[Shows you a summary of the case]
+
+[float]
+[[cases-examine-alerts]]
+=== Examine alerts attached to a case
+
+preview::[]
+
+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, view alert details>>, click the *View details* button.
+
+[role="screenshot"]
+image::images/cases-alert-tab.png[Shows you the Alerts tab]
+
+[float]
+[[cases-lens-visualization]]
+=== Add a Lens visualization
+
+beta[]
+
+Add a Lens visualization to your case to portray event and alert data through charts and graphs.
+
+[role="screenshot"]
+image::images/add-vis-to-case.gif[Shows how to add a visualization to a case]
+
+To add a Lens visualization to a comment within your case:
+
+. Click the *Visualization* button. The **Add visualization** dialog appears. 
+. 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.
+
++
+. Save the visualization to your Visualize Library by clicking the *Save to library* button (optional).
+.. Enter a title and description for the visualization. 
+.. 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.
+. After you've finished creating your visualization, click *Save and return* to go back to your case.
+. Click *Preview* to show how the visualization will appear in the case comment.
+. Click *Add Comment* to add the visualization to your case. 
+
+NOTE: Once a visualization has been added to a case, it cannot be modified or deleted. However, you can interact with the visualization by clicking the *Open Visualization* option in the comment menu.
+
+[role="screenshot"]
+image::images/cases-open-vis.png[Shows where the Open Visualization option is]
+
+[float]
+[[cases-export-import]]
+== Export and import cases
+
+Cases can be <<cases-export, exported>> and <<cases-import, imported>> as saved objects using the {kib} {kibana-ref}/managing-saved-objects.html[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.
+
+[float]
+[[cases-export]]
+=== Export a case
+Use the *Export* option to move cases between different Kibana 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).
+
+To export a case:
+
+. Open the main menu, go to *Stack Management -> {kib}*, then select the *Saved Objects* tab.
+. Search for the case by choosing a saved object type or entering the case title in the search bar.
+. Select one or more cases, then click the *Export* button.
+. 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.
+
+[role="screenshot"]
+image::images/cases-export-button.png[Shows the export saved objects workflow]
+
+[float]
+[[cases-import]]
+=== Import a case
+
+To import a case:
+
+. Open the main menu, go to *Stack Management -> {kib}*, then select the *Saved Objects* tab.
+. Click *Import*.
+. Select the NDJSON file containing the exported case and configure the import options.
+. Click *Import*.
+. 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. Alternatively, open the main menu, then go to *Stack Management -> Alerts and Insights -> Rules and Connectors -> Connectors* to access connectors.
+* 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.
+
+=========================
++
@@ -3,172 +3,17 @@
 
 = Cases
 
-Cases are used to open and track security issues directly in the {es-sec-app}.
-All cases list the original reporter and all users who contribute to a case
-(`participants`). Comments support Markdown syntax and allow linking to saved <<timelines-ui,Timelines>>. Additionally, you can send cases to these
-external systems from within {es-sec}:
+Collect and share information about security issues by opening a case in {elastic-sec}. Cases allow you to track key investigation details, collect alerts in a central location, and more. The {elastic-sec} UI provides several ways to create and manage cases. Alternatively, you can use the <<cases-api-overview, Cases API>> to perform the same tasks.
+
+You can also send cases to these external systems by <<cases-ui-integrations, configuring external connectors>>:
 
 * {sn} ITSM
 * {sn} SecOps
 * {jira} (including Jira Service Desk)
 * {ibm-r}
 * {swimlane}
 
-<<cases-ui-integrations>> describes how to set up external integrations. When configuring case fields, note that data from mapped fields can be pushed to external systems but cannot be pulled in.
-
-You can create and manage cases using the UI or the <<cases-api-overview>>.
-
-IMPORTANT: To send cases to external systems, you need the
-https://www.elastic.co/subscriptions[appropriate license] and your role needs *All* privileges for the *Action and Connectors* feature. For information about the base role privileges you need to access cases, refer to <<case-permissions>>.
-
-NOTE: From {elastic-sec}, you cannot access cases created in {observability} or Stack Management.
-
 [role="screenshot"]
 image::images/cases-home-page.png[Case UI Home]
 
-[float]
-[[cases-ui-open]]
-== Open a new case
-
-Open a new case to keep track of security issues and share their details with
-colleagues.
-
-. Go to *Investigate* -> *Cases*, 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.
-. Give the case a name, and add a description and any relevant tags.
-+
-TIP: In the `Description` area, you can use
-https://www.markdownguide.org/cheat-sheet[Markdown] syntax and insert a
-timeline link (click the icon in the top right corner of the area).
-
-. Choose whether you want alert statuses to sync with the case's status after they are added to the case. This option is enabled by default, but you can still turn it off after creating the case.
-. When ready, create the case.
-. If external connections are configured, you can:
-* Select which connector is used to send the case to an external system
-(`External incident management system`).
-* Send the case to an external system. You can send the case to more than one
-external system.
-
-[role="screenshot"]
-image::images/cases-ui-open.png[Shows an open case]
-
-[float]
-[[cases-ui-manage]]
-== Manage existing cases
-
-From the Cases page, you can search existing cases and filter them by tags, reporter, and status
-(open, in-progress, or closed).
-
-To explore a case, click on its name. You can then:
-
-* <<cases-summary>>
-* Add a new comment
-* <<cases-lens-visualization>>
-* Edit existing comments and the case's description
-* Add a connector (if you did not select one while creating the case)
-* Send updates to external systems (if external connections are configured)
-* Close the case
-* Reopen a closed case
-* Edit tags
-* Refresh the case to retrieve the latest updates
-
-NOTE: Comments can also contain Markdown syntax and Timeline links.
-
-[float]
-[[cases-summary]]
-== Review the case summary
-
-Click on an existing case to access the case 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 more 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.
-
-[role="screenshot"]
-image::images/cases-summary.png[Shows you a summary of the case]
-
-[float]
-[[cases-lens-visualization]]
-== Add a Lens visualization
-
-beta[]
-
-Add a Lens visualization to your case to portray event and alert data through charts and graphs.
-
-[role="screenshot"]
-image::images/add-vis-to-case.gif[Shows how to add a visualization to a case]
-
-To add a Lens visualization to a comment within your case:
-
-. Click the *Visualization* button. The Add visualization dialog appears. 
-. 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.
-
-+
-. Save the visualization to your Visualize Library by clicking the *Save to library* button (optional).
-.. Enter a title and description for the visualization. 
-.. Choose whether 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.
-. After you've finished creating your visualization, click *Save and return* to go back to your case.
-. Click *Preview* to show how the visualization will appear in the case comment.
-. Click *Add Comment* to add the visualization to your case. 
-
-NOTE: Once a visualization has been added to a case, it cannot be modified or deleted. However, you can interact with the visualization by clicking the *Open Visualization* option in the comment menu.
-
-[role="screenshot"]
-image::images/cases-open-vis.png[Shows where the Open Visualization option is]
-
-[float]
-[[cases-export-import]]
-== Export and import cases
-
-Cases can be <<cases-export, exported>> and <<cases-import, imported>> as saved objects through the Kibana {kibana-ref}/managing-saved-objects.html[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.
-
-[float]
-[[cases-export]]
-=== Export a case
-Use the *Export* option to move cases between different Kibana 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, and lens visualizations (which are exported as JSON blobs).
-
-To export a case:
-
-. Open the main menu, click *Stack Management -> Kibana*, then select the *Saved Objects* tab.
-. Search for the case by choosing a saved object type or entering the case title in the search bar.
-. Select one or more cases, then click the *Export* button.
-. 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.
-
-[role="screenshot"]
-image::images/cases-export-button.png[Shows the export saved objects workflow]
-
-[float]
-[[cases-import]]
-=== Import a case
-
-To import a case:
-
-. Open the main menu, click *Stack Management -> Kibana* and then select the *Saved Objects* tab.
-. Click *Import*.
-. Select the NDJSON file containing the exported case and configure the import options.
-. Click *Import*.
-. 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. Alternatively, open the main menu, then go to *Stack Management -> Alerts and Insights -> Rules and Connectors -> Connectors* to access connectors.
-* If the imported case had attached alerts, verify that the alerts’ source documents are present 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.
-
-=========================
-+
+NOTE: From {elastic-sec}, you cannot access cases created in {observability} or Stack Management.