Update documentation for security ticketing integration

content/en/security/ticketing_integrations.md

@@ -14,6 +14,16 @@
 - name: Code Security
   url: /security/code_security/
   icon: security-code-security
+- name: Cloud Security
+  url: /security/cloud_security_management/
+  icon: cloud-security-management
+further_reading:
+  - link: "/api/latest/security-monitoring/#create-cases-for-security-findings"
+    tag: "API"
+    text: "Ticketing integration API"
+  - link: "/incident_response/case_management/"
+    tag: "Documentation"
+    text: "Case Management"
 ---
 
 {{< product-availability >}}
@@ -25,41 +35,49 @@
 
 ## Case management and security products
 
-Case Management is supported for all security products that use signals:
+Case Management is supported for all security products that use signals or findings:
 
+- Code Security (in [Findings][5])
+- Cloud Security (in [Findings][11])
 - Cloud SIEM (in [Signals][4])
-- Code Security (in [Vulnerabilities][5])
-- App and API Protection (in [Signals][6])
-- Workload Protection (in [Signals][7])
+- App and API Protection (in [Signals][6] and [Findings][12])
+- Workload Protection (in [Signals][7] and [Findings][13])
+
+Open any signal or finding in these products or do a bulk selection of findings in the explorers, and use the **Create Ticket** button to create a case in Datadog.
 
-Open any signal in these products and use the **Create Case** button to create a case in Datadog.
 
 ## Bidirectional ticket syncing with Jira
 
 Bidirectional syncing enables you to update Jira tickets automatically when changes occur in Datadog, and update some Datadog information when changes occur in Jira.
 
 ### Supported products
 
-Bidirectional syncing is supported for the following Code Security vulnerability categories:
+Bidirectional syncing is supported for the following Code and Cloud Security finding categories:
 
 - Libraries (SCA)
 - Static Code (SAST)
+- Runtime Code (IAST)
 - Secret Scanning (SDS)
 - Infrastructure as Code (IaC)
+- Misconfigurations
+- Identity Risks
+- Host and Container Vulnerabilities
+- App and API Protection
+- Workload Protection
 
 ### Single source of truth
 
-Bidirectional syncing with Jira enables you to sync Jira tickets with Datadog cases, but Datadog is the single source of truth for issue resolution.
+Bidirectional syncing with Jira enables you to sync Jira tickets with Datadog cases. However, Datadog is the single source of truth for issue detection and resolution.
 
-A Datadog finding's related Jira ticket can be closed manually, but a Datadog finding remains open if Datadog cannot confirm that the issue is fixed. This restriction ensures that a finding is not closed and removed from the list of signals when someone closes a related Jira ticket.
+A Datadog finding's related Jira ticket can be closed manually. However, the Datadog finding remains open if Datadog cannot confirm that the issue is fixed. This restriction ensures that a finding is not closed and removed when someone closes a related Jira ticket.
 
 Closing a Datadog case without remediation does not close the finding either.
 
-Remediation of the finding in Datadog or defining an exception by muting the finding are the only ways to close a finding. Once the finding is remediated, its related cases and Jira tickets are closed.
+Remediation of the finding in Datadog or defining an exception by [muting the finding][14] are the only ways to close a finding. After the finding is remediated, its related cases and Jira tickets are closed.
 
 ### Set up bidirectional syncing
 
-The following steps set up bidirectional syncing with Jira and use Code Security vulnerabilities to verify that setup is successful.
+The following steps set up bidirectional syncing with Jira and verify that setup is successful.
 
 1. Set up the following prerequisites in your Datadog account, or verify that they are set up already. The prerequisites are listed in their setup order.
    1. The [Datadog Jira integration][2].
@@ -70,44 +88,48 @@
       2. In **Title**, select **Two-way sync**.
       3. Complete the remaining settings, and then click **Save changes**.
 2. Verify that bidirectional Case Management integration with Jira is working:
-   1. Open Code Security [Vulnerabilities][5].
-   2. Open any vulnerability.
-   3. Locate the **Create Ticket** option. The option is available in **Next Steps** or **Repositories** (in **Libraries (SCA)**).
+   1. Open [any product supporting bidirectional ticket syncing][20].
+   2. Open any Security finding.
+   3. Locate the **Create Ticket** option. The option is available in **Next Steps** or **Repositories** (in **Libraries (SCA)**). The button opens a **Create Ticket** modal.
    4. Click the **Jira** tab.
-   5. Verify the **Sync with Datadog (via Case Management)** section exists.
+   5. Verify that the **Case Management  <-> Jira Integration** section exists and bidirectional sync is enabled.
+
+{{< img src="security/jira_modal.png" alt="Modal used to create a Jira ticket for a Security finding, with bidirectional sync enabled." responsive="true" style="width:50%;">}}
 
 You are ready to start creating bidirectional Case Management tickets.
 
-If you do not see the **Sync with Datadog (via Case Management)** section, ensure that you have set up the prerequisites.
+If you do not see the **Case Management  <-> Jira Integration** section, ensure that you have completed the prerequisites.
 
-### Create bidirectional Case Management tickets
+### Create bidirectional tickets
 
-The following steps create a bidirectional Case Management ticket.
+The following steps create a bidirectional ticket for a Security finding.
 
