Join our Newsletter — 33% off our NHI Course
Home› Guides› Firmware and Bootkit Compromise Playbook: Verify, Reflash or…
Template Incident Response & Forensics

Firmware and Bootkit Compromise Playbook: Verify, Reflash or Replace Before You Trust

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 11 min read
On this page

A bootkit or firmware implant can survive the reimage that ends most incident playbooks, so a response that stops at "rebuild the disk" may hand the device straight back to the attacker. Bootkits in the EFI system partition, such as BlackLotus, run before the operating system and its security tools; implants in SPI flash, such as LoJax, survive operating system reinstalls and even disk replacement. Responding well means preserving pre-boot evidence, verifying firmware against known-good images, and making explicit decisions about reflashing or replacing hardware. This playbook template gives [Organisation] a ready-to-adapt response for suspected UEFI bootkit, firmware implant and boot chain tampering on Windows and Linux endpoints and servers, including baseboard management controllers. It is for incident responders, endpoint and infrastructure engineers, and IT asset owners. For the preventive controls see the Firmware and Boot Security Guide.

How to use this template

  • Adopt it as a sub-playbook of the [Organisation] incident response plan. See the Incident Response Plan Template.
  • Two tracks. Steps marked B apply to boot partition bootkits (EFI system partition, boot loaders). Steps marked F apply to implants in platform firmware (SPI flash, option ROMs, BMC). Treat a case as F until firmware has been verified.
  • Prepare the prerequisites in 9.1 (known-good firmware images, vendor contacts, spare hardware) before you need them. Without them, sections 4 to 6 default to hardware replacement.
  • Replace every [placeholder], record each decision with who made it and on what evidence, and review the template yearly and after each use.

1. Scope and triggers

1.1 This playbook applies to any [Organisation] laptop, desktop, server, hypervisor host or managed appliance where there is evidence or credible suspicion of tampering with the pre-boot environment.

1.2 Triggers include:

  • Unexpected changes to bootmgfw.efi or bootmgr.efi, or unexpected EFI binaries such as shimx64.efi or grubx64.efi on a Windows device's EFI system partition (indicators named in NSA's BlackLotus mitigation guide).
  • Secure Boot, Memory Integrity (HVCI) or BitLocker disabled without a change record, especially followed by an unscheduled reboot.
  • Measured boot or attestation failures: unexpected TPM PCR values, failed device health attestation, or a NAC block based on PCR changes.
  • Threat intelligence or a vendor advisory naming a firmware implant affecting [Organisation]'s hardware models.
  • Malware that returns after a clean reimage, or an EDR alert on writes to firmware or the boot partition.
  • Use of a vulnerable signed driver to access hardware (see the EDR Tampering and BYOVD Response Playbook).

1.3 ATT&CK techniques to record in the case:

TechniqueIDTrackImplication
BootkitT1542.003BLives in boot sectors or the EFI system partition; removed by restoring the partition and reimaging
System FirmwareT1542.001FLives in SPI flash; survives disk wipe; needs reflash or board replacement
Firmware CorruptionT1495FDestructive; device may not boot; replacement likely
RootkitT1014B or FOperating system telemetry cannot be trusted on the device

2. Roles and contacts

RoleResponsibilityNamed contact
Incident commanderDeclares the incident, owns decisions in sections 4 to 6[Name, out-of-band number]
Endpoint or server engineering leadBoot partition and firmware collection, reflash, rebuild[Name]
Forensic leadEvidence preservation, chain of custody, firmware comparison[Name or IR firm]
Hardware vendor and OEM supportKnown-good firmware images, verification tools, board replacement[Vendor, contract number, escalation]
IT asset managementModel, serial, firmware version, spares and disposal[Name]
Identity teamCredential resets for users and machine accounts on affected devices[Name]
Legal and data protectionNotification assessment, law enforcement engagement[Name]

3. Detection and triage

3.1 Do not reboot the device if a boot partition change is suspected. NSA's guidance is that a reboot executes the EFI binaries, so the partition must be restored to a known-good state, or evidence collected, first. Do not power it off unless containment requires it; record the decision.

