> 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/cached-credentials-discovery-with-cmdkey.md).
# Cached credentials discovery with cmdkey
### 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 |
| Detector Tags | LOLBIN Execution Analytics |
| ATT\&CK Tactic | Credential Access (TA0006), Discovery (TA0007) |
| ATT\&CK Technique | OS Credential Dumping (T1003), Account Discovery (T1087) |
| Severity | Low |
### Description
Cmdkey is a built-in Windows tool that can cache domain user credentials for use on specific target machines, Attackers can access cached user credentials using cmdkey /list.
### Attacker's Goals
Access cached user credentials.
### Investigative actions
* Check the initiator process for additional suspicious activity.
* Check if the host is a shared host that multiple users' credentials can be extracted from.
### Variations
The process cmdkey runs with modified name and extract cached credentials
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Discovery (TA0007) |
| ATT\&CK Technique | OS Credential Dumping (T1003), Account Discovery (T1087) |
| Severity | High |
**Description**
Cmdkey is a built-in Windows tool that can cache domain user credentials for use on specific target machines, Attackers can access cached user credentials using cmdkey /list.
**Attacker's Goals**
Access cached user credentials.
**Investigative actions**
* Check the initiator process for additional suspicious activity.
* Check if the host is a shared host that multiple users' credentials can be extracted from.
Transfer cached credentials with cmdkey to other standard output
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Discovery (TA0007) |
| ATT\&CK Technique | OS Credential Dumping (T1003), Account Discovery (T1087) |
| Severity | Medium |
**Description**
Cmdkey is a built-in Windows tool that can cache domain user credentials for use on specific target machines, Attackers can access cached user credentials using cmdkey /list.
**Attacker's Goals**
Access cached user credentials.
**Investigative actions**
* Check the initiator process for additional suspicious activity.
* Check if the host is a shared host that multiple users' credentials can be extracted from.
---
# 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/cached-credentials-discovery-with-cmdkey.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.