UEFI

UEFI
Name	UEFI
Caption	Unified Extensible Firmware Interface architecture
Developer	Unified Extensible Firmware Forum
Introduced	2005
Platform	x86, x86-64, ARM, ARM64, Itanium
Predecessor	BIOS

UEFI The Unified Extensible Firmware Interface is a specification for firmware interfaces between platform firmware and operating systems. It replaces legacy BIOS boot firmware on many Intel-based and AMD-based systems, enabling modern features such as native network boot, GUID Partition Table support, and a modular driver model. Major industry participants include Microsoft, Intel, Apple Inc., AMD, Dell Technologies, and Hewlett-Packard Enterprise.

Overview

UEFI defines a standardized software environment for booting operating systems and running pre-boot applications on platforms from vendors such as ASUS, Lenovo, Acer Inc., Samsung Electronics, Sony Corporation, and Toshiba. The specification is maintained by the Unified Extensible Firmware Forum with contributions from firms including Phoenix Technologies, Insyde Software, American Megatrends, Canonical (company), Red Hat, and Google. UEFI supports executable formats and runtime services used by operating systems like Microsoft Windows, Linux kernel, FreeBSD, macOS, and embedded systems developed by Wind River Systems.

History and Development

UEFI evolved from the Intel-led Intel Boot Initiative and its predecessor projects such as EFI, with early involvement from Intel Corporation, Compaq, and AMD. Key milestones include the formation of the Unified Extensible Firmware Forum in 2005 and subsequent specification releases that expanded functionality for vendors including Lenovo Group Limited and Dell EMC. The adoption curve accelerated when Microsoft Windows 8 introduced Secure Boot requirements, prompting coordination between Microsoft, hardware OEMs, and operating system projects like Canonical and SUSE to manage platform keys and certificate policies. The transition affected server vendors such as IBM and Oracle Corporation and cloud providers including Amazon Web Services, Microsoft Azure, and Google Cloud Platform.

Architecture and Components

UEFI architecture comprises a driver model, boot manager, runtime services, and configuration tables. Firmware vendors such as Phoenix Technologies Ltd., American Megatrends Inc., and Insyde Software Corporation implement platform firmware that loads drivers and protocols similar to device stacks used by Intel and AMD chipsets. Components include the PE/COFF executable format inherited from Microsoft Visual C++, device drivers for peripherals from NVIDIA Corporation and Broadcom, and protocols consumed by operating systems such as Red Hat Enterprise Linux and SUSE Linux Enterprise Server. The specification references standards like the GUID Partition Table and cryptographic algorithms maintained by RSA Security and NIST.

Boot Process and Secure Boot

The UEFI boot sequence replaces the traditional Master Boot Record-based flow used by vendors such as IBM PC Company with a multi-stage process: platform initialization, driver enumeration, Boot Manager execution, and OS loader invocation. Secure Boot uses public key infrastructure involving certificates from authorities such as Microsoft Corporation and opens mechanisms for third-party signing used by distributions like Debian and Fedora Project. Platform Key and Key Exchange Key management interact with tools from Canonical, Red Hat, and system utilities in OpenBSD and NetBSD. Network boot options integrate with services from PXE ecosystem vendors and server provisioning tools from VMware and Xen Project.

Implementation and Platform Support

UEFI implementations run on architectures including x86, x86-64, ARM, and Itanium supported by platforms from Intel Xeon, AMD EPYC, Qualcomm Snapdragon, and Apple M1-family systems. Major motherboard manufacturers like Gigabyte Technology and MSI ship UEFI firmware with graphical interfaces. Operating system support is provided by Microsoft Windows 10, Windows Server, distributions from Debian Project, Red Hat, SUSE, and BSD variants from FreeBSD Foundation. Virtualization platforms including VMware ESXi, KVM, Hyper-V, and Xen Project implement UEFI firmware for virtual machines; cloud images are provisioned for providers such as Amazon EC2 and Google Compute Engine.

Configuration and User Interface

UEFI exposes configuration through UEFI Shell, manufacturer GUIs, and platform setup utilities from American Megatrends and Insyde. Graphical configuration utilities resemble components in systems by Dell Technologies and HP Inc. and can be accessed alongside tools like efibootmgr on Linux distributions including Ubuntu and Fedora. Advanced configuration and firmware updates integrate with management frameworks from Redfish, Intels Management Engine-related tooling, and enterprise management suites from Microsoft System Center and VMware vSphere.

Security Issues and Vulnerabilities

UEFI security considerations include Secure Boot enforcement, firmware rootkits, and supply-chain attacks investigated by researchers at Google Project Zero, Kaspersky Lab, ESET Research, and Symantec. Vulnerabilities have been reported affecting implementations by Insyde Software, Phoenix Technologies, and American Megatrends, prompting advisories coordinated with CERT Coordination Center, US-CERT, and vendors like Microsoft. Mitigations include measured boot, Trusted Platform Module support standardized by the Trusted Computing Group, firmware signing, and platform attestation used by enterprise vendors such as Cisco Systems and Palo Alto Networks.

Category:Firmware