Category: wolfCrypt FIPS

We are pleased to announce the start of an official wolfSSL project to port wolfCrypt FIPS into libgcrypt. This initiative aims to replace the underlying cryptography in applications using libgcrypt with wolfCrypt’s certified algorithms. With wolfCrypt already achieving FIPS 140-3 certification, applications using libgcrypt’s API can immediately be deployed in environments that require certified cryptography, such as government, military, finance, and medical applications. This port not only enhances security but also saves developers significant time and effort. For developers, this integration means they can focus on building their applications without the burden of transitioning applications to meet cryptographic compliance. By using wolfCrypt, developers can ensure that their applications meet the highest security standards without the need for extensive testing and validation of multiple cryptographic libraries. This project also provides a seamless way to explore and evaluate wolfCrypt for future projects, offering a pathway to potentially transition applications to natively use wolfCrypt.

Furthermore, this effort has significant implications for Linux distributions, which often incorporate a wide array of cryptographic dependencies, such as libgcrypt, to provide comprehensive functionality to many packages. By ensuring that all cryptographic dependencies use a consistent cryptography provider like wolfCrypt, distributions can maintain uniform security standards across the entire system and applications. This consistency is crucial for reducing complexity and potential vulnerabilities that arise from using multiple cryptographic libraries. It simplifies the management of cryptographic standards and reduces the risk of incompatibilities or security gaps, particularly in environments where security and compliance are paramount.

Take a deeper look here: https://github.com/wolfSSL/libgcrypt-wolfssl/tree/libgcrypt-1.11.0-wolfCrypt

For more details or questions about this effort, please reach out to facts@wolfSSL.com or call us at +1 425 245 8247.

Download wolfSSL Now

This is an update to previous post Everything wolfSSL is Preparing for Post-Quantum as of Spring 2024 and an extension to post wolfSSL Support for Post-Quantum.

The National Institute of Standards and Technology (NIST) has recently updated its guidelines, enabling the certification of several post-quantum cryptographic algorithms through the Cryptographic Module Validation Program (CMVP). Notably, the digital signature algorithms ML-DSA (CRYSTALS-Dilithium), LMS, and XMSS are now fully certifiable under the updated SP800-140C standards.

In response to these developments, wolfSSL Inc. is proactively planning submissions to the CMVP for these algorithms. wolfSSL Inc. has a strong track record in cryptographic module validation, having previously achieved FIPS 140-3 Certificate #4718 for its wolfCrypt Module, the world’s first SP 800-140Br1 validated certificate.

While ML-KEM (CRYSTALS-Kyber) is not yet included in the approved security function list of SP 800-140C, wolfSSL is taking a forward-thinking approach by incorporating ML-KEM into its offerings. This strategic inclusion ensures that once ML-KEM receives approval and is certifiable, wolfSSL will be prepared to submit all four algorithms, ML-DSA, LMS, XMSS, and ML-KEM, for certification.

By staying ahead of regulatory changes and actively engaging in the certification process, wolfSSL continues to demonstrate its commitment to providing robust and compliant cryptographic solutions in the evolving landscape of post-quantum security.

Please don’t hesitate to contact us at support@wolfSSL.com or fips@wolfSSL.com anytime to share your feedback or input on this subject!

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

When it comes to securing data, cryptographic algorithms are the backbone of many systems. 3DES (Triple Data Encryption Standard) was once a FIPS (Federal Information Processing Standards) algorithm but is no longer supported by NIST as of 1 Jan 2024 (over 1 year ago!) Having 3DES in a FIPS module today could spell trouble on the near horizon, not only for security but also for compliance.

Early Expiration of Certificates

A FIPS certificate comes with an expiration date, but the CMVP has the authority to move a certificate to the “historical list” before that date or to “Revoke” a certificate if a non-compliance issue is found. Either action makes the certificate no longer valid for new procurements or for use in certain scenarios if already deployed in the field. The CMVP exercised this authority during the transition from SP 800-56Arev[1,2] to SP 800-56Arev3, which tightened the standards for key establishment methods. Modules that did not meet the updated criteria by July of 2022 were moved to the historical list ahead of their expected expiration dates.

