> 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/signed-process-creates-a-scheduled-task-via-file-access.md).
# Signed process creates a scheduled task via file access
### 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 | Execution (TA0002), Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Informational |
### Description
A signed process created a scheduled task via file access. Attackers may create scheduled tasks for execution and to establish persistence.
### Attacker's Goals
An attacker may gain persistence and execute malicious tools via scheduled tasks.
### Investigative actions
Check the created task file and look for the action triggered by the task.
### Variations
Signed process running from an untrusted directory creates a scheduled task via file access
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Persistence (TA0003) |
| ATT\&CK Technique | Scheduled Task/Job (T1053) |
| Severity | Low |
**Description**
A signed process created a scheduled task via file access. Attackers may create scheduled tasks for execution and to establish persistence.
**Attacker's Goals**
An attacker may gain persistence and execute malicious tools via scheduled tasks.
**Investigative actions**
Check the created task file and look for the action triggered by the task.
---
# 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/signed-process-creates-a-scheduled-task-via-file-access.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.