> 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-xsiam/configure-cortex-xsiam/multi-tenant/about-managed-threat-hunting/set-up-managed-threat-hunting.md).

# Set up Managed Threat Hunting

Set up Cortex XSIAM Managed Threat Hunting by approving tenant pairing and configuring notification emails for threat reports and inquiries.

To get started with Managed Threat Hunting:

1. Open the Cortex XSIAM tenant and approve the pairing request sent to your tenant.
   1. Navigate to **Notifications** and locate the **Request for Pairing** notification.
   2. Select **Approve** and then **Yes** to confirm.

      After the request is approved, Cortex XSIAM displays the Managed Threat Hunting label at the top of the page.
2. Configure notification emails for the impact reports and threat inquiries you want to send.
   1. Select Settings → Configurations → **Managed Services**.
   2. Enter one or more email addresses to which you want to send reports and inquires and **ADD** each one.
   3. **Save** your changes.
3. Test the email, by going to your defined email address mailbox, and locate the **Welcome to the Palo Alto Networks Cortex XSIAM Managed Threat Hunting Service** email. If you did not receive the email, contact Customer Support.
4. (Optional) If desired, forward Managed Threat Hunting alerts to external sources such as email or slack from the Settings → Configurations → General → **Notifications** page.

   This forwards the alert and the detailed report in a PDF format.


---

# 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-xsiam/configure-cortex-xsiam/multi-tenant/about-managed-threat-hunting/set-up-managed-threat-hunting.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.
