PH_RULE_WinTaskScheduler_TaskRegistered
Enabled
The Windows Task Scheduler service reported a new task was registered by a user. This relies on the Win-TaskScheduler-106 event from the FortiSIEM Agent. Ensure your FortiSIEM agent template is configured to collect the event log Microsoft-Windows-TaskScheduler/Operational.
6
Security
Correlation
Streaming
Execution
Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.
https://attack.mitre.org/tactics/TA0002T1053.002
Scheduled Task/Job: At (Windows)
Adversaries may abuse the at.exe utility to perform task scheduling for initial or recurring execution of malicious code. The at.exe command line utility has been deprecated in current versions of Windows in favor of schtasks.
https://attack.mitre.org/techniques/T1053/002Application
Microsoft Windows Task Scheduler Operational Logs via FortiSIEM Agent
Correlation
Ensure the scheduled task is expected for normal system operation and approved by security policy.
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 secondsIf the following defined pattern/s occur within a 300 second time window.
task_registeredThis is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType="Win-TaskScheduler-106"This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
reptDevName,user,taskThis is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*)>=1This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
hostName = task_registered.reptDevName,
user = task_registered.user,
task = task_registered.task,
incidentCount = task_registered.COUNT(*)