> 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-persistence-via-group-policy-registry-keys.md).

# Possible Persistence via group policy Registry keys

### 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       | Persistence (TA0003)                                                              |
| ATT\&CK Technique    | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) |
| Severity             | Medium                                                                            |

### Description

Group Policy registry keys were read during system startup. This behavior may indicate a persistence mechanism that triggers on reboot to execute malicious code.

### Attacker's Goals

Establish persistence on the host using Windows Group Policy mechanisms.

### Investigative actions

* Inspect the registry keys and determine which process or command is configured to run.
* Verify whether the executing process is benign and expected as part of normal system behavior.


---

# 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-persistence-via-group-policy-registry-keys.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.