Achieving FIPS 140-3 compliance on embedded Linux becomes difficult when different applications and system components rely on different cryptographic libraries.
This technical webinar shows how to build a unified FIPS 140-3 architecture on Yocto Linux using wolfCrypt FIPS. You’ll see how to replace or override OpenSSL, NSS, GnuTLS, libgcrypt, and Linux kernel cryptography, then walk through the practical integration and verification process.
This webinar covers
- Building a unified FIPS 140-3 architecture on embedded Linux
- Replacing OpenSSL, NSS, GnuTLS, libgcrypt, and kernel cryptography
- Integrating wolfCrypt FIPS into Yocto and Poky
- Generating FIPS configuration and verifying the module
- Current FIPS certificates and upcoming PQC support
Ask the Expert: Answers Key Questions
Our experts answer key questions about what attendees will learn
Why can’t I just validate OpenSSL?
Because applications, middleware, and the Linux kernel may each rely on different cryptographic implementations. A unified FIPS deployment requires every component to use the validated cryptographic module.
How do you get every Linux component onto one FIPS module?
OpenSSL, NSS, GnuTLS, libgcrypt, and Linux kernel cryptography can be redirected to wolfCrypt FIPS through providers, PKCS#11, shims, and the kernel module.
What does verification actually involve?
Verification includes generate the required FIPS configuration, run the module self-tests, and verify that system cryptographic operations are using the validated module.
Register now to learn how to replace multiple Linux cryptographic libraries with a unified FIPS 140-3 implementation.
Date: July 14 | 9 AM PT
As always, our webinar will include Q&A throughout. If you have questions about any of the above, please contact us at facts@wolfssl.com or call us at +1 425 245 8247.
Download wolfSSL Now