T1546

Event Triggered Execution

Linux · macOS · Windows · SaaS · IaaS · Office Suite6 pieces on this siteT1546 on attack.mitre.org

Adversaries may establish persistence and/or elevate privileges using system mechanisms that trigger execution based on specific events. Various operating systems have means to monitor and subscribe to events such as logons or other user activity such as running specific applications/binaries. Cloud environments may also support various functions and services that monitor and can be invoked in response to specific cloud events.

MITRE ATT&CK 19.2, retrieved 2026-09-12

If this is happening now

1

Checklists and playbooks to open while the alert is still live.

Detect it

2

Hunts and rules you can run, each stating what it needs and what else it returns.

The evidence it leaves

1

Where the traces live, and what each source proves and does not.

Practise it

1

Labs, timelines, evidence packs and tabletop scenarios to work before you need to.

Guided labMembers

Guided lab: the persistence that leaves almost no log

WMI event subscriptions run code on a condition you choose, survive reboots, live nowhere in the filesystem, and log nothing by default. The last of the persistence series, and the one that changes how you think about the other three.

T1546.003

Read

1

Analyses, case studies, guides, references and interview questions.

how MITRE says to see it

Behavioral Detection of Event Triggered Execution Across Platforms

  • Correlates unexpected modifications to WMI event filters, scheduled task triggers, or registry autorun keys with subsequent execution of non-standard binaries by SYSTEM-level processes.
  • Detects inotify or auditd configuration changes that monitor system files coupled with execution of script interpreters or binaries by cron or systemd timers.
  • Correlates launchd plist modifications with subsequent unauthorized script execution or anomalous parent-child process trees involving user agents.
  • Monitors cloud function creation triggered by specific audit log events (e.g., IAM changes, object creation), followed by anomalous behavior from new service accounts.

what reduces it

  • M1026 Privileged Account Management. Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
  • M1051 Update Software. Perform regular software updates to mitigate exploitation risk.

sub-techniques

The description, detection analytics and mitigations are reproduced from MITRE ATT&CK, version 19.2, under its terms of use. The checklists, hunts, labs and everything else linked here are this site’s.