Firmware Methodology · SPI Flash Evidence

Hardware Dump vs. Software Dump of SPI Flash

Why the difference matters when firmware integrity is part of a security investigation.

Software Dump

Fast

Hardware Dump

Reference

Forensics

Trust Boundary
In brief

A software dump tells you what the host is able to show you

A hardware dump shows the physical contents of the SPI Flash chip.

A software-based readout of SPI Flash memory is useful, but on a potentially compromised host it should not be treated as final proof that firmware is clean and unmodified.

What is a software dump?

A software dump is performed from inside a running operating system or pre-OS environment through platform-controlled access paths: drivers, MMIO/I/O mappings, the chipset SPI controller and platform access controls.

It is valuable for routine maintenance, backups, version inventory, controlled testing and quick diagnostics when the current host state is trusted.

Why can it be misleading?

If code below the operating system can influence SPI reads, the dumping tool may receive data that looks valid while the physical flash contents differ.

This matters for SMM, UEFI firmware and bootkit scenarios where the platform itself may be part of the trust problem.

What is a hardware dump?

A hardware dump is acquired with an external programmer connected directly to the SPI Flash chip, for example via SOIC/SOP clip or chip-off analysis.

It avoids the operating system, host drivers and the motherboard's internal SPI controller as the data source.

Practical guidance

Use the right acquisition method for the trust question

Operational mode

For daily administration, inventory and diagnostics, a software dump is often sufficient if the host is trusted.

  • BIOS/UEFI version inventory
  • Routine backup or comparison
  • Controlled lab testing
  • Platform-security configuration review

Investigation / forensic mode

If firmware compromise is suspected, a software dump should not be the sole basis of analysis.

  • Power down and secure the device
  • Perform an external hardware dump
  • Repeat the readout and compare hashes
  • Compare against vendor reference firmware
  • Analyse BIOS/UEFI, NVRAM, Option ROM and ME/PSP regions

Where GGFW fits

GGSec Firmware Toolkit provides read-only acquisition, platform-security evidence, offline analysis and live/image correlation. It helps document what the platform exposes and how protections are configured.

For suspected compromise, GGFW evidence can be combined with external hardware acquisition and analyst-led firmware review.

Common confusion

Hardware sequencing is not a hardware dump

On Intel platforms, tools may refer to software sequencing and hardware sequencing as operating modes of the internal SPI controller. That does not mean the flash was read by an external programmer.

A true hardware dump means physically connecting an external programmer to the SPI Flash chip. Changing the operating mode of the internal SPI controller does not remove trust from the host platform.

Summary

Convenient readout vs. forensic evidence

Software dump

Fast, convenient and useful when the platform is trusted. It shows what the host access path returns.

Hardware dump

Reference acquisition method for potentially compromised systems. It reads the physical SPI Flash chip externally.

Proper analysis

A hardware dump alone does not prove firmware is clean. It provides reliable input material for structured firmware analysis.

Further reading topics include flashrom Intel sequencing documentation, CHIPSEC, MITRE Copernicus / Smite'em, LoJax, MoonBounce, CosmicStrand, TrickBoot, CERT VU#766164 and public chipset SPI flash programming references.