UEFI Architecture and Boot Process
You'll learn how modern systems use UEFI firmware to initialize hardware and securely load the operating system, replacing legacy BIOS.
What Is UEFI?
Unified Extensible Firmware Interface (UEFI) is the modern firmware standard that sits between your hardware and operating system. Think of it as the "first responder" when you press the power button—it wakes up hardware, runs diagnostics, and hands control to your OS bootloader.
Unlike the old BIOS (limited to 16-bit mode, 1MB addressable memory, and MBR partition schemes), UEFI operates in 32-bit or 64-bit mode, supports GPT partitions, and provides a standardized programming interface.
Boot Stages Overview
- SEC (Security Phase): CPU initializes, verifies firmware isn't tampered with
- PEI (Pre-EFI Initialization): Basic hardware initialization—RAM, chipset
- DXE (Driver Execution Environment): Loads device drivers, initializes storage, graphics, network
- BDS (Boot Device Selection): Presents boot menu, locates bootloader on disk
- TSL (Transient System Load): Executes the chosen OS bootloader
- RT (Runtime): OS takes over, but UEFI services remain available
Security Implications
UEFI's architecture enables Secure Boot, which verifies digital signatures on bootloaders and kernel modules before execution—preventing rootkits from loading during startup. The firmware itself is stored in writable flash memory, making it a target for persistent malware if not properly protected.
Each boot stage builds a chain of trust: SEC verifies PEI, PEI verifies DXE drivers, and so on. Breaking this chain allows attackers to persist below the OS level, invisible to traditional antivirus.
Key Takeaway: UEFI replaces legacy BIOS with a modular, extensible firmware architecture that initializes hardware through distinct boot phases and enables modern security features like Secure Boot through a cryptographic chain of trust.