Scheduled Task/Job

Executive Summary

Scheduled Task/Job (T1053) is a MITRE ATT&CK technique associated with Execution, Persistence, Privilege Escalation. Adversaries may abuse task scheduling functionality to facilitate initial or recurring execution of malicious code.

Why Attackers Use It

Attackers use Scheduled Task/Job because it provides a reliable way to advance their objective within the Execution, Persistence, Privilege Escalation tactic, often with a favorable balance of impact versus detectability on Containers, ESXi, Linux, macOS, Network Devices, Windows environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.

MITRE Description

Adversaries may abuse task scheduling functionality to facilitate initial or recurring execution of malicious code. Utilities exist within all major operating systems to schedule programs or scripts to be executed at a specified date and time. A task can also be scheduled on a remote system, provided the proper authentication is met (ex: RPC and file and printer sharing in Windows environments). Scheduling a task on a remote system typically may require being a member of an admin or otherwise privileged group on the remote system.(Citation: TechNet Task Scheduler Security)

Adversaries may use task scheduling to execute programs at system startup or on a scheduled basis for persistence. These mechanisms can also be abused to run a process under the context of a specified account (such as one with elevated permissions/privileges). Similar to System Binary Proxy Execution, adversaries have also abused task scheduling to potentially mask one-time execution under a trusted system process.(Citation: ProofPoint Serpent)

Attack Flow

1. Attacker gains the prerequisite access or context described below.
2. Attacker executes Scheduled Task/Job to achieve its tactical objective (Execution, Persistence, Privilege Escalation).
3. Resulting access/data/effect is leveraged to advance the broader attack chain (see Related Techniques).

Prerequisites

• Platform(s): Containers, ESXi, Linux, macOS, Network Devices, Windows
• ATT&CK does not define one universal permission requirement for this technique. Establish the required access from the observed implementation and affected platform.

Common Tools

• Tool attribution is implementation-specific. Use ATT&CK procedure examples and local telemetry to identify the binaries, services, scripts, accounts, or cloud resources involved.

Commands

No universal command represents Scheduled Task/Job. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.

Network Traffic

• Network observability is implementation-dependent. Review DNS, proxy, firewall, flow, authentication, and packet telemetry around the activity window, then correlate remote endpoints and protocol behavior with host evidence.

Windows Events

Sysmon Events

Detection Opportunities

No MITRE detection guidance published for this technique.

Relevant ATT&CK Data Sources: N/A

Sigma Rules

A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.

Splunk Queries

Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.

Investigation Workflow

1. Confirm that the observed behavior is consistent with Scheduled Task/Job and rule out expected administrative or application activity.
2. Establish the first-seen time, initiating identity, source system, target system, and affected resources.
3. Collect relevant host, identity, network, cloud, and application telemetry for the surrounding time window.
4. Correlate parent and child activity, remote connections, file or configuration changes, and related ATT&CK techniques.
5. Determine scope by searching for the same observable across peer assets and identities.
6. Preserve volatile evidence and record confidence, assumptions, and telemetry gaps before containment.

Containment

1. Isolate affected host(s)/account(s) identified during investigation.
2. Revoke or rotate any credentials/tokens potentially exposed.
3. Apply the mitigations listed below where not already enforced.
4. Validate no related techniques (see Related Techniques) were chained against the same asset.

Mitigation

• M1018 -- User Account Management: User Account Management involves implementing and enforcing policies for the lifecycle of user accounts, including creation, modification, and deactivation.
• M1028 -- Operating System Configuration: Operating System Configuration involves adjusting system settings and hardening the default configurations of an operating system (OS) to mitigate adversary exploitation and prevent abuse of system functionality.
• M1022 -- Restrict File and Directory Permissions: Restricting file and directory permissions involves setting access controls at the file system level to limit which users, groups, or processes can read, write, or execute files.
• M1026 -- Privileged Account Management: Privileged Account Management focuses on implementing policies, controls, and tools to securely manage privileged accounts (e.g., SYSTEM, root, or administrative accounts).
• M1047 -- Audit: Auditing is the process of recording activity and systematically reviewing and analyzing the activity and system configurations.

Related Techniques

• T1053.002
• T1053.003
• T1053.005
• T1053.006
• T1053.007