Active Certificates: wolfSSL holds two active FIPS 140-3 certificates #4718 and #5041. Download wolfSSL → Entropy Validation: An Entropy Source Validation (ESV) is currently at the CMVP for an in-house, high-performance software jitter TRNG and the Jan 1, 2026 Transition! In addition to the above, here is a roadmap of how 2026 will go for […]
Read MoreMore TagMonth: March 2026
Is my part supported in 2026
It has been a while since we’ve updated our supported parts list. Here it is for this year!! If you do not see your part on this list, don’t worry. Reach out to us at facts@wolfssl.com letting us know the details of your system, and we can get you in touch with our porting experts. […]
Read MoreMore TagLive webinar: How to Get CRA-Ready: Secure Devices and Simplify Compliance
The EU Cyber Resilience Act (CRA) is about to reshape how every connected device is designed, secured, and maintained. Register now: How to Get CRA-Ready: Secure Devices and Simplify Compliance Date: March 19 | 9 AM PT As the CRA introduces new expectations for secure development and long-term product protection, teams need a clear understanding […]
Read MoreMore TagLive Partner Webinar: Post-Quantum mTLS 1.3 On Embedded Linux
Unlock Post-Quantum Security for Embedded Systems with mTLS 1.3 Join us on March 18 at 9 AM PT to learn how to implement post-quantum mTLS 1.3 on embedded Linux devices. This webinar guides engineers and security architects through generating, deploying, and validating quantum-resistant certificates on real hardware, from Raspberry Pi to i.MX.93, without the usual […]
Read MoreMore TagwolfHSM Support for Renesas RH850 F1KM
wolfHSM provides a hardware security module framework optimized for embedded systems, with continuous enhancements for the Renesas RH850 platform. Download wolfSSL → The RH850 F1KM port is designed to align closely with upstream wolfHSM and wolfSSL development while taking advantage of RH850 hardware cryptographic acceleration. Ongoing improvements focus on performance, reliability, and maintainability. Key technical […]
Read MoreMore TagRust support for post-quantum cryptography
wolfSSL is excited to announce the addition of post-quantum cryptographic algorithms in Rust to the wolfSSL 2026 roadmap! The planned additions to the wolfSSL Rust API include the ML-KEM, ML-DSA, LMS, XMSS, Falcon, and SPHINCS+ algorithms. These additions will bring direct support to Rust projects for the robust wolfSSL implementations of the most future-proof post-quantum […]
Read MoreMore TagAnnouncing wolfHSM TDA4 Platform Release v1.0.0
We’re pleased to announce the wolfHSM TDA4 platform release v1.0.0, expanding wolfHSM support to the Texas Instruments TDA4 family of SoCs. What’s Included in the TDA4 v1.0.0 Release Simple Build Environment An easy-to-use build environment designed to get developers up and running quickly on the application cores and the secure HSM core. wolfHSM Client and […]
Read MoreMore TagMake Your TPM Speak PKCS#11: Enable Hardware-Backed Keys Without Rewriting Your App
Trusted Platform Modules (TPMs) are widely available on modern platforms and provide a strong hardware-based root of trust for cryptographic keys. At the same time, many applications already rely on the PKCS#11 API to interact with Hardware Security Modules (HSMs) and other secure key stores. Bridging these two worlds allows developers to take advantage of […]
Read MoreMore TagLive Partner Webinar: Integrating Crypta Labs’ QRNG into wolfSSL
Integrating Crypta Labs’ QRNG into wolfSSL Join us for a focused joint webinar exploring how Crypta Labs’ Quantum Random Number Generator (QRNG) technology integrates with the wolfSSL cryptographic library using its RNG callback facility. The session walks through how external quantum entropy can be connected to wolfSSL and what that means in practice for TLS […]
Read MoreMore TagReplacing TF-M on ARMv8-M: wolfBoot Secure Domain & wolfPSA, now integrated with Zephyr for CRA compliance
ARMv8-M TrustZone (TrustZone-M) gives Cortex-M23, Cortex-M33, Cortex-M35P and related MCUs a clean, hardware-enforced way to split a system into two execution environments: Secure world: the hardware root of trust, key material, security services, and the code that configures isolation. Non-secure world: the main RTOS and application logic, kept away from secrets by hardware boundaries. In […]
Read MoreMore Tag