Skip to the content ForoHackers
Log inJoin

Hardware security: start here

Hardware security
#805 · Ophuscado · · Report

Hardware security is protecting the physical devices and chips that software trusts: processors, secure elements, boards and their debug ports. Software protections assume the hardware beneath them behaves, so flaws here are hard to patch and can undermine everything above. Study on your own devices and training boards.

Key concepts

  • Root of trust: a small, trusted component, such as boot ROM or a secure element, that starts the chain of verified software.
  • Secure boot and measured boot: each stage verifies, or records, the next before running it.
  • Side channels: timing, power, electromagnetic emissions and cache behaviour can leak secrets that software never reveals.
  • Physical access: debug ports, exposed buses and removable storage matter once an attacker holds the device.
  • Isolation: trusted execution environments and memory protection separate sensitive code from the rest.

Vocabulary

  • TPM: trusted platform module, a chip that holds keys and records boot measurements.
  • Secure element: a tamper-resistant chip for keys and credentials.
  • Fault injection: disturbing a chip, by voltage or clock glitches, to make it misbehave; also a way to test resilience.
  • Debug lock: disabling or protecting JTAG and similar ports in production.

What to study, in order

  1. Digital electronics and a microcontroller board, so you know what the pins carry.
  2. Secure boot: build one on a development board with signature checks.
  3. Read how a TPM measures boot and seals keys, and use one on your own computer for disk encryption.
  4. Study side-channel and speculative-execution research papers at the concept level, and the mitigations.
  5. Write a hardware threat model for a small device: who can touch it, which ports exist, what they expose.

Related tags

#firmware #bootloaders #microarchitecture #hardware-hacking #iot

Log in or join to reply.