CryptoComply
CryptoComply, from SafeLogic, Inc., holds FIPS 140-2 certificate #3309 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 operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy.
Certificate
| Certificate number | 3309 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | SafeLogic, Inc. · website |
| Software versions | 3.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
SafeLogic's CryptoComply is designed to provide FIPS 140-2 validated cryptographic functionality and is available for licensing.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (9)
Allowed algorithms
NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)
Tested configurations
- Ubuntu Linux 14.04 LTS running on Intel Xeon E5 without PAA (clang Compiler Version 4.0.0)
- Ubuntu Linux 15.04 running on POWER8 without PAA (clang Compiler Version 4.0.0)
- Ubuntu Linux 16.04 running on Intel Xeon E5 with PAA (clang Compiler Version 4.0.0)
- Ubuntu Linux 17.04 running on POWER8 with PAA (clang Compiler Version 4.0.0)
- Ubuntu Linux 17.04 running on POWER9 with PAA (clang Compiler Version 4.0.0) (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2018-10-19 | Initial | Acumen 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: 2018-10-19