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?
Launching an antivirus service after the operating system starts
Sending startup events to a remote log server once the OS is active
Validating cryptographic signatures of boot elements before loading
Implementing a hardware-level password prompt at the firmware screen
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 exactly are cryptographic signatures and how do they work in this context?
Open an interactive chat with Bash
How does validating pre-boot elements improve security over post-OS measures?
Open an interactive chat with Bash
What are examples of technologies commonly used for pre-boot validation?