CryptoComply for Java
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 | 2483 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | SafeLogic Inc. · website |
| Software versions | 2.2-fips |
Module description
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
- Mitigation of Other Attacks: N/A
Approved algorithms
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 219 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); MD5
Tested configurations
- Windows Server 2012 with Java Runtime Environment (JRE) v1.7.0_17 running on OEM PowerEdge R420 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2015-12-11 | Initial | Acumen Security |
| 2016-01-25 | Update | |
| 2018-03-29 | Update | 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: 2015-12-11, 2016-01-25, 2018-03-29