> 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/potential-phishing-has-been-detected.md).
# Potential Phishing has been detected
### Synopsis
| Field | Value |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 2 Hours |
| Deduplication Period | 1 Hour 30 Minutes |
| Required Data | Requires one of the following data sources:
Box Audit Log OR DropBox OR Google Workspace Audit Logs OR Microsoft 365 Emails OR Office 365 Audit OR Okta Audit Log
|
| Detection Modules | Email |
| Detector Tags | Phishing |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566) |
| Severity | Medium |
### Description
This email contains multiple indicators consistent with a phishing attack. The message likely attempts to steal credentials, distribute malware, or trick recipients into performing actions that compromise security through deceptive content or suspicious technical characteristics.
### Attacker's Goals
Trick recipients into revealing sensitive information, hijack the organization, or obtain money through deception.
### Investigative actions
* Review the email headers and metadata of to identify potential spoofing techniques or unusual routing patterns.
* Analyze any URLs or attachments in a secure sandbox environment to detect possible malware or phishing attempts.
* Correlate findings with recent alerts in the SIEM to assess whether similar accumulation patterns are forming.
* Engage potentially affected users to understand if any actions were taken in response to this email, which could increase the overall risk.
* Document and escalate findings if the accumulation of warnings suggests a broader phishing campaign.
### Variations
Potential Brand Impersonation has been detected
**Synopsis**
| Field | Value |
| ----------------- | ----------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566) |
| Severity | Medium |
**Description**
This email appears to impersonate a legitimate brand or service provider to deceive recipients. Attackers often mimic trusted companies like banks, cloud services, or popular brands to steal credentials, distribute malware, or conduct fraudulent activities.
**Attacker's Goals**
Trick recipients into revealing sensitive information, hijack the organization, or obtain money through deception.
**Investigative actions**
* Review the email headers and metadata of to identify potential spoofing techniques or unusual routing patterns.
* Analyze any URLs or attachments in a secure sandbox environment to detect possible malware or phishing attempts.
* Correlate findings with recent alerts in the SIEM to assess whether similar accumulation patterns are forming.
* Engage potentially affected users to understand if any actions were taken in response to this email, which could increase the overall risk.
* Document and escalate findings if the accumulation of warnings suggests a broader phishing campaign.
Potential Spear Phishing has been detected
**Synopsis**
| Field | Value |
| ----------------- | ----------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566) |
| Severity | Medium |
**Description**
This email represents a targeted spear phishing attack aimed at high-value personnel within your organization. These highly personalized attacks often target executives or privileged users to gain unauthorized access to sensitive systems or information.
**Attacker's Goals**
Trick recipients into revealing sensitive information, hijack the organization, or obtain money through deception.
**Investigative actions**
* Review the email headers and metadata of to identify potential spoofing techniques or unusual routing patterns.
* Analyze any URLs or attachments in a secure sandbox environment to detect possible malware or phishing attempts.
* Correlate findings with recent alerts in the SIEM to assess whether similar accumulation patterns are forming.
* Engage potentially affected users to understand if any actions were taken in response to this email, which could increase the overall risk.
* Document and escalate findings if the accumulation of warnings suggests a broader phishing campaign.
Potential Business Email Compromise has been detected
**Synopsis**
| Field | Value |
| ----------------- | ----------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566) |
| Severity | Medium |
**Description**
This email exhibits characteristics of a Business Email Compromise attack, where threat actors impersonate executives or trusted business partners to manipulate recipients into authorizing fraudulent financial transactions or wire transfers.
**Attacker's Goals**
Trick recipients into revealing sensitive information, hijack the organization, or obtain money through deception.
**Investigative actions**
* Review the email headers and metadata of to identify potential spoofing techniques or unusual routing patterns.
* Analyze any URLs or attachments in a secure sandbox environment to detect possible malware or phishing attempts.
* Correlate findings with recent alerts in the SIEM to assess whether similar accumulation patterns are forming.
* Engage potentially affected users to understand if any actions were taken in response to this email, which could increase the overall risk.
* Document and escalate findings if the accumulation of warnings suggests a broader phishing campaign.
Potential Exfiltration has been detected
**Synopsis**
| Field | Value |
| ----------------- | ----------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566) |
| Severity | Medium |
**Description**
This outbound email shows suspicious patterns consistent with data exfiltration attempts. The communication may involve unauthorized transmission of sensitive organizational data to external recipients through email channels.
**Attacker's Goals**
Trick recipients into revealing sensitive information, hijack the organization, or obtain money through deception.
**Investigative actions**
* Review the email headers and metadata of to identify potential spoofing techniques or unusual routing patterns.
* Analyze any URLs or attachments in a secure sandbox environment to detect possible malware or phishing attempts.
* Correlate findings with recent alerts in the SIEM to assess whether similar accumulation patterns are forming.
* Engage potentially affected users to understand if any actions were taken in response to this email, which could increase the overall risk.
* Document and escalate findings if the accumulation of warnings suggests a broader phishing campaign.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/potential-phishing-has-been-detected.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.