A custom system needs to confirm that unauthorized modifications are not introduced in early components before the main operating system loads. Which approach meets these needs?
Implementing a hardware-level password prompt at the firmware screen
Sending startup events to a remote log server once the OS is active
Launching an antivirus service after the operating system starts
Validating cryptographic signatures of boot elements before loading
An approach that checks cryptographic signatures in the early stages is effective in detecting any tampering before the OS loads. A password on firmware settings does not evaluate code integrity. Antivirus or logging services that start after the operating system is active do not secure the pre-OS environment. Validating the legitimacy of each component pre-boot significantly reduces the risk of compromised code being loaded.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are cryptographic signatures, and how do they work?
Open an interactive chat with Bash
Why is validating boot components critical before the operating system loads?
Open an interactive chat with Bash
What is the difference between pre-OS security and OS-level antivirus?