White Paper

White Paper: Hidden Risks of UEFI Secure Boot—and How RelianceOne™ Offers a Stronger Security Foundation

Issue link: https://read.uberflip.com/i/1544840

Contents of this Issue

Navigation

Page 4 of 4

WHITE PAPER The Hidden Risk of UEFI Secure Boot mrcy.com 5 Learn more Visit: mrcy.com Contact us The Mercury Systems logo is a registered trademark of Mercury Systems, Inc. Other marks used herein may be trademarks or registered trademarks of their respective holders. Mercury products identified in this document conform with the specifications and standards described herein. Conformance to any such standards is based solely on Mercury 's internal processes and methods. The information contained in this document is subject to change at any time without notice. © 2026 Mercury Systems, Inc. 8219.00E-0426-wp-UEFISecureBootComp MADE IN USA Corporate Headquarters 50 Minuteman Road Andover, MA 01810 USA +1 978.967.1401 tel +1 866.627.6951 tel +1 978.256.3599 fax International Headquarters Mercury International Avenue Eugène-Lance, 38 PO Box 584 CH-1212 Grand-Lancy 1 Geneva, Switzerland +41 22 884 51 00 tel Runtime Protection with a Kernel Protection Hypervisor To address these runtime threats, RelianceOne Trusted Platform includes a lightweight kernel protection hypervisor written primarily in Rust for memory safety. It is specifically designed to protect x86 CR0/CR4 control registers, preventing attackers from disabling critical security features during runtime. Unlike conventional hypervisors, Trusted Platform's runtime protection hypervisor does not virtualize or emulate hardware devices, resulting in virtually zero overhead for interrupt latency or instruction execution. Systems running Trusted Platform's runtime protection hypervisor boot Linux directly and operate with the performance characteristics of a "bare metal" environment. The runtime protection hyper visor protects itself against both kernel-level and DMA- based attacks, significantly constraining adversaries who achieve arbitrar y code execution within privileged components after secure boot attestation. This runtime protection extends trust beyond the boot process, providing substantially greater protection for cr yptographic key material and sensitive software or data released during RelianceOne Trusted Platform's measured boot process. PRE-DEPLOYMENT RUNTIME Reboot Trusted Platform seals Key Load Key into TPM Boot into desired boot state Trusted Platform Attempts unlock of key Boots into OS Boot System Trusted Platform checks OS signature

Articles in this issue

Links on this page

view archives of White Paper - White Paper: Hidden Risks of UEFI Secure Boot—and How RelianceOne™ Offers a Stronger Security Foundation