Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
UEFI and BIOS security protects the firmware that initialises a computer before any operating system loads, covering flash write protection, signed updates, Secure Boot, and System Management Mode.

What Is UEFI and BIOS Security?
Press the power button and a great deal happens before any operating system exists. UEFI firmware initialises memory controllers, trains buses, enumerates devices, and eventually hands control to a bootloader. It is a substantial piece of software, typically several megabytes of code in SPI flash, with its own drivers, its own network stack in some implementations, and full authority over the machine. UEFI and BIOS security is the practice of protecting that software and the flash it lives in.
Firmware executes first, which means it can decide what runs next and what that software is permitted to see. It persists in flash memory on the motherboard, so replacing the disk changes nothing. It is invisible to operating system security tooling, because that tooling is inside the environment the firmware created. And one component of it, System Management Mode, runs at a privilege level above the kernel and the hypervisor, entered by hardware interrupt, with its own memory region. A compromise of SMM is sometimes described as ring minus two, and that is not marketing.
BIOS is the older interface this replaced; UEFI is the specification nearly all systems made since about 2010 implement. The security properties are different enough that the terms are not interchangeable, but estates contain both, and legacy compatibility support modules reintroduce old weaknesses on modern hardware.
Research has repeatedly found protections present but switched off. CHIPSEC, the open framework maintained by Intel, tests exactly these registers and is the fastest way to discover that a production laptop model has SMM protection disabled. ThinkPwn and related SMM vulnerabilities allowed arbitrary code execution in System Management Mode across multiple vendors. LogoFAIL, disclosed by Binarly in December 2023, found exploitable image parsers in boot logo handling across most major firmware codebases, meaning a crafted image file in the EFI system partition could execute code before the operating system.
Key material has leaked too. The MSI breach of April 2023 resulted in the publication of Intel Boot Guard private keys for a number of product lines, which removes the hardware anchor for those models entirely. PKfail in July 2024 showed hundreds of models shipping with publicly known test platform keys.
Implants built on these weaknesses include LoJax, MoonBounce, and BlackLotus, covered in more detail in our note on firmware security.
Start with inventory: firmware version per device, collected centrally alongside operating system patch state. Most endpoint management platforms already report it and nobody looks. Then run CHIPSEC, or your vendor’s equivalent assessment, against a sample of each hardware model you deploy, before standardising on it rather than after.
Set firmware administrative passwords through vendor management tooling, disable legacy boot and external boot where the role does not need it, and bring firmware into patch management with a defined cadence. On Linux, fwupd and the Linux Vendor Firmware Service make this routine. Enable BitLocker or equivalent so boot measurements are enforced, and treat an unexpected recovery prompt as a potential tampering signal rather than a nuisance.
NIST SP 800-147 and SP 800-193 provide the requirement language for procurement, and the NCSC device security guidance expects firmware update support to be a purchasing criterion with a stated support period. Our Hardware Penetration Test Services assess platform firmware configuration on the specific models you deploy, which is more useful than a vendor datasheet.
BIOS is the legacy firmware interface that dates from the early PC and offers no signature verification of what it loads. UEFI is the modern specification that replaced it, with a modular driver architecture, GPT disk support, and security features including Secure Boot and signed capsule updates. Legacy compatibility modes in UEFI reintroduce the older boot path and should be disabled where possible.
Yes, if the flash write protections are not enabled. Code running with administrative or kernel privileges can attempt to write SPI flash directly, and several documented implants did exactly that. Correctly configured protection registers, signed update enforcement, and a hardware root of trust such as Boot Guard are what prevent it, which is why verifying those settings matters more than assuming they are set.
Use CHIPSEC, the open source platform assessment framework maintained by Intel, which tests flash write protection, SMM protections, and related configuration and reports which checks fail. Run it against a representative device of each hardware model during build validation. Vendor management tools also report firmware password state and Secure Boot status for central reporting.
Apply them on a defined cadence with a pilot group, rather than automatically across the estate. A failed firmware update can leave a device unbootable, so staged rollout and a tested recovery path matter more here than for operating system patches. Security-relevant firmware advisories, particularly those affecting boot integrity or management controllers, justify an accelerated schedule.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.