> 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/possible-pass-the-hash.md).

# Possible Pass-the-Hash

### 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)                                        |
| ATT\&CK Technique    | Use Alternate Authentication Material: Pass the Hash (T1550.002) |
| Severity             | Low                                                              |

### Description

An account was successfully logged on to with new credentials. This login type is rare and may be an attacker's attempt to pass-the-hash and move laterally within a network.

### Attacker's Goals

An attacker is attempting to steal credentials and move laterally within a network.

### Investigative actions

* Audit all login events and review for discrepancies.
* Look for LSASS process access, an indication of an attacker attempting to obtain password hashes.
* Check for the RunAs command with the /netonly option.


---

# 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/possible-pass-the-hash.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.