808bits

SafeLogic Inc.

22 FIPS 140 certificates · 8 active · data as of 2026-09-08

SafeLogic Inc. holds 22 FIPS 140 certificates in NIST's Cryptographic Module Validation Program, covering CryptoComply. 8 are still active, 14 have moved to the historical list.

4 certificates on the 140-2 sunset list. Every FIPS 140-2 validation still active moves to the historical list on 2026-09-21. What that means and the full list.
CertModuleStandardStatusLevelValidated
5349CryptoComply Native Go ModuleFIPS 140-3active · sunsets 2031-04-2612026-06-23
5264CryptoComply BoringCrypto ModuleFIPS 140-3active · sunsets 2029-07-2212026-05-13
5040CryptoComply 140-3 FIPS ProviderFIPS 140-3active · sunsets 2029-08-2612025-07-17
4912CryptoComply for Java 140-3FIPS 140-3active · sunsets 2029-07-2812024-12-05
4678CryptoComply for .NETFIPS 140-2active · sunsets 2026-09-2112024-02-26
3273CryptoComply for ServerFIPS 140-2active · sunsets 2026-09-2112018-08-29
2038CryptoComply for ServerFIPS 140-2active · sunsets 2026-09-2112013-11-15
1938CryptoComply for MobileFIPS 140-2active · sunsets 2026-09-2112013-04-30
4781CryptoComply 140-3 FIPS ProviderFIPS 140-3historical12024-08-27
4660CryptoComply for JavaFIPS 140-2historical12023-11-28
4240CryptoComply for JavaFIPS 140-2historical12022-06-01
4163CryptoComply for HSMFIPS 140-2historical32022-02-22
4136CryptoComply for LibgcryptFIPS 140-2historical12022-01-18
4135CryptoComply for NSSFIPS 140-2historical12022-01-13
3876CryptoComply for HSMFIPS 140-2historical32021-03-30
3829CryptoComply for HSMFIPS 140-2historical32021-02-26
3309CryptoComplyFIPS 140-2historical12018-10-19
3080CryptoComply for JavaFIPS 140-2historical12017-12-13
3007CryptoComply for LibgcryptFIPS 140-2historical12017-08-28
2997CryptoComply for NSSFIPS 140-2historical12017-08-18
2804CryptoComply for JavaFIPS 140-2historical12016-12-08
2483CryptoComply for JavaFIPS 140-2historical12015-12-11

NIST records the vendor as free text, so one company can appear under several spellings. Those are grouped here. Corporate families are not: a product line can change owner, and the certificates stay with the registration that earned them. The nShield modules run from nCipher Corporation through Thales to Entrust, and this tracker keeps those as three vendors because that is how NIST holds them.