Examkin

Question

Difficulty: MediumHardware and Embedded Systems Security

An enterprise data center security team is deploying new high-density rack servers equipped with Baseboard Management Controllers (BMCs). To protect against persistent firmware-level compromise, the security architect must ensure that the BMC initial boot code cannot be altered and that attackers cannot downgrade the firmware to a previously signed version containing known security vulnerabilities. Which of the following hardware security mechanisms should the architect specify to fulfill these requirements?

  1. Hardware Root of Trust anchored in One-Time Programmable (OTP) eFuses with anti-rollback version trackingAnswer
  2. B
    Inline network intrusion prevention system (NIPS) configured to inspect and drop unapproved firmware flashing payloads
  3. C
    Continuous SIEM event log monitoring and alert rules targeting unauthorized management portal access
  4. D
    AES-256 symmetric encryption keys stored in flash memory to decrypt incoming firmware binaries prior to installation

Answer

Hardware Root of Trust anchored in One-Time Programmable (OTP) eFuses with anti-rollback version tracking
Establishing a hardware Root of Trust (RoT) anchored in One-Time Programmable (OTP) eFuses ensures that the initial boot code validation key is burned directly into silicon during manufacturing and cannot be altered. When combined with eFuse-backed anti-rollback version counters, the processor compares the version number of any incoming firmware against the hardware counter. If an attacker attempts to flash an older, vulnerable firmware version (even if validly signed by the vendor in the past), the hardware anti-rollback check fails and halts execution.

Step-by-Step Solution

1
Analyze the scenario requirements
Identified two primary hardware protection needs: immutable boot integrity verification and protection against firmware version downgrade attacks on out-of-band controllers.
Baseboard Management Controllers run low-level microcode that requires hardware-backed verification to prevent rootkits.
2
Evaluate hardware security mechanisms for boot integrity and anti-rollback
One-Time Programmable (OTP) eFuses store cryptographically hashed keys permanently in silicon, establishing an unalterable Root of Trust (RoT). eFuse counters are blown during firmware updates to enforce anti-rollback.
Software-based or flash-based storage can be overwritten, whereas eFuses cannot be reversed once blown.
3
Differentiate correct hardware control from network, detective, or symmetric crypto alternatives
Select the option that combines hardware Root of Trust via OTP eFuses with anti-rollback logic.
Network controls (NIPS), detective controls (SIEM), and symmetric keys in flash do not provide immutable hardware boot chain validation.

Key Concept

Hardware Root of Trust and Anti-Rollback Protection
Estimated Time:1m 30s
Rate this question

Topics

Hardware and Embedded Systems Security

More questions from this topic