Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 817

Persistence

What is Persistence?

PersistenceThe MITRE ATT&CK tactic (TA0003) covering techniques that let an attacker maintain access to a system across reboots, credential changes, and incident response.


Persistence (MITRE ATT&CK tactic TA0003) groups techniques that allow adversaries to keep their foothold even when systems are rebooted, passwords are reset, or operators try to clean up. Common implementations include autostart registry keys, scheduled tasks, Windows services, WMI event subscriptions, BITS jobs, login items on macOS, cron jobs on Linux, malicious browser extensions, OAuth tokens, and backdoored Active Directory accounts. Adversaries often layer multiple persistence mechanisms in case one is removed. Defenders detect persistence via process-creation logs, autoruns inventories (Sysinternals Autoruns, EDR), Sigma rules, and by hunting for anomalous scheduled tasks, services, or LSA providers, and they neutralise it by completely re-imaging compromised hosts.

Examples

  1. 01

    A backdoor installed as a Windows service with a random GUID name.

  2. 02

    A malicious OAuth app granted persistent access to a Microsoft 365 mailbox.

Frequently asked questions

What is Persistence?

The MITRE ATT&CK tactic (TA0003) covering techniques that let an attacker maintain access to a system across reboots, credential changes, and incident response. It belongs to the Defense & Operations category of cybersecurity.

What does Persistence mean?

The MITRE ATT&CK tactic (TA0003) covering techniques that let an attacker maintain access to a system across reboots, credential changes, and incident response.

How does Persistence work?

Persistence (MITRE ATT&CK tactic TA0003) groups techniques that allow adversaries to keep their foothold even when systems are rebooted, passwords are reset, or operators try to clean up. Common implementations include autostart registry keys, scheduled tasks, Windows services, WMI event subscriptions, BITS jobs, login items on macOS, cron jobs on Linux, malicious browser extensions, OAuth tokens, and backdoored Active Directory accounts. Adversaries often layer multiple persistence mechanisms in case one is removed. Defenders detect persistence via process-creation logs, autoruns inventories (Sysinternals Autoruns, EDR), Sigma rules, and by hunting for anomalous scheduled tasks, services, or LSA providers, and they neutralise it by completely re-imaging compromised hosts.

How do you defend against Persistence?

Defences for Persistence typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for Persistence?

Common alternative names include: Foothold persistence, TA0003.

Related terms

See also