Skip to content

15 ยท Techniques

Bootkit techniques

Each page explains one technique the catalogue's bootkit families use, at the level a responder needs: what it changes and where in the boot chain, 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 bootkit; the matrix shows which family uses which. Techniques of rootkits that load later, as drivers or kernel modules, are on rootkits.dev.

Persisting in the boot chain7

Where bootkit code is stored so it runs at every boot: a module added to or patched in the SPI flash firmware, a boot manager replaced on the EFI system partition, the MBR or a volume's boot sectors rewritten, or sectors outside any partition. The place decides what survives a reinstall or a new disk, and what an offline check can see: the ESP and the disk's sectors can be read from a collection, the firmware needs a dump.

Getting past Secure Boot4

How a bootkit gets code to run where the platform should refuse it: an old, still-trusted boot manager booted on purpose, an attacker key enrolled in shim's list, a flaw in the firmware's own image parser, or flash write protections the firmware left open. Their traces are split between files staged on the ESP and places the platform keeps: firmware variables, the Secure Boot databases, the flash settings.

Taking over the boot3

How a bootkit stays in control from one boot stage to the next: hooking the firmware's boot services or the BIOS disk interrupt, patching each loader in memory after it has been read and checked, and switching off the kernel's code signing before it starts. The loader and kernel files on disk stay as they were, so these steps show mostly in memory, in Measured Boot logs, or through the stage that started them.

Hiding and protecting itself1

How a bootkit keeps its sectors and files from being seen or repaired once the system runs: a hooked disk driver that returns the original boot code when the infected sectors are read, and blocks writes to them. A system in that state lies about its own disk, which is why a disk read offline, or from trusted media, is the one to trust.

Which family uses which technique

Techniques by goal down the side, the catalogue's families across the top, grouped by where they live: in the firmware, or on the disk in the UEFI or legacy BIOS boot path. A lit node means the family's page documents its use of the technique.

ATT&CK coverage

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