We are pleased to announce the publication of a white paper jointly developed by Renesas and wolfSSL. Security Technology Trends in Industrial Automation Equipment Secure industrial automation equipment for evolving cybersecurity demands with lifecycle-based design, regulatory readiness, secure boot, OTA updates, key management, PQC migration, and Renesas RA/RX/RZ hardware security with wolfSSL/wolfBoot stacks—use this guide […]
Read MoreMore TagCategory: wolfBoot
wolfSSL Advances Functional Safety with ISO 26262 Documentation and ASIL-D Certification Roadmap
As automotive software continues to grow in complexity, functional safety has become just as important as cybersecurity. To help customers build safety-critical systems, wolfSSL now offers ISO 26262 documentation designed to simplify the integration of wolfSSL into products pursuing Automotive Safety Integrity Level (ASIL) certification. This documentation provides developers with the supporting materials needed to […]
Read MoreMore TagwolfBoot 2.9.0 Released
The wolfSSL team is pleased to announce wolfBoot 2.9.0, expanding hardware support, adding new image and cryptographic options, and continuing security hardening across boot and update flows. More Hardware Targets wolfBoot 2.9.0 adds support for several new platforms, including: STM32N6, STM32U3, STM32C5, STM32G4 and STM32WBA NXP LPC54S018M-EVK and Kinetis KL26 Xilinx Zynq-7000 ZC702 NXP T2080 […]
Read MoreMore TagwolfBoot Brings Verified Boot to AArch64 UEFI: Booting Linux on the NVIDIA Jetson Orin Nano
wolfBoot now runs as a native AArch64 UEFI application, extending its measured, cryptographically verified boot to any 64-bit ARM platform that boots through UEFI firmware, and anchoring a complete ARM Root of Trust (RoT) from silicon to the operating system. We validated it end to end on an NVIDIA Jetson Orin Nano Developer Kit, taking […]
Read MoreMore TagwolfBoot Adds Persistent Failure Diagnostics
Ever had a device in the field reject a firmware update or roll back to an older image, with no clue why? wolfBoot can now tell you. With the new WOLFBOOT_PERSIST_FAILURE_STATUS option, wolfBoot records the cause of every update, self-update and rollback failure into a dedicated flash region, so your application can read it back […]
Read MoreMore TagwolfBoot as the Xilinx ZynqMP FSBL: a full-featured secure first-stage replacement
wolfBoot can now run as the First Stage Boot Loader (FSBL) on Xilinx ZynqMP, replacing the stock Xilinx FSBL entirely. On a ZCU102 (xczu9eg) the BootROM hands control straight to wolfBoot in on-chip memory (OCM) at EL3; wolfBoot brings up the processing system, verifies a signed image with its own keys, and boots Linux to […]
Read MoreMore TagwolfBoot Now Supports the STM32WBA
wolfBoot, the secure bootloader from wolfSSL, has a new target: ST’s STM32WBA family of Cortex-M33 wireless microcontrollers with TrustZone and Bluetooth LE 5.4. The port has been validated on the NUCLEO-WBA55CG board (STM32WBA55CG: 1 MB flash, 128 KB SRAM). Why the STM32WBA The WBA family is ST’s current-generation wireless line: an Arm Cortex-M33 with TrustZone-M, […]
Read MoreMore TagwolfBoot Microchip PolarFire SoC support for full HSS replacement
wolfBoot can now boot a Microchip PolarFire SoC (MPFS250T) entirely on its own — no Hart Software Services (HSS) required — and bring up 4-CPU SMP Linux from a signed, verified image. One bootloader, one root of trust wolfBoot can now run in M-Mode directly on the E51 hart out of eNVM and handles all […]
Read MoreMore TagLMS versus XMSS versus SLH-DSA for Secure Boot
Here at wolfSSL we always stay on top of our customer’s requirements. By now you’ve heard us talk about the NSA’s (National Security Agency) CNSA 2.0 (Commercial National Security Algorithm Suite 2.0) ad nauseum. Well, let’s focus in on it again and zero in on that first line: It states that for Software and Firmware […]
Read MoreMore TagwolfBoot for CNSA 2.0 Secure Boot on Zynq UltraScale+ MPSoC
Executive Summary Problem: Zynq UltraScale+ MPSoC secure boot authenticates the FSBL with RSA-4096 in immutable BootROM. CNSA 2.0 requires post-quantum algorithms for long-term software and firmware verification. RSA-4096 is not quantum-resistant, so the BootROM cannot be the final CNSA 2.0 firmware-authentication answer. Solution: Use wolfBoot as the system-level post-quantum authorization layer. Keep AMD secure boot […]
Read MoreMore Tag