> 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/potential-dcsync-by-an-unusual-user.md).
# Potential DCSync by an unusual user
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Windows Event Collector OR XDR Agent with eXtended Threat Hunting (XTH)
|
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Credential Access (TA0006), Defense Impairment (TA0112) |
| ATT\&CK Technique | OS Credential Dumping: DCSync (T1003.006), Rogue Domain Controller (T1207) |
| Severity | Informational |
### Description
Attackers may leverage the domain replication process to extract sensitive information (DCSync).
### Attacker's Goals
An attacker is trying to retrieve Active Directory data, including password hashes.
### Investigative actions
Check whether the replicating account is an account that should initiate a DC synchronization.\* Check the role of the account, and see if it should initiate a DC synchronization.\* Check if the account performing the DCSync is related to a new DC.\* Find the source host of the DCSync (correlate between event 4662 and 4624 based on the field 'Logon ID').\* Check if the account was recently added to an administrative groups/had new sensitive privileges assigned to it.\* Monitor suspicious traffic to/from the host to identify lateral movement or access to sensitive resources.
### Variations
Possible DCSync by an unusual user
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Defense Impairment (TA0112) |
| ATT\&CK Technique | OS Credential Dumping: DCSync (T1003.006), Rogue Domain Controller (T1207) |
| Severity | Low |
**Description**
Attackers may leverage the domain replication process to extract sensitive information (DCSync).
**Attacker's Goals**
An attacker is trying to retrieve Active Directory data, including password hashes.
**Investigative actions**
Check whether the replicating account is an account that should initiate a DC synchronization.\* Check the role of the account, and see if it should initiate a DC synchronization.\* Check if the account performing the DCSync is related to a new DC.\* Find the source host of the DCSync (correlate between event 4662 and 4624 based on the field 'Logon ID').\* Check if the account was recently added to an administrative groups/had new sensitive privileges assigned to it.\* Monitor suspicious traffic to/from the host to identify lateral movement or access to sensitive resources.
---
# 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/potential-dcsync-by-an-unusual-user.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.