The same could happen with certificates that include 3DES now. Should the CMVP decide to enforce a hard transition on 3DES, any certificate with that algorithm could be revoked or made historical sooner than its listed expiration date. This means one could suddenly lose compliance, disrupting operations and requiring urgent updates to systems which can take many months or years to complete as anyone in the FIPS space is well aware.

An Example of Future-Proofing

An excellent example of future-proofing is the wolfSSL FIPS 140-3 module certificate #4718. Unlike many competing solutions, wolfSSL ensured that 3DES was not included in the boundary of this module. This proactive decision protects users of the wolfSSL Inc. wolfCrypt FIPS 140-3 module from the risks associated with 3DES and potential early certificate invalidation by the CMVP. By contrast, most of the competition did not do this future planning and still include 3DES in their boundary. This leaves users of those modules exposed to potential compliance issues and security risks.

What Should You Do?

1. Avoid 3DES in New Designs: Choose FIPS modules that use stronger algorithms like AES. Ensure your vendors are aware of the risks and are providing compliant solutions.
2. Audit Your Current Systems: If you’re already using a FIPS-certified module with 3DES, plan to migrate to a more secure alternative or re-validate that module without 3DES included in the boundary. Don’t wait for the CMVP to force your hand.
3. Stay Informed: Keep an eye on updates from NIST and the CMVP. Understanding upcoming changes can help one with planning and preparing before CMVP decisions impact their systems.
4. Test Your Transition Plans: Ensure that moving away from deprecated algorithms like 3DES won’t cause unexpected issues. Test thoroughly in a controlled environment.

Conclusion

3DES served its purpose in its time, but it is simply a liability now. If your systems rely on a FIPS certificate that includes 3DES, it’s time to act. By planning ahead and staying informed, you can ensure your systems remain secure and compliant, no matter what changes the CMVP enforces. Choosing solutions like wolfSSL’s FIPS 140-3 module, which proactively excludes outdated algorithms, can give you peace of mind and protect you from future disruptions.

If you have any questions or would like to talk with one of our team about this subject please send an email to fips@wolfssl.com or support@wolfssl.com. For general inquiries, you can also reach out to facts@wolfssl.com or +1 425 245 8247. Our staff are more than happy to help any way they can.

Download wolfSSL Now

wolfSSL’s crypto library, wolfCrypt, has obtained a 5-year FIPS 140-3 Validated Certificate #4718. wolfCrypt FIPS is known for its unmatched portability, runs on everything, and is highly optimized for dozens of hardware targets.

