Skip to content

Windows Event ID 4702: A scheduled task was updated

Written when an existing scheduled task is updated or changed. It can catch “hijacking,” where a legitimate task’s action is rewritten to something malicious.

Overview

The subcategory is Audit Other Object Access Events. It is generated when an existing task’s definition is changed, and includes the updated task XML. As with creation 4698, the XML content (executable, arguments, triggers, run privileges) is central to reading it.

How it is triggered

  • Editing an existing task (GUI / schtasks /change / Set-ScheduledTask / API).

Security review points

  • An attacker may rewrite the Actions of an existing legitimate task to malicious content, achieving persistence more quietly than by creating a new task. Confirm that the updated XML’s executable and arguments are as expected.
  • Watch for elevation and auto-run introduced by the update, such as run privileges raised to SYSTEM, or a trigger changed to logon or a short interval.

Notes for log review

  • Legitimate software updates also change tasks. Know the “original definition” per task and evaluate by the difference (what changed).
  • Read it as a task history together with creation 4698, enabling 4700, disabling 4701, and deletion 4699.

MITRE ATT&CK mapping

TechniqueTacticWhat this event shows
T1053.005 Scheduled TaskExecution, Persistence, Privilege EscalationRewriting an existing task’s Actions for quieter persistence than creating a new one

Mapping as of ATT&CK v19.2. ATT&CK detection strategy DET0441 (T1053.005) also lists this event ID as a log source. To search by technique, see the ATT&CK reverse lookup.

Detection rules

SigmaHQ has 2 and Microsoft Sentinel has 2 public detection rules that use this event ID as a condition.

RuleTypeSeverity
Suspicious Scheduled Task UpdateSigmaHigh
Gain Code Execution on ADFS Server via SMB + Remote Service or Scheduled TaskSentinel analytics ruleMedium
Scheduled Tasks Names Used By SVR For GraphicalProton BackdoorSigma (threat-specific)High
Scheduled Task Creation or Update from User Writable DirectorySentinel hunting query-

Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.

Key fields

FieldMeaning
Task NameThe updated task name
Task Content (XML)The updated task definition
Subject\Account NameThe account that performed the update

References