> 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-spf-result.md).
# Suspicious SPF Result
### 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 | Spoofing |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | Social Engineering: Impersonation (T1684.001) |
| Severity | Informational |
### Description
The email has a suspicious SPF result of fail, soft fail, or policy, which may indicate a potential domain misconfiguration or spoofing.
### Attacker's Goals
Impersonate internal users or familiar individuals.
* Trick users into clicking on malicious links or attachments.
### Investigative actions
* Check the email address for any unusual spellings.
* Check the email address for any missing letters.
* Verify the sender's domain to confirm its legitimacy.
* Examine the sender's IP address and reputation.
* Verify the domain's connection to the IP address and investigate the reason SPF didn't pass.
* Verify whether the sender's IP address has appeared in different log sources before.
* Verify if the sender's IP address is identifiable.
* 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.
### Variations
Internal domain SPF deviation
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | Social Engineering: Impersonation (T1684.001) |
| Severity | Informational |
**Description**
* An email was sent from an internal root domain that has historically passed SPF checks, but returned a suspicious SPF result of fail, soft fail, or policy for the first time in the past 30 days.
* This deviation may indicate an attempt to spoof or impersonate a trusted internal sender, a tactic commonly associated with BEC and internal phishing.
* Such a sudden SPF outcome from a typically trusted domain warrants further investigation.
**Attacker's Goals**
Impersonate internal users or familiar individuals.
* Trick users into clicking on malicious links or attachments.
**Investigative actions**
* Check the email address for any unusual spellings.
* Check the email address for any missing letters.
* Verify the sender's domain to confirm its legitimacy.
* Examine the sender's IP address and reputation.
* Verify the domain's connection to the IP address and investigate the reason SPF didn't pass.
* Verify whether the sender's IP address has appeared in different log sources before.
* Verify if the sender's IP address is identifiable.
* 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.
Known domain SPF deviation
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | Social Engineering: Impersonation (T1684.001) |
| Severity | Informational |
**Description**
* An email was sent from a domain that has historically passed SPF checks, but returned a suspicious SPF result of fail, soft fail, or policy for the first time in the past 30 days.
* This deviation may indicate an attempt to spoof or impersonate a legitimate external sender.
* Such a sudden SPF outcome from a previously trusted external domain warrants further investigation.
**Attacker's Goals**
Impersonate internal users or familiar individuals.
* Trick users into clicking on malicious links or attachments.
**Investigative actions**
* Check the email address for any unusual spellings.
* Check the email address for any missing letters.
* Verify the sender's domain to confirm its legitimacy.
* Examine the sender's IP address and reputation.
* Verify the domain's connection to the IP address and investigate the reason SPF didn't pass.
* Verify whether the sender's IP address has appeared in different log sources before.
* Verify if the sender's IP address is identifiable.
* 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/suspicious-spf-result.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.