ATT&CK Reference
Portfolio

TA0003 · PERSISTENCE

Boot or Logon Autostart Execution

T1547Linux · macOS · Windows · Network Devicesattack.mitre.org

Run keys, startup folders, Winlogon helpers, and LSA drivers that execute on boot or logon.

Detect it with

Registry writes to Run/RunOnce by non-installer processes; new files in Startup folders.

Why it matters on shift

Boot or Logon Autostart Execution is one of the concrete ways adversaries achieve persistence. Recognising it in telemetry lets you name the technique in your ticket and pivot to what came before and after.

What to look for next

After persistence, the next tactic is usually Privilege Escalation. Search your telemetry for the transition before closing the ticket.

14 sub-techniques

How it shows up in practice

  1. T1547.001

    Registry Run Keys / Startup Folder

    Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in.

  2. T1547.002

    Authentication Package

    Adversaries may abuse authentication packages to execute DLLs when the system boots. Windows authentication package DLLs are loaded by the Local Security Authority (LSA) process at system start.

  3. T1547.003

    Time Providers

    Adversaries may abuse time providers to execute DLLs when the system boots. The Windows Time service (W32Time) enables time synchronization across and within domains.

  4. T1547.004

    Winlogon Helper DLL

    Adversaries may abuse features of Winlogon to execute DLLs and/or executables when a user logs in. Winlogon.exe is a Windows component responsible for actions at logon/logoff as well as the secure attention sequence (SAS) triggered by Ctrl-Alt-Delete.

  5. T1547.005

    Security Support Provider

    Adversaries may abuse security support providers (SSPs) to execute DLLs when the system boots. Windows SSP DLLs are loaded into the Local Security Authority (LSA) process at system start.

  6. T1547.006

    Kernel Modules and Extensions

    Adversaries may modify the kernel to automatically execute programs on system boot. Loadable Kernel Modules (LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand.

  7. T1547.007

    Re-opened Applications

    Adversaries may modify plist files to automatically run an application when a user logs in.

  8. T1547.008

    LSASS Driver

    Adversaries may modify or add LSASS drivers to obtain persistence on compromised systems. The Windows security subsystem is a set of components that manage and enforce the security policy for a computer or domain.

  9. T1547.009

    Shortcut Modification

    Adversaries may create or modify shortcuts that can execute a program during system boot or user login.

  10. T1547.010

    Port Monitors

    Adversaries may use port monitors to run an adversary supplied DLL during system boot for persistence or privilege escalation. A port monitor can be set through the AddMonitor API call to set a DLL to be loaded at startup.

  11. T1547.012

    Print Processors

    Adversaries may abuse print processors to run malicious DLLs during system boot for persistence and/or privilege escalation. Print processors are DLLs that are loaded by the print spooler service, spoolsv.exe, during boot.

  12. T1547.013

    XDG Autostart Entries

    Adversaries may add or modify XDG Autostart Entries to execute malicious programs or commands when a user’s desktop environment is loaded at login. XDG Autostart entries are available for any XDG-compliant Linux system.

  13. T1547.014

    Active Setup

    Adversaries may achieve persistence by adding a Registry key to the Active Setup of the local machine. Active Setup is a Windows mechanism that is used to execute programs when a user logs in.

  14. T1547.015

    Login Items

    Adversaries may add login items to execute upon user login to gain persistence or escalate privileges. Login items are applications, documents, folders, or server connections that are automatically launched when a user logs in.

Kill-chain context

← beforeExecutionPersistenceafter →Privilege Escalation