RidgeRun Platform Security Manual - NXP i.MX95 Yocto Build Process

🚧 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:

Share This Page

Facebook Twitter LinkedIn WhatsApp Email Copy Link

Close

Send Email Using

Gmail (Web) Thunderbird (default mail app)

Close

RidgeRun Platform Security Manual

< >

RidgeRun Platform Security Manual from RidgeRun

Contents Pin

• Introduction
  • Why Do I Need To Secure My Project?
  • What Do I Need Before Securing My Project?
  • When Is My Project Secure Enough?
  • How Can RidgeRun Help?
• General Security Concepts
  • Root Of Trust
  • Secure Boot
  • Trusted Execution Environment (TEE)
  • Trusted Platform Module (TPM)
  • Measured Boot and Integrity Measurement Architecture (IMA)
  • Disk Encryption
  • Over-the-Air updates (OTA)
  • Kiosk Modes
• Getting Started
  • Platform Support
  • NVIDIA Jetson
    • JetPack Build Process
      • Security Flow
      • Secure Boot
      • Trusted Execution Environment (TEE)
      • Disk Encryption
      • Over-the-Air
        • Main Providers
        • NVIDIA Jetson - Mender
        • NVIDIA Jetson - RAUC
          • Bring Up and Yocto Integration
          • Update Flow and Custom Bootloader
          • Advanced Topics and Troubleshooting
      • Trusted Platform Module (TPM)
      • Kiosk Modes
      • Bringing NVIDIA Jetson Secure Boot To Production
        • Integrate your NVIDIA flashing scripts with HSM
        • How to integrate your signing server with CI/CD
        • Setting up your signing server
        • Integrating your signing server with Yocto
    • Yocto Build Process
      • Build Environment Setup
      • Secure Boot
        • Boot Chain
        • Key Management
        • Fuse Configuration
        • Factory Provisioning
      • Kernel Hardening
      • Trusted Execution Environment (TEE)
      • Disk Encryption
      • Over-the-Air Updates
      • Production Checklist
  • NXP i.MX95
    • Security Flow
    • Yocto Build Process
      • Secure Boot
      • Disk Encryption
      • Over-the-Air (OTA)
      • Antirollback
• Contact Us
• Sponsor your Favorite Feature

NXP i.MX95 Yocto Build Process

This section explains how the security features of the NXP i.MX95 platform fit into a Yocto-based development workflow. The developer should first prepare and build a working reference image, confirm that the board boots correctly, and then apply the security procedures in the order that matches the product requirements.

The security flow provides the overall sequence, while the following sections describe how to configure, build, install, and validate each protection. The procedures are based on a Toradex Verdin i.MX95 platform and should be adapted when a different BSP, machine configuration, or boot-media layout is used.

Info

The developer can build the reference image used throughout this guide by following the NXP i.MX95 Technical Guide: Yocto Support guide.

Security Flow

The Security Flow provides the platform overview and the “From Fresh to Secure” roadmap. It is located directly under the i.MX95 platform because its concepts apply beyond the Yocto build.

Security Procedures

• Secure Boot
• Disk Encryption
• Over-the-Air (OTA)
• Antirollback

Each procedure identifies its required setup, tools, commands, validation steps, and limitations. The developer should complete the baseline build and installation before beginning the security-specific validation.

RidgeRun Platform Security Manual

Back to top ↑ < >