WolfCrypt is commonly utilized in standard operating environments due to its royalty-free pricing model and exceptional support across multiple platforms. The wolfCrypt FIPS module has been validated on numerous Operating Environments (OEs). The current list of planned OEs for the wolfCrypt FIPS 140-3 certificate (#4718) is listed here for reference. wolfSSL can easily add additional OEs to existing wolfCrypt FIPS certificates. To learn more about this process, contact us at fips@wolfssl.com today!

Certificate #4718 Current OE List:

Operating System	Processor	Processor Algorithm Acceleration	Product (TBA = To Be Announced at a later time)
Android 13	Exynos 9611 without PAA	No	Samsung Galaxy XCover Pro
Linux 5.4	BCM56260B0IFSBG - Sabre2	No	WTM 4000
Red Hat Enterprise Linux Workstation 8.9	Intel® Xeon® W-2255 @ 3.7GHz	No	Precision 5820 Tower
FreeRTOS v10.4	Renesas R7FA6E10F	No	Network Interface Card for Aclara RF
Linux 5.15	Freescale i.MX7 Dual Arm Cortex A-7	No	iSTAR physical access controller
Linux 4.14	Intel® Atom® E3930 @1.30GHz	No	Ricoh IM C3010
Linux 4.14	Intel® Atom® E3940 @1.60GHz	No	Ricoh IM C4510
NET+OS v7.6	Digi International NS9210	No	Spectrum Infusion System
Yocto (kirkstone) 4.0	NXP i.MX6UL	No	Novum IQ Infusion Platform
MQX 3.4	NXP PowerQUICC II MPC8313e 32bit	No	FEI-Zyfer Time and Frequency System
CodeOS v1.4	CodeCorp CT8200 (ARM FA626TE)	No	Series CR2700 Code Reader(s)
OpenRTOS v10.5	STM32L4R5	No	Teledyne Webb SOM Module
Endace Crypto Firmware 2.1	Intel® Xeon® Silver 4316 CPU @2.30GHz	No	EndaceProbe 2144
Endace Crypto Firmware 2.1	Intel® Xeon® Silver 4316 CPU @2.30GHz	Yes	EndaceProbe 2144
Endace Crypto Firmware 2.1	Intel® Xeon® Gold 6338N CPU @2.20GHz	No	EndaceProbe 2184
Endace Crypto Firmware 2.1	Intel® Xeon® Gold 6338N CPU @2.20GHz	Yes	EndaceProbe 2184
Endace Crypto Firmware 2.1	Intel® Xeon® Gold 5418N CPU @1.80GHz	Yes	EndaceProbe 94C8
Endace Crypto Firmware 2.1	Intel® Xeon® Gold 6230N CPU @2.30GHz	Yes	EndaceProbe 92C8
Anyware Trusted Zero Client Firmware Kernel 6.1	AMD Ryzen Embedded R1305G	No	Anyware Trusted Zero Client
Anyware Trusted Zero Client Firmware Kernel 6.1	AMD Ryzen Embedded R1305G	Yes	Anyware Trusted Zero Client
Anyware Trusted Zero Client Firmware Kernel 6.1	AMD Ryzen Embedded R2314	Yes	HP tz655 Trusted Zero Client
Fusion Embedded RTOS 5.0	Analog Devices ADSP-BF516 (Blackfin)	No	Classone ® IP Radio Gateway
Linux 5.4	NXP i.MX8M	No	Harman MUSE MU Controller
Linux 4.9	ARM Cortex-A7	No	Harman N2612S Video encoder/decoder
Linux 5.10	NXP i.MX8	No	Harman N4321D audio transcoder
REDACTED Linux 5.4	Xilinx Zynq-7000 SoC	No	TBA
REDACTED Linux 5.4	Xilinx Zynq-7000 SoC	Yes	TBA
REDACTED Linux 4.19	Xilinx Zynq Ultrascale+	No	TBA
REDACTED Linux 4.19	Xilinx Zynq Ultrascale+	Yes	TBA
REDACTED Linux 4.9	Ambarella S5L SoC	No	TBA
REDACTED Linux 4.9	Ambarella S5L SoC	Yes	TBA
REDACTED Linux 5.4	i.MX8 Quad Max SoC	No	TBA
REDACTED Linux 5.4	i.MX8 Quad Max SoC	Yes	TBA
FreeRTOS v10.4	NXP i.MX RT1051	No	Harman CE-REL8 Universal Control Extender
Linux 5.15	MTK MT8395	No	Harman N3322D Video encoder/decoder
Android 14	Qualcomm SM8350 Snapdragon	No	Samsung Galaxy S21
Android 14	Qualcomm SM8350 Snapdragon	Yes	Samsung Galaxy S21
Linux 6.6	Xilinx Zynq Ultrascale+	No	SEL Switch
Linux 6.6	Altera SoC FPGA	No	SEL-2740
Linux 5.15	i.MX6UL	No	TBA
Debian 12.5	Intel® Xeon® E3-1275v6 @3.80GHz	No	TBA
OS: Ubuntu Version 22.04 Hypervisor: VMWare ESXi Version 7.0.3	Intel® Xeon® E5-2697 v3	No	TBA
Nucleus 3.0 version 2013.08.1	Freescale Vybrid VF500	No	XL200P Radio
Yocto 4.0-r7 (kirkstone)	STM32MP157	No	Claria Plus
Linux 6.6	Freescale i.MX7 Dual Arm Cortex A-7	No	TBA
Linux 6.6	Freescale i.MX7 Dual Arm Cortex A-7	Yes	TBA
HP Imaging & Printing Linux 4.9 Kernel	ARM Cortex-A72	No	HP PN 3PZ95-60002
HP Imaging & Printing Linux 4.9 Kernel	ARM Cortex-A72	Yes	HP PN 3PZ95-60002
HP Imaging & Printing Linux 4.9 Kernel	ARM Cortex-A53	No	HP PN 6QN27-60001A
HP Imaging & Printing Linux 4.9 Kernel	ARM Cortex-A53	Yes	HP PN 6QN27-60001A
Microsoft Windows CE 6.0	ARM Cortex-A8	No	HP Color LaserJet Enterprise M553
OS: RHEL 8.10 Hypervisor: qemu-kvm 6.2 on RHEL 8.10	Intel® Xeon® Gold 6526Y @2.80GHz	No	Dell R660
OS: RHEL 8.10 Hypervisor: qemu-kvm 6.2 on RHEL 8.10	Intel® Xeon® Gold 6526Y @2.80GHz	Yes	Dell R660
Windows 11 Pro	Intel® Core™ i7-1255U @ 1.70 Ghz	No	Dell Precision 3570
Windows 11 Pro	Intel® Core™ i7-1255U @ 1.70 Ghz	Yes	Dell Precision 3570
Android 13	Qualcomm Snapdragon 8 Gen 2 (SoC)	No	Samsung Galaxy S23
Android 13	Qualcomm Snapdragon 8 Gen 2 (SoC)	Yes	Samsung Galaxy S23
iOS 17.3	Apple A15 Bionic	No	iPhone 14
iOS 17.3	Apple A15 Bionic	Yes	iPhone 14
Linux 5.4	Dual ARM Cortex A7	No	Lenovo XClarity Controller
Linux 5.4	Dual ARM Cortex A7	Yes	Lenovo XClarity Controller
Linux 6.6	Dual ARM Cortex A7	No	Lenovo XClarity Controller
Linux 6.6	Dual ARM Cortex A7	Yes	Lenovo XClarity Controller
Android 11	MTK MT6762	No	TBA
Linux 4.14	MIPS 24Kc V7.4	No	TBA
Ubuntu 20.04.6	NXP i.MX8M	No	TBA
UEFI Specification Version 2.3.1 (32-bit)	Intel® Atom™ Processor Z3745D	No	Dell Venue 8 Pro
UEFI Specification Version 2.6.0 (64-bit)	Intel Core i5-7300U	No	Dell Latitude 7480
UEFI Specification Version 2.6.0 (64-bit)	Intel Core i5-7300U	Yes	Dell Latitude 7480
Linux 5.15 Yocto (Kirkstone)	NXP i.MX8M Mini Quad Cortex®-A53	No	TBA
QNX 6.6	NXP i.MX6	No	TBA
Windows Server 2022	Intel® Xeon® Gold 6414U CPU	No	PowerEdge R660 Rack Server
Cesium 2.93	STM32H753	No	TBA
HP Imaging & Printing Linux 5.10	ARM Cortex-A72 without PAA	No	HP Color LaserJet Enterprise 6700
HP Imaging & Printing Linux 5.10	ARM Cortex-A72 with PAA	Yes	HP Color LaserJet Enterprise 6700
HP Imaging & Printing Linux 5.10	ARM Cortex-A53 without PAA	No	HP Color LaserJet Enterprise 5700
HP Imaging & Printing Linux 5.10	ARM Cortex-A53 with PAA	Yes	HP Color LaserJet Enterprise 5700
Linux 6.6	NXP LS1012	No	TBA
Debian GNU/Linux 8 (jessie)	Broadcom BCM56771	No	TBA
Linux IPHO00559B23 3.4	Broadcom BCM6838	No	TBA
Linux IPHO00550F22 4.1	Broadcom BCM6858	No	TBA
Debian GNU/Linux 8 (jessie)	Broadcom BCM5634	No	TBA
Digi Embedded Yocto 5.0	NXP i.mx6UL	No	TBA

If you have questions about any of the above, please contact us at facts@wolfSSL.com or +1 425 245 8247.

Download wolfSSL Now

cURL is a popular open-source project that is used to transfer data between client and server with URLs through various protocols. It is widely utilized and often serves as the backbone for data transfer and communication between systems. curl (the command line tool) and libcurl (the library underneath) both provide support for secure communication by leveraging SSL/TLS libraries, the FIPS 140-3 certified wolfSSL library being one of them.

With the wolfCrypt FIPS 140-3 module, wolfSSL provides and makes use of an array of cryptographic algorithms that are rigorously tested and validated under NIST’s CMVP (Cryptographic Module Validation Program). When leveraged with cURL, the result is a FIPS 140-3 compliant build with the full feature set and utility that cURL users have come to expect, in addition to the cryptographic assurance that can help them meet security standards and requirements.

Additionally, there is also the tinycurl library, designed for smaller systems and more embedded use cases. tinycurl has the same capability to utilize FIPS wolfSSL.

Are you interested in curl with FIPS 140-3 wolfSSL? Contact us!

If you have questions about any of the above or need assistance, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247.

Download wolfSSL Now

Last week we put out a blog post sharing our integration of wolfCrypt into WireGuard. But did you know that we’ve already ported our FIPS 140-3 certified cryptographic engine into WireGuard GO, the official user space implementation of WireGuard in golang?

In cases where WireGuard’s functionality is desired, but a kernel isn’t available or installing a kernel-level VPN isn’t feasible, WireGuard GO offers a flexible solution.

And if you require FIPS compliance in your WireGuard GO deployments, our latest efforts make this possible. Using our golang wrapper go-wolfssl, we replaced WireGuard GO’s standard crypto (ChachaPoly, Curve25519, Blake2s) with our own FIPS certified algorithms (AES GCM, ECC P-256, SHA-256). One thing to note here is that FIPS-ified WireGuard GO end-points may only communicate with other FIPS-ified end-points. This is because the same set of algorithms would be required on both sides for interoperability.

Although the usual trade-off of WireGuard vs WireGuard GO is performance vs simplicity and flexibility, wolfCrypt’s ability to utilize hardware acceleration for AES and SHA can let you keep reaping WireGuard GO’s benefits without having to compromise on performance.

See the README here for instructions to get started using WireGuard GO with wolfCrypt.

Are you interested in WireGuard GO with wolfCrypt FIPS 140-3?

If you have questions about any of the above or need assistance, please contact us at facts@wolfSSL.com or +1 425 245 8247.

Download wolfSSL Now

As WireGuard continues to grow in popularity for its simplicity and efficiency in VPN deployments, security-conscious organizations are increasingly demanding solutions that adhere to stringent security standards, such as the Federal Information Processing Standard (FIPS 140-3). FIPS certification is a key requirement for governmental agencies and industries like healthcare and finance, where secure cryptographic implementations are mandatory. However, WireGuard’s default cryptographic implementations, while highly secure, are not FIPS-certified.

This is where wolfCrypt steps in. wolfCrypt is a lightweight, portable, and highly optimized cryptographic library that offers FIPS 140-3 certification, making it an ideal partner for users seeking FIPS compliance in their WireGuard deployments. With our planned integration, we’ll replace the standard crypto suite that WireGuard offers (ChachaPoly, Curve25519, Blake2s) with our own certified algorithms (AES GCM, ECC P-256, SHA-256). One thing to note here is that FIPS-ified WireGuard end-points may only communicate with other FIPS-ified end-points. But this of course is not a bug, but a feature. FIPS can only talk to FIPS.

So by leveraging our incoming integration, users can gain access to a VPN solution that is both secure and FIPS-compliant. This is especially important for industries with strict security requirements. The performance of WireGuard, combined with the certified cryptographic operations of wolfCrypt, ensures that you don’t sacrifice speed or security. In fact, with wolfCrypt’s ability to utilize hardware acceleration for AES and SHA, you might end up with a much faster WireGuard. Additionally, wolfCrypt’s small footprint makes it a practical choice for deployments in constrained environments, including IoT devices, embedded systems, and edge computing setups. You get a robust, certified security layer without bogging down performance.

Are you interested in WireGuard with wolfCrypt?

If you have questions about any of the above or need assistance, please contact us at facts@wolfSSL.com or call us at +1 425 245 8247.

Download wolfSSL Now

The wolfSSL team has noticed an uptick in questions about FedRAMP requirements. Today, we want to cover the differences between FIPS and FedRAMP.

FIPS:

The Federal Information Processing Standards (FIPS) stipulate security requirements for cryptographic modules, which wolfSSL Inc. meets with our wolfCrypt FIPS module. NIST and the CMVP then encourage all federal programs using cryptography to follow these standards. Federal Procurement Officers (at the urging of NIST and the CMVP) then require FIPS compliance for solutions that consume cryptography and are used within the scope of their federal program(s).

FEDRAMP:

The Federal Risk and Authorization Management Program (FedRAMP) focuses on the security assessment, authorization, and continuous monitoring of cloud products and services. A prerequisite for FedRAMP is the proper implementation of a FIPS-validated cryptographic module by the cloud service provider.

Both programs aim to enhance data security but differ in scope. While FIPS focuses on cryptographic module validation and cryptography, FedRAMP ensures the overall security of cloud services, one part of which is proper implementation of FIPS validated cryptography for all cryptography running in the cloud. Beyond checking for proper FIPS implementations, FedRAMP also ensures the cloud service provider is fully compliant with NIST SP 800-53 IE: Security Controls, a NIST Risk Management Framework (RMF), service is monitored continuously, data protection methods are robust, incidents can be detected, responded to and recovered from, and more. For a complete list please refer to SP 800-53 at this [LINK].

To support wolfSSL customers, wolfSSL Inc. offers a service to fully validate any Operational Environment (OE) (IoT, embedded, FPGA, Digital Signal Processor (DSP), laptop, desktop, server blade, or cloud system). wolfSSL Inc (the vendor) will fully test and validate the OE of choice using a third-party NVLAP accredited FIPS lab (or CSTL) and get the OE listed as a CMVP-validated OE on the wolfCrypt FIPS Certificate. This is a CMVP-backed OE addition which is guaranteed to be acceptable by any federal program with a FIPS requirement, as opposed to vendor affirmation or user affirmation which often fall short of the mark. Additionally, once the primary certificate is updated with the OE of choice, a rebranded cert with the customer’s logo and letterhead can be offered including that new OE.

wolfSSL’s wolfCrypt FIPS module supports the latest FIPS 140-3 standards and holds the world’s first SP800-140Br1 FIPS 140-3 validated certificate (#4718). Our expert support team is available to assist with the proper implementation of the module on your target OE, a critical step for achieving a successful FedRAMP effort.

Beyond getting proper OE’s for FEDRAMP initiatives, wolfSSL can support customers that are either:

1. Using an alternative OS within AWS, Azure, or Oracle cloud, or,
2. If you are standing up your own cloud, support you with meeting the FedRAMP FIPS requirements for the operating system of your choice.

For more information on how wolfSSL can help with your FIPS or FedRAMP compliance needs, shoot us an email at fips@wolfSSL.com today!

If you have questions about any of the above, please contact us at facts@wolfSSL.com or +1 425 245 8247.

Download wolfSSL Now

Do you need a FIPS 140-3 validated cryptography library for your ARM-based platform? wolfCrypt has been FIPS 140-3 validated (certificate #4718). While full FIPS 140-3 support on ARM isn’t available just yet, it’s on our radar. We’re making strides to bring this capability to you soon.

FIPS validating a crypto library on a resource-constrained device can be more involved than doing a validation on a standard desktop-like platform. Variances in OS, Flash/RAM, filesystem (or lack of), entropy, communication, and more can make things interesting. Going through our past ARM-based validations, we have figured out how to make this process easier with wolfCrypt!

If you are interested in exploring FIPS 140-3 cryptography validations on ARM platforms, reach out to us at either facts@wolfSSL.com or +1 425 245 8247!

To learn more about our FIPS 140-3 certification, check out wolfCrypt FIPS Q&A.

Download wolfSSL Now

wolfSSL fans! Do you like FIPS? Do you like virtual machines? Guess what – wolfSSL’s crypto library, wolfCrypt, has been validated as the world’s first SP800-140Br1 FIPS 140-3 certificate! However, with the recent changes to the FIPS submission process, OE additions are slightly delayed via a manual process until such time as the CMVP can update the automated WebCryptik tool to support OEUP scenarios. wolfSSL Inc. is moving forward with our CSTL hoping to achieve our first OEUP manual submission in the very near future! As the landscape continues to evolve, wolfSSL remains committed to keeping wolfCrypt compliant with the latest FIPS standards. Stay tuned for more updates!

If you’re interested in getting a FIPS 140-3 approved crypto library running in your virtual or any operating environment, or if you have any questions about the process, please don’t hesitate to contact us at fips@wolfSSL.com or facts@wolfSSL.com, or call us at +1 425 245 8247. We look forward to hearing from you.

Download wolfSSL Now