RidgeRun Platform Security Manual - Platform Support

🚧 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
      • Secure Boot
      • Trusted Execution Environment (TEE)
      • Disk Encryption
  • NXP i.MX95
    • Security Flow
    • Yocto Build Process
      • Secure Boot
      • Disk Encryption
      • Over-the-Air (OTA)
      • Antirollback
• Contact Us
• Sponsor your Favorite Feature

The RidgeRun Platform Security Manual provides practical guidance for implementing and validating security mechanisms on embedded Linux platforms.

Security capabilities and implementation procedures vary depending on the SoC, hardware platform, BSP, operating system, build system, and software release.

The following table shows the security features currently supported and covered by this manual for each platform.

Security features and supported platforms

Security Feature	NXP i.MX95	NVIDIA Jetson
Secure Boot	Supported	Supported
Trusted Execution Environment (TEE)		Supported
Disk Encryption	Supported	Supported
Trusted Platform Module (TPM)		Supported
Secure OTA	Supported	Supported
Anti-rollback	Supported
Kiosk Mode / Access Restrictions		Supported

Info

Supported indicates that the security feature is currently covered by the RidgeRun Platform Security Manual for that platform. An empty entry does not necessarily mean that the hardware is incapable of supporting the feature; it means that the feature is not currently covered as a

supported implementation in this manual.

NXP i.MX95

The NXP i.MX95 section provides a practical path for implementing and validating security mechanisms using the platform's security architecture.

The guide explains the boot and trust architecture and provides procedures for the security features currently supported by this manual, including Secure Boot, disk encryption, secure OTA updates, and anti-rollback.

The platform-specific procedures are integrated into the i.MX95 Yocto build process and include implementation and validation steps.

See NXP i.MX95 Security for the available guides.

NVIDIA Jetson

The NVIDIA Jetson section provides practical guidance for implementing and validating security mechanisms available on Jetson platforms.

The documentation covers security features such as Secure Boot, Trusted Execution Environments (TEE), disk encryption, Trusted Platform Module (TPM) integration, secure OTA updates, and system access restrictions.

Depending on the product software architecture, these security mechanisms can be integrated using JetPack / L4T or a Yocto-based build process. The security objective remains the same, while the build, configuration, signing, and deployment procedures may differ.

See NVIDIA Jetson Security for the available guides.

Platform and software version considerations

Security support should always be evaluated against a specific hardware and software baseline.

Implementation details may vary depending on:

• SoC and module.
• Board configuration.
• BSP release.
• Bootloader version.
• Linux kernel version.
• JetPack / L4T release.
• Yocto release and layers.
• Security lifecycle or fuse configuration.
• Product-specific hardware configuration.

A security procedure validated on one hardware or software configuration should not automatically be assumed to apply unchanged to another.

Other platforms

The platforms listed above represent the security implementations currently covered by the RidgeRun Platform Security Manual.

RidgeRun can also evaluate and implement security mechanisms for embedded platforms that are not currently covered by this manual. This can include evaluating platform security capabilities, mapping them to product security requirements, implementing the required mechanisms, and validating the resulting security configuration.

Please Contact RidgeRun for engineering support with a platform or security requirement not currently covered by this manual.

RidgeRun Platform Security Manual

Back to top ↑ < >