Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Persistence is everything an attacker does to keep access after a reboot, a password reset, or a remediation effort. It is the difference between an incident and a recurring one.

What Is Persistence in Cybersecurity?
Persistence is the set of techniques an attacker uses to retain access to a system across interruptions: reboots, credential changes, software updates, and attempted clean-ups. In the MITRE ATT&CK framework it is tactic TA0003, and it is the stage that determines whether a security team is dealing with an incident or with the same incident four times.
An attacker who gains access without establishing persistence loses everything the moment the machine restarts. One who establishes it well can go quiet for months and return on demand, which is why the first thing a capable intruder does after initial access is secure a way back in—often several, deliberately varied in quality so that the obvious one absorbs the investigation.
Windows offers a large catalogue, and attackers choose based on how much noise they can afford:
schtasks or written directly into the TaskCache registry keys to hide them from the Task Scheduler interface.sethc.exe, which yields a SYSTEM shell from the login screen.On Linux the usual choices are cron jobs, systemd service units and timers, shell profile scripts, an added key in ~/.ssh/authorised_keys, a modified SSH configuration, or an LD_PRELOAD entry. Kernel modules provide the stealthiest option, as covered under kernel rootkit techniques. On macOS, launch agents and daemons play the equivalent role.
This is where modern intrusions increasingly settle, because it survives rebuilding the endpoint entirely:
At the extreme end, UEFI implants such as LoJax and BlackLotus survive disk replacement and operating system reinstallation. These are rare and associated with well-resourced groups, but they define the upper bound of what “remove the malware” can mean.
Persistence hunting is one of the highest-value activities a security team can perform, because every technique must leave a configuration change somewhere that the operating system will read at the next trigger. Practical approaches include:
systemctl list-timers and crontab audits cover Linux.Eradication is where incident response succeeds or fails. The sequence that works is to identify every persistence mechanism before touching any of them, then remove them together and rotate the relevant credentials in one coordinated action. Removing one at a time tells the attacker they have been found and lets them re-establish through a mechanism you have not located yet. Where account or ticket persistence is involved, credential rotation is part of eradication rather than a follow-up task.
Our Investigation and Incident Response Services treat persistence enumeration as the central deliverable of containment, because an incident is only closed when every route back has been accounted for.
Capable intruders install several, deliberately differing in sophistication. A noisy registry run key may be left as a decoy, with a WMI subscription or a scheduled task as the real mechanism and an identity-layer foothold such as an added service principal credential as the fallback. That layering is why responders should enumerate everything before removing anything.
It removes host-based persistence on that machine, provided the rebuild is from clean media and firmware is verified. It does nothing about identity persistence, which is now the more common and more damaging form. A forged Kerberos ticket, an added credential on a cloud application, or a mail forwarding rule all survive any number of endpoint rebuilds.
Scheduled tasks and services on servers, WMI event subscriptions, and cloud identity changes. These three cover the techniques used most often by groups that matter, and all produce discrete creation events you can alert on. Baselining autostart entries across a representative sample of hosts also surfaces anomalies quickly and is achievable without new tooling.
The mechanisms themselves are ordinary administrative features. Scheduled tasks, services, cron jobs, and service principal credentials all exist because legitimate software needs them, which is precisely why they make good hiding places. Detection therefore depends on knowing what is normal in your environment rather than on treating any particular technique as inherently suspicious.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.