Detection rules › Elastic

Remote Scheduled Task Creation via RPC

Author
Elastic
Source
upstream

Identifies scheduled task creation from a remote source. This could be indicative of adversary lateral movement.

MITRE ATT&CK coverage

TacticTechniques
ExecutionT1053 Scheduled Task/Job, T1053.005 Scheduled Task/Job: Scheduled Task
PersistenceT1053 Scheduled Task/Job, T1053.005 Scheduled Task/Job: Scheduled Task
Privilege EscalationT1053 Scheduled Task/Job, T1053.005 Scheduled Task/Job: Scheduled Task
Lateral MovementT1021 Remote Services

Event coverage

ProviderEvent IDTitle
Security-Auditing4698A scheduled task was created.

Stages and Predicates

Stage 1: eql:iam

event.action:"scheduled-task-created" and winlog.event_data.ClientProcessId:0 and winlog.event_data.RpcCallClientLocality:0

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
event.actioneq
  • scheduled-task-created corpus 3 (elastic 3)
winlog.event_data.ClientProcessIdwildcard
  • 0
winlog.event_data.RpcCallClientLocalitywildcard
  • 0

Neighbors

Broader alternatives (more inclusive than this rule)

These rules match a superset of what this rule catches. They cover the same events plus more. Use them if you want wider coverage and can absorb more false positives.