> 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/well-known-brand-in-sender-headers-with-header-inconsistencies.md).

# Well-known brand in sender headers with header inconsistencies

### Synopsis

| Field                | Value                    |
| -------------------- | ------------------------ |
| Activation Period    | 14 Days                  |
| Training Period      | 30 Days                  |
| Test Period          | N/A (single event)       |
| Deduplication Period | 1 Day                    |
| Required Data        | Microsoft 365 Emails     |
| Detection Modules    | Email                    |
| Detector Tags        | Brand Impersonation      |
| ATT\&CK Tactic       | Defense Evasion (TA0005) |
| ATT\&CK Technique    | Impersonation (T1656)    |
| Severity             | Informational            |

### Description

Sender headers include a well-known brand with header inconsistencies indicating possible impersonation.

### Attacker's Goals

Impersonate known legitimate brands or other technological entities to trick recipients into disclosing information or executing malicious code unwillingly.

### Investigative actions

* Identify the specific emails responsible for the accumulation of these alerts.
* Review their headers and content for patterns or anomalies.
* Assess the email's context and attack techniques to determine the potential risk.
* Review the email headers and metadata of each flagged email 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.
* Engage potentially affected users to understand if any actions were taken in response to these emails, which could increase the overall risk.
* Document and escalate findings in case this is a broader phenomenon.


---

# 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/well-known-brand-in-sender-headers-with-header-inconsistencies.md?ask=<question>&goal=<endgoal>
```

`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.