Runs a hypothesis-driven threat hunt for Windows Scheduled Task persistence (T1053), guiding SIEM/EDR queries against task creation events (e.g. Event ID 4698), suspicious task actions, and unusual scheduling patterns. Use when hunting for scheduled-task persistence, after threat intel flags related campaigns, during incident response, or when alerts fire on schtasks/at.exe activity.
Start a fresh conversation. Replace the highlighted placeholders.
Use hunting-for-scheduled-task-persistence to perform an authorized hypothesis-driven hunt for Windows Scheduled Task persistence, analyze task-creation events, suspicious task actions, and unusual schedules, then produce the documented Hunt ID report for [EDR/SIEM platform, authorized host scope, time window, and relevant alerts or IOCs].
Required inputs
[EDR/SIEM platform, authorized host scope, time window, and relevant alerts or IOCs]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: hunting-for-scheduled-task-persistencedescription: Runs a hypothesis-driven threat hunt for Windows Scheduled Task persistence (T1053), guiding SIEM/EDR queries against task creation events (e.g. Event ID 4698), suspicious task actions, and unusual scheduling patterns. Use when hunting for scheduled-task persistence, after threat intel flags related campaigns, during incident response, or when alerts fire on schtasks/at.exe activity.domain: cybersecuritysubdomain: threat-huntingtags: - threat-hunting- mitre-attack- scheduled-tasks- persistence- t1053- proactive-detectionversion: '1.0'author: mahipallicense: Apache-2.0d3fend_techniques: - Execution Isolation- Process Termination- Hardware-based Process Isolation- Platform Monitoring- Process Suspensionnist_csf: - DE.CM-01- DE.AE-02- DE.AE-07- ID.RA-05mitre_attack: - T1046- T1057- T1082- T1083- T1547
Hunting For Scheduled Task Persistence
When to Use
When proactively hunting for indicators of hunting for scheduled task persistence in the environment
After threat intelligence indicates active campaigns using these techniques
During incident response to scope compromise related to these techniques
When EDR or SIEM alerts trigger on related indicators
During periodic security assessments and purple team exercises
Prerequisites
EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
Sysmon deployed with comprehensive configuration
Windows Security Event Log forwarding enabled
Threat intelligence feeds for IOC correlation
Workflow
Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
Analyze Results: Examine query results for anomalies, correlating across multiple data sources.
Validate Findings: Distinguish true positives from false positives through contextual analysis.
Correlate Activity: Link findings to broader attack chains and threat actor TTPs.
Document and Report: Record findings, update detection rules, and recommend response actions.
Key Concepts
Concept
Description
T1053.005
Scheduled Task
T1053.003
Cron
T1053.002
At
Tools & Systems
Tool
Purpose
CrowdStrike Falcon
EDR telemetry and threat detection
Microsoft Defender for Endpoint
Advanced hunting with KQL
Splunk Enterprise
SIEM log analysis with SPL queries
Elastic Security
Detection rules and investigation timeline
Sysmon
Detailed Windows event monitoring
Velociraptor
Endpoint artifact collection and hunting
Sigma Rules
Cross-platform detection rule format
Common Scenarios
Scenario 1: Cobalt Strike persistence via schtasks creating periodic beacon
Scenario 2: Ransomware scheduled task for re-execution after reboot
Scenario 3: APT encoded PowerShell task running every 30 minutes
Scenario 4: Insider task to periodically copy sensitive files