|
| 1 | +--- |
| 2 | +title: Assignee Management |
| 3 | +description: "Assign Datadog users to security findings to manage triage ownership across Cloud Security, Code Security, App and API Protection, and Workload Protection." |
| 4 | +site_support_id: case_management |
| 5 | +products: |
| 6 | +- name: Cloud Security |
| 7 | + url: /security/cloud_security_management/ |
| 8 | + icon: cloud-security-management |
| 9 | +- name: Code Security |
| 10 | + url: /security/code_security/ |
| 11 | + icon: security-code-security |
| 12 | +- name: App and API Protection |
| 13 | + url: /security/application_security/ |
| 14 | + icon: app-sec |
| 15 | +- name: Workload Protection |
| 16 | + url: /security/workload_protection/ |
| 17 | + icon: cloud-security-management |
| 18 | +further_reading: |
| 19 | + - link: "/security/ticketing_integrations/" |
| 20 | + tag: "Documentation" |
| 21 | + text: "Manage security findings with third-party ticketing tools" |
| 22 | + - link: "/incident_response/case_management/" |
| 23 | + tag: "Documentation" |
| 24 | + text: "Case Management" |
| 25 | +--- |
| 26 | + |
| 27 | +{{< product-availability >}} |
| 28 | + |
| 29 | +Assignee management lets you assign a Datadog user directly to a security finding to establish ownership during triage. You can assign a user without creating a [Case][1] or a third-party ticket first. |
| 30 | + |
| 31 | +If a finding is linked to a Case or ticket, the finding's assignee and the linked Case or ticket assignee stay in sync. Cases and tickets remain optional. |
| 32 | + |
| 33 | +## Supported products |
| 34 | + |
| 35 | +You can assign users to findings in the following products: |
| 36 | + |
| 37 | +- [Cloud Security][2] |
| 38 | +- [Code Security][3] |
| 39 | +- [App and API Protection][4] |
| 40 | +- [Workload Protection][5] |
| 41 | + |
| 42 | +## Assign a user to a finding |
| 43 | + |
| 44 | +You can assign a user from the findings explorer, the finding side panel, or the finding detail page: |
| 45 | + |
| 46 | +1. Open a finding, or hover over a finding in the explorer. |
| 47 | +2. In the {{< ui >}}Assignee{{< /ui >}} control, select a Datadog user. |
| 48 | + |
| 49 | +{{< img src="security/assignee_management/assign_finding.png" alt="The Assignee control on a finding with a Datadog user selected" responsive="true" style="width:100%;">}} |
| 50 | + |
| 51 | +To unassign a finding, open the {{< ui >}}Assignee{{< /ui >}} control and clear the selected user. |
| 52 | + |
| 53 | +{{< img src="security/assignee_management/unassign_finding.png" alt="Clearing the selected user from the Assignee control to unassign a finding" responsive="true" style="width:100%;">}} |
| 54 | + |
| 55 | +## Assign multiple findings at once |
| 56 | + |
| 57 | +To assign one user to several findings in a single action: |
| 58 | + |
| 59 | +1. In the findings explorer, select up to 50 findings. |
| 60 | +2. Click {{< ui >}}Assign{{< /ui >}} and select a Datadog user. |
| 61 | +3. If some selected findings already have an assignee, choose how to handle them: |
| 62 | + - {{< ui >}}Exclude Vulnerabilities with Existing Assignees{{< /ui >}}: skip findings that already have an assignee. |
| 63 | + - {{< ui >}}Override Existing Assignees{{< /ui >}}: reassign all selected findings to the new user. |
| 64 | + |
| 65 | + {{< img src="security/assignee_management/bulk_assign_options.png" alt="Bulk assignment dialog with options to exclude vulnerabilities with existing assignees or override existing assignees" responsive="true" style="width:100%;">}} |
| 66 | +4. If any selected findings are linked to shared tickets, Datadog warns you that reassigning updates the ticket assignee and affects all findings linked to those tickets. |
| 67 | + |
| 68 | + {{< img src="security/assignee_management/bulk_assign_shared_ticket_warning.png" alt="Warning that reassigning findings on shared tickets updates the ticket assignee and all linked findings" responsive="true" style="width:100%;">}} |
| 69 | +5. Confirm to apply the assignment. |
| 70 | + |
| 71 | +## Assignees, Cases, and tickets |
| 72 | + |
| 73 | +Assignment works independently of Cases, and the finding assignee and any linked Case or ticket assignee stay in sync. |
| 74 | + |
| 75 | +### Bidirectional sync |
| 76 | + |
| 77 | +When [bidirectional syncing][6] is set up, assigning or unassigning a finding that is linked to a Case or ticket also updates the linked Case or ticket assignee. Assignee changes made in the external tool propagate back to the finding. |
| 78 | + |
| 79 | +Assignee sync is supported for Jira and Linear. ServiceNow ticket assignees are not synced. |
| 80 | + |
| 81 | +### Case creation carryover |
| 82 | + |
| 83 | +When you create a Case for a finding that already has an assignee, the assignee carries over to the new Case. |
| 84 | + |
| 85 | +### Assignee precedence |
| 86 | + |
| 87 | +The finding assignee is resolved as follows: |
| 88 | + |
| 89 | +| Action | Finding assignee outcome | |
| 90 | +|--------|--------------------------| |
| 91 | +| Create a Case for the finding | The finding's assignee is carried over to the Case. | |
| 92 | +| Attach a Case that has an assignee | The Case's assignee takes precedence. | |
| 93 | +| Attach a Case that has no assignee | The finding's assignee is preserved. | |
| 94 | +| Detach or delete the Case | The finding's assignee is preserved. | |
| 95 | + |
| 96 | +### Permissions for linked Cases and tickets |
| 97 | + |
| 98 | +Updating a linked Case or ticket assignee is subject to [Case Management project][7] permissions. If you or the target assignee are not authorized for the Case's project, Datadog still assigns the finding, leaves the Case assignee unchanged, and notifies you that the Case was not updated. |
| 99 | + |
| 100 | +### Shared tickets |
| 101 | + |
| 102 | +When several findings are linked to one ticket, assigning or unassigning one finding's assignee updates the ticket and all other findings linked to that ticket. |
| 103 | + |
| 104 | +## Assignee facet |
| 105 | + |
| 106 | +The following facet is available for filtering findings by assignee: |
| 107 | + |
| 108 | +- {{< ui >}}Assignee{{< /ui >}}: the assigned user's name. |
| 109 | + |
| 110 | +You can query this facet and build dashboards with it. |
| 111 | + |
| 112 | +## Permissions |
| 113 | + |
| 114 | +To assign or unassign findings, you must have the `security_monitoring_findings_write` or `appsec_vm_write` permission. See [Role Based Access Control][8] for more information about Datadog's default roles and granular role-based access control permissions. |
| 115 | + |
| 116 | +## Further reading |
| 117 | + |
| 118 | +{{< partial name="whats-next/whats-next.html" >}} |
| 119 | + |
| 120 | +[1]: /incident_response/case_management/ |
| 121 | +[2]: https://app.datadoghq.com/security/compliance |
| 122 | +[3]: https://app.datadoghq.com/security/code-security |
| 123 | +[4]: https://app.datadoghq.com/security/appsec/inventory/finding |
| 124 | +[5]: https://app.datadoghq.com/security/workload-protection/findings |
| 125 | +[6]: /security/ticketing_integrations/#bidirectional-ticket-syncing |
| 126 | +[7]: /incident_response/case_management/projects/ |
| 127 | +[8]: /account_management/rbac/permissions/#cloud-security-platform |
0 commit comments