> 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/execution-of-an-uncommon-process-with-a-local-domain-user-sid-at-an-early-startup-stage.md).
# Execution of an uncommon process with a local/domain user SID at an early startup stage
### 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 | Generic Persistence Analytics |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Boot or Logon Autostart Execution (T1547) |
| Severity | Informational |
### Description
Execution of an uncommon process with a local/domain user SID at an early startup stage may be an indication of a persistent mechanism on boot that is being actively abused.
### Attacker's Goals
* Attackers aim to get persistence to continue operating even after a reboot.
### Investigative actions
* Check if the CGO (causality group owner) is familiar and if any configuration, parameters, or registry keys have been modified.
### Variations
Execution of an uncommon process with a local/domain user SID at an early startup stage with suspicious characteristics
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Boot or Logon Autostart Execution (T1547) |
| Severity | Low |
**Description**
Execution of an uncommon process with a local/domain user SID at an early startup stage may be an indication of a persistent mechanism on boot that is being actively abused.
**Attacker's Goals**
* Attackers aim to get persistence to continue operating even after a reboot.
**Investigative actions**
* Check if the CGO (causality group owner) is familiar and if any configuration, parameters, or registry keys have been modified.
Execution of an uncommon process with a local/domain user SID at an early startup stage with uncommon characteristics
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Boot or Logon Autostart Execution (T1547) |
| Severity | Low |
**Description**
Execution of an uncommon process with a local/domain user SID at an early startup stage may be an indication of a persistent mechanism on boot that is being actively abused.
**Attacker's Goals**
* Attackers aim to get persistence to continue operating even after a reboot.
**Investigative actions**
* Check if the CGO (causality group owner) is familiar and if any configuration, parameters, or registry keys have been modified.
---
# 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/execution-of-an-uncommon-process-with-a-local-domain-user-sid-at-an-early-startup-stage.md?ask=&goal=
```
`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.