Skip to content

20 ยท Techniques

Rootkit techniques

Each page explains one technique the catalogue's rootkit families use, at the level a responder needs: what it changes and where, the traces it leaves, how to check a host offline and live, what the checker sees, and how to recover. Techniques are grouped by what they achieve for the rootkit; the matrix shows which family uses which. Boot-level techniques are covered on bootkits.dev.

Getting into the kernel5

How rootkit code reaches the kernel: a driver or kernel module loaded under a signature that should not be trusted, a signed but vulnerable driver abused to write kernel memory, or the check on what loads switched off. Loading is the step most likely to leave traces on disk: a driver or module file, a service or load entry, and log lines.

Hiding12

How a rootkit keeps its files, processes, modules and connections out of what the system reports: by hooking the functions that answer, filtering their results, or unlinking its objects from the lists the kernel walks. A host that hides things this way lies to the tools run on it, which is why an offline look at its disk or memory matters.

Blinding defences1

How a rootkit stops security tools from seeing it: removing the kernel callbacks they register, or tampering with what they rely on from the kernel. The host keeps running and reporting, but the defences no longer see what happens on it.

Backdoors and covert channels2

How a rootkit keeps a way back in that ordinary monitoring misses: a backdoor that wakes on a crafted packet instead of listening on a port, or an authentication module that lets a hard-coded password in.

Which family uses which technique

Techniques by goal down the side, the catalogue's families across the top, grouped by platform. A mark means the family's page documents its use of the technique.

ATT&CK coverage

The MITRE ATT&CK techniques each technique page maps to.