TechKnowSurge
VideoSecurityFree

Hardening - Boot Order

Controlling the boot order on a computer is a foundational security measure that prevents unauthorized users from bypassing the operating system by booting from external media such as USB drives or network sources. Disabling unused boot options like PXE and USB boot reduces the attack surface and keeps the system locked to its intended startup path.

Complete this video to capture a CTF flag worth 1 point.

About this video

Boot order defines the sequence in which a computer checks available devices for a loadable operating system, and its default configuration frequently introduces unnecessary security risk. Many systems are set to attempt a PXE network boot, then check optical or removable drives, then USB devices, and finally fall back to the primary hard drive or solid-state drive. While this sequence was designed for legitimate use cases like remote OS deployment and system repair, it also means that anyone with physical access to a machine can insert a bootable USB drive loaded with a separate operating system and gain unrestricted access to the file system, bypassing any security controls on the installed OS entirely. Addressing this risk is a straightforward but essential step in system hardening. Once an operating system has been installed and configured, boot options that are no longer needed — particularly PXE boot and USB boot — should be disabled in the system firmware settings. USB boot can be re-enabled temporarily when legitimate maintenance requires it, then disabled again when the task is complete. Locking boot order to the primary drive, combined with a firmware password to prevent unauthorized changes to these settings, significantly reduces the risk of physical-access attacks that circumvent software-level security measures.

What you'll learn

What's covered

Boot Order Security

Key terms

Attack Surface
The total set of points in a system where an unauthorized user can attempt to enter or extract data.
Boot Order
The sequence in which a computer's BIOS or UEFI firmware attempts to load an operating system from available storage devices and interfaces.
Preboot Execution Environment
PXE
A network boot standard that allows computers to start and load an operating system or diagnostic image from a network server rather than a local storage device. PXE is used for mass OS deployment, diskless workstation configurations, and remote system recovery.
Vulnerability
A weakness in a system, application, or process that can be exploited by a threat actor.
Access Control
A security mechanism that restricts access to resources based on policies, roles, or identity.

Topics

System Hardening Boot Order Bios Uefi Pxe Boot Endpoint Security Attack Surface Reduction

Transcript

I remember back in my computer classes in high school, we would mess with the instructor, and I feel a little bit bad about it now, but we would try to change and manipulate the desktop or certain aspects of the computer. We would change that. And so what he would do is he'd start locking down the computer so we wouldn't be able to change certain aspects of the computer. And what we'd do to get around that is we just boot to a floppy. At the time, they were the 3 and 1/2 inch floppies. We'd pop those in there, we'd boot to floppy, and then we could essentially do anything that we wanted to do.

So one thing that we need to do with our computers is to make sure that an adversary or somebody is not allowed to do that. We need to change the boot order and make sure that the boot order is set properly.

How the Boot Order Works

Computers will have some sort of boot order. What was common back about 20 years ago is it would first of all try the network. It would try to do what's called a PXE, or pixie, boot. So it would look at the network and say, hey, do I have an operating system that's available to me? And then if it didn't, then it would go to, at the time there were floppy drives or disc drives, and you would stick a disc into there, then it would try that. And if that didn't have it there, then it would go to USB. And if that wasn't there, then it would go to the hard disk drive.

The reason for this is because you might have had an operating system that needed to be repaired. The operating system was usually installed on some sort of solid state drive or disc drive, and so if you needed to repair that, you would stick in your USB, you'd boot to that, and then you would repair the operating system.

Why This Is a Security Problem

Now the problem is that people can get around security measures by doing this. What will happen is they could stick Linux on a USB thumb drive. They stick that into there, boot up to that Linux version, and then they have access to the full machine and are able to access files. This is problematic from a security perspective.

Changing the Boot Order

So one of the first things we're going to want to do, once we update and patch and do all of that, is that we're going to want to change the boot order and remove some of these. Like, we probably don't have a PXE boot on our system, so we turn that off. And USB: once we're done installing the operating system, we're going to want to turn off the USB boot and only turn it on when we're needing that functionality. So now it's just going to boot to the solid state drive or disc drive that you have on the system.

About TechKnowSurge

TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.

Explore free tools and programs →