White Paper

Securing Embedded Operating Systems: The Key to Cyber Resiliency at the Edge

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

Contents of this Issue

Navigation

Page 5 of 5

WHITE PAPER Securing Embedded Operating Systems: The Key to Cyber Resiliency at the Edge mrcy.com 6 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. 8227.00E-0726-wp-SecuringEmbeddedOperatingSystems 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 EMEA Headquarters Avenue Eugène-Lance, 38 PO Box 584 CH-1212 Grand-Lancy 1 Geneva, Switzerland +41 22 884 51 00 tel RELIANCEONE™ FOR LINUX As cyberattacks increase against vulnerable commercial, infrastructure and defensive systems, the need for specialized security software for embedded OS is growing concurrently. Mercury's RelianceOne for Linux offers robust Linux system- hardening and security capabilities for operationally deployed Linux systems. See our NAVAIR case study and RMF control- mapping whitepaper for how this approach performs against real programs and real compliance requirements. RelianceOne is designed using a threat model that assumes an attacker will gain root (admin) access to your system, meaning it maintains the integrity and confidentiality of critical data and configurations while assuring operations. It also lets customers rapidly and affordably address the majority of their technical AI/cybersecurity controls with a single product. RelianceOne protects container contents from registry to runtime, ensuring image contents remain confidential and authentic. Policies limit damage from malicious code and seamless integration with allowlisting enables secure updates to container workloads while automatically blocking malicious workloads. Simplify mandatory access control ▪ Simplifies mandatory access control (MAC) policy creation — only protect required apps, libraries, scripts and data ▪ Denies default access to protected assets, even from root, and restricts hardware access ▪ Blocks unauthorized basic input-output system and firmware changes ▪ Secures software updates and cryptographically protects MAC policies in secure boot OS hardening and attack surface reduction ▪ Removes unneeded OS features that aid attacker analysis ▪ Blocks unsigned modules and process debugging ▪ Eliminates kernel features that could weaken hardened configurations Runtime and at rest security ▪ Enforces runtime protections: no debugging, copying, memory reads or unauthorized code loading ▪ Verifies protected entities haven't changed; decrypts only when needed ▪ Binds sensitive apps and data to unique hardware to prevent cloning or execution on altered devices ▪ Cryptographically validates data and configuration files before protected apps can access them

Articles in this issue

Links on this page

view archives of White Paper - Securing Embedded Operating Systems: The Key to Cyber Resiliency at the Edge