QuestionCould this task provide unauthorized persistence?
ScopeFictional server APP-01; task configuration and creation logs for the preceding 24 hours.
Collection timeNo live collection. Evidence references below are illustrative.
Evidence to examine
- E01 Task definition
- Launches PowerShell with a script in a user-writable directory.
- E02 Task-creation event
- Records creation outside the maintenance window supplied for this example.
A task definition and a creation event do not establish that the script ran or that an attacker created it.
What this supports
The combination warrants investigation for possible persistence. It does not confirm compromise.
Alternative explanations
An approved administrator script, a deployment job or a maintenance exception could explain the task.
What is missing
The script’s content and origin, execution history, creating account, related activity and confirmation from the system owner.
Recommended next stepAsk the owner to validate the change. Within approved collection scope, preserve the task definition, inspect the script and check execution history. Use those results to decide whether to close the case or escalate it.
Containment or system changes would require separate authorization.