RidgeRun Platform Security Manual - 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.
- Introduction
- General Security Concepts
- Getting Started
- Contact Us
- Sponsor your Favorite Feature
Yocto Build Process
This section explains how the security features of NVIDIA Jetson platforms fit into a Yocto-based development workflow. The developer should first prepare and build a working reference image, confirm that the target Jetson platform boots correctly, and then apply the security procedures that match the product requirements.
The following sections describe how to configure, build, integrate, and validate each security mechanism within the Yocto build process. These procedures use the NVIDIA Jetson security capabilities together with the Yocto build system, allowing the required security configuration to become part of a reproducible product image.
Security Procedures
Each procedure identifies the required configuration, build integration, tools, commands, validation steps, and relevant limitations.
The developer should first confirm that the baseline Yocto image builds, boots, and operates correctly on the target Jetson platform before enabling security-specific configurations. This provides a known-good baseline that can be used to distinguish build or platform issues from problems introduced by the security configuration.
Yocto and Jetson Security Integration
The security objective is independent of the build system used by the product. For example, Secure Boot still provides a mechanism for authenticating software before execution whether the product is developed using the standard JetPack/L4T workflow or Yocto.
What changes is how the security configuration is integrated into the software build and deployment process.
In a Yocto-based product, the required security configuration should become part of the reproducible build wherever possible. Depending on the security mechanism, this may include:
- Yocto configuration variables.
- Recipes and classes.
- NVIDIA-specific Yocto layers.
- Signing configuration and cryptographic keys.
- Boot image generation.
- Root filesystem configuration.
- Trusted firmware or TEE components.
- Image deployment and flashing procedures.
The resulting images should be validated on the target hardware before production security settings are applied.