808bits

CryptoComply for .NET

FIPS 140-2 certificate #4678 · SafeLogic Inc. · data as of 2026-10-09

CryptoComply for .NET, from SafeLogic Inc., holds FIPS 140-2 certificate #4678 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys.

Certificate

Certificate number4678
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSafeLogic Inc. · website
Software versions1.0.2

Module description

Quoted from the NIST CMVP entry for this certificate.

SafeLogic's CryptoComply for .NET is designed to provide FIPS 140 validated cryptographic functionality and is available for licensing.

Security level exceptions

  • Physical Security: N/A

Approved algorithms (17)

AlgorithmCAVP certificates
AESA1905
CKGvendor affirmed
CVLA1905
DRBGA1905
DSAA1905
ECDSAA1905
HMACA1905
KASA1905
KAS-SSCA1905
KDAA1905
KTS
KTS-RSA
PBKDFA1905
RSAA1905
SHA-3A1905
SHSA1905
Triple- DES

Allowed algorithms

RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Microsoft Windows 10 Professional (64-bit) on .NET 4.5.2 framework running on Dell XPS 15 7590 with Intel Core i7-9750H (single-user mode)

Validation history

DateTypeLab
2024-02-26InitialAcumen Security

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2024-02-26

Source documents