T1546 Event Triggered Execution
EnterpriseAdversaries 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. Adversaries may abuse these mechanisms as a means of maintaining persistent access to a victim via repeatedly executing malicious code. After gaining access to a victim system, adversaries may create/modify event triggers to point to malicious content that will be executed whenever the event trigger is invoked. Since the execution can be proxied by an account with higher permissions, such as SYSTEM or service accounts, an adversary may be able to abuse these triggered execution mechanisms to escalate their privileges.
platforms
Platforms this applies to.
tactics
ATT&CK tactics this technique serves.
sub-techniques (18)
More specific entries beneath this one.
mitigations
ATT&CK mitigations that reduce this.
detected by (10)
Data components that detect this.
NIST CSF 2.0 — areas of relevance (Protect / Detect)
NIST CSF 2.0 areas this most relates to (evidence-ranked).
- PR.PSPlatform Securitystrong · backed by 5 of 9 mapped controls
- DE.CMContinuous Monitoringmoderate · backed by 4 of 9 mapped controls
- PR.AAIdentity Management, Authentication, and Access Controlmoderate · backed by 4 of 9 mapped controls
Derived from MITRE CTID (Apache-2.0) and the NIST 800-53 ↔ CSF crosswalk (public domain). Indicative relevance along the Protect/Detect axis — not a compliance assessment or coverage claim.
mitigating controls (9)
Security controls that mitigate this.
software (4)
Malware and tools associated with this.
campaigns (1)
Campaigns that use this.
Detected by (Sigma) (10)
Sigma detection rules related to this.
source
Where this definition is published.