Detection rules › Elastic
Unusual Scheduled Task Update
Identifies first-time modifications to scheduled tasks by user accounts, excluding system activity and machine accounts.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Execution | T1053 Scheduled Task/Job, T1053.005 Scheduled Task/Job: Scheduled Task |
| Persistence | T1053 Scheduled Task/Job, T1053.005 Scheduled Task/Job: Scheduled Task |
| Privilege Escalation | T1053 Scheduled Task/Job, T1053.005 Scheduled Task/Job: Scheduled Task |
Event coverage
| Provider | Event ID | Title |
|---|---|---|
| Security-Auditing | 4702 | A scheduled task was updated. |
Stages and Predicates
Stage 1: kql:new_terms
not user.name:"*$" and not winlog.event_data.SubjectUserSid:("S-1-5-18" or "S-1-5-19" or "S-1-5-20") and event.category:"iam"Exclusions
Top-level NOT(...) conjuncts — predicates this rule actively suppresses.
| Stage | Field | Kind | Excluded values |
|---|---|---|---|
| 1 | SubjectUserSid | in | S-1-5-18, S-1-5-19, S-1-5-20 |
| 2 | user | ends_with | $ |
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.
| Field | Kind | Values |
|---|---|---|
event.category | eq |
|
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.
- Suspicious Scheduled Task Update (drops 3 filters this rule applies)