> 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/rare-unsigned-process-execution-by-scheduled-task.md).
# Rare unsigned process execution by scheduled task
### 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 | Scheduled tasks Analytics |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Low |
### Description
Rare and unsigned process was executed by a scheduled task.
### Attacker's Goals
Attackers may attempt to gain persistence on the endpoint using scheduled tasks.
### Investigative actions
* Review the process executed by the schedule task.
* Investigate the specific scheduled task execution chain.
### Variations
Uncommon unsigned process execution by scheduled task
**Synopsis**
| Field | Value |
| ----------------- | -------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Informational |
**Description**
Uncommon and unsigned process was executed by a scheduled task.
**Attacker's Goals**
Attackers may attempt to gain persistence on the endpoint using scheduled tasks.
**Investigative actions**
* Review the process executed by the schedule task.
* Investigate the specific scheduled task execution chain.
Process, with a rare untrusted signature, execution by scheduled task
**Synopsis**
| Field | Value |
| ----------------- | -------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Low |
**Description**
Process with a rare and untrusted signature was executed by a scheduled task.
**Attacker's Goals**
Attackers may attempt to gain persistence on the endpoint using scheduled tasks.
**Investigative actions**
* Review the process executed by the schedule task.
* Investigate the specific scheduled task execution chain.
Rare unsigned process execution from a suspicious folder by scheduled task
**Synopsis**
| Field | Value |
| ----------------- | -------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Low |
**Description**
Rare and unsigned process was execution from a suspicious folder by a scheduled task.
**Attacker's Goals**
Attackers may attempt to gain persistence on the endpoint using scheduled tasks.
**Investigative actions**
* Review the process executed by the schedule task.
* Investigate the specific scheduled task execution chain.
Rare unsigned process execution with high entropy by scheduled task
**Synopsis**
| Field | Value |
| ----------------- | -------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Low |
**Description**
Rare and unsigned process was execution with high entropy by a scheduled task.
**Attacker's Goals**
Attackers may attempt to gain persistence on the endpoint using scheduled tasks.
**Investigative actions**
* Review the process executed by the schedule task.
* Investigate the specific scheduled task execution chain.
Rare unsigned process execution with high integrity level by scheduled task
**Synopsis**
| Field | Value |
| ----------------- | -------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Low |
**Description**
Rare and unsigned process was execution with high integrity level by a scheduled task.
**Attacker's Goals**
Attackers may attempt to gain persistence on the endpoint using scheduled tasks.
**Investigative actions**
* Review the process executed by the schedule task.
* Investigate the specific scheduled task execution chain.
Rare unsigned process execution by scheduled task on a sensitive server
**Synopsis**
| Field | Value |
| ----------------- | -------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Medium |
**Description**
Rare and unsigned process was executed by a scheduled task.
**Attacker's Goals**
Attackers may attempt to gain persistence on the endpoint using scheduled tasks.
**Investigative actions**
* Review the process executed by the schedule task.
* Investigate the specific scheduled task execution chain.
---
# 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/rare-unsigned-process-execution-by-scheduled-task.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.