CyberKit

Persistence

Mechanisms that keep attacker access across reboots.

What it is

Persistence is any technique that lets an adversary keep access through reboots, logoffs, or credential changes: registry run keys, scheduled tasks, services, and many more.

Why it matters

Persistence is what makes an intrusion durable; eradication fails if even one mechanism is missed, so enumerating all of them is central to recovery.

In practice

A scheduled task that re-launches an implant at every login, surviving a reboot.

What to look for

  • New Run keys, services, scheduled tasks, WMI subscriptions or cron entries.
  • Startup items pointing at user-writable paths.
  • Accounts created around the time of compromise.

Common mistake

Removing the one mechanism you found. Attackers often plant several; sweep every common location before declaring the host clean.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • CrowdStrike Falcon Commercial

    An EDR agent that records process, file and network activity on each host and flags this kind of behavior.

  • Microsoft Defender for Endpoint Commercial

    Microsoft's EDR, with advanced hunting tables you can query for this activity across Windows, macOS and Linux.

  • Velociraptor Open source

    Collects and hunts for artifacts across many hosts at once, often during live response. Our notes.

  • Sysmon Free

    Free Windows logging of process starts, network connections and more, which many detections rely on. Our notes.

ATT&CK techniques

  • T1547: Boot or Logon Autostart Execution

Read next

Sources