> 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/uncommon-sensitive-registry-hive-dump.md).

# Uncommon sensitive registry hive dump

### 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 with eXtended Threat Hunting (XTH) |
| ATT\&CK Tactic       | Credential Access (TA0006)                   |
| ATT\&CK Technique    | OS Credential Dumping (T1003)                |
| Severity             | Low                                          |

### Description

A sensitive registry hive was extracted, which is used for accessing credentials.

### Attacker's Goals

* Adversary may attempt to extract credentials from the Windows Registry
* Credentials can then be used to perform lateral movement and access restricted information.

### Investigative actions

* Investigate the process that tried to access the registry hive.
* Investigate the actions of the user for which his credentials were stored in the registry hive.

### Variations

<details>

<summary>Uncommon sensitive registry hive dump by unsigned and rare process</summary>

**Synopsis**

| Field             | Value                         |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)    |
| ATT\&CK Technique | OS Credential Dumping (T1003) |
| Severity          | High                          |

**Description**

A sensitive registry hive was extracted, which is used for accessing credentials.

**Attacker's Goals**

* Adversary may attempt to extract credentials from the Windows Registry
* Credentials can then be used to perform lateral movement and access restricted information.

**Investigative actions**

* Investigate the process that tried to access the registry hive.
* Investigate the actions of the user for which his credentials were stored in the registry hive.

</details>

<details>

<summary>Uncommon sensitive registry hive dump by injected process</summary>

**Synopsis**

| Field             | Value                         |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)    |
| ATT\&CK Technique | OS Credential Dumping (T1003) |
| Severity          | High                          |

**Description**

A sensitive registry hive was extracted, which is used for accessing credentials.

**Attacker's Goals**

* Adversary may attempt to extract credentials from the Windows Registry
* Credentials can then be used to perform lateral movement and access restricted information.

**Investigative actions**

* Investigate the process that tried to access the registry hive.
* Investigate the actions of the user for which his credentials were stored in the registry hive.

</details>

<details>

<summary>Uncommon sensitive registry hive dump by reg.exe lolbin process which was executed by rare causality process</summary>

**Synopsis**

| Field             | Value                         |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)    |
| ATT\&CK Technique | OS Credential Dumping (T1003) |
| Severity          | High                          |

**Description**

A sensitive registry hive was extracted, which is used for accessing credentials.

**Attacker's Goals**

* Adversary may attempt to extract credentials from the Windows Registry
* Credentials can then be used to perform lateral movement and access restricted information.

**Investigative actions**

* Investigate the process that tried to access the registry hive.
* Investigate the actions of the user for which his credentials were stored in the registry hive.

</details>

<details>

<summary>Uncommon sensitive registry hive dump by reg.exe lolbin process</summary>

**Synopsis**

| Field             | Value                         |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)    |
| ATT\&CK Technique | OS Credential Dumping (T1003) |
| Severity          | Medium                        |

**Description**

A sensitive registry hive was extracted, which is used for accessing credentials.

**Attacker's Goals**

* Adversary may attempt to extract credentials from the Windows Registry
* Credentials can then be used to perform lateral movement and access restricted information.

**Investigative actions**

* Investigate the process that tried to access the registry hive.
* Investigate the actions of the user for which his credentials were stored in the registry hive.

</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/uncommon-sensitive-registry-hive-dump.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.
