Sigma rule: Remote Schtasks Creation

Rule

Title

Remote Schtasks Creation

Status

unsupported

Level

medium

Author

Jai Minton, oscd.community

Date

2020/10/05

File

unsupported/windows/win_remote_schtask.yml

Commit

ccbb0369507f796db0b0ae6854c8a2be471b9d84

Detects remote execution via scheduled task creation or update on the destination host

Log source

product

windows

service

security

definition

The Advanced Audit Policy setting Object Access > Audit Other Object Access Events has to be configured to allow this detection (not in the baseline recommendations by Microsoft).

Detection

selection1:
    EventID: 4624
    Logon_Type: 3
selection2:
    EventID:
        - 4698
        - 4702
filter1:
    Source_Network_Address:
        - '::1'
        - '127.0.0.1'
filter2:
    Source_Network_Address: '-'
timeframe: 30d
condition: (selection1 and not filter1) or selection2 and not filter2
#   where:
#       selection1: TargetLogonID = selection2: SubjectLogonID, grouped by host over 30seconds | eventcount > 1
#   Rule should trigger where the SubjectLogonID from event 4698 or 4702 is the same as the TargetLogonID from event 4624 with a Logon_Type of 3, in a 30second period, provided its from the same host.
#   This logic would be similar to the Splunk 'Transaction' operator which groups related events over a timeframe.
#       This takes both field values (e.g. Logon_ID), and an expression provided (e.g. startswith=(EventCode=4624) maxspan=30s) which occurs over the raw event log to find events, at which point a Union based on the criteria provided occurs to merge these events into a single transaction.
#   This is similar to stats as an aggregation function, but allows you to see the raw text of events rather than to calculate stats on then, and it retains the raw event to allow an eval expression to occur for grouping. This is beneficial as fields such as LogonIDs are reused over time.
#   By having this you can group logon events to their remote schtask creation event (as it is searching for a logon followed by a schtask creation) even by using a search timeframe over a long period of time e.g. 30days without running the risk of incorrectly grouping a logonID at one time, to a task creation at another.
#   Rule logic is currently not supported by SIGMA.

False positives (as the rule lists them)

• Unknown

Tags

• attack.lateral_movement
• attack.persistence
• attack.execution
• attack.t1053.005

MITRE ATT&CK ids this rule names

• T1053.005

References

• https://drive.google.com/file/d/1lKya3_mLnR3UQuCoiYruO3qgu052_iS_/view

Read on 2026-11-03T00:58:21.399Z under licence sigma-drl-1.1@d5f4c36a from https://github.com/SigmaHQ/sigma/blob/ccbb0369507f796db0b0ae6854c8a2be471b9d84/unsupported/windows/win_remote_schtask.yml