3.2 Collect, in this order where possible:

  1. A copy of the EFI system partition and the boot configuration data, with hashes.
  2. Secure Boot state, the DB and DBX contents, and on Windows the Secure Boot servicing state under HKLM\SYSTEM\CurrentControlSet\Control\Secureboot.
  3. Measured boot logs and TPM attestation results, where available.
  4. EDR telemetry, Windows event logs and Linux logs covering the period before the trigger, including any changes to BitLocker or Memory Integrity.
  5. Firmware version, model and serial; on track F, an SPI flash image taken with vendor-supported tools or an approved forensic method.
  6. BMC firmware version and logs for servers.

3.3 Verify firmware by comparing the extracted image, or the hash reported by the platform, with the vendor's known-good image for that exact model and version. Record the method used. (MITRE D3FEND D3-FV Firmware Verification, D3-TBI TPM Boot Integrity.)

3.4 Classify severity: [Critical] for any confirmed firmware implant or bootkit on a privileged system (domain controller, hypervisor, PAM server, build server); [High] for confirmed cases on user devices; [Medium] for unverified integrity failures pending analysis.

3.5 Scope across the fleet. Search for the same indicators on every device of the same model and in the same management domain. A firmware implant usually means the attacker already had administrative or physical access.

4. Containment

4.1 Isolate affected devices from the network through EDR or switch port controls. Keep them powered unless the decision in 3.1 says otherwise.

4.2 Revoke trust that the device holds: disable its machine account and certificates, revoke VPN and Wi-Fi certificates, and remove it from device compliance so conditional access blocks it. See the Machine Identity, PKI and Certificate Lifecycle Guide.

4.3 Reset credentials of every user who signed in to the device since the earliest suspected compromise, and any service account or secret stored on it. Assume anything the operating system could read was exposed.

4.4 Block the indicators fleet-wide: EDR rules that prevent writes to the EFI system partition and unscheduled changes to BitLocker, Memory Integrity and Secure Boot settings.

4.5 Decision (incident commander): whether to keep the device for forensic analysis or law enforcement, or proceed to eradication. Record the decision and the evidence.

5. Eradication

5.1 Track B (boot partition):

  • Restore the EFI system partition from a known-good source before any reboot.
  • Fully reimage devices that have already booted the malicious binary; NSA states removal after installation is unreliable.
  • Apply current Secure Boot mitigations. For BlackLotus (CVE-2023-24932), Microsoft's KB5025885 adds the Windows UEFI CA 2023 certificate to DB and updates the boot manager (AvailableUpdates = 0x5944, event 1036 and 1799), then revokes Windows Production PCA 2011 in DBX (0x80, event 1037), with an optional SVN update (0x200, event 1042). Update recovery and installation media first: the revocations cannot be reverted while Secure Boot stays on, and Microsoft notes they are preventive, not a cure for an infected device.
  • Back up BitLocker recovery keys before changes, because some devices enter recovery.

5.2 Track F (platform firmware):

  • Reflash the SPI flash with the vendor's known-good image for that exact board, using a method that does not depend on the possibly compromised firmware where the vendor supports one (for example a hardware recovery mechanism or an external programmer).
  • Verify the result by re-extracting and comparing the image.
  • For servers, update and verify BMC firmware and reset BMC credentials.
  • Decision (incident commander with engineering lead): replace the motherboard or device instead of reflashing when the vendor cannot supply a verified image, reflash cannot be verified, the implant persists after reflash, the platform's signing keys are known to be compromised, or the device is a privileged system where residual doubt is unacceptable. ESET's LoJax analysis gives reflash with a board-specific clean image or motherboard replacement as the only remediation.

5.3 Close the entry route: remove the vulnerable driver, patch the firmware vulnerability, enable firmware write protection and hardware root of trust features where the platform supports them.

6. Recovery

6.1 Rebuild the operating system from a trusted image only after firmware and boot partition are verified. NIST CSF 2.0 RC.RP-03 expects restoration assets to be verified before use; apply this to images and recovery media too.

