An organization's security team suspects code modifications at the earliest point of a device's startup sequence. Which method best validates that the device's code is untampered at every step prior to full operation?
Verify the startup code through periodic manual checks after each update.
Use a scanner to detect harmful changes when the OS finishes loading.
Enable a password on the device's interface to lock out unauthorized edits.
Activate a measured sequence that logs each step to a hardware-based trust mechanism.
Activating a measured sequence that logs each step to a hardware-based trust mechanism validates the code at multiple stages. This ensures cryptographic hashes are stored and compared for integrity. Setting a password on the interface may hinder unwanted access but does not address hidden changes to the code. Scanning after the operating system loads misses early modifications. Manual checks are sporadic and miss continuous verification at each startup phase.
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 is a hardware-based trust mechanism?
Open an interactive chat with Bash
What are cryptographic hashes and how are they used in code integrity checks?
Open an interactive chat with Bash
What is a measured boot sequence, and how does it ensure security?