808bits

CryptoComply for NSS

FIPS 140-2 certificate #2997 · SafeLogic Inc. · data as of 2026-10-21

CryptoComply for NSS, from SafeLogic Inc., holds FIPS 140-2 certificate #2997 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. This validation entry is a non-security relevant modification to Cert. #2711

Certificate

Certificate number2997
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSafeLogic Inc. · website
Software versions4.0

Module description

Quoted from the NIST CMVP entry for this certificate.

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

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Physical Security: N/A
  • Design Assurance: Level 2

Approved algorithms (9)

AlgorithmCAVP certificates
AES3605, 3606, 3607, 3609
CVL626, 627
DRBG936, 937
DSA1002, 1003
ECDSA739, 740
HMAC2300, 2301
RSA1854, 1855, 2034, 2035
SHS2966, 2967
Triple-DES2007, 2008

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength)

Tested configurations

  • Red Hat Enterprise Linux 7.1 running on HP ProLiant DL380p Gen8 with PAA Red Hat Enterprise Linux 7.1 running on HP ProLiant DL380p Gen8 without PAA (single-user mode)

Validation history

DateTypeLab
2017-08-18InitialAcumen Security
2018-02-07UpdateAcumen Security
2018-03-29UpdateAcumen 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
  • Validation dates on record: 2017-08-18, 2018-02-07, 2018-03-29

Source documents