> 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/cortex-advanced-email-security/threat-inbox.md).

# Threat Inbox

Use Threat Inbox to review, investigate, and respond to suspected email threats in Cortex XSIAM.

{% hint style="info" %}

### Notice

Requires the Advanced Email Security module.
{% endhint %}

The **Threat Inbox** provides you with a centralized environment to monitor, triage, investigate, and remediate email-based threats across your organization. It provides immediate context on which emails were suspicious and why they were flagged. It enables you to view and act on malicious emails within a selected timeframe and pivot to other views for forensic investigations. Find the inventory of malicious emails under **Modules → Email Security → Threat Inbox**.

The page displays three widgets, which simplify email threat triage by providing immediate context on detected threats.

The page also displays high-context inventories of malicious email threats, whether discovered by detection rules under the **Malicious** tab, or reported by users under the **User Reported** tab. If an email was tagged as malicious and then reported by a user, it only appears in the **User Reported** tab.

The widgets and the tabs are interactive. When you apply a filter to any of the widgets, the other widgets and the tables in the tabs update automatically to reflect the filtered data. When you switch from one tab to another or filter the tables, the widgets update automatically to summarize the filtered tables.

### Malicious email widgets <a href="#malicious-email-widgets" id="malicious-email-widgets"></a>

* **Email Verdict Overview**: How many malicious emails were tagged out of all the emails collected. Malicious emails are emails for which at least one issue was created with a severity level of Medium or above. Use the filters for the following cases:
  * Change the duration to last 24 hours, last 7 days, last 30 days, or a custom duration to update the displayed data according to your preferred time frame. The maximum is 30 days.
  * Add a filter to update the display in the format: filtered/total malicious/total scanned emails.
* **Detection Tags**: Top five detection tags that appear in the displayed emails. Click the widget to get more detailed information in the malicious emails table below.
* **Remediation Type**: How many emails have a configured remediation policy. Click the widget to get more detailed information in the malicious emails table below.

### Malicious emails tables

The tables under **Malicious** tab and the **User Reported** tab both display details of emails tagged as malicious with a few differences. The tables can be filtered by any of the following fields:

* **Detected at**: Date and time of detection.
* **Subject**: Subject line of the email.
* **Direction**: Inbound or outbound.
* **Internet Message ID**: Unique identifier of the email.
* **URLs**: Number of URLs in the email message.
* **Attachments**: Number of attachments in the email message.
* **Issues Breakdown**: Number of issues generated based on the email and their severities.
* **Severity**: Maximum severity of all issues related to this email.
* **Detection Tags**: Tags in the issues that are based on this email.
* **Rarity**: How rare an email exchange between the sender and recipient is. For emails with multiple recipients, this reflects the strictest rarity level (weakest connection) among all sender-recipient pairs.
* **Source**: Source of the email data.
* **Remediation Type**: Indicates if the email has remediation actions configured.
* **Remediation Status**: Which remediation actions were run.
* **Case ID**: Associated Case ID.
* **Status**: Reflection of the statuses of all issues based on this email. The status is **Resolved** only when all related issues are resolved; otherwise, it remains **Open**.
* **Mailboxes Exposed (Reported):** Appears only in the **User Reported** tab. Displays how many users received the email and how many of them reported it as phishing. The email row appears under **User Reported** even if only one recipient reports it.

Click each row in the table to see the full details of the specific email.

### Malicious email view

Click any row in the Malicious emails tables to display email data, enriched with insights in the following tabs:

* **Overview**: General metadata including Internet Message ID, Subject, Severity, Generated Issue Count, Rarity, Remediation Action Taken, Source, Case ID, and Status. Hover next to any field to copy its value. The AI Summary, which appears only for malicious emails listed in the **Malicious** tab, is a high-level summary of the AI based analysis of the email.
* **Message**: The full body of the email and any attachments. Detected sentiments are categorized and highlighted in different colors. Click **View as Image** to see a snapshot of the email. If there were any QR codes in the message, they are also displayed here.
* **Sender and Domain**: Raw email headers, SPF, DKIM, and DMARC authentication indicators, Sender information, Network information, and Domain intelligence. Hover next to each field name to copy the values for further investigation.
* **URLs**: Included malicious URLs. For each URL, you can see the full address, domain, category, popularity and the verdict. The URLs that were embedded or attached as QR codes are marked with a small QR code symbol. You can further filter the results in the table.
* **Attachments**: Included attachments which are determined to be malware.
* **Issues**: Issues that were generated based on this email. The fields displayed are Observation Time, Name, Detection Method, Severity, and Description.
* **AI Analyst**: (Beta mode) Appears only for malicious emails reported by users. An AI-generated analysis designed to accelerate threat triage and incident response. Located directly within your workspace, this tool automatically synthesizes critical email data to provide immediate context on potential attacks. Each reported email analysis extracts and highlights the targeted recipients, embedded URLs, attached files, supporting threat evidence, and the suspected intent behind the malicious message, allowing you to quickly evaluate risks and make informed decisions without manually parsing the raw email contents.

### Quick remediation actions <a href="#quick-remediation-actions" id="quick-remediation-actions"></a>

Use the more options icon at the top of the email card to take the following quick remediation actions:

* **Open Causality Card**: Opens the causality card of the related issue that has the highest severity value. When the highest severity value is the same for a number of issues, opens the latest issue card.
* **Soft Delete Email**
* **Undelete Email**
* **Report As Phishing**
* **Send Warning Email**
* **Move Email to Folder**
* **Mark as Safe**: Changes the status of all issues related to the email as Resolved.
* **Mark as Malicious**


---

# 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/cortex-advanced-email-security/threat-inbox.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.
