Module Name
RSA BSAFE(R) Crypto-J JSAFE and JCE Software Module
Historical Reason
Moved to historical list due to sunsetting
Caveat
When operated in FIPS Mode. No assurance of the minimum strength of generated keys
Security Level Exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Design Assurance: Level 3
Embodiment
Multi-Chip Stand Alone
Description
RSA BSAFE Crypto-J security software is designed to help protect sensitive data as it is stored using strong encryption techniques to provide a persistent level of protection. It supports a wide range of industry standard encryption algorithms offering Java developers the flexibility to choose the option most appropriate to meet their requirements.
Tested Configuration(s)
- Google Dalvik(tm) JRE 6.0 on Google(tm) Android(tm) 4.1.2 ARMv7 (32-bit) running on Google Nexus 7(tm) (Wi-Fi, 2012)
- OpenJDK 8.0 on CentOS 6.7 (64-bit) running on a Dell(TM) PowerEdge(TM) (single-user mode)
- Oracle(R) JRE 8.0 on Microsoft(R) Windows 8.1 (64-bit) running on an HP ENVY 15
Approved Algorithms
| AES | Cert. #3263 |
| CVL | Certs. #471 and #1024 |
| DRBG | Cert. #722 |
| DSA | Cert. #932 |
| ECDSA | Cert. #619 |
| HMAC | Cert. #2062 |
| KTS | AES Cert. #3263 |
| PBKDF | vendor affirmed |
| RSA | Cert. #1663 |
| SHS | Cert. #2701 |
| Triple-DES | Cert. #1852 |
Other Algorithms
AES (non-compliant); DES; DESX; Diffie-Hellman (CVL Cert. #1024, key agreement); EC Diffie-Hellman (CVL Cert. #1024, key agreement); ECIES; RNG (non-compliant); HMAC-MD5; MD2; MD5; PKCS#5; PKCS#12; RC2; RC4; RC5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength); RSA (non-compliant); RIPEMD160; scrypt; Shamir Secret Sharing; Triple-DES (non-compliant)
Software Versions
6.2 and 6.2.1.1
