> 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/suspicious-theme-and-sentiment-in-email.md).
# Suspicious theme and sentiment in email
### Synopsis
| Field | Value |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Hour |
| 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 | Impact (TA0040) |
| ATT\&CK Technique | Financial Theft (T1657) |
| Severity | Informational |
### Description
The email's body has a theme and sentiment that may indicate a malicious attempt.
### 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 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/suspicious-theme-and-sentiment-in-email.md?ask=&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.