Which security concept involves validating the device's bootloader before the operating system loads?

• A. Sideloading
• B. Bootloader Security
• C. Device Hardening
• D. Application Wrapping

Answer: (B)

This question tests the idea of establishing trust during the device boot by validating the bootloader before anything else runs. The bootloader is the first piece of code that starts after firmware hands control to the system, so ensuring its integrity is crucial to prevent attackers from loading malicious software early in the startup process. When the device boots, a trusted component (like the firmware) checks the bootloader’s digital signature; if it’s valid, the bootloader is allowed to execute and proceed to load the operating system, often continuing to verify subsequent components. This creates a secure chain of trust from firmware to bootloader to the OS, making it much harder for tampered or malicious boot code to take control. That focus on protecting and validating the bootloader itself—before the OS even loads—is what the term Bootloader Security captures. In practice, this concept is closely related to Secure Boot, which is a concrete implementation of that same protection mechanism. The other options describe different security ideas—sideloading is about installing apps from outside official sources, device hardening is a broad set of practices to reduce risk, and application wrapping protects apps rather than the boot process.