Module Name
CryptoComply for Java
Historical Reason
Moved to historical list due to sunsetting
Transitional Note
Pending SP 800-56Arev3 transition revalidation
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
Security Level Exceptions
Embodiment
Multi-Chip Stand Alone
Description
SafeLogic's CryptoComply for Java is designed to provide FIPS 140-2 validated cryptographic functionality and is available for licensing.
Tested Configuration(s)
- CentOS 6 and OpenJDK 1.7 running on HP ProLiant DL360 G7 Server using an Intel Xeon X5670 (single-user mode)
Approved Algorithms
| AES |
Cert. #4702 |
| CKG |
vendor affirmed |
| CVL |
Certs. #1342, #1343, #1344 and #1345 |
| DRBG |
Cert. #1600 |
| DSA |
Cert. #1244 |
| ECDSA |
Cert. #1160 |
| HMAC |
Cert. #3114 |
| KAS |
Cert. #130 |
| KAS |
SP 800-56Arev2, vendor affirmed |
| KBKDF |
Cert. #145 |
| KTS |
AES Cert. #4702; key establishment methodology provides between 128 and 256 bits of encryption strength |
| KTS |
SP800-56B, vendor affirmed |
| KTS |
Triple-DES Cert. #2494; key establishment methodology provides 112 bits of encryption strength |
| PBKDF |
vendor affirmed |
| RSA |
Cert. #2562 |
| SHA-3 |
Cert. #24 |
| SHS |
Cert. #3849 |
| Triple-DES |
Cert. #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)
