> 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/analytics-alerts/alerts-by-name/saas-email-was-reported-by-the-user-or-administrator-as-a-phishing-attempt.md).

# SAAS - Email was reported by the user or administrator as a phishing attempt

### Synopsis

| Field                | Value                    |
| -------------------- | ------------------------ |
| Activation Period    | 14 Days                  |
| Training Period      | 30 Days                  |
| Test Period          | N/A (single event)       |
| Deduplication Period | 1 Hour                   |
| Required Data        | Office 365 Audit         |
| Detection Modules    | Email                    |
| ATT\&CK Tactic       | Collection (TA0009)      |
| ATT\&CK Technique    | Email Collection (T1114) |
| Severity             | Informational            |

### Description

An email reported by the user or administrator as a phishing attempt has been detected.

### Attacker's Goals

Trick the user into interacting with a malicious email by disguising it as legitimate, potentially leading to credential theft, malware infection, or data exfiltration.

### Investigative actions

* Analyze the sender's IP address and domain reputation.
* Check if the sender has appeared in other logs or alerts across the organization.
* Review any URLs or attachments for signs of phishing, malware, or command-and-control communication.
* Correlate user actions (e.g., link clicks, file downloads) to assess potential compromise.
* Determine whether similar emails were sent to other users to identify a broader campaign.

### Variations

<details>

<summary>SAAS - Phishing report with suspicious verdict on internal domain sender</summary>

**Synopsis**

| Field             | Value                    |
| ----------------- | ------------------------ |
| ATT\&CK Tactic    | Collection (TA0009)      |
| ATT\&CK Technique | Email Collection (T1114) |
| Severity          | Low                      |

**Description**

An email with an internal sender domain was reported as a phishing attempt.This may indicate either a compromised internal account or an external attacker impersonating an internal user.

**Attacker's Goals**

Trick the user into interacting with a malicious email by disguising it as legitimate, potentially leading to credential theft, malware infection, or data exfiltration.

**Investigative actions**

* Analyze the sender's IP address and domain reputation.
* Check if the sender has appeared in other logs or alerts across the organization.
* Review any URLs or attachments for signs of phishing, malware, or command-and-control communication.
* Correlate user actions (e.g., link clicks, file downloads) to assess potential compromise.
* Determine whether similar emails were sent to other users to identify a broader campaign.

</details>

<details>

<summary>SAAS - Phishing report with with suspicious verdict</summary>

**Synopsis**

| Field             | Value                    |
| ----------------- | ------------------------ |
| ATT\&CK Tactic    | Collection (TA0009)      |
| ATT\&CK Technique | Email Collection (T1114) |
| Severity          | Low                      |

**Description**

An email with a Malware/Block verdict reported by the user or administrator has been detected.

**Attacker's Goals**

Trick the user into interacting with a malicious email by disguising it as legitimate, potentially leading to credential theft, malware infection, or data exfiltration.

**Investigative actions**

* Analyze the sender's IP address and domain reputation.
* Check if the sender has appeared in other logs or alerts across the organization.
* Review any URLs or attachments for signs of phishing, malware, or command-and-control communication.
* Correlate user actions (e.g., link clicks, file downloads) to assess potential compromise.
* Determine whether similar emails were sent to other users to identify a broader campaign.

</details>


---

# 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/analytics-alerts/alerts-by-name/saas-email-was-reported-by-the-user-or-administrator-as-a-phishing-attempt.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.