6.2 Re-enable Secure Boot in standard mode, BitLocker with TPM, and Memory Integrity. Confirm attestation passes and record the new baseline PCR values.

6.3 Re-enrol the device with new machine credentials and certificates. Do not restore old machine secrets.

6.4 Monitor the device closely for [30] days: EFI partition integrity, attestation results and EDR alerts.

6.5 Dispose of replaced boards and devices through secure disposal with a record, or retain them as evidence as decided in 4.5.

7. Communication and notification

7.1 Brief executives on scope, especially the hardware replacement decision and its cost and lead time.

7.2 Inform the hardware vendor with model, firmware version and indicators, under an agreed TLP label, and ask whether other customers are affected.

7.3 Legal assesses notification duties where personal data on affected devices may have been exposed, and whether to engage law enforcement or the national CSIRT, since firmware implants are often linked to state actors.

7.4 Tell affected users what will happen to their device and which credentials they must reset.

8. Post-incident review

8.1 Within [10] working days, review: entry route, how the implant was detected, time from trigger to isolation, whether the "do not reboot" rule held, and whether known-good images were available.

8.2 Record outcomes per device: reimaged, reflashed and verified, or replaced.

8.3 Track actions: firmware inventory gaps, devices without attestation, missing vendor images, Secure Boot mitigation status across the fleet.

8.4 Map lessons to controls: NIST SP 800-53 SI-7 (with SI-7(9) Verify Boot Process and SI-7(10) Protection of Boot Firmware), and the Protection, Detection and Recovery principles of NIST SP 800-193.

Implementation guidance

9.1 Prerequisites to prepare now:

  • A firmware inventory: model, board revision, firmware and BMC versions for every device class. See the Hardware and Firmware SBOM Guide.
  • Known-good firmware images and hashes from each vendor, stored offline.
  • A tested procedure, per device class, to extract and verify firmware and to reflash it.
  • Spare hardware or a vendor replacement agreement for privileged systems.
  • Updated recovery and installation media that boot after Secure Boot revocations.
  • EDR rules for EFI partition writes and boot security setting changes, and attestation reporting where available.

9.2 Reimage, reflash or replace:

FindingDefault actionEscalate to replacement when
Boot partition change, not yet executedRestore partition before reboot, then patchFirmware verification fails
Bootkit executedFull reimage plus Secure Boot mitigationsFirmware verification fails or reinfection occurs
Firmware implant confirmedVerified reflash from known-good imageNo verified image, reflash cannot be verified, privileged system, or vendor signing keys compromised
Signing key compromise at the vendorFollow vendor guidance; increase monitoringVendor cannot revoke or rotate keys for the platform

The last row is not theoretical: the MSI signing keys leak exposed Intel Boot Guard private keys for 116 products, keys that are hard to revoke on devices already in use.

9.3 Testing: exercise the playbook on a lab device of each major class: collect the EFI partition, extract and compare firmware, and run a reflash. Measure the time each step takes so the incident commander can plan.

9.4 Metrics: share of device classes with known-good images on file; share of the fleet reporting attestation; time from trigger to isolation; share of the Windows fleet with current Secure Boot mitigations applied; number of devices replaced versus reflashed per incident.

See also the Rootkits and Bootkits Guide and the Linux Secure Boot and Shim Guide.

References: NIST: SP 800-61 Rev. 3 Incident Response Recommendations and Considerations for Cybersecurity Risk Management · NIST: SP 800-193 Platform Firmware Resiliency Guidelines · NSA: BlackLotus Mitigation Guide · Microsoft: KB5025885 Windows Boot Manager revocations for CVE-2023-24932 · ESET: LoJax, first UEFI rootkit found in the wild · MITRE ATT&CK: Pre-OS Boot: System Firmware · MITRE D3FEND: Firmware Verification

Related NHI Mgmt Group resources: Firmware and Boot Security Guide · Rootkits and Bootkits Guide · EDR Tampering and BYOVD Response Playbook · Incident Response Plan Template

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.