> 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/rarely-seen-sender-address-in-the-organization.md).

# Rarely seen sender address in the organization

### 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                                              |
| ATT\&CK Tactic       | Reconnaissance (TA0043), Initial Access (TA0001)   |
| ATT\&CK Technique    | Phishing for Information (T1598), Phishing (T1566) |
| Severity             | Informational                                      |

### Description

An email was received from a sender that has not been observed in the organization in the last 30 days.

### Attacker's Goals

Aim to steal sensitive information

* Trick recipients into downloading harmful payloads
* Aim to gain unauthorized access to the organization's systems.

### Investigative actions

* Check the email address for any unusual spellings, missing letters, or unknown domains.
* If the message contains attachments or links, scrutinize them for any suspicious indications.
* Monitor further actions taken, such as file downloads or access to potentially malicious links.


---

# 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/rarely-seen-sender-address-in-the-organization.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.