LoFP LoFP / t1053

t1053

TitleTags
administrative activity
administrator or network operator can create file in crontab folders for automation purposes. please update the filter macros to remove false positives.
administrator or network operator can create this file for automation purposes. please update the filter macros to remove false positives.
administrator or network operator can use this application for automation purposes. please update the filter macros to remove false positives.
administrator or network operator can use this commandline for automation purposes. please update the filter macros to remove false positives.
administrators may create scheduled tasks on remote systems, but this activity is usually limited to a small set of hosts or users.
administrators may start scheduled tasks on remote systems, but this activity is usually limited to a small set of hosts or users.
any legitimate cron file.
azure kubernetes cronjob/job may be done by a system administrator.
bear in mind, administrators debugging scheduled task entries may trigger this analytic, necessitating fine-tuning and filtering to distinguish between legitimate and potentially malicious use of 'schtasks.exe'.
benign scheduled tasks creations or executions that happen often during software installations
creation of legitimate files in sudoers.d folder part of administrator work
false positives are possible if legitimate applications are allowed to register tasks that call a shell to be spawned. filter as needed based on command-line or processes that are used legitimately.
false positives may arise from legitimate actions by administrators or network operators who may use these commands for automation purposes. therefore, it's recommended to adjust filter macros to eliminate such false positives.
false positives may arise from legitimate applications that create tasks to run as system. therefore, it's recommended to adjust filters based on parent process or modify the query to include world writable paths for restriction.
false positives may arise when administrators or network operators create files in systemd directories for legitimate automation tasks. therefore, it's important to adjust filter macros to account for valid activities. to implement this search successfully, it's crucial to ingest appropriate logs, preferably using the linux sysmon add-on from splunkbase for those using sysmon.
false positives may occur with some of the selected binaries if you have tasks using them (which could be very common in your environment). exclude all the specific trusted tasks before using this rule
false positives will be limited to legitimate applications creating a task to run as system. filter as needed based on parent process, or modify the query to have world writeable paths to restrict it.
if known behavior is causing false positives, it can be exempted from the rule.
if the source ip is not localhost then it's super suspicious, better to monitor both local and remote changes to gpo scheduledtasks
it is possible scripts or administrators may trigger this analytic. filter as needed based on parent process, application.
legitimate administration activities
legitimate administrators may run these commands
legitimate applications may trigger this behavior, filter as needed.
legitimate applications may use random scheduled task names.
legitimate modification of crontab
legitimate processes that run at logon. filter according to your environment
legitimate scheduled jobs may be created during installation of new software.
legitimate scheduled tasks may be created during installation of new software.
legitimate scheduled tasks running third party software.
legitimate software naming their tasks as guids
legitimate software or scripts using cron jobs for recurring tasks.
software installation
software installers that run from temporary folders and also install scheduled tasks are expected to generate some false positives
software that uses the appdata folder and scheduled tasks to update the software in the appdata folders
some installers were seen using this method of creation unfortunately. filter them in your environment
the main source of false positives could be the legitimate use of scheduled tasks from these directories. careful tuning of this search may be necessary to suit the specifics of your environment, reducing the rate of false positives.
this analytic may also capture legitimate administrative activities such as system updates or maintenance tasks, which can be classified as false positives. filter as needed.
unlikely
unlikely (at.exe deprecated as of windows 8)
while it is possible for legitimate scripts or administrators to trigger this behavior, filtering can be applied based on the parent process and application to reduce false positives. analysts should reference the provided references to understand the context and threat landscape associated with this activity.
while it is possible to have false positives, due to legitimate administrative tasks, these are usually limited and should still be validated and investigated as appropriate.
windows administrator tasks or troubleshooting
windows management scripts or software