> 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/unusual-adfs-remote-synchronization-network-connections-from-non-adfs-server.md).

# Unusual ADFS Remote Synchronization network connections from non-ADFS server

### Synopsis

| Field                | Value                                                                                                   |
| -------------------- | ------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                 |
| Training Period      | 30 Days                                                                                                 |
| Test Period          | N/A (single event)                                                                                      |
| Deduplication Period | 1 Day                                                                                                   |
| Required Data        | <p>Requires one of the following data sources:<br>Palo Alto Networks Firewall EAL Logs OR XDR Agent</p> |
| Detector Tags        | Active Directory Federation Services Analytics                                                          |
| ATT\&CK Tactic       | Credential Access (TA0006), Lateral Movement (TA0008)                                                   |
| ATT\&CK Technique    | Forge Web Credentials: SAML Tokens (T1606.002), Exploitation of Remote Services (T1210)                 |
| Severity             | Low                                                                                                     |

### Description

Detected an unauthorized configuration sync request to the ADFS Policy Store from a non-ADFS server, step for forging SAML tokens in a Golden SAML attack.

### Attacker's Goals

The attack goal is to forge a valid SAML token to impersonate any user and gain persistent, unauthorized access to cloud resources, effectively bypassing MFA and standard security controls.

### Investigative actions

* Correlate this network event with AD FS service account activity. The attacker must use the service account's credentials to authenticate this request.
* Check for a possible DCSync alerts.
* Check alerts that related to ADFS server.
* Check for other correlated alerts on on-premises systems that may be related to the Golden SAML attack.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Inspect the source machine for the presence of tools like AADInternals or custom SOAP-based scripts.


---

# 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/unusual-adfs-remote-synchronization-network-connections-from-non-adfs-server.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.