> 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/abnormal-user-login-to-domain-controller.md).

# Abnormal User Login to Domain Controller

### Synopsis

| Field                | Value                                                                 |
| -------------------- | --------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                               |
| Training Period      | 30 Days                                                               |
| Test Period          | N/A (single event)                                                    |
| Deduplication Period | 1 Day                                                                 |
| Required Data        | XDR Agent                                                             |
| Detection Modules    | Identity Analytics                                                    |
| ATT\&CK Tactic       | Lateral Movement (TA0008), Privilege Escalation (TA0004)              |
| ATT\&CK Technique    | Valid Accounts (T1078), Use Alternate Authentication Material (T1550) |
| Severity             | Informational                                                         |

### Description

A user account has successfully logged on to a Domain Controller (DC), generating a Windows Event Log. This may be a sign of DC and Active Directory (AD) compromise.

### Attacker's Goals

A malicious user may attempt to access a domain controller to access and control Active Directory.

### Investigative actions

* Ensure that the user is not a Domain Admin account. By default, Administrator groups have permission to access the domain controller.
* Check if the user is a service account that accesses a domain controller as part of its normal behavior.
* Verify that the user is not authenticating to group policy.

### Variations

<details>

<summary>Rare RDP User Login to Domain Controller by an Abnormal Department</summary>

**Synopsis**

| Field             | Value                                                                 |
| ----------------- | --------------------------------------------------------------------- |
| ATT\&CK Tactic    | Lateral Movement (TA0008), Privilege Escalation (TA0004)              |
| ATT\&CK Technique | Valid Accounts (T1078), Use Alternate Authentication Material (T1550) |
| Severity          | Medium                                                                |

**Description**

A user account has successfully interactively logged on to a Domain Controller (DC), generating a Windows Event Log. This may be a sign of DC and Active Directory (AD) compromise.

**Attacker's Goals**

A malicious user may attempt to access a domain controller to access and control Active Directory.

**Investigative actions**

* Ensure that the user is not a Domain Admin account. By default, Administrator groups have permission to access the domain controller.
* Check if the user is a service account that accesses a domain controller as part of its normal behavior.
* Verify that the user is not authenticating to group policy.

</details>

<details>

<summary>Abnormal RDP User Login to Domain Controller</summary>

**Synopsis**

| Field             | Value                                                                 |
| ----------------- | --------------------------------------------------------------------- |
| ATT\&CK Tactic    | Lateral Movement (TA0008), Privilege Escalation (TA0004)              |
| ATT\&CK Technique | Valid Accounts (T1078), Use Alternate Authentication Material (T1550) |
| Severity          | Low                                                                   |

**Description**

A user account has successfully interactively logged on to a Domain Controller (DC), generating a Windows Event Log. This may be a sign of DC and Active Directory (AD) compromise.

**Attacker's Goals**

A malicious user may attempt to access a domain controller to access and control Active Directory.

**Investigative actions**

* Ensure that the user is not a Domain Admin account. By default, Administrator groups have permission to access the domain controller.
* Check if the user is a service account that accesses a domain controller as part of its normal behavior.
* Verify that the user is not authenticating to group policy.

</details>

<details>

<summary>RDP User Login to Domain Controller</summary>

**Synopsis**

| Field             | Value                                                                 |
| ----------------- | --------------------------------------------------------------------- |
| ATT\&CK Tactic    | Lateral Movement (TA0008), Privilege Escalation (TA0004)              |
| ATT\&CK Technique | Valid Accounts (T1078), Use Alternate Authentication Material (T1550) |
| Severity          | Informational                                                         |

**Description**

A user account has successfully logged on to a Domain Controller (DC), generating a Windows Event Log. This may be a sign of DC and Active Directory (AD) compromise.

**Attacker's Goals**

A malicious user may attempt to access a domain controller to access and control Active Directory.

**Investigative actions**

* Ensure that the user is not a Domain Admin account. By default, Administrator groups have permission to access the domain controller.
* Check if the user is a service account that accesses a domain controller as part of its normal behavior.
* Verify that the user is not authenticating to group policy.

</details>

<details>

<summary>Abnormal User Login to Domain Controller by an Abnormal Department</summary>

**Synopsis**

| Field             | Value                                                                 |
| ----------------- | --------------------------------------------------------------------- |
| ATT\&CK Tactic    | Lateral Movement (TA0008), Privilege Escalation (TA0004)              |
| ATT\&CK Technique | Valid Accounts (T1078), Use Alternate Authentication Material (T1550) |
| Severity          | Informational                                                         |

**Description**

A user account has successfully logged on to a Domain Controller (DC), generating a Windows Event Log. This may be a sign of DC and Active Directory (AD) compromise.

**Attacker's Goals**

A malicious user may attempt to access a domain controller to access and control Active Directory.

**Investigative actions**

* Ensure that the user is not a Domain Admin account. By default, Administrator groups have permission to access the domain controller.
* Check if the user is a service account that accesses a domain controller as part of its normal behavior.
* Verify that the user is not authenticating to group policy.

</details>


---

# 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/abnormal-user-login-to-domain-controller.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.
