> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr/detect-investigate-and-respond-to-threats/managed-services-in-cortex-xdr.md).

# Managed Services in Cortex XDR

The Managed Services page in Cortex XDR centralizes the review, tracking, assignment, and collaboration for threat and status reports sent by Unit 42 security analysts.

The Managed Services page is the central place to review and act on the reports that Unit 42 managed services security analysts and threat hunters send about your Cortex XDR tenant. Use this page to track incoming reports, follow up with the analysts who authored them, and keep the status and ownership of each report current for your team.

Use the Managed Services page to:

* Review incoming reports from your managed service provider. Reports that Unit 42 analysts create for Managed Threat Hunting (MTH) or Managed Detection and Response (MDR) activity appear in this grid. The Type column identifies the kind of report, such as Threat Report, Impact Report, Cyber Hygiene Report, or Monthly Status Report. You can filter the grid by report type.
* Track and update the status of each report as your team triages, investigates, and closes out the activity described in it.
* Assign reports to a specific member of your team so that ownership of follow-up work is clear.
* Collaborate directly with the reporting analyst by adding comments or attachments to a report.
* Find cases that no one is handling so that your team can pick them up.
* Export report data for offline review, record-keeping, or sharing outside Cortex XDR.

The Managed Services hub page is available only if your organization subscribes to Unit 42 Managed Threat Hunting (MTH) or Unit 42 Managed Detection and Response (MDR). The page is located under **Managed Services** in the left navigation menu.

### Prerequisites

To change the status or assignee of a report, or to add comments and attachments, your role must include the Managed Services action permission. Without this permission, you can view reports, but the related controls are unavailable, and right-clicking a report shows only **Copy**.

### Open a report

Click a row to open the report in a side panel. In the side panel, you can:

* Read the full report description.
* Change the status or assignee of the report.
* Click the case ID tag to open the related case in a new browser tab, if the report is linked to a case.
* Review previous comments, and add a new comment or attachment to continue the conversation with the reporting analyst.

If you switch the grid to split view, the selected report opens in a reading pane next to the list instead of in a side panel.

{% hint style="info" %}

### NOTE:

The case ID tag is unavailable if your role doesn't include permissions for cases and issues.
{% endhint %}

### Change the status of a report

Use the right-click menu to update one or more reports at the same time without opening each report.

1. Select the checkbox for each report that you want to update. To update a single report, you can instead right-click its row without selecting any checkboxes.
2. Right-click a report row.
3. Select **Change status**.
4. Select the new status.

The grid refreshes and shows a confirmation message when the update finishes.

{% hint style="info" %}

### NOTE:

If any checkboxes are selected, the action applies to all selected reports, even if you right-click a row that isn't selected. A status is unavailable in the menu if all target reports already have that status.
{% endhint %}

The following statuses are available:

* New
* In Progress
* On Hold
* Resolved False Positive (FP)
* Resolved True Positive (TP)
* Resolved Other
* Resolved Security Testing

### Change the assignee of a report

Assign a report to a specific person on your team so that ownership of the follow-up work is clear.

1. Select the checkbox for each report that you want to update. To update a single report, you can instead right-click its row without selecting any checkboxes.
2. Right-click a report row.
3. Select **Change assignee**.
4. In the **Assignee** field, select a user, or click **Assign to me**. To remove the current assignee, clear the field.
5. Click **Ok**.

The grid refreshes and shows a confirmation message when the update finishes.

### Find unassigned cases

Use **Self managed cases** to find unresolved cases that no one on your team is handling, so that someone can pick them up.

Click **Self managed cases** in the upper right hand corner. The **Cases** page opens in a new browser tab, filtered to show cases that meet all of the following conditions:

* The case isn't resolved.
* The case has no assignee.
* The case was last updated between 180 days ago and 10 minutes ago.

### Switch between Basic mode and Advanced mode

The filter bar above the grid has two modes:

* **Basic mode** is the default. Use it to add simple field conditions, such as **Type**, **Status**, or **Severity**, in a single filter group.
* **Advanced mode** opens a query builder. Use it to create multiple filter groups and to use operators that Basic mode doesn't support, such as "not equal to."

To switch modes, click the mode button at the right side of the filter bar.

If your filter uses more than one filter group, or uses an operator that Basic mode doesn't support, the filter bar stays in Advanced mode and Basic Mode is unavailable. Hover over the button to see the reason.

### Export report data

Click the export icon to download the reports to a CSV file. The file includes only the columns currently shown in the grid, and it applies your current filters, search, and sort order. Narrow the results before you export to limit the file to the reports that you need.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr/detect-investigate-and-respond-to-threats/managed-services-in-cortex-xdr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