-1. Open Code Security [Vulnerabilities][5].
-2. Open any vulnerability.
-3. Locate the **Create Ticket** option. The option is available in **Next Steps** or **Repositories** (in **Libraries (SCA)**).
-4. Click the **Jira** tab. You can use a new or existing ticket. Let's look at creating new Jira ticket.
-5. In **Sync with Datadog (via Case Management)**, complete the following settings:
+1. Open [any product supporting bidirectional ticket syncing][20].
+2. Open any Security finding.
+3. Locate the **Create Ticket** option. The option is available in **Next Steps** or **Repositories** (in **Libraries (SCA)**). The button opens a **Create Ticket** modal.
+4. Create ticket for any third-party tool supported (see sections below)
+
+{{% collapse-content title="Jira ticket" level="h4" expanded=false %}}
+1. Click the **Jira** tab. You can use a new or existing ticket. Let's look at creating a new Jira ticket.
+2. In **Case Management  <-> Jira Integration**, complete the following settings:
    1. **Case Management project:** select a Case Management project that has [Jira integration enabled][3].
    2. **Jira account:** select the Jira account where you want the ticket created.
    3. **Project:** select the Jira project to use.
    4. **Issue type:** select the Jira issue type to create.
-6. To add more fields to the Jira ticket Datadog creates, use **Add Optional Field** to add the fields.
-7. Click **Create Ticket**.
+3. To add more fields to the Jira ticket Datadog creates, use **Add Optional Field** to add the fields.
+4. Click **Create Ticket**.
 
 Notes:
-
-- Once you select a **Case Management project**, you can click **Edit integration** to verify that the integration is configured with **Two-way sync**.
 - Bidirectional sync with Jira is available for certain Jira ticket attributes, such as status, assignee, and comments, but not all Jira fields are available.
+{{% /collapse-content %}}
 
 ### Manage bidirectional Case Management tickets
 
-Existing bidirectional Jira tickets are listed in a signal or vulnerability's **Ticketing** or **Next Steps** sections.
+Existing bidirectional Jira tickets are listed in the finding's **Ticketing** or **Next Steps** sections.
 
-Here's an example from a Static Code (SAST) vulnerability:
+Here's an example from a Static Code (SAST) finding:
 
-{{< img src="security/bidir-jira-existing.png" alt="signal with existing Jira ticket: in the Next Steps section, under Ticket Created, a pill with the Jira logo and text 'CJT-16'" responsive="true" style="width:100%;">}}
+{{< img src="security/bidir-jira-existing.png" alt="finding with existing Jira ticket: in the Next Steps section, under Ticket Created, a pill with the Jira logo and text 'CJT-16'" responsive="true" style="width:100%;">}}
 
 Hover over the Jira ticket to see its details.
 
@@ -119,7 +141,14 @@
 
 In **Datadog Associated Case**, the related Datadog case is provided. Click the case name to open it in [Case Management][1].
 
-Deleting a case does not delete related Jira tickets, but deleting a case project detaches all tickets from related signals.
+#### Automatic detachment and ticket opening/closing
+
+Archiving a case does not delete related Jira tickets, but deleting a case project detaches all tickets from related Security findings.
+
+Detaching a ticket from a Security finding does not delete it.
+
+If there are no open findings left attached to a ticket (because they are all detached or resolved or muted), it is automatically closed.
+Similarly, if at least one open finding is attached to a closed ticket (because it was attached or detected again or unmuted), it is automatically reopened.
 
 ### Bidirectional Case Management facets
 
@@ -132,14 +161,32 @@
 
 You can query attributes and create dashboards using these facets.
 
+## Ticketing integration API
+
+The link between Datadog Cases and existing Security findings can be managed with the public API.
+
+Dedicated endpoints allow users to [create Datadog case for existing security findings][15], [attach security findings to an existing Datadog case][16], and [detach security findings from their case][17].
+
+Users can also [create Jira issues for security findings][18] and [attach security findings to a Jira issue][19].
+
 
 [1]: /incident_response/case_management/
 [2]: /integrations/jira/
-[3]: /incident_response/case_management/notifications_integrations/#third-party-tickets
-[4]: https://app.datadoghq.com/security/siem/signals?column=time&order=desc&viz=stream
-[5]: https://app.datadoghq.com/security/appsec/vm/library
-[6]: https://app.datadoghq.com/security/appsec/signals?query=%40workflow.rule.type%3A%22Application%20Security%22&viz=stream
-[7]: https://app.datadoghq.com/security/workload-protection/signals?query=%40workflow.rule.type%3A%22Workload%20Security%22
+[3]: /incident_response//case_management/notifications_integrations/#third-party-tickets
+[4]: https://app.datadoghq.com/security/siem/signals
+[5]: https://app.datadoghq.com/security/code-security
+[6]: https://app.datadoghq.com/security/appsec/signals
+[7]: https://app.datadoghq.com/security/workload-protection/signals
 [8]: /integrations/jira/#configure-a-jira-webhook
 [9]: /incident_response/case_management/projects/
 [10]: /security/ticketing_integrations/#prerequisites
+[11]: https://app.datadoghq.com/security/compliance
+[12]: https://app.datadoghq.com/security/appsec/inventory/finding
+[13]: https://app.datadoghq.com/security/workload-protection/findings
+[14]: https://app.datadoghq.com/security/automation_pipelines/mute
+[15]: /api/latest/security-monitoring/#create-cases-for-security-findings
+[16]: /api/latest/security-monitoring/#attach-security-findings-to-a-case
+[17]: /api/latest/security-monitoring/#detach-security-findings-from-their-case
+[18]: /api/latest/security-monitoring/#create-jira-issues-for-security-findings
+[19]: /api/latest/security-monitoring/#attach-security-findings-to-a-jira-issue
+[20]: /security/ticketing_integrations/#supported-products