CryptoComply for Libgcrypt
CryptoComply for Libgcrypt, from SafeLogic Inc., holds FIPS 140-2 certificate #4136 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.
Caveat: When installed and configured per Security Policy section 3 and 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. #3604
Certificate
| Certificate number | 4136 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | SafeLogic Inc. · website |
| Software versions | 5.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
SafeLogic's CryptoComply for Libgcrypt is designed to provide FIPS 140 validated cryptographic functionality and is available for licensing.
Security level exceptions
- Physical Security: N/A
- Design Assurance: Level 3
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| AES | C709 |
| CKG | vendor affirmed |
| DRBG | C709 |
| DSA | C709 |
| HMAC | C709 |
| RSA | C709 |
| SHS | C709 |
| Triple-DES | C709 |
Allowed algorithms
NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)
Tested configurations
- Oracle Linux 7.6 64 bit running on an Oracle Server X7-2 with an Intel(R) Xeon(R) Silver 4114
- Oracle Linux 7.6 64 bit running on an Oracle X7-2 Server with an AMD(R) EPYC(R) 7551 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-01-18 | Initial | Leidos Accredited Testing & Evaluation (AT&E) Lab |
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: 2022-01-18