CryptoComply for Java
CryptoComply for Java, from SafeLogic Inc., holds FIPS 140-2 certificate #3080 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. No assurance of the minimum strength of generated keys
Certificate
| Certificate number | 3080 |
|---|---|
| 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.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
SafeLogic's CryptoComply for Java is designed to provide FIPS 140-2 validated cryptographic functionality and is available for licensing.
Security level exceptions
- Physical Security: N/A
Approved algorithms (15)
| Algorithm | CAVP certificates |
|---|---|
| AES | 4702 |
| CKG | vendor affirmed |
| CVL | 1342, 1343, 1344, 1345 |
| DRBG | 1600 |
| DSA | 1244 |
| ECDSA | 1160 |
| HMAC | 3114 |
| KAS | vendor affirmed |
| KBKDF | 145 |
| KTS | vendor affirmed |
| PBKDF | vendor affirmed |
| RSA | 2562 |
| SHA-3 | 24 |
| SHS | 3849 |
| Triple-DES | 2494 |
Allowed algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
Tested configurations
- CentOS 6 and OpenJDK 1.7 running on HP ProLiant DL360 G7 Server using an Intel Xeon X5670 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2017-12-13 | Initial | UL Verification Services, Inc. |
| 2018-03-29 | Update | Acumen Security |
| 2018-05-23 | Update | UL Verification Services, Inc. |
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-12-13, 2018-03-29, 2018-05-23