> 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/authentication-attempt-from-a-dormant-account.md).

# Authentication Attempt From a Dormant Account

### Synopsis

| Field                | Value                                                                                                       |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                     |
| Training Period      | 30 Days                                                                                                     |
| Test Period          | N/A (single event)                                                                                          |
| Deduplication Period | 31 Days                                                                                                     |
| Required Data        | <p>Requires one of the following data sources:<br>Palo Alto Networks Firewall traffic Logs OR XDR Agent</p> |
| ATT\&CK Tactic       | Defense Evasion (TA0005)                                                                                    |
| ATT\&CK Technique    | Valid Accounts (T1078)                                                                                      |
| Severity             | Informational                                                                                               |

### Description

A dormant user account tried to authenticate to a service using a TGS after having been unused for a year or more. This may indicate the account is misused by an attacker.

### Attacker's Goals

Use a compromised user account that has not been used in a long time and therefore less likely to be noticed.

### Investigative actions

* See whether the service authentication was successful.
* Confirm that the activity is benign (e.g. the user returned from a long leave of absence).
* Check whether you have issues with your Cloud Identity Engine failing to sync data from Active Directory.

### Variations

<details>

<summary>Authentication Attempt From a Dormant Account to a sensitive server</summary>

**Synopsis**

| Field             | Value                    |
| ----------------- | ------------------------ |
| ATT\&CK Tactic    | Defense Evasion (TA0005) |
| ATT\&CK Technique | Valid Accounts (T1078)   |
| Severity          | Low                      |

**Description**

A dormant user account tried to authenticate to a service using a TGS after having been unused for a year or more. This may indicate the account is misused by an attacker on a sensitive server.

**Attacker's Goals**

Use a compromised user account that has not been used in a long time and therefore less likely to be noticed.

**Investigative actions**

* See whether the service authentication was successful.
* Confirm that the activity is benign (e.g. the user returned from a long leave of absence).
* Check whether you have issues with your Cloud Identity Engine failing to sync data from Active Directory.

</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/authentication-attempt-from-a-dormant-account.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.
