Jump to content

RidgeRun Platform Security Manual - NXP i.MX95

From RidgeRun Developer Wiki

🚧 Documentation is under development

The RidgeRun Platform Security Manual guide is currently under active development. Some sections may be incomplete or change without notice.

Questions? Contact RidgeRun or email to support@ridgerun.com.

Follow us on: YouTube Twitter LinkedIn Email Share this page

Share This Page

NVIDIA partner logo NXP partner logo




NXP i.MX95

The NXP i.MX95 is designed for secure connected-edge systems that must process data locally, respond in real time, and remain trustworthy throughout their lifetime. Its combination of Cortex-A55 application processing, real-time and safety domains, edge-AI acceleration, high-speed connectivity, and EdgeLock Secure Enclave makes it suitable for demanding automotive, industrial, medical, and IoT applications.

These capabilities also increase the security responsibilities of the developer. A platform that controls vehicle functions, industrial equipment, cameras, medical devices, or connected gateways must protect more than the initial boot image. It must establish trust at startup, authenticate software before execution, protect sensitive data, accept only authorized updates, and prevent vulnerable software from being restored.

This guide presents a practical path for securing an i.MX95 platform. It explains the boot and trust architecture, shows how the Yocto build participates in the security flow, and provides procedures for Secure Boot, encrypted boot, disk encryption, secure OTA updates, and antirollback.

The developer can use this guide to move from a working reference image to a validated security configuration. Each stage explains what is being protected, where the security decision is made, how the result can be tested, and what evidence should be collected before the platform is prepared for production enforcement. The Yocto-specific security procedures are organized under Yocto Build Process.

These protections address different threats and should be planned and validated together.


Security Flow

The Security Flow introduces the i.MX95 boot architecture, security concepts, trust boundaries, and the overall path from a fresh platform to a security-enabled product.

Yocto Build Process

The Yocto Build Process section contains the platform-specific security flow and the detailed procedures required to build, install, and validate the security features.

See NXP i.MX95 Yocto Build Process.




Cookies help us deliver our services. By using our services, you agree to our use of cookies.